Accepted Jingle ICE ProtoXEP as XEP-0371

xep-0371.xml

@@ -9,8 +9,8 @@
   <title>Jingle ICE Transport Method</title>
   <abstract>This specification defines a Jingle transport method that results in sending media data using datagram associations via the User Datagram Protocol (UDP) or using end-to-end connections via the Transport Control Protocol (TCP). This transport method is negotiated via the Interactive Connectivity Establishment (ICE) methodology (which provides robust NAT traversal for media traffic) and also supports the ability to exchange candidates throughout the life of the session, consistent with so-called "Trickle ICE" (draft-ietf-ice-trickle).</abstract>
   &LEGALNOTICE;
-  <number>XXXX</number>
+  <number>0371</number>
-  <status>ProtoXEP</status>
+  <status>Experimental</status>
   <interim/>
   <type>Standards Track</type>
   <sig>Standards</sig>
@@ -28,6 +28,12 @@
   <supersededby/>
   <shortname>jingle-ice</shortname>
   &stpeter;
+  <revision>
+    <version>0.1</version>
+    <date>2016-01-21</date>
+    <initials>XEP Editor (asw)</initials>
+    <remark><p>Initial published version approved by the XMPP Council.</p></remark>
+  </revision>
   <revision>
     <version>0.0.2</version>
     <date>2015-12-30</date>
@@ -171,7 +177,7 @@ INITIATOR                              RESPONDER
     ]]></example>
   </section2>
   <section2 topic='Syntax' anchor='protocol-syntax'>
-    <p>The &TRANSPORT; element's 'pwd' and 'ufrag' attributes MUST be included whenever sending one or more candidates to the other party, e.g. in a session-initiate, session-accept, transport-info, content-add, or transport-replace message. The values for these attributes are separately generated for both the initiator and the responder, in accordance with RFC 5245 and as shown in the examples. The attributes of the &lt;transport/&gt; element are as follows.</p>
+    <p>The &TRANSPORT; element's 'pwd' and 'ufrag' attributes MUST be included whenever sending one or more candidates to the other party, e.g., in a session-initiate, session-accept, transport-info, content-add, or transport-replace message. The values for these attributes are separately generated for both the initiator and the responder, in accordance with RFC 5245 and as shown in the examples. The attributes of the &lt;transport/&gt; element are as follows.</p>
     <table caption='Transport Attributes'>
       <tr>
         <th>Name</th>
@@ -291,7 +297,7 @@ INITIATOR                              RESPONDER
     to='romeo@montague.example/dr4hcr0st3lup4c'
     type='result'/>
     ]]></example>
-    <p>Depending on the application type, a user agent controlled by a human user might need to wait for the user to affirm a desire to proceed with the session before continuing. When the user agent has received such affirmation (or if the user agent can automatically proceed for any reason, e.g. because no human intervention is expected or because a human user has configured the user agent to automatically accept sessions with a given entity), it returns a Jingle session-accept message. This message MUST contain a &TRANSPORT; element qualified by the 'urn:xmpp:jingle:transports:ice:0' namespace, which SHOULD in turn contain one &CANDIDATE; element for each ICE candidate generated by or known to the responder, but MAY instead be empty (with each candidate to be sent as the payload of a transport-info message).</p>
+    <p>Depending on the application type, a user agent controlled by a human user might need to wait for the user to affirm a desire to proceed with the session before continuing. When the user agent has received such affirmation (or if the user agent can automatically proceed for any reason, e.g., because no human intervention is expected or because a human user has configured the user agent to automatically accept sessions with a given entity), it returns a Jingle session-accept message. This message MUST contain a &TRANSPORT; element qualified by the 'urn:xmpp:jingle:transports:ice:0' namespace, which SHOULD in turn contain one &CANDIDATE; element for each ICE candidate generated by or known to the responder, but MAY instead be empty (with each candidate to be sent as the payload of a transport-info message).</p>
      <p>Note: See the <link url='#security'>Security Considerations</link> section of this document regarding the exposure of IP addresses by the responder's client.</p>
     <example caption="Responder accepts the session request"><![CDATA[
 <iq from='juliet@capulet.example/yn0cl4bnw0yr3vym'

xep.ent

@@ -1375,3 +1375,4 @@ IANA Service Location Protocol, Version 2 (SLPv2) Templates</link></span> <note>
 <!ENTITY xep0368 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0368.html'>SRV records for XMPP over TLS (XEP-0368)</link></span> <note>XEP-0368: SRV records for XMPP over TLS &lt;<link url='http://xmpp.org/extensions/xep-0368.html'>http://xmpp.org/extensions/xep-0368.html</link>&gt;.</note>" >
 <!ENTITY xep0369 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0369.html'>Mediated Information eXchange (MIX) (XEP-0369)</link></span> <note>XEP-0369: Mediated Information eXchange (MIX) &lt;<link url='http://xmpp.org/extensions/xep-0369.html'>http://xmpp.org/extensions/xep-0369.html</link>&gt;.</note>" >
 <!ENTITY xep0370 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0370.html'>Jingle HTTP Transport Method (XEP-0370)</link></span> <note>XEP-0370: Jingle HTTP Transport Method &lt;<link url='http://xmpp.org/extensions/xep-0370.html'>http://xmpp.org/extensions/xep-0370.html</link>&gt;.</note>" >
+<!ENTITY xep0371 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0371.html'>Jingle ICE Transport Method (XEP-0371)</link></span> <note>XEP-0371: Jingle ICE Transport Method &lt;<link url='http://xmpp.org/extensions/xep-0371.html'>http://xmpp.org/extensions/xep-0371.html</link>&gt;.</note>" >