From 441471d7d6c02b5f52f0a09e059f41b51d9d7d25 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 28 May 2008 21:09:35 +0000 Subject: [PATCH] 0.18 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1881 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0176.xml | 60 ++++++++-------------------------------------------- 1 file changed, 9 insertions(+), 51 deletions(-) diff --git a/xep-0176.xml b/xep-0176.xml index e25bcd4b..3438aa45 100644 --- a/xep-0176.xml +++ b/xep-0176.xml @@ -21,12 +21,18 @@ - TO BE ASSIGNED + NOT_YET_ASSIGNED &joebeda; &scottlu; &stpeter; &hildjj; &seanegan; + + 0.18 + 2008-05-28 + psa +

Removed content-replace action from acceptance flow, since in ICE that information is sent via STUN, not in the signalling channel.

 + 0.17 2008-03-20 @@ -197,10 +203,6 @@ INITIATOR RESPONDER |<-----------------------------------| | STUN Binding Result | |----------------------------------->| - | Jingle content-replace | - |----------------------------------->| - | Jingle ack (XMPP IQ-result) | - |<-----------------------------------| | Jingle session-accept | |<-----------------------------------| | Jingle ack (XMPP IQ-result) | @@ -539,59 +541,15 @@ INITIATOR NAT RESPONDER |<===============RTP now can flow===============| | | | ]]> -

Note: The initiator (controlling agent) is using "aggressive nomination" as described in Section 8.1.1.2 of &icecore; and therefore includes the USE-CANDIDATE attribute in the STUN Binding Requests it sends.

+

Note: Here the initiator (controlling agent) is using "aggressive nomination" as described in Section 8.1.1.2 of &icecore; and therefore includes the USE-CANDIDATE attribute in the STUN Binding Requests it sends.

If, based on STUN connectivity checks, the parties determine that they will be able to exchange media between a given pair of local candidates and remote candidates (i.e., the pair is "nominated" and ICE processing is "completed"), the parties shall proceed as follows:

    -
  1. The initiator sends a Jingle content-replace action to the responder.
    2. -
  2. The responder acknowledges receipt of the content-replace.
  3. The responder sends a Jingle session-accept action to the initiator.
  4. The initiator acknowledges receipt of the session-accept.
-

First the initiator sends a Jingle content-replace action to the responder. The content-replace MUST contain information about the nominated pair, including the "rem-addr" and "rem-port" attributes (which specify the IP address and port for the responder's end of the pair, which is a "remote address" according to the initiator). This enables both parties to explicitly agree to both ends of the connection pair (i.e., the local address+port and the remote address+port).

- - - - - [ ... ] - - - - - - - - ]]> -

The responder then acknowledges the content-replace action.

- - ]]> -

The responder then sends a session-accept action to the initiator, specifying the candidate that succeeded.

+

First, the responder sends a session-accept action to the initiator, specifying the candidate that succeeded. The session-accept MUST contain information about the nominated pair, including the "rem-addr" and "rem-port" attributes (which specify the IP address and port for the responder's end of the pair, which is a "remote address" according to the initiator). This enables both parties to explicitly agree to both ends of the connection pair (i.e., the local address+port and the remote address+port).