Jingle (XEP-0166)
The approach taken in this specification is to use the existing IBB mechanisms described in XEP-0047 for transporting the data, and to define Jingle-specific methods only to start and end the in-band bytestream.
The basic flow is as follows.
|
| ack |
|<---------------------------|
| session-accept |
|<---------------------------|
| ack |
|--------------------------->|
| IBB "SESSION" |
|<==========================>|
| session-terminate |
|<---------------------------|
| ack |
|--------------------------->|
| |
]]>
This flow is illustrated in the following examples (to prevent confusion these use a "stub" transport instead of a real application type).
First the initiator sends a Jingle session-initiate request.
Note: The Jingle IBB Transport Method defines one attribute in addition to those defined in XEP-0047: the 'stanza' attribute. This attribute specifies whether the initiator intends to send IBB data using <message/> or <iq/> stanzas, but is purely advisory. The default value is "iq", and it is RECOMMENDED to send IBB data using IQ stanzas instead of message stanzas because IQ stanzas provide feedback to the sender regarding delivery to the recipient (e.g., if the recipient is on a small pipe and cannot handle a large volume of IBB packets in quick succession).
The responder immediately acknowledges receipt (but does not yet accept the session).
If the offer is acceptable, the responder returns a Jingle session-accept and the initiator acknowledges the session-accept.
The initiator then immediately begins sending IBB packets using an IQ-set for each chunk as described in XEP-0047, and the responder acknowledges each IQ-set.
Once the parties have finished using the bytestream (e.g., because a complete file has been sent), either party can send a Jingle session-terminate action.
The other party then acknowledges the session-terminate and the Jingle session is finished.
The same processing rules and usage guidelines defined in XEP-0047 apply to the Jingle IBB Transport Method.
The same security considerations defined in XEP-0047 apply to the Jingle IBB Transport Method.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA)
This specification defines the following XML namespace:
Upon advancement of this specification from a status of Experimental to a status of Draft, the XMPP Registrar
If the protocol defined in this specification undergoes a revision that is not fully backwards-compatible with an older version, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of XEP-0053.
The XMPP Registrar shall add to its registry of Jingle transport methods a definition for the "jingle-ibb" transport method. The registry submission is as follows:
ibb
A method for exchanging data over In-Band Bytestreams.
streaming
XEP-xxxx
]]>
]]>