From 79b6b0e61fb441f2c94e10e54c03083a81a25e1a Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Thu, 25 Sep 2008 19:43:42 +0000 Subject: [PATCH] 0.10 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2266 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0177.xml | 227 ++++++++++++++++++++++++++++----------------------- 1 file changed, 126 insertions(+), 101 deletions(-) diff --git a/xep-0177.xml b/xep-0177.xml index b1a02526..2d4c139d 100644 --- a/xep-0177.xml +++ b/xep-0177.xml @@ -20,12 +20,25 @@ - TO BE ASSIGNED + NOT_YET_ASSIGNED &joebeda; &stpeter; &scottlu; &hildjj; &seanegan; + + 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 @@ -82,7 +95,8 @@ -

&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) connection (see &rfc0768;). This "raw-udp" method results in a lossy transport method suitable for use in media applications where some packet loss is tolerable (e.g., audio and video).

+

&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) "connection" (see &rfc0768;). This "raw-udp" method results in a lossy transport method suitable for use in media applications where some packet loss is tolerable (e.g., audio and video).

+

Note: The Raw UDP transport does not provide end-to-end traversal of Network Address Translators (NATs); 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. However, this method can prove useful when the communications architecture includes intermediate gateways or relays, as described in XEP-0176.

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

@@ -91,10 +105,9 @@
  • Make it relatively easy to implement support in standard Jabber/XMPP clients.
  • 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.
    • -

    Note: The Raw UDP transport does not provide traversal of Network Address Translators (NATs); if NAT traversal is needed, &xep0176; SHOULD be used. 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 may work in some circumstances. The method can therefore be thought of as the Jingle equivalent of the "I'm Feeling Lucky" button; it is also helpful for use in unit-testing of Jingle implementation by developers working on a local network (see &xep0208;).

     -

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

    +

    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. @@ -104,27 +117,32 @@ -

      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 content type. 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:tmp:jingle:transports:raw-udp' namespace &NSNOTE;, 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 'name' attributes of the &CANDIDATE; element.

      +

      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 content type. 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:0' 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 'generation', 'ip', and 'port' attributes are REQUIRED. The 'ip' and 'port' attributes are self-explanatory. The 'generation' attribute provides a tracking mechanism for determining 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).

      -

      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 Section 4.1.3 of &ice;. 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 client needs 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:

      +

      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 &ice;. 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:

      @@ -153,14 +171,58 @@ type='result'/> ]]>

      Once the responder acknowledges the session initiation request, it:

      -
        +
        1. MUST attempt to send media data via UDP to the IP and port specified in the initiator's Raw UDP candidate.
          2. +
        2. MUST send an informational message of <trying/>.
        3. SHOULD send its own Raw UDP candidate to the initiator via a Jingle "transport-info" message.
          4. -
        4. SHOULD send an informational message of <trying/>.
          5. -
      -

      These are done simultaneously in order to ensure that a connection can be made, since the initiator's Raw UDP candidate may not result in success.

      + +

      These are done simultaneously in order to ensure that a connection can be made, since the initiator's Raw UDP candidate might not result in success.

      -

      The responder MUST immediately attempt to send data to the IP and port specified in the initiation request. If all goes well, the data will be received by the initiator and media will flow. Because delivery of UDP data is not acknowledged, a party that receives media SHOULD send an informational message of <received/> to the other party as specified below.

      +

      The responder MUST immediately attempt to send data to the IP and port specified in the initiation request. If all goes well, the data will be received by the initiator and media will flow. Because delivery of UDP data is not acknowledged, a party that receives media MUST send an informational message of <received/> to the other party as specified below.

      +       + +

      When it attempts to send data to a Raw UDP candidate, a party MUST send an informational message of <trying/>, including the candidate ID for tracking purposes.

      + + + + + + ]]> + + ]]> +

      If a party receives data, it MUST send an informational message of <received/>, including the candidate ID for tracking purposes.

      + + + + + + ]]> + + ]]>

      As noted, the responder SHOULD send its own Raw UDP candidate to the initiator by sending a transport-info message to the initiator, as shown in the following example.

      @@ -169,13 +231,16 @@ id='jingle2' to='romeo@montague.net/orchard' type='set'> - - - + + @@ -188,54 +253,12 @@ to='juliet@capulet.com/balcony' type='result'/> ]]> -

      Naturally, the initiator SHOULD also attempt to send media to the responder as specified above. This media, too, may or may not get through, but if it does then the other party SHOULD acknowledge receipt.

      -       - -

      When it attempts to send data to a Raw UDP candidate, a party SHOULD send an informational message of <trying/>.

      - - - - - - ]]> - - ]]> -

      If a party receives data, it SHOULD send an informational message of <received/>.

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

      Naturally, the initiator SHOULD also attempt to send media to the responder as specified above. This media, too, might or might not get through, but if it does then the other party MUST acknowledge success by sending a <received/> message.

       -

      Informational messages MAY be sent by either party within the context of the Raw UDP transport to communicate whether the party has attempted to send media or has received media. The informational message MUST be an IQ-set containing a &JINGLE; element of type "session-info", where the informational message is a payload element qualified by the 'urn:xmpp:tmp:jingle:transports:raw-udp:info' namespace &NSNOTE;. The following payload elements are defined:

      +

      Informational messages are sent within the context of the Raw UDP transport to communicate whether the party has attempted to send media or has received media. The informational message MUST be an IQ-set containing a &JINGLE; element of type "session-info", where the informational message is a payload element qualified by the 'urn:xmpp:jingle:transports:raw-udp:info:0' namespace &VNOTE;. The following payload elements are defined:

      NAT Type
      @@ -255,7 +278,7 @@ -

      If an entity supports the Jingle Raw UDP transport, it MUST return a feature of "urn:xmpp:tmp:jingle:transports:raw-udp" &NSNOTE; in response to &xep0030; information requests.

      +

      If an entity supports the Jingle Raw UDP transport, it MUST return a feature of "urn:xmpp:jingle:transports:raw-udp:0" &VNOTE; in response to &xep0030; information requests.

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

      Naturally, support MAY also be determined via the dynamic, presence-based profile of Service Discovery defined in &xep0115;.

      +

      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.

       -

      In order to secure the data stream that is negotiated via the Jingle ICE-UDP transport, implementations SHOULD use encryption methods appropriate to the transport method and media being exchanged (for details regarding audio and video exchanges via RTP, refer to XEP-0167 and XEP-0180).

      +

      In order to secure the data stream that is negotiated via the Jingle ICE-UDP transport, implementations SHOULD use encryption methods appropriate to the transport method and media being exchanged (for details regarding RTP sessions, refer to &xep0167;).

       @@ -288,27 +311,25 @@ - -

      Until this specification advances to a status of Draft, its associated namespaces shall be:

      + +

      This specification defines the following XML namespaces:

        -
      • urn:xmpp:tmp:jingle:transports:raw-udp
        • -
      • urn:xmpp:tmp:jingle:transports:raw-udp:info
        • -
      -

      Upon advancement of this specification, the ®ISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.

      -

      The following namespaces are requested, and are thought to be unique per the XMPP Registrar's requirements:

      -
        -
      • urn:xmpp:jingle:transport:raw-udp
        • -
      • urn:xmpp:jingle:transport:raw-udp:info
        • +
      • urn:xmpp:jingle:transports:raw-udp:0
        • +
      • urn:xmpp:jingle:transports:raw-udp:info:0
      +

      Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespaces to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.

      +       + +

      If the protocol defined in this specification undergoes a major revision that is not fully backward-compatible with an older version, or that contains significant new features, 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 include "raw-udp" in its registry of Jingle transport methods. The registry submission is as follows:

      raw-udp - A method for exchanging data over a raw UDP connection. + A method for exchanging data over raw UDP datagrams. lossy - XEP-0176 + XEP-0177 ]]>       @@ -321,29 +342,31 @@ - + - - - - - - - - - - - + + + + + + + + + + @@ -360,19 +383,21 @@ - + - + - - - - - + + + + + + + ]]>
      Element