XEP-0176: Jingle ICE-UDP Transport Method

Copyright (c) 1999 - 2009 XMPP Standards Foundation. See Legal Notices.


This specification defines a Jingle transport method that results in sending media data using raw datagram associations via the User Datagram Protocol (UDP). This transport method is negotiated via the Interactive Connectivity Establishment (ICE) methodology, which provides robust NAT traversal for media traffic.

NOTICE: This document is currently within Last Call or under consideration by the XMPP Council for advancement to the next stage in the XSF standards process.


Table of Contents


1. Introduction
2. Glossary
3. Requirements
4. Jingle Conformance
5. Protocol Description
    5.1. Overall Flow
    5.2. Session Initiation
    5.3. Syntax
    5.4. Response
    5.5. Candidate Negotiation
    5.6. Connectivity Checks
    5.7. Acceptance of Successful Candidate
    5.8. Modifying an Existing Candidate
    5.9. Negotiating a New Candidate
6. Fallback to Raw UDP
7. Determining Support
    7.1. ICE Support
    7.2. SDP Offer / Answer Support
8. Implementation Notes
9. Deployment Notes
10. Security Considerations
    10.1. Sharing IP Addresses
    10.2. Encryption of Media
11. IANA Considerations
12. XMPP Registrar Considerations
    12.1. Protocol Namespaces
    12.2. Protocol Versioning
    12.3. Service Discovery Features
    12.4. Jingle Transport Methods
13. XML Schema
14. Acknowledgements

Appendices
    A: Document Information
    B: Author Information
    C: Legal Notices
    D: Relation to XMPP
    E: Discussion Venue
    F: Requirements Conformance
    G: Notes
    H: Revision History


1. Introduction

Jingle [1] 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 application formats, leaving that up to separate specifications.

The current document defines a transport method for establishing and managing data exchanges between XMPP entities over the User Datagram Protocol (see RFC 768 [2]), using the ICE methodology developed within the IETF and specified in Interactive Connectivity Establishment (ICE) [3] (hereafter referred to as ICE-CORE). Use of the ice-udp method results in a datagram transport suitable for media applications where some packet loss is tolerable (e.g., audio and video).

Note: ICE-CORE has been approved for publication as an RFC but has not yet been published as an RFC. While every effort has been made to keep this document synchronized with ICE-CORE, the interested reader is referred to ICE-CORE for a detailed description of the ICE methodology.

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

2. Glossary

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

3. Requirements

The Jingle transport method defined herein are 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. Enable use of UDP as the transport protocol.
  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.

4. Jingle Conformance

In accordance with Section 10 of XEP-0166, this document specifies the following information related to the Jingle ice-udp transport method:

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

  2. The semantics of the <transport/> element are defined in the ICE Negotiation section of this document.

  3. Successful negotiation of the ice-udp method results in use of a datagram transport that is suitable for applications where some packet loss is tolerable, such as audio and video.

  4. If multiple components are to be communicated by the application type that uses the transport, the transport shall support those components and assign identifiers for them as described in the specification that defines the application type.

5. Protocol Description

5.1 Overall Flow

The overall protocol flow for negotiation of the Jingle ICE-UDP Transport Method is as follows (note: many of these events happen simultaneously, not in sequence).

INITIATOR                              RESPONDER
    |                                      |
    |  Jingle session-initiate stanza      |
    |  (with one or more candidates)       |
    |------------------------------------->|
    |  Jingle ack (XMPP IQ-result)         |
    |<-------------------------------------|
    |  Jingle session-accept stanza        |
    |  (with one or more candidates)       |
    |<-------------------------------------|
    |  Jingle ack (XMPP IQ-result)         |
    |------------------------------------->|
    |  multiple STUN Binding Requests      |
    |<====================================>|
    |  multiple STUN Binding Results       |
    |<====================================>|
    |<=========MEDIA NOW FLOWS============>|
    |                                      |
    |  optional Jingle transport-info      |
    |  stanzas (one candidate per stanaza) |
    |<------------------------------------>|
    |                                      |
    

Note: The examples in this document follow the scenario described in Section 17 of ICE-CORE, except that we substitute the Shakespearean characters "Romeo" and "Juliet" for the generic entities "L" and "R".

5.2 Session Initiation

In order for the initiator in a Jingle exchange to start the negotiation, it sends a Jingle "session-initiate" stanza that includes at least one content type, as described in XEP-0166. If the initiator wishes to negotiate the ice-udp transport method for an application format, it MUST include a <transport/> child element qualified by the 'urn:xmpp:jingle:transports:ice-udp:1' namespace (see Namespace Versioning regarding the possibility of incrementing the version number). This element SHOULD in turn contain one <candidate/> element for each of the higher-priority transport candidates as determined in accordance with the ICE methodology, but MAY instead be empty (with each candidate to be sent as the payload of a transport-info message).

Example 1. Initiation

<iq from='romeo@montague.lit/orchard'
    id='jingle1'
    to='juliet@capulet.lit/balcony'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:0'
          action='session-initiate'
          initiator='romeo@montague.lit/orchard'
          sid='a73sjjvkla37jfea'>
    <content name='this-is-the-audio-content'>
      <description xmlns='urn:xmpp:jingle:apps:rtp:1' media='audio'>
        <payload-type id='96' name='speex' clockrate='16000'/>
        <payload-type id='97' name='speex' clockrate='8000'/>
        <payload-type id='18' name='G729'/>
        <payload-type id='0' name='PCMU' />
        <payload-type id='103' name='L16' clockrate='16000' channels='2'/>
        <payload-type id='98' name='x-ISAC' clockrate='8000'/>
      </description>
      <transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'
                 pwd='asd88fgpdd777uzjYhagZg'
                 ufrag='8hhy'>
        <candidate component='1'
                   foundation='1'
                   generation='0'
                   id='el0747fg11'
                   ip='10.0.1.1'
                   network='1'
                   port='8998'
                   priority='2130706431'
                   protocol='udp'
                   type='host'/>
        <candidate component='1'
                   foundation='2'
                   generation='0'
                   id='y3s2b30v3r'
                   ip='192.0.2.3'
                   network='1'
                   port='45664'
                   priority='1694498815'
                   protocol='udp'
                   rel-addr='10.0.1.1'
                   rel-port='8998'
                   type='srflx'/>
      </transport>
    </content>
  </jingle>
