diff --git a/xep-0176.xml b/xep-0176.xml index 8b0ea764..f737c7d7 100644 --- a/xep-0176.xml +++ b/xep-0176.xml @@ -27,6 +27,12 @@ &stpeter; &hildjj; &seanegan; + + 0.14 + 2008-01-02 + psa +

Modified flow for ICE completion to require content-modify from initiator to responder, thus mapping to sending of revised offer in SIP; added rem-addr and rem-port attributes to map to a=remote-candidates information in SDP; changed raddr and rport attributes to rel-addr and rel-port to prevent confusion with rem-addr and rem-port attributes.

 + 0.13 2007-12-28 @@ -173,10 +179,10 @@ INITIATOR RESPONDER |<-----------------------------------| | STUN Binding Result | |----------------------------------->| - | Jingle content-accept | - |<-----------------------------------| - | Jingle ack (XMPP IQ-result) | + | Jingle content-modify | |----------------------------------->| + | Jingle ack (XMPP IQ-result) | + |<-----------------------------------| | Jingle session-accept | |<-----------------------------------| | Jingle ack (XMPP IQ-result) | @@ -298,17 +304,29 @@ INITIATOR RESPONDER asd88fgpdd777uzjYhagZg - raddr + rel-addr A related address as defined in &icecore;. - Raddr value in a=candidate line + raddr value in a=candidate line 10.0.1.1 - rport + rel-port A related port as defined in &icecore;. - Rport value in a=candidate line + rport value in a=candidate line 8998 + + rem-addr + A IP address for a remote address as defined in &icecore;. + connection-address value in a=remote-candidates line + 192.0.2.1 + + + rem-port + The port for a remote address as defined in &icecore;. + port value in a=remote-candidates line + 3478 + type A Candidate Type as defined in &icecore;. The allowable values are "host" for host candidates, "prflx" for peer reflexive candidates, "relay" for relayed candidates, and "srflx" for server reflexive candidates. @@ -497,7 +515,56 @@ INITIATOR NAT RESPONDER

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.

-

If, based on STUN connectivity checks, the parties determine that they will be able to exchange media a given candidate, the responder sends a &JINGLE; element with an action of 'content-accept' (or 'session-accept') to the initiator, specifying the candidate that succeeded.

+

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-modify action to the responder.
    2. +
  2. The responder acknowledges receipt of the content-modify.
    3. +
  3. The responder sends a Jingle content-accept or session-accept action to the initiator.
    4. +
  4. The initiator acknowledges receipt of the content-accept.
    5. +
+

First the initiator sends a Jingle content-modify action to the responder. The content-modify 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).

+ + + + + [ ... ] + + + + + + + + ]]> +

The responder then acknowledges the content-modify action.

+ + ]]> +

The responder then sends a &JINGLE; element with an action of 'content-accept' (or 'session-accept') to the initiator, specifying the candidate that succeeded.