service
Click on the red underlined text to get to the source
... then instruct the proxy to tunnel to an information service
restricted to managers. Since each proxy knows the identity ...
... intermediate proxies are "proxy1" or "proxy2", and the machine with
the service that "initial" wishes to access is called "final". The
examples also assume that the BEEP framework ...
... proxy connecting to another, and finally that second proxy finding a
service outside.
initial proxy1 proxy2 final
...
... initiator connecting through two proxys,
the second proxy attempting to connect to the specified service and
finding the destination is not a BEEP ...
... BEEP server. (Of course, specifying
the telnet service can be expected to lead to this error.) The same
would result if the destination did not support the TUNNEL profile ...
... initiator connecting through two proxys, the
second proxy attempting to connect to the specified service and
accepting that the destination is not a BEEP ...
... locally configured to know that all SEP2 servers are beyond proxy2.
Proxy2 has been locally configured to chose "final" as the server of
choice for SEP2 services. Note that "final" does not necessarily
need to offer the requested profile in its initial greeting.
...
... server, while "profile" is intended to route to a particular service.
Otherwise, these two attributes are very similar.
...
... has no attributes, then this peer is hosting the BEEP service that
the initiator wishes to use. In this case, the listener ...
... code meaning
==== =======
421 Service not available
(E.g., the proxy does not have sufficient resources.)
...
... BEEP peers can
offer a range of services with appropriate greetings, the TUNNEL
profile should be configured with care. It is reasonable to strictly
limit the hosts ...
... TUNNEL
profile should be configured with care. It is reasonable to strictly
limit the hosts and services that a proxy is allowed to contact. It
is also reasonable to limit the use of the TUNNEL profile ...
... element into a new source route to reach the desired
service. This can prevents two attacks:
...
... Gulbrandsen, A., Vixie, P. and L. Esibov, "A DNS RR for specifying the location of services (DNS SRV)", RFC 2782prop, February 2000. ...