diff --git a/xep-0261.xml b/xep-0261.xml index 4274a07e..ef0459d3 100644 --- a/xep-0261.xml +++ b/xep-0261.xml @@ -4,13 +4,6 @@ %ents; ]> - - -
Jingle In-Band Bytestreams Transport Method @@ -29,6 +22,12 @@ jingle-ibb jingle &stpeter; + + 0.7 + 2011-05-16 + psa +

Further clarified order of layers, in particular the reuse of IBB <open/> and <close/> elements.

 + 0.6 2011-03-07 @@ -106,18 +105,22 @@ Initiator Responder |<---------------------------| | IBB "SESSION" | |<==========================>| + | IBB | + |--------------------------->| + | ack | + |<---------------------------| | session-terminate | |<---------------------------| | ack | |--------------------------->| | | ]]> -

This flow is illustrated in the following sections (to prevent confusion these use a "stub" description instead of a real application type).

+

This flow is illustrated in the following sections (to prevent confusion these use an "example" description instead of a real application type).

First the initiator sends a Jingle session-initiate request.

- - - + + @@ -154,8 +157,8 @@ Initiator Responder initiator='romeo@montague.lit/orchard' responder='juliet@capulet.lit/balcony' sid='a73sjjvkla37jfea'> - - + + @@ -227,7 +230,7 @@ Initiator Responder action='transport-info' initiator='romeo@montague.lit/orchard' sid='a73sjjvkla37jfea'> - + @@ -236,13 +239,27 @@ Initiator Responder ]]>

Here the Jingle Session ID is the same ("a73sjjvkla37jfea") but the new IBB Session ID ("bt8a71h6") is different from the old IBB Session ID that is already in use ("ch3d9s71").

+

The initiator opens the second session by sending an IBB <open/> element, which the responder acknowledges (not shown).

+ + + + ]]> +

The parties can then exchange data over the second session (see XEP-0047).

If a party wishes to close one session within a bytestream, it sends an IBB <close/> element as defined in XEP-0047 specifying the appropriate IBB SessionID.

- - + ]]>

The receiving party then acknowledges that the IBB session has been closed by returning an IQ-result.

@@ -255,7 +272,8 @@ Initiator Responder -

If a party wishes to close the bytestream itself (e.g., because the parties have finished using all sessions associated with the bytestream), it sends a Jingle session-terminate action as defined in XEP-0166.

+

Whenever a party is finished with a particular session within the bytestream, it SHOULD send an IBB <close/> as shown above. This applies to all sessions, including the last one.

+

To close the bytestream itself (e.g., because the parties have finished using all sessions associated with the bytestream), a party sends a Jingle session-terminate action as defined in XEP-0166.

A Jingle implementation SHOULD support security preconditions that are enforced before application media is allowed to flow over the bytestream, such as those described in &xtls;.

 -

See XEP-0047 for security considerations related to the user of Base64.

+

See XEP-0047 for security considerations related to the use of Base64.

 @@ -336,7 +354,9 @@ Initiator Responder ibb - A method for data exchange over In-Band Bytestreams. + + A method for data exchange over In-Band Bytestreams. + streaming XEP-0261 @@ -358,9 +378,15 @@ Initiator Responder - - - + + +