</iq>
    

5.3 Syntax

The <transport/> element's 'pwd' and 'ufrag' attributes MUST be included in the session-initiate request, in subsequent content-add and transport-replace actions, and when offering candidates via the transport-info action. The attributes MAY be included in a session-accept action. The values are separately generated for both the initiator and the responder, in accordance with ICE-CORE and as shown in the examples. The attributes are defined as follows.

Table 1: Transport Attributes

Name Description SDP Syntax Example
pwd A Password as defined in ICE-CORE. a=ice-pwd line asd88fgpdd777uzjYhagZg
ufrag A User Fragment as defined in ICE-CORE. a=ice-ufrag line 8hhy

The attributes of the <candidate/> element are described in the following table:

Table 2: Candidate Attributes

Name Description SDP Syntax Example
component A Component ID as defined in ICE-CORE. Component ID value in a=candidate line 1
foundation A Foundation as defined in ICE-CORE. Foundation value in a=candidate line 1
generation An index, starting at 0, that enables the parties to keep track of updates to the candidate throughout the life of the session. N/A 0
id A unique identifier for the candidate. N/A el0747fg11
ip The Internet Protocol (IP) address for the candidate transport mechanism; this may be either an IPv4 address or an IPv6 address. IP Address value in a=candidate line 192.0.2.3
network An index, starting at 0, referencing which network this candidate is on for a given peer (used for diagnostic purposes if the calling hardware has more than one Network Interface Card). N/A 0
port The port at the candidate IP address. Port value in a=candidate line 45664
priority A Priority as defined in ICE-CORE [6] Priority value in a=candidate line 2130706431
protocol The protocol to be used. The only value defined by this specification is "udp". Transport protocol field in a=candidate line udp
rel-addr A related address as defined in ICE-CORE. raddr value in a=candidate line 10.0.1.1
rel-port A related port as defined in ICE-CORE. rport value in a=candidate line 8998
rem-addr A IP address for a remote address as defined in ICE-CORE. connection-address value in a=remote-candidates line 192.0.2.1
rem-port The port for a remote address as defined in ICE-CORE. port value in a=remote-candidates line 3478
type A Candidate Type as defined in ICE-CORE. The allowable values are "host" for host candidates, "prflx" for peer reflexive candidates, "relay" for relayed candidates, and "srflx" for server reflexive candidates. Typ field in a=candidate line srflx

5.4 Response

As described in XEP-0166, to acknowledge receipt of the session initiation request, the responder immediately returns an IQ-result.

Example 2. Responder acknowledges receipt of session-initiate request

<iq from='juliet@capulet.lit/balcony'
    id='jingle1'
    to='romeo@montague.lit/orchard'
    type='result'/>
    

Depending on the application type, a user agent controlled by a human user might need to wait for the user to affirm a desire to proceed with the session before continuing. When the user agent has received such affirmation (or if the user agent can automatically proceed for any reason, e.g. because no human intervention is expected or because a human user has configured the user agent to automatically accept sessions with a given entity), it returns a Jingle session-accept message. This message SHOULD also contain a <transport/> element that in turn contain one <candidate/> element for each of the responder's higher-priority transport candidates, just as for the session-initiate message, but MAY instead be empty (with each candidate to be sent as the payload of a transport-info message).

Note: See the Security Considerations section of this document regarding the exposure of IP addresses on behalf by the responder's client.

Example 3. Responder accepts the session request

<iq from='juliet@capulet.lit/balcony'
    id='accept1'
    to='romeo@montague.lit/orchard'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:0'
          action='session-accept'
          initiator='romeo@montague.lit/orchard'
          responder='juliet@capulet.lit/balcony'
          sid='a73sjjvkla37jfea'>
    <content creator='initiator' name='this-is-the-audio-content'>
      <description xmlns='urn:xmpp:jingle:apps:rtp:1' media='audio'>
        <payload-type id='97' name='speex' clockrate='8000'/>
        <payload-type id='18' name='G729'/>
      </description>
      <transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'>
        <candidate component='1'
                   foundation='1'
                   generation='0'
                   id='or2ii2syr1'
                   ip='192.0.2.1'
                   network='0'
                   port='3478'
                   priority='2130706431'
                   protocol='udp'
                   type='host'/>
      </transport>
    </content>
  </jingle>
</iq>
    

5.5 Candidate Negotiation

The initiator and responder negotiate connectivity over ICE by exchanging XML-formatted transport candidates for the channel. This negotiation proceeds immediately in order to maximize the possibility that connectivity can be established (and therefore media can be exchanged) as quickly as possible. In order to expedite session establishment, the initiator SHOULD include transport candidates in its session-initiate message but MAY also send additional transport candidates as soon as it learns of them, even before receiving acknowledgement of the session-initiate message (i.e., the initiator MUST consider the session to be live as soon as it sends the session-initiate message). [7]

