%ents; ]>
Jingle Raw UDP Transport Method This specification defines a Jingle transport method that results in sending media data using raw datagram associations via the User Datagram Protocol (UDP). This simple transport method does not provide NAT traversal, and the ICE-UDP transport method should be used if NAT traversal is required. &LEGALNOTICE; 0177 Draft Standards Track Standards Council XMPP Core XEP-0166 jingle-raw-udp jingle:transports:raw-udp http://xmpp.org/schemas/jingle-transports-raw-udp.xsd jingle &joebeda; &stpeter; &scottlu; &hildjj; &seanegan; 1.1 2009-12-23 psa

Added type attribute to candidate element for consistency with XEP-0176.

 1.0 2009-06-10 psa

Per a vote of the XMPP Council, advanced specification from Experimental to Draft.

 0.17 2009-04-04 psa

Removed security consideration about sending IP address before session acceptance, since that functionality is no longer supported.

 0.16 2009-03-09 psa

Minor changes to track modifications to XEP-0166; updated security considerations for consistency with XEP-0176.

 0.15 2009-02-11 psa

Simplified flow by including responder candidate in session-accept.

 0.14 2008-12-16 psa
  • Removed the <trying/> info message.
  • Because the removal of the <trying/> info message is backwards-incompatible, modified protocol version number from 0 to 1 and changed namespace from urn:xmpp:jingle:transports:raw-udp:0 to urn:xmpp:jingle:transports:raw-udp:1.
  • Specified that media must be sent but only after session acceptance.
 0.13 2008-12-07 psa

Per list consensus, removed the <received/> info message.

 0.12 2008-10-20 psa

For consistency with the ICE-UDP transport method, added component attribute to handle RTCP candidates and allowed multiple <candidate/> child elements.

 0.11 2008-09-30 psa

Clarified protocol flow.

 0.10 2008-09-25 psa
  • Added an ID attribute to the candidate, trying, and received elements for tracking purposes.
  • Specified that trying and received messages must be sent.
  • Modified namespaces to incorporate namespace versioning.
  • Cleaned up XML schemas.
 0.9 2007-11-27 psa

Further editorial review.

 0.8 2007-11-15 psa

Editorial review and consistency check.

 0.7 2007-06-25 psa

More clearly specified the hit-or-miss nature of the transport; corrected informational messages.

 0.6 2007-04-17 psa

Specified Jingle conformance, including definition of transport type as datagram; added section on service discovery.

 0.5 2007-03-23 psa

Updated to reflect changes to XEP-0166; clarified media data checking.

 0.4 2006-12-21 psa

Recommended sending of candidate in initiation request to save a round trip and expedite the negotiation; removed name attribute; clarified flow of negotiation; modified spec to use provisional namespace before advancement to Draft (per XEP-0053).

 0.3 2006-10-31 psa

Added informational messages; clarified connectivity checks and acceptance process; mentioned that the Raw UDP candidate is conceptually equivalent to the concept of an in-use candidate from the ICE specification; added reference to RFC 4347.

 0.2 2006-07-12 se/psa

Removed candidate element and specified exchange of address information via transport-info messages; clarified usage of name attribute.

 0.1 2006-03-01 psa/jb

Initial version (split from XEP-0166).

&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 application formats, leaving that up to separate specifications. The current document defines a transport method for establishing and managing data between XMPP entities using a raw User Datagram Protocol (UDP) association (see &rfc0768;). This "raw-udp" method results in a datagram transport method suitable for use in media applications where some packet loss is tolerable (e.g., audio and video).

The Raw UDP transport does not provide end-to-end traversal of Network Address Translators (NATs), or even basic connectivity checks; if NAT traversal is needed, Jingle clients SHOULD use &ice; as described in &xep0176;. The Raw UDP transport method is defined only for the purpose of specifying the IP address and port that an entity considers "most likely to succeed" and is a "hit-or-miss" method that might work end-to-end in some circumstances (especially when the sending entity is a gateway or relay, for example when a back-to-back user agent or call manager sends an early media offer to the initiator on behalf of the responder, as described in &xep0167;).

The Jingle transport method 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 over the IP address and port that the parties consider most likely to succeed.
  2. Make it relatively easy to implement support in standard Jabber/XMPP clients.
  3. 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.

In accordance with Section 10 of XEP-0166, this document specifies the following information related to the Jingle Raw UDP transport type:

  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 Transport Initiation section of this document.

  3. Successful negotiation of the Raw 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.

The overall protocol flow for negotiation of the Jingle Raw UDP Transport Method is as follows.

| | ack | |<-----------------------------------| | session-accept (w/candidate) | |<-----------------------------------| | ack | |----------------------------------->| |<========MEDIA NOW FLOWS===========>| | | ]]>

