endpoint
Click on the red underlined text to get to the source
... connection is established, the proxy tells the outside endpoint that
it will be tunneling. If the outside machine agrees, the proxy ...
... machine does no further interpretation of the data. In particular,
it does not look for any BEEP framing. The two endpoint machines may
therefore negotiate TLS between them, passing certificates ...
... TLS between them, passing certificates
appropriate to the endpoints rather than the proxy, with the
assurance that even the proxy ...
... Endpoint Example ...
... proxy2. Proxy2 has been locally configured to use "final" as
"operator console". This example is almost identical to the previous
example, except that "endpoint" is intended to route to a particular
server, while "profile ...
... [3] Proxy2 receives the TUNNEL element with simply the endpoint
specified. Local provisioning maps this to
<tunnel ...
... profile" attribute is a URI [5]. The format of the "endpoint"
attribute is any string that may appear as an attribute value.
...
...
Similarly, if the outermost element has an "endpoint" attribute, then
it must have no nested elements. The proxy ...
... is responsible for determining the appropriate routing to reach a
peer indicated by the value of the "endpoint" attribute. Rather than
source routing, this provides a hop-by-hop ...
... elements, but it does
have attributes other than "profile" or "endpoint", then this peer is
the final BEEP hop. (This corresponds to "proxy2" in the "Non-BEEP ...
... proxy, with an innermost "profile" or
"endpoint" attribute which the firewall proxy understands. Local
...
... proxy to translate a particular "profile"
or "endpoint" element into a new source route to reach the desired
...
... to be prevented, the proxy must allow only "profile" or "endpoint"
connections, always refusing to even attempt source-routed
...