The first step in negotiating connectivity is for each party to send transport candidates to the other party. [9] These candidates SHOULD be gathered by following the procedure specified in Section 4.1.1 of ICE-CORE (typically by communicating with a standalone STUN server in order to discover the client's public IP address and port) and prioritized by following the procedure specified in Section 4.1.2 of ICE-CORE.

Each candidate or set of candidates shall be sent as <candidate/> children of a <transport/> element qualified by the 'urn:xmpp:jingle:transports:ice-udp:1' namespace. The <transport/> element is sent via a Jingle action of session-initiate, session-accept, or transport-info.

Either party MAY include multiple <candidate/> elements in one <transport/> element, especially in the session-initiate and session-accept messages sent at the beginning of the session negotiation. Including multiple candidates in the session-initiate and session-accept messages can help to ensure interoperability with entities that implement the SDP offer/answer model described in RFC 3264; in particular, an entity SHOULD include multiple candidates in its session-initiate or session-accept message if the other party advertises support for the "urn:ietf:rfc:3264" service discovery feature as described in the SDP Offer / Answer Support section of this document. However, including one candidate per subsequent transport-info action typically results in a faster negotiation because the candidates most likely to succeed are sent first (in the session-info and session-accept messages) and it is not necessary to gather all candidates before beginning to send any candidates; furthermore, because certain candidates can be more "expensive" in terms of bandwidth or processing power, either party might not want to advertise the existence of such candidates unless it is necessary to do so after other candidates have failed.

If the party that receives a candidate in a Jingle message can successfully process a given candidate or set of candidates, it returns an IQ-result (if not, for example because the candidate data is improperly formatted, it returns an IQ-error). At this point, the receiving entity is only indicating receipt of the candidate or set of candidates, not telling the other party that the candidate will be used.

The initiator can keep sending candidates (without stopping to receive an acknowledgement of receipt from the responder for each candidate) until it has exhausted its supply of possible or desirable transport candidates; for each candidate or set of candidates, the responder acknowledges receipt. The responder can also keep sending potential candidates, which the initiator will acknowledge.

5.6 Connectivity Checks

As the initiator and responder receive candidates, they probe the various transport candidates for connectivity. In performing these connectivity checks, each party SHOULD follow the procedure specified in Section 7 of ICE-CORE. The following business rules apply:

  1. Each party sends a STUN Binding Request (see RFC 5389 [10]) from each local candidate it generated to each remote candidate it received.
  2. In accordance with ICE-CORE, the STUN Binding Requests MUST include the PRIORITY attribute (computed according to Section 7.1.1.1. of ICE-CORE).
  3. For the purposes of the Jingle ICE-UDP Transport Method, both parties are full ICE implementations and therefore the controlling role MUST be assumed by the initiator and the controlled role MUST be assumed by the responder.
  4. The STUN Binding Requests generated by the initiator MAY include the USE-CANDIDATE attribute to indicate that the initiator wishes to cease checks for this component.
  5. The STUN Binding Requests generated by the initiator MUST include the ICE-CONTROLLING attribute.
  6. The STUN Binding Requests generated by the responder MUST include the ICE-CONTROLLED attribute.
  7. The parties MUST use STUN short term credentials to authenticate requests and perform message integrity checks. As in ICE-CORE, the username in the STUN Binding Request is of the form "ufrag-of-sender:ufrag-of-peer" and the password is the value of the 'pwd' attribute provided by the peer. [11]

When it receives a STUN Binding Request, each party MUST return a STUN Binding Response, which indicates either an error case or the success case. As described in Section 7.1.2.2 of ICE-CORE, a connectivity check succeeds if all of the following are true:

  1. The STUN transaction generated a success response.
  2. The source IP address and port of the response equals the destination IP address and port to which the Binding Request was sent.
  3. The destination IP address and port of the response match the source IP address and port from which the Binding Request was sent.

For the candidates exchanged in the previous section, the connectivity checks would be as follows (this diagram mirrors the example in ICE-CORE).

INITIATOR                  NAT                  RESPONDER
    |                       |                       |
    |                       | STUN Binding Request  |
    |                       | from 192.0.2.1:3478   |
    |                       | to   10.0.1.1:8998    |
    |                       |   (dropped)           |
    |                       |  x====================|
    | STUN Binding Request  |                       |
    | from 10.0.1.1:8998    |                       |
    | to   192.0.2.1:3478   |                       |
    | USE-CANDIDATE         |                       |
    |======================>|                       |
    |                       | STUN Binding Request  |
    |                       | from 192.0.2.3:45664  |
    |                       | to   192.0.2.1:3478   |
    |                       | USE-CANDIDATE         |
    |                       |======================>|
    |                       | STUN Binding Response |
    |                       | from 192.0.2.1:3478   |
    |                       | to   192.0.2.3:45664  |
    |                       |<======================|
    | STUN Binding Response |                       |
    | from 192.0.2.1:3478   |                       |
    | to   10.0.1.1:8998    |                       |
    | map  192.0.2.3:45664  |                       |
    |<======================|                       |
    |                       |                       |
    |<==Media Now Can Flow==|                       |
    |                       |                       |
    |                       | STUN Binding Request  |
    |                       | from 192.0.2.1:3478   |
    |                       | to   192.0.2.3:45664  |
    |                       |<======================|
    | STUN Binding Request  |                       |
    | from 192.0.2.1:3478   |                       |
    | to   10.0.1.1:8998    |                       |
    |<======================|                       |
    | STUN Binding Response |                       |
    | from 10.0.1.1:8998    |                       |
    | to   192.0.2.1:3478   |                       |
    | map  192.0.2.1:3478   |                       |
    |======================>|                       |
    |                       | STUN Binding Response |
    |                       | from 192.0.2.3:45664  |
    |                       | to   192.0.2.1:3478   |
    |                       | map  192.0.2.1:3478   |
    |                       |======================>|
    |                       |                       |
    |                       |==Media Now Can Flow==>|
    |                       |                       |
    

Note: Here the initiator (controlling agent) is using "aggressive nomination" as described in Section 8.1.1.2 of ICE-CORE and therefore includes the USE-CANDIDATE attribute in the STUN Binding Requests it sends.

5.7 Acceptance of Successful Candidate

If, based on STUN connectivity checks, the parties determine that they will be able to exchange media between a given pair of local candidates and remote candidates (i.e., the pair is "nominated" and ICE processing is "completed"), they can then begin using that candidate pair to exchange media. There is no need for the parties to communicate the chosen candidate pair in the signalling channel.

In the unlikely event that one of the parties determines that it cannot establish connectivity even after sending and checking lower-priority candidates, it SHOULD terminate the session as described in XEP-0166.

5.8 Modifying an Existing Candidate

The creator of a content type MAY modify an existing, in-use candidate at any time during the session, for example to change the IP address or port. This is done by sending a transport-replace action with the changed candidate information, where the value of the 'generation' attribute is incremented to specify that the candidate information is a modification to an existing candidate.

An example follows (change to IP address and port).

Example 4. Initiator modifies the in-use candidate

<iq from='romeo@montague.lit/orchard'
    id='rep2'
    to='juliet@capulet.lit/balcony'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:0'
          action='transport-replace'
          initiator='romeo@montague.lit/orchard'
          sid='a73sjjvkla37jfea'>
    <content creator='initiator' name='this-is-the-audio-content'>
      <transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'
                 pwd='asd88fgpdd777uzjYhagZg'
                 ufrag='8hhy'>
        <candidate component='1'
                   foundation='1'
                   generation='1'
                   id='y3s2b30v3r'
                   ip='192.0.2.3'
                   network='1'
                   port='45665'
                   priority='1694498815'
                   protocol='udp'
                   type='srflx'/>
      </transport>
    </content>
  </jingle>
</iq>
    

The recipient then acknowledges receipt.

Example 5. Recipient acknowledges transport-replace

<iq from='juliet@capulet.lit/balcony'
    id='rep2'
    to='romeo@montague.lit/orchard'
    type='result'/>
    

If the transport-replace is acceptable, the recipient then sends a transport-accept action (if not, the recipient sends a transport-reject action).

Example 6. Responder definitively accepts the replaced candidate

<iq from='juliet@capulet.lit/balcony'
    id='accept2'
    to='romeo@montague.lit/orchard'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:0'
          action='transport-accept'
          initiator='romeo@montague.lit/orchard'
          responder='juliet@capulet.lit/balcony'
          sid='a73sjjvkla37jfea'>
    <content creator='initiator' name='this-is-the-audio-content'>
      <transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'
                 pwd='asd88fgpdd777uzjYhagZg'
                 ufrag='8hhy'>
        <candidate component='1'
                   foundation='1'
                   generation='1'
                   id='y3s2b30v3r'
                   ip='192.0.2.3'
                   network='1'
                   port='45665'
                   priority='1694498815'
                   protocol='udp'
                   type='srflx'/>
      </transport>
    </content>
  </jingle>
</iq>
    

The initiator then acknowledges the responder's acceptance:

Example 7. Initiator acknowledges content acceptance

<iq from='romeo@montague.lit/orchard'
    id='accept2'
    to='juliet@capulet.lit/balcony'
    type='result'/>
    

The parties then use the modified candidate in subsequent communications.

5.9 Negotiating a New Candidate

Even after media has begun to flow, either party MAY continue to send additional candidates to the other party (e.g., because the user agent has become aware of a new media proxy or network interface card). As above, such candidates are shared by sending a transport-info action.

Example 8. Initiator sends a subsequent candidate

<iq from='romeo@montague.lit/orchard'
    id='info4'
    to='juliet@capulet.lit/balcony'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:0'
          action='transport-info'
          initiator='romeo@montague.lit/orchard'
          sid='a73sjjvkla37jfea'>
    <content creator='initiator' name='this-is-the-audio-content'>
      <transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'
                 pwd='asd88fgpdd777uzjYhagZg'
                 ufrag='8hhy'>
        <candidate component='1'
                   foundation='1'
                   generation='0'
                   id='m3110wc4nd'
                   ip='10.0.1.2'
                   network='0'
                   port='9001'
                   priority='21149780477'
                   protocol='udp'
                   type='host'/>
      </transport>
    </content>
  </jingle>
</iq>
    

The receiving party MUST acknowledge receipt of the candidate.

Example 9. Recipient acknowledges receipt

<iq from='juliet@capulet.lit/balcony'
    id='info4'
    to='romeo@montague.lit/orchard'
    type='result'/>
    

The parties SHOULD check the newly-offered candidate for connectivity, as described previously. If the parties determine that media can flow over the candidate, the initiating party MAY send a transport-replace action to the responder in order to use the new candidate.

Example 10. Initiator sends transport-replace

<iq from='romeo@montague.lit/orchard'
    id='rep3'
    to='juliet@capulet.lit/balcony'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:0'
          action='transport-replace'
          initiator='romeo@montague.lit/orchard'
          responder='juliet@capulet.lit/balcony'
          sid='a73sjjvkla37jfea'>
    <content creator='initiator' name='this-is-the-audio-content'>
      <transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'
                 pwd='asd88fgpdd777uzjYhagZg'
                 ufrag='8hhy'>
        <candidate component='1'
                   foundation='1'
                   generation='0'
                   id='m3110wc4nd'
                   ip='10.0.1.2'
                   network='0'
                   port='9001'
                   priority='21149780477'
                   protocol='udp'
                   type='host'/>
      </transport>
    </content>
  </jingle>
</iq>
    

The responder then acknowledges the replaced transport definition.

Example 11. Responder acknowledges transport-replace

<iq from='juliet@capulet.lit/balcony'
    id='rep3'
    to='romeo@montague.lit/orchard'
    type='result'/>
    

The responder then accepts the replaced transport definition.

Example 12. Responder definitively accepts the replaced transport definition

<iq from='juliet@capulet.lit/balcony'
    id='accept3'
    to='romeo@montague.lit/orchard'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:0'
          action='transport-accept'
          initiator='romeo@montague.lit/orchard'
          responder='juliet@capulet.lit/balcony'
          sid='a73sjjvkla37jfea'>
    <content creator='initiator' name='this-is-the-audio-content'>
      <transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'
                 pwd='asd88fgpdd777uzjYhagZg'
                 ufrag='8hhy'>
        <candidate component='1'
                   foundation='1'
                   generation='0'
                   id='m3110wc4nd'
                   ip='10.0.1.2'
                   network='0'
                   port='9001'
                   priority='21149780477'
                   protocol='udp'
                   type='host'/>
      </transport>
    </content>
  </jingle>
</iq>
    

The initiator then acknowledges content acceptance.

Example 13. Initiator acknowledges content acceptance

<iq from='romeo@montague.lit/orchard'
    id='accept3'
    to='juliet@capulet.lit/balcony'
    type='result'/>
    

The parties then use the new candidate in subsequent communications.

6. Fallback to Raw UDP

It can happen that the responder does not support ICE, in which case it can be necessary to fall back to use of the Jingle Raw UDP Transport Method [12]. One typical scenario is communication between an ICE-aware Jingle endpoint and a non-ICE-aware SIP endpoint through a Jingle-to-SIP gateway, as follows:

  1. The Jingle endpoint sends a session-initiate request to the SIP endpoint, specifying a transport method of ICE-UDP.
  2. Based on capabilities information, the gateway knows that the SIP endpoint does not support ICE, so it enables the endpoints to use its media relay. It does this by:

The session flow is as follows.

Romeo                    Gateway                    Juliet
  |                         |                         |
  |   session-initiate      |                         |
  |   (audio definition)    |                         |
  |------------------------>|                         |
  |   ack                   |                         |
  |<------------------------|                         |
  |   transport-replace     |                         |
  |   (Raw UDP)             |                         |
  |<------------------------|                         |
  |   ack                   |                         |
  |------------------------>|                         |
  |   transport-accept      |                         |
  |------------------------>|                         |
  |   ack                   |                         |
  |<------------------------|   SIP INVITE            |
  |                         |------------------------>|
  |                         |   200 OK                |
  |                         |<------------------------|
  |   session-accept        |                         |
  |<------------------------|                         |
  |   ack                   |                         |
  |------------------------>|                         |
  |                    MEDIA SESSION                  |
  |<=================================================>|
  |                         |   session-terminate     |
  |                         |<------------------------|
  |   session-terminate     |                         |
  |<------------------------|                         |
  |   ack                   |                         |
  |------------------------>|   ack                   |
  |                         |------------------------>|
  |                         |                         |
    

The protocol flow is as follows, showing only the stanzas sent between Romeo and the gateway (acting on Juliet's behalf).

Example 14. Initiator sends session-initiate

<iq from='romeo@montague.lit/orchard'
    id='jingle1'
    to='juliet@capulet.lit/balcony'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:0'
          action='session-initiate'
          initiator='romeo@montague.lit/orchard'
          sid='a73sjjvkla37jfea'>
    <content creator='initiator' name='voice'>
      <description xmlns='urn:xmpp:jingle:apps:rtp:1' media='audio'>
        <payload-type id='96' name='speex' clockrate='16000'/>
        <payload-type id='97' name='speex' clockrate='8000'/>
        <payload-type id='18' name='G729'/>
        <payload-type id='103' name='L16' clockrate='16000' channels='2'/>
        <payload-type id='98' name='x-ISAC' clockrate='8000'/>
      </description>
      <transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'/>
    </content>
  </jingle>
</iq>
    

Example 15. Responder acknowledges session-initiate

<iq from='juliet@capulet.lit/balcony'
    id='accept1'
    to='romeo@montague.lit/orchard'
    type='result'/>
    

Immediately the gateway sends a transport-replace action to Romeo, specifying a transport of Raw UDP with a candidate whose IP address and port identify a media relay at the gateway.

Example 16. Gateway sends transport-replace on behalf of responder

<iq from='juliet@capulet.lit/balcony'
    id='replace1'
    to='romeo@montague.lit/orchard'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:0'
          action='transport-replace'
          initiator='romeo@montague.lit/orchard'
          sid='a73sjjvkla37jfea'>
    <content creator='initiator' name='voice1'>
      <transport xmlns='urn:xmpp:jingle:transports:raw-udp:1'>
        <candidate generation='0'
                   id='a9j3mnbtu1'
                   ip='10.1.1.104'
                   port='13540'/>
      </transport>
    </content>
  </jingle>
</iq>
    

Romeo then acknowledges the transport-replace action and immediately also sends a transport-accept.

Example 17. Initiator acknowledges transport-replace

<iq from='romeo@montague.lit/orchard'
    id='replace1'
    to='juliet@capulet.lit/balcony'
    type='result'/>
    

Example 18. Initiator accepts new transport

<iq from='romeo@montague.lit/orchard'
    id='accept1'
    to='juliet@capulet.lit/balcony'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:0'
          action='transport-accept'
          initiator='romeo@montague.lit/orchard'
          sid='a73sjjvkla37jfea'>
    <content creator='responder' name='voice2'>
      <transport xmlns='urn:xmpp:jingle:transports:raw-udp:1'>
        <candidate generation='0'
                   id='a9j3mnbtu1'
                   ip='10.1.1.104'
                   port='13540'/>
      </transport>
    </content>
  </jingle>
</iq>
    

The gateway then acknowledges the acceptance on behalf of Juliet.

Example 19. Gateway acknowledges transport-accept

<iq from='juliet@capulet.lit/balcony'
    id='accept1'
    to='romeo@montague.lit/orchard'
    type='result'/>
    

Eventually, the responder sends a session-accept through the gateway.

Example 20. Responder sends session-accept

<iq from='juliet@capulet.lit/balcony'
    id='accept1'
    to='romeo@montague.lit/orchard'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:0'
          action='session-accept'
          initiator='romeo@montague.lit/orchard'
          responder='juliet@capulet.lit/balcony'
          sid='a73sjjvkla37jfea'>
    <content creator='initiator' name='voice'>
      <description xmlns='urn:xmpp:jingle:apps:rtp:1' media='audio'>
        <payload-type id='18' name='G729'/>
      </description>
      <transport xmlns='urn:xmpp:jingle:transports:raw-udp:1'/>
    </content>
  </jingle>
</iq>
    

Example 21. Initiator acknowledges session-accept

<iq from='romeo@montague.lit/orchard'
    id='accept1'
    to='juliet@capulet.lit/balcony'
    type='result'/>
    

The endpoints now begin to exchange session media, and can continue the session as long as desired.

Eventually, one of the endpoints terminates the session.

Example 22. Responder terminates the session

<iq from='juliet@capulet.lit/balcony'
    id='term1'
    to='romeo@montague.lit/orchard'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:0'
          action='session-terminate'
          initiator='romeo@montague.lit/orchard'
          sid='a73sjjvkla37jfea'>
    <reason>
      <success/>
      <text>Sorry, gotta go!</text>
    </reason>
  </jingle>
</iq>
    

The other party then acknowledges termination of the session:

Example 23. Initiator acknowledges termination

<iq from='romeo@montague.lit/orchard'
    id='term1'
    to='juliet@capulet.lit/balcony'
    type='result'/>
    

7. Determining Support

7.1 ICE Support

If an entity supports the Jingle ice-udp transport, it MUST return a feature of "urn:xmpp:jingle:transports:ice-udp:1" (see Namespace Versioning regarding the possibility of incrementing the version number) in response to Service Discovery [13] information requests.

Example 24. Service discovery information request

<iq from='romeo@montague.lit/orchard'
    id='disco1'
    to='juliet@capulet.lit/balcony'
    type='get'>
  <query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>
  

Example 25. Service discovery information response

<iq from='juliet@capulet.lit/balcony'
    id='disco1'
    to='romeo@montague.lit/orchard'
    type='result'>
  <query xmlns='http://jabber.org/protocol/disco#info'>
    <feature var='urn:xmpp:jingle:transports:ice-udp:1'/>
  </query>
</iq>
    

In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in Entity Capabilities [14]. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.

7.2 SDP Offer / Answer Support

If an entity supports the SDP offer / answer model described in RFC 3264 and therefore prefers to receive multiple candidates in a single "transport-info" action, it MUST advertise support for the "urn:ietf:rfc:3264" service discovery feature. Typically this feature will be advertised only by gateways between Jingle and SIP.

Example 26. Service discovery information request

<iq from='romeo@montague.lit/orchard'
    id='disco2'
    to='sip.shakespeare.lit'
    type='get'>
  <query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>
  

Example 27. Service discovery information response

<iq from='sip.shakespeare.lit'
    id='disco2'
    to='romeo@montague.lit/orchard'
    type='result'>
  <query xmlns='http://jabber.org/protocol/disco#info'>
    ...
    <feature var='urn:ietf:rfc:3264'/>
    <feature var='urn:xmpp:jingle:transports:ice-udp:1'/>
    ...
  </query>
</iq>
    

8. Implementation Notes

In order to speed the negotiation process so that media can flow as quickly as possible, the initiator SHOULD gather and prioritize candidates in advance, or as soon as the principal begins the process of initiating a session.

9. Deployment Notes

This specification applies exclusively to Jabber/XMPP clients and places no additional requirements on Jabber/XMPP servers. However, service administrators might wish to deploy a STUN server in order to ease the client-to-client negotiation process, and a TURN server for media relaying (see TURN [15]).

10. Security Considerations

10.1 Sharing IP Addresses

By definition, the exchange of transport candidates results in exposure of the sender's IP addresses, which comprise a form of personally identifying information. A Jingle client MUST enable a user to control which entities will be allowed to receive such information. If a human user explicitly accepts a session request, then the client SHOULD consider that action to imply approval of IP address sharing. However, waiting for a human user to explicitly accept the session request can result in delays during session setup, since it is more efficient to immediately begin sharing transport candidates. Therefore, it is RECOMMENDED for the client to immediately send transport candidates to a contact (without waiting for explicit user approval of the session request) in the following cases:

  1. The user has permanently and formally authorized the contact to view the user's presence information via a presence subscription as reflected in an XMPP roster item (see XMPP IM [16]).
  2. The user has temporarily and dynamically shared presence with the contact via "directed presence" as described in RFC 3921.
  3. The user has explicitly added the contact to a "whitelist" of entities who are allowed to access the user's personally-identifying information.

10.2 Encryption of Media

In order to secure the data stream that is negotiated via the Jingle ICE transport, implementations SHOULD use encryption methods appropriate to the transport method and media being exchanged (for details regarding RTP exchanges, refer to Jingle RTP Sessions [17]).

11. IANA Considerations

This document requires no interaction with the Internet Assigned Numbers Authority (IANA) [18].

12. XMPP Registrar Considerations

12.1 Protocol Namespaces

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 [19] shall add the foregoing namespaces to the registry located at <http://xmpp.org/registrar/namespaces.html>, as described in Section 4 of XMPP Registrar Function [20].

12.2 Protocol Versioning

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.

12.3 Service Discovery Features

If an entity supports the SDP offer / answer model described in RFC 3264 and therefore prefers to receive one "transport-info" action with multiple candidates, it MUST advertise support for the "urn:ietf:rfc:3264" feature.

The registry submission is as follows.

Registry Submission

<var>
  <name>urn:ietf:rfc:3264</name>
  <desc>
    Signals support for the SDP offer / answer model 
    described in RFC 3264
  </desc>
  <doc>XEP-0176</doc>
</var>
    

12.4 Jingle Transport Methods

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

<transport>
  <name>ice-udp</name>
  <desc>
    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.
  </desc>
  <type>datagram</type>
  <doc>XEP-0176</doc>
</transport>
    

13. XML Schema

<?xml version='1.0' encoding='UTF-8'?>

<xs:schema
    xmlns:xs='http://www.w3.org/2001/XMLSchema'
    targetNamespace='urn:xmpp:jingle:transports:ice-udp:1'
    xmlns='urn:xmpp:jingle:transports:ice-udp:1'
    elementFormDefault='qualified'>

  <xs:element name='transport'>
    <xs:complexType>
      <xs:sequence>
        <xs:element name='candidate' 
                    type='candidateElementType'
                    minOccurs='0' 
                    maxOccurs='unbounded'/>
      </xs:sequence>
      <xs:attribute name='pwd' type='xs:string' use='optional'/>
      <xs:attribute name='ufrag' type='xs:string' use='optional'/>
    </xs:complexType>
  </xs:element>

  <xs:complexType name='candidateElementType'>
    <xs:simpleContent>
      <xs:extension base='empty'>
        <xs:attribute name='component' type='xs:unsignedByte' use='required'/>
        <xs:attribute name='foundation' type='xs:unsignedByte' use='required'/>
        <xs:attribute name='generation' type='xs:unsignedByte' use='required'/>
        <xs:attribute name='id' type='xs:NCName' use='required'/>
        <xs:attribute name='ip' type='xs:string' use='required'/>
        <xs:attribute name='network' type='xs:unsignedByte' use='required'/>
        <xs:attribute name='port' type='xs:unsignedShort' use='required'/>
        <xs:attribute name='priority' type='xs:positiveInteger' use='required'/>
        <xs:attribute name='protocol' type='xs:NCName' use='required'/>
        <xs:attribute name='rel-addr' type='xs:string' use='optional'/>
        <xs:attribute name='rel-port' type='xs:unsignedShort' use='optional'/>
        <xs:attribute name='rem-addr' type='xs:string' use='optional'/>
        <xs:attribute name='rem-port' type='xs:unsignedShort' use='optional'/>
        <xs:attribute name='type' use='required'>
          <xs:simpleType>
            <xs:restriction base='xs:NCName'>
              <xs:enumeration value='host'/>
              <xs:enumeration value='prflx'/>
              <xs:enumeration value='relay'/>
              <xs:enumeration value='srflx'/>
            </xs:restriction>
          </xs:simpleType>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>

  <xs:simpleType name='empty'>
    <xs:restriction base='xs:string'>
      <xs:enumeration value=''/>
    </xs:restriction>
  </xs:simpleType>

</xs:schema>
  

14. Acknowledgements

Thanks to Diana Cionoiu, Olivier Crête, Tim Julien, Steffen Larsen, Robert McQueen, Mike Ruprecht, and Paul Witty for their feedback.


Appendices


Appendix A: Document Information

Series: XEP
Number: 0176
Publisher: XMPP Standards Foundation
Status: Proposed
Type: Standards Track
Version: 0.24
Last Updated: 2009-02-17
Approving Body: XMPP Council
Dependencies: XMPP Core, XEP-0166
Supersedes: None
Superseded By: None
Short Name: N/A
Source Control: HTML  RSS


Appendix B: Author Information

Joe Beda

Email: jbeda@google.com
JabberID: jbeda@google.com

Scott Ludwig

Email: scottlu@google.com
JabberID: scottlu@google.com

Peter Saint-Andre

JabberID: stpeter@jabber.org
URI: https://stpeter.im/

Joe Hildebrand

Email: jhildebrand@jabber.com
JabberID: hildjj@jabber.org

Sean Egan

Email: seanegan@google.com
JabberID: seanegan@google.com

Robert McQueen

Email: robert.mcqueen@collabora.co.uk
JabberID: robert.mcqueen@collabora.co.uk


Appendix C: Legal Notices

Copyright

This XMPP Extension Protocol is copyright (c) 1999 - 2009 by the XMPP Standards Foundation (XSF).

Permissions

Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.

Disclaimer of Warranty

## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ##

Limitation of Liability

In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising out of the use or inability to use the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.

IPR Conformance

This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at <http://xmpp.org/extensions/ipr-policy.shtml> or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA).

Appendix D: Relation to XMPP

The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 3920) and XMPP IM (RFC 3921) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.


Appendix E: Discussion Venue

There exists a special venue for discussion related to the technology described in this document: the <jingle@xmpp.org> mailing list.

The primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.org> discussion list.

Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.

Errata may be sent to <editor@xmpp.org>.


Appendix F: Requirements Conformance

The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".


Appendix G: Notes

1. XEP-0166: Jingle <http://xmpp.org/extensions/xep-0166.html>.

2. RFC 768: User Datagram Protocol <http://tools.ietf.org/html/rfc0768>.

3. Interactive Connectivity Establishment (ICE): A Methodology for Network Address Translator (NAT) Traversal for Offer/Answer Protocols <http://tools.ietf.org/html/draft-ietf-mmusic-ice>. Work in progress.

4. RFC 3264: An Offer/Answer Model with the Session Description Protocol (SDP) <http://tools.ietf.org/html/rfc3264>.

5. RFC 4566: SDP: Session Description Protocol <http://tools.ietf.org/html/rfc4566>.

6. In accordance with the rules specified in Section 4.1.1 of ICE-CORE, the priority values shown in the examples within this document have been calculated as follows. The "type preference" for host candidates is stipulated to be "126" and for server reflexive candidates "100". The "local preference" for network 0 is stipulated to be "4096", for network 1 "2048", and for network 2 "1024".

7. Given in-order delivery as mandated by XMPP Core [8], the responder will receive such transport-info messages after receiving the session-initiate message; if not, it is appropriate for the responder to return <unknown-session/> errors since according to its state machine the session does not exist.

8. RFC 3920: Extensible Messaging and Presence Protocol (XMPP): Core <http://tools.ietf.org/html/rfc3920>.

9. The fact that both parties send candidates means that Jingle requires each party to be a full implementation of ICE, not a lite implementation as specified in ICE-CORE.

10. RFC 5389: Session Traversal Utilities for NAT (STUN) <http://tools.ietf.org/html/rfc5389>.

11. Thus when Romeo sends a STUN Binding Request to Juliet the credentials will be STUN username "8hhy:9uB6" and password "YH75Fviy6338Vbrhrlp8Yh" whereas when Juliet sends a STUN Binding Request to Romeo the credentials will be STUN username "9uB6:8hhy" and password "asd88fgpdd777uzjYhagZg".

12. XEP-0177: Jingle Raw UDP Transport Method <http://xmpp.org/extensions/xep-0177.html>.

13. XEP-0030: Service Discovery <http://xmpp.org/extensions/xep-0030.html>.

14. XEP-0115: Entity Capabilities <http://xmpp.org/extensions/xep-0115.html>.

15. Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) <http://tools.ietf.org/html/draft-ietf-behave-turn>. Work in progress.

