element
Click on the red underlined text to get to the source
... tunnel. The peers exchange "tunnel"
elements that specify a source route, with the outermost element
...
... elements that specify a source route, with the outermost element
being stripped off and used to decide the next hop. The innermost,
...
... next hop. The innermost,
empty "tunnel" element tells the final destination that it is,
indeed, the final destination ...
... tunnel/>
[3] At this point, immediately after sending the <ok/> element,
proxy1 starts passing octets transparently. It continues to do
...
... [3] This close is optional. "Initial" may also send another <tunnel>
element, attempting to contact a different server, for example.
...
... at the protocol level is two-fold: The "initial" machine does not
include the innermost "tunnel" element, and the final proxy
("proxy2") therefore does not expect a BEEP ...
... profiles/SEP2"/>
Note the lack of an innermost no-attribute <tunnel> element.
[2] Proxy1 maps this to
...
... tunnel>
based on local configuration, then processes the new
element, stripping off the outer element and routing
...
... based on local configuration, then processes the new
element, stripping off the outer element and routing
<tunnel profile ...
...
[3] Proxy2 receives the TUNNEL element with simply the SEP2
URI specified. Local provisioning maps this to
...
... tunnel>
Note the presence of an innermost no-attribute <tunnel> element.
Proxy2 then strips the outermost element, looking up the
...
... tunnel> element.
Proxy2 then strips the outermost element, looking up the
appropriate address and port, and forwards the <tunnel ...
... address and port, and forwards the <tunnel/>
element to the final machine.
[4] Proxy2 starts ...
... tunnel>
Note the lack of an innermost no-attribute <tunnel> element.
[2] Proxy1 maps this to
...
... tunnel>
based on local configuration, then processes the new
element, stripping off the outer element and routing
...
... based on local configuration, then processes the new
element, stripping off the outer element and routing
<tunnel endpoint ...
...
[3] Proxy2 receives the TUNNEL element with simply the endpoint
specified. Local provisioning maps this to
...
... tunnel>
Note the presence of an innermost no-attribute <tunnel> element.
Proxy2 then strips the outermost element, looking up the
...
... tunnel> element.
Proxy2 then strips the outermost element, looking up the
appropriate address and port, and forwards the <tunnel ...
... address and port, and forwards the <tunnel/>
element to the final machine.
[4] Proxy2 starts ...
... element defined in this profile is the "tunnel" element. It
is described in the following DTD, with additional limitations as
...
...
o endpoint, but only on the innermost element; or,
o no attributes, but only on the innermost element ...
... element from the initiator, either in the "start" element on channel
zero or on the new channel ...
...
In either case, the outermost "tunnel" element is examined. If it
has no attributes, then this peer is hosting the BEEP ...
... plaintext greeting is sent.
If the outermost element has a "port" attribute and an "fqdn"
attribute but no "srv" attribute, then "fqdn" is looked up as an A
record ...
... IPv6
address. In each of these cases, a transport connection is
established to the so-identified server. If the outermost element
has a "srv" attribute, the concatenation of the "srv" attribute and
...
... is attempted as if the "srv" attribute were not specified.
Alternately, if the outermost element has a "profile" attribute, then
it must have no nested elements ...
... element has a "profile" attribute, then
it must have no nested elements. The proxy processing this element
...
... it must have no nested elements. The proxy processing this element
is responsible for determining the appropriate routing to reach a
...
... service.
Similarly, if the outermost element has an "endpoint" attribute, then
it must have no nested elements ...
... element has an "endpoint" attribute, then
it must have no nested elements. The proxy processing this element
...
... it must have no nested elements. The proxy processing this element
is responsible for determining the appropriate routing to reach a
...
... identified.
Then, if the outermost element has no nested elements, but it does
have attributes other than "profile ...
...
Then, if the outermost element has no nested elements, but it does
have attributes other than "profile" or "endpoint ...
... example above.) In this case, as soon as the final underlying
transport connection is established, an "ok" element is returned over
the listening session, and the tunneling ...
... frame with the completion flag set (more=".") of the RPY carrying the
"ok" element, the proxy begins copying octets directly and without
any interpretation between the two underlying transport connections ...
... transport connections.
If the identified server cannot be contacted, an "error" element is
returned over the listening channel and any connection ...
... an initiator is closed. If there is a nested "tunnel" element, and
the server that has been contacted does not offer a BEEP greeting, or
...
...
If there is a nested "tunnel" element, and the identified server is
contacted and offers a BEEP greeting including the TUNNEL profile ...
... BEEP greeting including the TUNNEL profile,
then the outermost element from the "tunnel" element received is
...
... then the outermost element from the "tunnel" element received is
stripped off, a new TUNNEL channel ...
... channel is started on the initiating
session, and the stripped (inner) element is sent to start the next
hop. In this case, the peer is considered a "proxy ...
... TUNNEL channel,
it awaits an "error" or an "ok" element in response. If it receives
an "error" element, it closes the initiated session ...
... it awaits an "error" or an "ok" element in response. If it receives
an "error" element, it closes the initiated session and its
underlying transport connection ...
... session and its
underlying transport connection. It then passes the "error" element
unchanged back on the listening session. If, on the other hand, it
...
... unchanged back on the listening session. If, on the other hand, it
receives an "ok" element, it passes the "ok" element back on the
listening session ...
... session. If, on the other hand, it
receives an "ok" element, it passes the "ok" element back on the
listening session. Starting ...
... trailer of the frame with the completion flag set (more=".") of the
RPY carrying the "ok" element, the proxy begins copying octets
directly and without any interpretation between the two underlying
...
... BEEP. The attributes on the
"tunnel" element may need to be extended to handle other transport
layers.
...
... In a mapping where multiple underlying transport connections are
used, once the "ok" element is passed, all channels are closed,
including channel ...
... that the beginning of any reply from the destination machine be
included as part of the CDATA text of the error element, for
debugging purposes.
...