RFC 3620:The TUNNEL Profile
RFC-Ref

session


Click on the red underlined text to get to the source

... unlike the way starting a TLS negotiation discards cached session state and starts ...


... channel zero, are implicitly closed. o Any previously cached information about the BEEP session is discarded. ...
... transport connection is established, an "ok" element is returned over the listening session, and the tunneling of data starts. No BEEP ...
... TUNNEL channel is started on the initiating session, and the stripped (inner) element is sent to start the next hop ...
... element in response. If it receives an "error" element, it closes the initiated session and its underlying transport connection. It then passes the "error" element ...
... transport connection. It then passes the "error" element unchanged back on the listening session. If, on the other hand, it receives an "ok" element, it passes the "ok" element ...
... element, it passes the "ok" element back on the listening session. Starting with the octet following the END(CR)(LF ...


... transport connection initially established remains, and all other underlying transport connections for the session should be closed as well. If a transport security ...
... layer (such as TLS) has been negotiated over the session, the semantics for the TUNNEL profile are ill-defined. ...



Google
Web
RFC-Ref