16. RFC 3921: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence <http://tools.ietf.org/html/rfc3921>.

17. XEP-0167: Jingle RTP Sessions <http://xmpp.org/extensions/xep-0167.html>.

18. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.

19. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <http://xmpp.org/registrar/>.

20. XEP-0053: XMPP Registrar Function <http://xmpp.org/extensions/xep-0053.html>.


Appendix H: Revision History

Version 0.24 (2009-02-17)

Simplified flow by including candidates in session-initiate and session-accept.

(psa/rm)

Version 0.23 (2008-12-19)

Specified id attribute and added it to the examples; updated namespaces to reflect changes to other Jingle specifications; completed editorial review.

(psa)

Version 0.22 (2008-09-30)

Corrected fallback scenario to use transport-replace and transport-accept.

(psa)

Version 0.21 (2008-09-25)

(psa)

Version 0.20 (2008-07-31)

For consistency with XEP-0166, removed profile attribute, changed content-replace to transport-replace, and changed content-accept to transport-accept.

(psa)

Version 0.19 (2008-06-04)

Allowed batching of multiple candidates in a single transport-info action for optional interworking with the SDP offer-answer model, and added urn:ietf:rfc:3264 service discovery feature to advertise such support; updated security considerations regarding sharing of IP addresses.

(psa)

