moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

ICE-11 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@103 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2006-10-13 16:00:23 +00:00
parent 425f74b027
commit e180445339
2 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
xep-0176.xml
View File

@ -2,7 +2,7 @@
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
<!ENTITY ice10 "<cite>ICE-10</cite>">
<!ENTITY ice11 "<cite>ICE-11</cite>">
]>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
@ -60,7 +60,8 @@
<li>In Jingle, each candidate transport is sent in a separate IQ exchange (rather than sending all candidates at once as in draft-ietf-mmusic-ice); this approach takes advantage of the request-response semantics of the XMPP &IQ; stanza type and enables the parties to send higher-priority candidates earlier in the negotiation.</li>
<li>Syntax from the Session Description Protocol (see &rfc4566;) is mapped to an XML syntax suitable for sending over the XMPP signalling channel.</li>
</ul>
<p><em>Note: This document depends on the IETF's Interactive Connectivity Establishment (ICE) specification, which is a work in progress. Every effort has been made to keep this document synchronized with draft-ietf-mmusic-ice, for which the latest published version is 10 (hereafter referred to as "&ice10;"). The interested reader is referred to the &ice10; for a detailed description of the ICE methodology, which for the most part this document merely maps to XMPP syntax.</em></p>
<p><em>Note: This document depends on the IETF's Interactive Connectivity Establishment (ICE) specification, which is a work in progress. Every effort has been made to keep this document synchronized with draft-ietf-mmusic-ice, for which the latest published version is 11 (hereafter referred to as "&ice11;"). The interested reader is referred to the &ice11; for a detailed description of the ICE methodology, which for the most part this document merely maps to XMPP syntax.</em></p>
<p><em>Note: This document still needs to be updated to track the changes between ICE-10 and ICE-11. That work will be completed as soon as possible.</em></p>
</section1>
<section1 topic='Requirements' anchor='reqs'>
<p>The Jingle transport method defined herein is designed to meet the following requirements:</p>
@ -138,13 +139,13 @@
</tr>
<tr>
<td>component</td>
<td>A Component ID as defined in &ice10;</td>
<td>A Component ID as defined in &ice11;</td>
<td>Component ID value in a=candidate line</td>
<td>1</td>
</tr>
<tr>
<td>foundation</td>
<td>A Foundation as defined in &ice10;</td>
<td>A Foundation as defined in &ice11;</td>
<td>Foundation value in a=candidate line</td>
<td>1</td>
</tr>
@ -174,43 +175,43 @@
</tr>
<tr>
<td>priority</td>
<td>A Priority as defined in &ice10;</td>
<td>A Priority as defined in &ice11;</td>
<td>Priority value in a=candidate line</td>
<td>9909</td>
</tr>
<tr>
<td>protocol</td>
<td>The protocol to be used; allowable values are: "udp" (when standard &ice10; is used); "tcp", "tcp-act", and "tcp-pass" (when &ice-tcp; is used); and "ssltcp" (definition to follow)</td>
<td>The protocol to be used; allowable values are: "udp" (when standard &ice11; is used); "tcp", "tcp-act", and "tcp-pass" (when &ice-tcp; is used); and "ssltcp" (definition to follow)</td>
<td>a=ice-ufrag line</td>
<td>udp</td>
</tr>
<tr>
<td>pwd</td>
<td>A Password as defined in &ice10;</td>
<td>A Password as defined in &ice11;</td>
<td>a=ice-pwd line</td>
<td>asd88fgpdd777uzjYhagZg</td>
</tr>
<tr>
<td>type</td>
<td>A Candidate Type as defined in &ice10;; the allowable values are "host" for host candidates, "srflx" for server reflexive candidates, "prflx" for peer reflexive candidates, and "relay" for relayed candidates</td>
<td>A Candidate Type as defined in &ice11;; the allowable values are "host" for host candidates, "srflx" for server reflexive candidates, "prflx" for peer reflexive candidates, and "relay" for relayed candidates</td>
<td>Typ field in a=candidate line</td>
<td>srflx</td>
</tr>
<tr>
<td>ufrag</td>
<td>A User Fragment as defined in &ice10;</td>
<td>A User Fragment as defined in &ice11;</td>
<td>a=ice-ufrag line</td>
<td>8hhy</td>
</tr>
</table>
</section3>
<section3 topic='Negotiation Flow' anchor='protocol-negotiate-flow'>
<p>The first step in negotiating connectivity is for each client to immediately begin sending candidate transport methods to the other client. These candidates SHOULD be gathered by following the procedure specified in Section 4.1 of &ice10; and prioritized by following the procedure specified in Section 4.2 of &ice10;. Each candidate MUST be sent in a &JINGLE; element with an action of "transport-info".</p>
<p>The first step in negotiating connectivity is for each client to immediately begin sending candidate transport methods to the other client. These candidates SHOULD be gathered by following the procedure specified in Section 4.1 of &ice11; and prioritized by following the procedure specified in Section 4.2 of &ice11;. Each candidate MUST be sent in a &JINGLE; element with an action of "transport-info".</p>
<p>If the responder receives and can successfully process a given candidate, it returns an IQ-result (if not, for example because the candidate data is improperly formatted, it returns an error).</p>
<p>Note well that the responder is only indicating receipt of the candidate, not telling the initiator that the candidate will be used.</p>
<p>The initiator keeps sending candidates, one after the other (without stopping to receive an acknowledgement of receipt from the responder for each candidate) until it has exhausted its supply of possible or desirable candidate transports. (Because certain candidates may be more "expensive" in terms of bandwidth or processing power, the initiator may not want to advertise their existence unless necessary.) For each candidate, the responder acknowledges receipt.</p>
<p>At the same time (i.e., immediately after provisionally accepting the session, not waiting for the initiator to begin or finish sending candidates), the responder also begins sending candidates that may work for it. As above, the initiator acknowledges receipt of the candidates.</p>
<p>As the initiator and responder receive candidates, they probe the various candidate transports for connectivity. In performing these connectivity checks, client SHOULD follow the procedure specified in Section 7 of &ice10;.</p>
<p>As the initiator and responder receive candidates, they probe the various candidate transports for connectivity. In performing these connectivity checks, client SHOULD follow the procedure specified in Section 7 of &ice11;.</p>
<example caption="Initiating Entity Sends a Candidate"><![CDATA[
<iq to='juliet@capulet.com/balcony' from='romeo@montague.net/orchard' id='info1' type='set'>
<jingle xmlns='http://jabber.org/protocol/jingle'

2
xep.ent
View File

@ -398,7 +398,7 @@
<!ENTITY dnssd "<span class='ref'>DNS-Based Service Discovery</span> <note>DNS-Based Service Discovery &lt;<link url='http://files.dns-sd.org/draft-cheshire-dnsext-dns-sd.txt'>http://files.dns-sd.org/draft-cheshire-dnsext-dns-sd.txt</link>&gt;. Work in progress.</note>" >
<!ENTITY geoprivpol "<span class='ref'>Geopriv Policy</span> <note>Geopriv Policy &lt;<link url='http://www.ietf.org/internet-drafts/draft-ietf-geopriv-policy-08.txt'>http://www.ietf.org/internet-drafts/draft-ietf-geopriv-policy-08.txt</link>&gt;. Work in progress.</note>" >
<!ENTITY iax "<span class='ref'>IAX</span> <note>IAX: Inter-Asterisk eXchange Version 2 &lt;<link url='http://www.ietf.org/internet-drafts/draft-guy-iax-01.txt'>http://www.ietf.org/internet-drafts/draft-ietf-guy-iax-01.txt</link>&gt;. Work in progress.</note>" >
<!ENTITY ice "<span class='ref'>Interactive Connectivity Establishment (ICE)</span> <note>Interactive Connectivity Establishment (ICE): A Methodology for Network Address Translator (NAT) Traversal for Offer/Answer Protocols &lt;<link url='http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-10.txt'>http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-10.txt</link>&gt;. Work in progress.</note>" >
<!ENTITY ice "<span class='ref'>Interactive Connectivity Establishment (ICE)</span> <note>Interactive Connectivity Establishment (ICE): A Methodology for Network Address Translator (NAT) Traversal for Offer/Answer Protocols &lt;<link url='http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-11.txt'>http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-11.txt</link>&gt;. Work in progress.</note>" >
<!ENTITY ice-tcp "<span class='ref'>TCP Candidates with Interactive Connectivity Establishment (ICE)</span> <note>TCP Candidates with Interactive Connectivity Establishment (ICE) &lt;<link url='http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-tcp-01.txt'>http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-tcp-01.txt</link>&gt;. Work in progress.</note>" >
<!ENTITY mdns "<span class='ref'>Multicast DNS</span> <note>Multicast DNS &lt;<link url='http://files.multicastdns.org/draft-cheshire-dnsext-multicastdns.txt'>http://files.multicastdns.org/draft-cheshire-dnsext-multicastdns.txt</link>&gt;. Work in progress.</note>" >
<!ENTITY pidf "<span class='ref'>Presence Information Data Format (PIDF) </span> <note>RFC 3863: Presence Information Data Format (PIDF) &lt;<link url='http://www.ietf.org/rfc/rfc3863.txt'>http://www.ietf.org/rfc/rfc3863.txt</link>&gt;.</note>" >