From 6bdc2081816b3b46010f8d0593510f694052c2d5 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 30 Oct 2006 22:18:25 +0000 Subject: [PATCH] 0.3-pre1 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@133 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0177.xml | 86 +++++++++++++++++++++++++++++++++++++++++----------- 1 file changed, 69 insertions(+), 17 deletions(-) diff --git a/xep-0177.xml b/xep-0177.xml index 01abf81a..027e8f71 100644 --- a/xep-0177.xml +++ b/xep-0177.xml @@ -10,7 +10,7 @@ This document defines a Jingle transport method that results in sending data over a raw User Datagram Protocol (UDP) connection. &LEGALNOTICE; 0177 - Proposed + Experimental Standards Track Standards JIG Council @@ -26,6 +26,12 @@ &scottlu; &hildjj; &seanegan; + + 0.3 + 2006-10-30 + psa + Added informational messages; 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 @@ -40,7 +46,7 @@ -

&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 (session) types, 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;).

+

&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 between XMPP entities using a raw User Datagram Protocol (UDP) connection (see &rfc0768;).

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

@@ -49,14 +55,15 @@
  • 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) and is provided only for the purpose of specifying the IP address and port that an entity considers most likely to succeed without the need for NAT traversal. If NAT traversal is needed, &xep0176; SHOULD be used.

    In order for the initiating entity 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 methods. If the initiating entity wishes to negotiate the Raw UDP transport, it MUST include an empty &TRANSPORT; child element qualified by the 'http://jabber.org/protocol/jingle/transport/raw-udp' namespace.

    - @@ -65,18 +72,19 @@ ]]>     - -

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

    - + +

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

    + ]]>     -

    Once the session is provisionally accepted, each entity should send one &TRANSPORT; element in a transport-info meessage, containing exactly one &CANDIDATE; element per channel, whose 'ip' and 'port' attributes specify the IP address and port number of the candidate that the initiator has reason to believe will be most likely to succeed for that channel. (Note: In older versions of XEP-0166, this was referrred to as the "default candidate".) This is not necessarily the initiator'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 firewall or network address translator (NAT) it is behind, if any. If the NAT is symmetric (not permissive), the candidate SHOULD specify a relay address. Otherwise it SHOULD be an address derived via prior discovery using &rfc3489;, which will be an address on the outside of the firewall or NAT.

    +

    Once the session is provisionally accepted, each entity should send one &TRANSPORT; element in a transport-info meessage, containing exactly one &CANDIDATE; element per channel, whose 'ip' and 'port' attributes specify the IP address and port number of the candidate that the initiator has reason to believe will be most likely to succeed for that channel. This is not necessarily the initiator'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. If the NAT is symmetric (not permissive), the candidate SHOULD specify a relay address. Otherwise it SHOULD be an address derived via prior discovery using &rfc3489;, which will be an address on the outside of the firewall or NAT.

    +

    Note: The Raw UDP candidate is equivalent to the "in-use" candidate as described in &ice;. (In older versions of XEP-0166, this was referrred to as the "default candidate".)

    - + @@ -85,18 +93,62 @@ ]]> -

    Note: The 'name' attribute specifies the name of the channel and 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).

    -

    Either entity may send this transport-info message at any time, after which the recipient should send and receive data to and from the new address.

    +

    The 'generation', 'ip', 'name', and 'port' attributes are REQUIRED. The 'name' attribute specifies the name of the channel and 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).

    +

    Either entity may send this transport-info message at any time, after which the recipient should attempt to send data to the specified address. If the data can be delivered, the recipient MUST send a Jingle transport-accept, content-accept, or session-accept action to the initiator.

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

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

     - + -

    The syntax and semantics informational message payloads specific to the Raw UDP transport method will be defined in a future version of this specification.

    +

    Informational messages may be sent by the receiver within the context of the Raw UDP transport to communicate the status of transport checking. The informational message MUST be an IQ-set containing a &JINGLE; element of type "transport-info", where the informational message is a payload element qualified by the 'http://jabber.org/protocol/jingle/info/raw-udp' namespace; the following payload elements are defined:

    + + + + + + + + + + + + + + + + + +
    ElementMeaning
    <failed/>Connectivity checks failed.
    <succeeded/>Connectivity checks succeeded.
    <trying/>Connectivity checks are underway.
    +

    Note: Because the informational message is sent in an IQ-set, the receiving party MUST return either an IQ-result or an IQ-error (normally only an IQ-result to acknowledge receipt; no error flows are defined or envisioned at this time).

         -

    In order to secure the end-to-end data stream, implementations SHOULD use encryption methods appropriate to the transport method in use.

    +

    In order to secure the data stream, implementations SHOULD use encryption methods appropriate to the transport method; in the case of UDP, that would include Datagram Transport Layer Security (DTLS) as specified in &rfc4347;.