Version 0.18 (2008-05-28)

Removed content-replace action from acceptance flow, since in ICE that information is sent via STUN, not in the signalling channel.

(psa)

Version 0.17 (2008-03-20)

Moved pwd and ufrag attributes from candidate element to transport element since they describe session-level or media-level information.

(psa)

Version 0.16 (2008-02-29)

Changed content-modify to content-replace per XEP-0166.

(psa)

Version 0.15 (2008-01-06)

Clarified several small points regarding candidate gathering procedures and STUN connectivity checks.

(psa)

Version 0.14 (2008-01-02)

Modified flow for ICE completion to require content-modify from initiator to responder, thus mapping to sending of revised offer in SIP; added rem-addr and rem-port attributes to map to a=remote-candidates information in SDP; changed raddr and rport attributes to rel-addr and rel-port to prevent confusion with rem-addr and rem-port attributes.

(psa)

Version 0.13 (2007-12-28)

Added further details about connectivity checks; defined raddr and rport attributes for complete mapping to SDP.

(psa)

Version 0.12 (2007-11-28)

Moved ice-tcp definition to a separate specification.

(psa)

Version 0.11 (2007-11-27)

Further editorial review; also added sections on modification of existing candidates and exchange of subsequent candidates.

(psa)

Version 0.10 (2007-11-15)

Editorial review and consistency check.

(psa)

Version 0.9 (2007-06-28)

Updated to track ICE-16.

(psa)

Version 0.8 (2007-04-17)

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 datagram and ice-tcp as streaming.

(psa)

Version 0.7 (2007-03-23)

Updated to track ICE-14 and ICE-TCP-03; moved text on discovery of STUN servers to separate specification.

(psa)

Version 0.6 (2006-12-21)

Modified spec to use provisional namespace before advancement to Draft (per XEP-0053).

(psa)

Version 0.5 (2006-10-31)

Updated to track ICE-12; corrected service discovery process; completed editorial review; removed mention of DTMF, which is for audio only.

(psa)

Version 0.4 (2006-09-13)

Updated to track ICE-10; added section on service discovery.

(psa)

Version 0.3 (2006-07-12)

Specified that DTMF must use in-band signalling (XEP-0181).

(se/psa)

Version 0.2 (2006-03-24)

Recommended use of RTP-native methods for DTMF.

(psa)

Version 0.1 (2006-03-01)

Initial version (split from XEP-0166).

(psa/jb)

END