diff --git a/xep-0176.xml b/xep-0176.xml index 4ec715f6..0ea56cd6 100644 --- a/xep-0176.xml +++ b/xep-0176.xml @@ -2,7 +2,8 @@ %ents; -ICE-14"> +ICE-CORE"> +ICE-TCP"> ]> @@ -27,6 +28,12 @@ &scottlu; &hildjj; &seanegan; + + 0.8 + 2007-04-17 + psa +

Separately defined ice-tcp and ice-udp transport methods to enable clearer definition of transport methods and reuse by application types; specified Jingle conformance, including definition of ice-udp as lossy and ice-tcp as reliable.

 + 0.7 2007-03-23 @@ -71,29 +78,39 @@ -

&xep0166; defines a framework for negotiating and managing out-of-band data sessions over XMPP. In order to provide a flexible framework, the base Jingle specification defines neither data transport methods nor content formats, leaving that up to separate specifications. The current document defines a transport method for establishing and managing data connections between XMPP entities, using the ICE methodology currently being developed within the IETF.

+

&xep0166; defines a framework for negotiating and managing out-of-band data sessions over XMPP. In order to provide a flexible framework, the base Jingle specification defines neither data transport methods nor content formats, leaving that up to separate specifications. The current document defines two transport methods (ice-udp and ice-tcp) for establishing and managing data connections between XMPP entities, using the ICE methodology currently being developed within the IETF. The ice-udp method results in a lossy transport suitable for use in media applications where some packet loss is tolerable (e.g., audio and video), whereas the ice-tcp method results in a reliable transport suitable for use in applications where packet loss is not tolerable (e.g., file transfer).

The process for ICE negotiation is largely the same in Jingle as it is in &icecurr;. There are several differences:

-

Note: This document depends on the IETF's &ice; specification, which is a work in progress. Every effort has been made to keep this document synchronized with draft-ietf-mmusic-ice, for which the latest published version is 14 (hereafter referred to as "&icecurr;"). The interested reader is referred to &icecurr; for a detailed description of the ICE methodology, which for the most part this document merely maps to XMPP syntax.

+

Note: This document depends on the IETF's &ice; specification, which is a work in progress. Every effort has been made to keep this document synchronized with draft-ietf-mmusic-ice, for which the latest published version is 15 (hereafter referred to as "&icecurr;"). The interested reader is referred to &icecurr; for a detailed description of the ICE methodology, which for the most part this document merely maps to XMPP syntax.

+ + +

The reader is referred to &icecurr; and &icetcp; for a description of various terms used in the context of ICE. Those terms are not reproduced here.

 -

The Jingle transport method defined herein is designed to meet the following requirements:

+

The Jingle transport methods defined herein is designed to meet the following requirements:

  1. Make it possible to establish and manage out-of-band connections between two XMPP entities, even if they are behind Network Address Translators (NATs) or firewalls.
    2. +
  2. Enable use of either UDP (see &icecurr;) or TCP (see &ice-tcp;) as the transport protocol itself.
  3. Make it relatively easy to implement support in standard Jabber/XMPP clients.
  4. Where communication with non-XMPP entities is needed, push as much complexity as possible onto server-side gateways between the XMPP network and the non-XMPP network.
 - -

The reader is referred to &icecurr; for a description of various terms used in the context of ICE. Those terms are not reproduced here.

+ +

In accordance with Section 8 of XEP-0166, this document specifies the following information related to the Jingle ice-udp and ice-tcp transport types:

+
    +

  1. The transport negotiation process is defined in the Protocol Description section of this document.

    2. +

  2. The semantics of the &DESCRIPTION; element are defined in the Transport Initiation section of this document.

    3. +

  3. Successful negotiation of the ice-udp method results in use of a lossy transport that is suitable for applications where some packet loss is tolerable, such as audio and video; successful negotiation of the ice-tcp method results in use of a reliable transport that is suitable for applications where packet loss is not tolerable, such as file transfer.

    4. +

  4. If multiple components are to be communicated over the transport in the context of the Real-time Transport Protocol (RTP; see &rfc3550;), the component numbered "1" shall be associated with RTP and the component numbered "2" shall be associated with the Real Time Control Protocol (RTCP).

    5. +
-

