From abfcae5310fb5699b367bb1470711eb74d82fa4d Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Fri, 19 Dec 2008 18:19:27 +0000 Subject: [PATCH] namespace and address consistency git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2584 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0177.xml | 51 ++++++++++++++++++++++++++------------------------- 1 file changed, 26 insertions(+), 25 deletions(-) diff --git a/xep-0177.xml b/xep-0177.xml index b83429cd..ca4b1e5b 100644 --- a/xep-0177.xml +++ b/xep-0177.xml @@ -20,7 +20,8 @@ - NOT_YET_ASSIGNED + N/A + jingle &joebeda; &stpeter; &scottlu; @@ -33,8 +34,8 @@
  • 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.
    • -
  • Because the changes are most likely 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.
 @@ -176,16 +177,16 @@ INITIATOR RESPONDER

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

- + @@ -224,20 +225,20 @@ INITIATOR RESPONDER

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

]]>

As soon as the responder acknowledges the session initiation request, it SHOULD send its own Raw UDP candidate to the initiator via a Jingle "transport-info" message. It does this by sending a transport-info message to the initiator, as shown in the following example (notice that this example includes two &CANDIDATE; elements, one for RTP and the other for RTCP).

@@ -258,24 +259,24 @@ INITIATOR RESPONDER ]]>

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

]]>

It is then the responsibility of the responder to accept the session offer.

- + @@ -291,9 +292,9 @@ INITIATOR RESPONDER ]]>

And the initiator acknowledges the session acceptance.

]]> @@ -330,17 +331,17 @@ INITIATOR RESPONDER

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

]]> @@ -367,7 +368,7 @@ INITIATOR RESPONDER

Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespace 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 backwards-compatible with an older version, 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.

+ &NSVER;

The XMPP Registrar shall include "raw-udp" in its registry of Jingle transport methods. The registry submission is as follows: