From 38020c4a0c4a1e77a62702fa9c17f5e33e1437aa Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 27 Nov 2007 19:45:02 +0000 Subject: [PATCH] 0.9 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1423 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0177.xml | 71 +++++++++++++++++++++++++++++++++------------------- 1 file changed, 45 insertions(+), 26 deletions(-) diff --git a/xep-0177.xml b/xep-0177.xml index 9ac3469c..9368eca6 100644 --- a/xep-0177.xml +++ b/xep-0177.xml @@ -6,7 +6,7 @@
- Jingle Raw UDP Transport + Jingle Raw UDP Transport Method This document defines a Jingle transport method that results in sending data over a raw User Datagram Protocol (UDP) connection. &LEGALNOTICE; 0177 @@ -26,6 +26,12 @@ &scottlu; &hildjj; &seanegan; + + 0.9 + 2007-11-27 + psa +

Further editorial review.

 + 0.8 2007-11-15 @@ -85,7 +91,7 @@
  • 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;).

    +

    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:

    @@ -100,7 +106,10 @@

    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 'http://www.xmpp.org/extensions/xep-0177.html#ns' 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.

    + Permissive - Server reflexive or peer reflexive candidate discovered via &rfc3489; + Server reflexive or peer reflexive candidate discovered via STUN (see &rfc3489; and &rfc3489bis;)     -

    As described in XEP-0166, to provisionally accept the session initiation request, the receiver returns an IQ-result:

    - +

    As described in XEP-0166, to acknowledge the session initiation request, the responder returns an IQ-result:

    + ]]> -

    Once the responder provisionally accepts the session, it:

    +

    Once the responder acknowledges the session initiation request, it:

    • MUST attempt to send media data via UDP to the IP and port specified in the initiator's Raw UDP candidate.
    • SHOULD send its own Raw UDP candidate to the initiator via a Jingle "transport-info" message.
      • @@ -153,7 +165,10 @@

      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.

      +

      The initiator MUST then acknowledge receipt by returning an IQ result (or a standard XMPP error).

      + ]]> -

      Naturally, the initiator SHOULD also attend 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.

      +

      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/>.

      - ]]> + to='juliet@capulet.lit/balcony' + type='result'/> ]]>

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

      ]]> - + to='romeo@montague.lit/orchard' + type='result'/> ]]>       -

      Informational messages MAY be sent by the 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 'http://www.xmpp.org/extensions/xep-0177.html#ns-info' namespace &NSNOTE;. The following payload elements are defined:

      +

      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 'http://www.xmpp.org/extensions/xep-0177.html#ns-info' namespace &NSNOTE;. The following payload elements are defined:

      @@ -239,18 +257,18 @@

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

      + type='get'> ]]> + type='result'> ... @@ -258,6 +276,7 @@ ]]> +

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