From b6235033861d089e12582414b53fb0b0ba87b57d Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Fri, 1 Aug 2008 03:48:02 +0000 Subject: [PATCH] 0.20 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2113 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0176.xml | 157 ++++++++++++++++++++++++++------------------------- 1 file changed, 79 insertions(+), 78 deletions(-) diff --git a/xep-0176.xml b/xep-0176.xml index f1a7353f..9d863f81 100644 --- a/xep-0176.xml +++ b/xep-0176.xml @@ -11,7 +11,7 @@ This specification defines a Jingle transport method that results in sending media data using raw datagram sockets via the User Datagram Protocol (UDP). This transport method is negotiated via the Interactive Connectivity Establishment (ICE) methodology defined by the IETF and thus provides robust NAT traversal for media traffic. &LEGALNOTICE; 0176 - Proposed + Experimental Standards Track Standards Council @@ -27,6 +27,12 @@ &stpeter; &hildjj; &seanegan; + + 0.20 + 2008-07-31 + psa +

For consistency with XEP-0166, removed profile attribute, changed content-replace to transport-replace, and changed content-accept to transport-accept.

 + 0.19 2008-06-04 @@ -200,15 +206,15 @@ INITIATOR RESPONDER |----------------------------------->| | STUN Binding Request | | (dropped) | - | x---------------------------------| + | x=================================| | STUN Binding Request | - |----------------------------------->| + |===================================>| | STUN Binding Result | - |<-----------------------------------| + |<===================================| | STUN Binding Request | - |<-----------------------------------| + |<===================================| | STUN Binding Result | - |----------------------------------->| + |===================================>| | Jingle session-accept | |<-----------------------------------| | Jingle ack (XMPP IQ-result) | @@ -227,7 +233,7 @@ INITIATOR RESPONDER action='session-initiate' initiator='romeo@montague.net/orchard' sid='a73sjjvkla37jfea'> - + [ ... ] @@ -238,7 +244,7 @@ INITIATOR RESPONDER ]]> -

The 'pwd' and 'ufrag' attributes MUST be included in the session-initate request, in subsequent content-add and content-replace actions, and when offering candidates via the transport-info action. The attributes SHOULD NOT be included in a session-accept action. The values are separately generated for both the initiator and the responder, in accordance with &icecore; and as shown in the examples. The attributes are defined as follows.

+

The 'pwd' and 'ufrag' attributes MUST be included in the session-initiate request, in subsequent content-add and transport-replace actions, and when offering candidates via the transport-info action. The attributes SHOULD NOT be included in a session-accept action. The values are separately generated for both the initiator and the responder, in accordance with &icecore; and as shown in the examples. The attributes are defined as follows.

@@ -393,7 +399,7 @@ INITIATOR RESPONDER action='transport-info' initiator='romeo@montague.net/orchard' sid='a73sjjvkla37jfea'> - + @@ -419,7 +425,7 @@ INITIATOR RESPONDER action='transport-info' initiator='romeo@montague.net/orchard' sid='a73sjjvkla37jfea'> - + @@ -461,7 +467,7 @@ INITIATOR RESPONDER action='transport-info' initiator='romeo@montague.lit/orchard' sid='a73sjjvkla37jfea'> - + @@ -508,45 +514,48 @@ INITIATOR NAT RESPONDER | | from 192.0.2.1:3478 | | | to 10.0.1.1:8998 | | | (dropped) | - | | x--------------------| + | | x====================| | STUN Binding Request | | | from 10.0.1.1:8998 | | | to 192.0.2.1:3478 | | | USE-CANDIDATE | | - |---------------------->| | + |======================>| | | | STUN Binding Request | | | from 192.0.2.3:45664 | | | to 192.0.2.1:3478 | | | USE-CANDIDATE | - | |---------------------->| + | |======================>| | | STUN Binding Response | | | from 192.0.2.1:3478 | | | to 192.0.2.3:45664 | - | |<----------------------| + | |<======================| | STUN Binding Response | | | from 192.0.2.1:3478 | | | to 10.0.1.1:8998 | | | map 192.0.2.3:45664 | | - |<----------------------| | + |<======================| | + | | | |================RTP now can flow==============>| + | | | | | STUN Binding Request | | | from 192.0.2.1:3478 | | | to 192.0.2.3:45664 | - | |<----------------------| + | |<======================| | STUN Binding Request | | | from 192.0.2.1:3478 | | | to 10.0.1.1:8998 | | - |<----------------------| | + |<======================| | | STUN Binding Response | | | from 10.0.1.1:8998 | | | to 192.0.2.1:3478 | | | map 192.0.2.1:3478 | | - |---------------------->| | + |======================>| | | | STUN Binding Response | | | from 192.0.2.3:45664 | | | to 192.0.2.1:3478 | | | map 192.0.2.1:3478 | - | |---------------------->| + | |======================>| + | | | |<===============RTP now can flow===============| | | | ]]> @@ -569,7 +578,7 @@ INITIATOR NAT RESPONDER initiator='romeo@montague.net/orchard' responder='juliet@capulet.com/balcony' sid='a73sjjvkla37jfea'> - + [ ... ] @@ -615,7 +624,7 @@ INITIATOR NAT RESPONDER

If the responder cannot find a suitable candidate transport or it receives a ¬acceptable; error from the initiator in response to its acceptance of a suitable transport, it SHOULD terminate the session as described in Section 6.8 of XEP-0166.

-

The creator of a content type MAY modify an existing, in-use candidate at any time during the session, for example to change the IP address or port. This is done by sending a content-replace action with the changed candidate information, where the value of the 'generation' is incremented to specify that the candidate information is a modification to an existing candidate.

+

The creator of a content type MAY modify an existing, in-use candidate at any time during the session, for example to change the IP address or port. This is done by sending a transport-replace action with the changed candidate information, where the value of the 'generation' is incremented to specify that the candidate information is a modification to an existing candidate.

An example follows (change to IP address and port).

- + @@ -645,27 +654,24 @@ INITIATOR NAT RESPONDER ]]>

The recipient then acknowledges receipt.

- ]]> -

If the content-replace is acceptable, the recipient then sends a content-accept action.

+

If the transport-replace is acceptable, the recipient then sends a transport-accept action.

- - - [ ... ] - + @@ -703,7 +709,7 @@ INITIATOR NAT RESPONDER action='transport-info' initiator='romeo@montague.net/orchard' sid='a73sjjvkla37jfea'> - + @@ -728,21 +734,18 @@ INITIATOR NAT RESPONDER to='romeo@montague.net/orchard' type='result'/> ]]> -

The parties SHOULD check the newly-offered candidate for connectivity, as described previously. If the parties determine that media can flow over the candidate, the initiating party shall send a content-replace action to the responder.

- The parties SHOULD check the newly-offered candidate for connectivity, as described previously. If the parties determine that media can flow over the candidate, the initiating party shall send a transport-replace action to the responder.

+ - - [ ... ] - @@ -760,28 +763,25 @@ INITIATOR NAT RESPONDER ]]> -

The responder then acknowledges the replaced content definition.

- The responder then acknowledges the replaced transport definition.

+ ]]> -

The responder then accepts the replaced content definition.

- The responder then accepts the replaced transport definition.

+ - - - [ ... ] - + @@ -942,43 +942,44 @@ INITIATOR NAT RESPONDER - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Name