In order for the initiator in a Jingle exchange to start the negotiation, it MUST send a Jingle "session-initiate" stanza as described in XEP-0166. This stanza MUST include at least one transport method. If the initiator wishes to negotiate the ICE transport, it MUST include an empty &TRANSPORT; child element qualified by the 'http://www.xmpp.org/extensions/xep-0176.html#ns' namespace &NSNOTE;.

+

In order for the initiator in a Jingle exchange to start the negotiation, it MUST send a Jingle "session-initiate" stanza as described in XEP-0166. This stanza MUST include at least one transport method. If the initiator wishes to negotiate the ice-udp or ice-tcp transport, it MUST include an empty &TRANSPORT; child element qualified by the 'http://www.xmpp.org/extensions/xep-0176.html#ns-udp' or 'http://www.xmpp.org/extensions/xep-0176.html#ns-tcp' namespace &NSNOTE;.

... - + @@ -118,7 +135,7 @@

If the responder provisionally accepts the session initiation request as shown above, both initiator and responder MUST immediately negotiate connectivity over the ICE transport by exchanging XML-formatted candidate transports for the channel. This negotiation proceeds immediately in order to maximize the possibility that media can be exchanged as quickly as possible. Concurrent with negotiation of the ICE candidates, it is possible for the initiator and responder to negotiate which content types the session will include, which transport methods will be tried for each content type, etc. Those negotiation flows are shown in XEP-0166. This document specifies only negotiation of the ICE transport method.

-

The candidate syntax and negotiation flow are described below.

+

The candidate syntax and negotiation flow are described below. (This document shows negotiation for the ice-udp transport method, but the same principles apply to the ice-tcp transport method.)

The following is an example of the candidate format:

- + protocol - The protocol to be used. The allowable values are: "udp" (when standard &icecurr; is used); "tcp-act", "tcp-pass", and "tcp-so" (when &ice-tcp; is used); and "ssltcp" (definition to follow in a separate specification). + The protocol to be used. The allowable values are: "udp" (when the ice-udp transport method is used); "tcp-act", "tcp-pass", and "tcp-so" (when the ice-tcp transport method is used); in addition, future specifications may specify other allowable values. Transport protocol field in a=candidate line udp @@ -237,7 +254,7 @@ initiator='romeo@montague.net/orchard' sid='a73sjjvkla37jfea'> - + - + - + - + - + -

If an entity supports the Jingle ICE transport, it MUST return a feature of "http://www.xmpp.org/extensions/xep-0176.html#ns" &NSNOTE; in response to &xep0030; information requests.

+

If an entity supports the Jingle ice-udp transport, it MUST return a feature of "http://www.xmpp.org/extensions/xep-0176.html#ns-udp" &NSNOTE; in response to &xep0030; information requests.

... - + + ... + + + ]]> +

If an entity supports the Jingle ice-tcp transport, it MUST return a feature of "http://www.xmpp.org/extensions/xep-0176.html#ns-tcp" &NSNOTE; in response to &xep0030; information requests.

+ + + + ]]> + + + ... + ... @@ -419,15 +457,29 @@

Until this specification advances to a status of Draft, its associated namespace shall be "http://www.xmpp.org/extensions/xep-0176.html#ns"; upon advancement of this specification, the ®ISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.

 -

The XMPP Registrar shall include "ice" in its registry of Jingle transport methods. The registry submission is as follows:

+

The XMPP Registrar shall include "ice-udp" and "ice-tcp" in its registry of Jingle transport methods. The registry submission is as follows:

- ice + ice-tcp - A method for negotiation of out-of-band connections with built-in NAT and firewall - traversal, equivalent to the IETF's Interactive Connectivity Establishment (ICE) - methodology. + A method for negotiation of out-of-band TCP connections with built-in NAT + and firewall traversal, equivalent to the IETF's Interactive Connectivity + Establishment (ICE) methodology when resulting in the use of TCP as the + transport protocol. + reliable + XEP-0176 + + + + ice-udp + + A method for negotiation of out-of-band UDP connections with built-in NAT + and firewall traversal, equivalent to the IETF's Interactive Connectivity + Establishment (ICE) methodology when resulting in the use of UDP as the + transport protocol. + + lossy XEP-0176 ]]> @@ -435,13 +487,14 @@ - + @@ -465,19 +518,9 @@ - - - - - - - - - - - + - + @@ -500,6 +543,65 @@ - ]]> + ]]> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ]]> +