From 7d839f60a4d8d630aac4dd4b4f50b4efdf754776 Mon Sep 17 00:00:00 2001 From: "Matthew A. Miller" Date: Tue, 5 Jan 2016 10:10:22 -0700 Subject: [PATCH] ProtoXEP jingle-ice: Updates to address Council feedback --- inbox/jingle-ice.xml | 47 ++++++++++++++++++++++++++++++++++---------- 1 file changed, 37 insertions(+), 10 deletions(-) diff --git a/inbox/jingle-ice.xml b/inbox/jingle-ice.xml index 10aafbbd..191b1358 100644 --- a/inbox/jingle-ice.xml +++ b/inbox/jingle-ice.xml @@ -28,6 +28,17 @@ jingle-ice &stpeter; + + 0.0.2 + 2015-12-30 + psa + +
    +
  • Added a 'tcptype' attribute to support ICE-TCP (RFC 6544) instead of overloading the existing 'type' attribute, with values of "active", "passive", and "so".
    • +
  • Modified the syntax of the end-of-candidates indication so that it is wrapped in a <transport/> element in the same namespace.
    • +
+ + 0.0.1 2015-12-16 @@ -248,23 +259,29 @@ INITIATOR RESPONDER rel-addr A related address as defined in RFC 5245. - raddr value in a=candidate line + Value of raddr attribute in a=candidate line 10.0.1.1 rel-port A related port as defined in RFC 5245. - rport value in a=candidate line + Value of rport attribute in a=candidate line 8998 + + tcptype + A TCP candidate type as defined in RFC 6455. The allowable values are "active" for TCP active candidates, "passive" for TCP passive candidates, and "so" for TCP simultaneous-open candidates. + Value of tcptype attribute in a=candidate line + so + type - A Candidate Type as defined in RFC 5245 or RFC 6455. The allowable values are "host" for host candidates, "prflx" for peer reflexive candidates, "relay" for relayed candidates, "srflx" for server reflexive candidates, "tcp-active" for TCP active candidates, "tcp-passive" for TCP passive candidates, and "tcp-so" for TCP simultaneous-open candidates (the last three map to values from RFC 6455). - Typ field in a=candidate line + An ICE candidate type as defined in RFC 5245. The allowable values are "host" for host candidates, "prflx" for peer reflexive candidates, "relay" for relayed candidates, and "srflx" for server reflexive candidates. Note that TCP candidate types (RFC 6455) are handled via the 'tcptype' attribute. + Value of typ attribute in a=candidate line srflx -

Note this specification does not provide an no equivalent of the "ice-options" attribute defined in Section 15.5 of RFC 5245, since it is not needed in XMPP given the existence of the Service Discovery extension (XEP-0030).

+

Note this specification does not provide an equivalent of the "ice-options" attribute defined in Section 15.5 of RFC 5245, since it is not needed in XMPP given the existence of the Service Discovery extension (XEP-0030).

As described in XEP-0166, to acknowledge receipt of the session initiation request, the responder immediately returns an IQ-result.

@@ -391,7 +408,7 @@ INITIATOR NAT RESPONDER

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

 -

As explained in the Trickle ICE specification, when a party has completed gathering of candidates it will send an "end-of-candidates indication" to the other party. In Jingle, this takes the form of an informational message as described under Informational Messages. This specificaton defines only a standalone "end-of-candidates indication" (i.e., not a way to indicate ICE completion in an offer or answer).

+

As explained in the Trickle ICE specification, when a party has completed gathering of ICE candidates it will send an "end-of-candidates indication" to the other party. In Jingle, this takes the form of an informational message as described under Informational Messages. This specificaton defines only a standalone "end-of-candidates indication" (i.e., not a way to indicate ICE completion in an offer or answer).

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"), they can then begin using that candidate pair to exchange media.

@@ -698,7 +715,9 @@ Romeo Gateway Juliet initiator='romeo@montague.example/dr4hcr0st3lup4c' sid='a73sjjvkla37jfea'> - + + + @@ -890,6 +909,15 @@ Romeo Gateway Juliet + + + + + + + + + @@ -897,9 +925,6 @@ Romeo Gateway Juliet - - - @@ -917,6 +942,8 @@ Romeo Gateway Juliet + +