The following sections describe the protocol flow in detail.

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 Raw UDP transport for a given content type, it MUST include a &TRANSPORT; child element qualified by the 'urn:xmpp:jingle:transports:raw-udp:1' namespace &VNOTE;, which MUST This is required to avoid a round trip and help expedite the negotiation. include the initiator's Raw UDP candidate via the 'ip', 'port', 'generation', and 'id' attributes of the &CANDIDATE; element. The &TRANSPORT; element MAY include more than one &CANDIDATE; element (typically one for RTP and another for RTCP).

]]>

All attributes are REQUIRED. The 'ip' and 'port' attributes are self-explanatory. The 'component' attribute enables the parties to distinguish between different aspects of the media stream that each need to use a separate transport address (e.g., RTP and RTCP). The 'generation' attribute defines which version of this candidate is in force (this is useful if the candidate is redefined mid-stream, for example if the port is changed). The 'id' attribute uniquely identifies this candidate for tracking purposes.

Note: The "Raw UDP candidate" is the candidate that the entity has reason to believe will be most likely to succeed for that content type, and thus is equivalent to the "default" candidate as described in the ICE specification. This is not necessarily the entity's preferred address for communication, but instead is the "address most likely to succeed", i.e., the address that is assumed to be reachable by the vast majority of target entities. To determine reachability, the sender needs to classify ahead of time the permissiveness of the NAT or firewall it is behind, if any. It then SHOULD assign the Raw UDP candidate as follows, where the candidate types are as described in ICE:

NAT Type Recommended Raw UDP Candidate Type
None Host candidate
Symmetric Relay candidate
Permissive Server reflexive or peer reflexive candidate discovered via STUN (see &rfc5389;)

If the client is aware of which type of candidate it is sending, the candidate element MAY contain a 'type' attribute. Although this information is merely a hint about the candidate type, this information can help the recipient be aware of how permissive the peer's NAT or firewall is. The values of the 'type' attribute are "host", "prflx", "relay", and "srflx" (as in the ICE specification and XEP-0176).

As described in XEP-0166, to acknowledge the session initiation request, the responder returns an IQ-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 MUST contain a &TRANSPORT; element qualified by the 'urn:xmpp:jingle:transports:raw-udp:1' namespace, which SHOULD in turn contain one &CANDIDATE; element for each Raw UDP candidate generated by or known to the responder.

]]>

(Notice that the foregoing example includes two &CANDIDATE; elements, one for RTP and the other for RTCP.)

The initiator then acknowledges the session acceptance.

]]>

Upon sending the session-accept action, the responder MUST immediately attempt to send media to the initiator. Upon receiving the session-accept action, the initiator MUST immediately attempt to send media to the responder. The exact media to send depends on the application type being negotiated and therefore is out of scope for this specification (e.g., for Jingle RTP Sessions it would be appropriate to send comfort noise as specified in &rfc3389;).

An implementation SHOULD enforce a timeout on receipt of media, such that if no media is received from the other party within a reasonable period of time, the implementation will consider the session to have failed and therefore send to the other party a Jingle "session-terminate" action with a reason code of <timeout/>.

]]>

The other party then acknowledges termination of the session.

]]>

To advertise its support for the Jingle Raw UDP Transport Method, when replying to &xep0030; information requests an entity MUST return URNs for any version of this protocol that the entity supports -- e.g., "urn:xmpp:jingle:transports:raw-udp:1" for this version and "urn:xmpp:jingle:transports:raw-udp:0" for the previous version &VNOTE;.

]]> ]]>

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 &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.

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

Application types that use the Jingle Raw UDP transport method MAY also define their own application-specific encryption methods, such as the Secure Real-time Transport Protocol (SRTP) for RTP exchanges as described in XEP-0167: Jingle RTP Sessions.

This document requires no interaction with &IANA;.

This specification defines the following XML namespace:

  • urn:xmpp:jingle:transports:raw-udp:1

The ®ISTRAR; includes the foregoing namespace in its registry at &NAMESPACES;, as governed by &xep0053;.

 &NSVER;

The XMPP Registrar includes "raw-udp" in its registry of Jingle transport methods at &JINGLETRANSPORTS;. The registry submission is as follows:

raw-udp A method for exchanging data over raw UDP associations. datagram XEP-0177 ]]> The protocol documented by this schema is defined in XEP-0177: http://www.xmpp.org/extensions/xep-0177.html ]]>

Thanks to Thiago Camargo, Paul Chitescu, Diana Cionoiu, Olivier Crête, Steffen Larsen, Robert McQueen, Mike Ruprecht, Jakob Schroeter, Justin Uberti, Unnikrishnan Vikrama Panicker, and Paul Witty for their feedback.