From b7e2c3a89853688539529e062d07b66e60110429 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 26 Jun 2007 02:33:50 +0000 Subject: [PATCH] 0.7 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1008 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0177.xml | 82 +++++++++++++++++++++++++++++----------------------- 1 file changed, 46 insertions(+), 36 deletions(-) diff --git a/xep-0177.xml b/xep-0177.xml index 72392265..4ec095bc 100644 --- a/xep-0177.xml +++ b/xep-0177.xml @@ -26,6 +26,12 @@ &scottlu; &hildjj; &seanegan; + + 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 @@ -73,7 +79,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) 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. This is also helpful for bootstrapping of Jingle implementation by developers working on a local network. If NAT traversal is needed, &xep0176; SHOULD be used.

    +

    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:

    @@ -130,34 +136,16 @@ ]]>

    Once the responder provisionally accepts the session, it:

      -
    • MUST check the initiator's Raw UDP candidate by attempting to send data via UDP to the specified IP and port (see next section).
      • +
    • 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.
      • -
    • MAY send an informational message.
      • +
    • SHOULD send an informational message of <trying/>.

    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.

    - -

    The responder MUST immediately attempt to send data to the IP and port specified in the initiation request. Because delivery of UDP data is not acknowledged, the data SHOULD be sent using the echo protocol (&rfc0862;) over the IP address and port specified in the Raw UDP candidate; if the data is echoed back, the recipient would then send a Jingle "content-accept" (or "session-accept") action to the initiator.

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

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

    - - ]]> + +

    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.

     -

    While checking the initiator's Raw UDP candidate, 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.

    +

    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.

    ]]> -

    Naturally, the initiator then MUST also check the responder's Raw UDP candidate by following the checking procedure outlined above.

    +

    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.

     -

    While checking the initiator's Raw UDP candidate, the responder MAY send an informational message to communicate the status of transport checking. The informational message MUST be an IQ-set containing a &JINGLE; element of type "session-info", where the informational message is a payload element specified in the Informational Messages section of this document.

    +

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

    +

    Each informational message MUST be an IQ-set containing a &JINGLE; element of type "session-info", where the informational message is a payload element specified in the Informational Messages section of this document.

     -

    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 "session-info", where the informational message is a payload element qualified by the 'http://www.xmpp.org/extensions/xep-0177.html#ns-info' namespace (see Protocol Namespaces). The following payload elements are defined:

    +

    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:

    - - - - - - + + - +
    Element Meaning
    <failed/>Connectivity checks failed.
    <succeeded/>Connectivity checks succeeded.<received/>The party has received media.
    <trying/>Connectivity checks are underway.The party is trying to send media.

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

    @@ -256,7 +241,8 @@     - + - ]]> + ]]> + + + + + + + + + + + + + + + + + + ]]> +