destination
Click on the red underlined text to get to the source
... empty "tunnel" element tells the final destination that it is,
indeed, the final destination. The term "proxy ...
... element tells the final destination that it is,
indeed, the final destination. The term "proxy" is used to refer any
of the BEEP ...
... of the BEEP peers other than the initiator and the final destination.
In one use of this profile ...
... proxy attempting to connect to the specified service and
finding the destination is not a BEEP server. (Of course, specifying
the telnet ...
... telnet service can be expected to lead to this error.) The same
would result if the destination did not support the TUNNEL profile.
...
... proxy attempting to connect to the specified service and
accepting that the destination is not a BEEP server. The difference
at the protocol level is two-fold: The "initial" machine does not
...
...
Note that the 450 error code is appropriate when the destination
machine could not be contacted, while the 550 error code is
...
... machine could not be contacted, while the 550 error code is
appropriate when the destination machine could be contacted but the
next phase of the protocol could not be negotiated. It is suggested
that the beginning of any reply from the destination ...
... destination machine could be contacted but the
next phase of the protocol could not be negotiated. It is suggested
that the beginning of any reply from the destination machine be
included as part of the CDATA text of the error element, for
...