1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-27 19:52:18 -05:00

updated references

This commit is contained in:
Peter Saint-Andre 2014-02-27 19:41:04 -07:00
parent dedab2f195
commit 1d789d59cd
2 changed files with 13 additions and 4 deletions

View File

@ -10,7 +10,7 @@
<abstract>This document specifies an XMPP protocol extension for discovering services external to the XMPP network.</abstract> <abstract>This document specifies an XMPP protocol extension for discovering services external to the XMPP network.</abstract>
&LEGALNOTICE; &LEGALNOTICE;
<number>0215</number> <number>0215</number>
<status>Deferred</status> <status>Experimental</status>
<type>Standards Track</type> <type>Standards Track</type>
<sig>Standards</sig> <sig>Standards</sig>
<approver>Council</approver> <approver>Council</approver>
@ -23,6 +23,12 @@
&stpeter; &stpeter;
&seanegan; &seanegan;
&mlundblad; &mlundblad;
<revision>
<version>0.6</version>
<date>2014-02-27</date>
<initials>psa</initials>
<remark><p>Updated references to IETF specifications.</p></remark>
</revision>
<revision> <revision>
<version>0.5</version> <version>0.5</version>
<date>2010-02-17</date> <date>2010-02-17</date>
@ -86,7 +92,7 @@
</header> </header>
<section1 topic='Introduction' anchor='intro'> <section1 topic='Introduction' anchor='intro'>
<p>An XMPP client or other entity might need to discover services external to the XMPP network in order to complete certain XMPP-related use cases. One example is the discovery of STUN servers (see &rfc5389;) and TURN relays (see &turn;) for the sake of negotiating media exchanges via &xep0176;. <note>The protocol specified herein is functionally equivalent to the protocol currently used in the Google Talk service for discovery of STUN servers, as documented at &lt;<link url='http://code.google.com/apis/talk/jep_extensions/jingleinfo.html'>http://code.google.com/apis/talk/jep_extensions/jingleinfo.html</link>&gt;, but has been broadened in scope to address additional use cases if desired.</note> An XMPP entity can already discover such external services in several ways, including:</p> <p>An XMPP client or other entity might need to discover services external to the XMPP network in order to complete certain XMPP-related use cases. One example is the discovery of STUN servers (see &rfc5389;) and TURN relays (see &rfc5766;) for the sake of negotiating media exchanges via the &xep0176;. <note>The protocol specified herein is functionally equivalent to the protocol currently used in the Google Talk service for discovery of STUN servers, as documented at &lt;<link url='http://code.google.com/apis/talk/jep_extensions/jingleinfo.html'>http://code.google.com/apis/talk/jep_extensions/jingleinfo.html</link>&gt;, but has been broadened in scope to address additional use cases if desired.</note> An XMPP entity can already discover such external services in several ways, including:</p>
<ol> <ol>
<li>The service is specified in the application's default settings.</li> <li>The service is specified in the application's default settings.</li>
<li>The service is manually added into the application's configuration by a human user.</li> <li>The service is manually added into the application's configuration by a human user.</li>
@ -285,6 +291,7 @@
</credentials> </credentials>
</iq> </iq>
]]></example> ]]></example>
<p>For TURN, the server might construct time-limited credentials as described in &turn-rest;.</p>
<p>If the server cannot obtain credentials at the service, it returns an appropriate stanza error, such as &notfound;, &remoteserver;, &timeout;, or &notauthorized;.</p> <p>If the server cannot obtain credentials at the service, it returns an appropriate stanza error, such as &notfound;, &remoteserver;, &timeout;, or &notauthorized;.</p>
</section2> </section2>
</section1> </section1>
@ -374,7 +381,7 @@
<service> <service>
<name>turn</name> <name>turn</name>
<desc>a server that provides Traversal Using Relays around NAT (TURN)</desc> <desc>a server that provides Traversal Using Relays around NAT (TURN)</desc>
<doc>draft-ietf-behave-turn</doc> <doc>RFC 5766</doc>
</service> </service>
]]></code> ]]></code>
</section3> </section3>
@ -432,7 +439,7 @@
</section1> </section1>
<section1 topic='Acknowledgements' anchor='ack'> <section1 topic='Acknowledgements' anchor='ack'>
<p>Thanks to Justin Karneges, Evgeniy Khramtsov, and Unnikrishnan Vikrama Panicker for their feedback.</p> <p>Thanks to Philipp Hancke, Justin Karneges, Evgeniy Khramtsov, and Unnikrishnan Vikrama Panicker for their feedback.</p>
</section1> </section1>
</xep> </xep>

View File

@ -606,6 +606,7 @@ THE SOFTWARE.
<!ENTITY rfc5576 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5576'>RFC 5576</link></span> <note>RFC 5576: Source-Specific Media Attributes in the Session Description Protocol (SDP) &lt;<link url='http://tools.ietf.org/html/rfc5576'>http://tools.ietf.org/html/rfc5576</link>&gt;.</note>" > <!ENTITY rfc5576 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5576'>RFC 5576</link></span> <note>RFC 5576: Source-Specific Media Attributes in the Session Description Protocol (SDP) &lt;<link url='http://tools.ietf.org/html/rfc5576'>http://tools.ietf.org/html/rfc5576</link>&gt;.</note>" >
<!ENTITY rfc5646 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5646'>RFC 5646</link></span> <note>RFC 5646: Tags for Identifying Languages &lt;<link url='http://tools.ietf.org/html/rfc5646'>http://tools.ietf.org/html/rfc5646</link>&gt;.</note>" > <!ENTITY rfc5646 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5646'>RFC 5646</link></span> <note>RFC 5646: Tags for Identifying Languages &lt;<link url='http://tools.ietf.org/html/rfc5646'>http://tools.ietf.org/html/rfc5646</link>&gt;.</note>" >
<!ENTITY rfc5763 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5763'>RFC 5763</link></span> <note>RFC 5763: Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS) &lt;<link url='http://tools.ietf.org/html/rfc5763'>http://tools.ietf.org/html/rfc5763</link>&gt;.</note>" > <!ENTITY rfc5763 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5763'>RFC 5763</link></span> <note>RFC 5763: Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS) &lt;<link url='http://tools.ietf.org/html/rfc5763'>http://tools.ietf.org/html/rfc5763</link>&gt;.</note>" >
<!ENTITY rfc5766 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5766'>RFC 5766</link></span> <note>RFC 5766: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) &lt;<link url='http://tools.ietf.org/html/rfc5766'>http://tools.ietf.org/html/rfc5766</link>&gt;.</note>" >
<!ENTITY rfc5802 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5802'>RFC 5802</link></span> <note>RFC 5802: Salted Challenge Response Authentication Mechanism (SCRAM) SASL and GSS-API Mechanisms &lt;<link url='http://tools.ietf.org/html/rfc5802'>http://tools.ietf.org/html/rfc5802</link>&gt;.</note>" > <!ENTITY rfc5802 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5802'>RFC 5802</link></span> <note>RFC 5802: Salted Challenge Response Authentication Mechanism (SCRAM) SASL and GSS-API Mechanisms &lt;<link url='http://tools.ietf.org/html/rfc5802'>http://tools.ietf.org/html/rfc5802</link>&gt;.</note>" >
<!ENTITY rfc5888 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5888'>RFC 5888</link></span> <note>RFC 5888: The Session Description Protocol (SDP) Grouping Framework &lt;<link url='http://tools.ietf.org/html/rfc5888'>http://tools.ietf.org/html/rfc5888</link>&gt;.</note>" > <!ENTITY rfc5888 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5888'>RFC 5888</link></span> <note>RFC 5888: The Session Description Protocol (SDP) Grouping Framework &lt;<link url='http://tools.ietf.org/html/rfc5888'>http://tools.ietf.org/html/rfc5888</link>&gt;.</note>" >
<!ENTITY rfc5952 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5952'>RFC 5952</link></span> <note>RFC 5952: A Recommendation for IPv6 Address Text Representation &lt;<link url='http://tools.ietf.org/html/rfc5952'>http://tools.ietf.org/html/rfc5952</link>&gt;.</note>" > <!ENTITY rfc5952 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5952'>RFC 5952</link></span> <note>RFC 5952: A Recommendation for IPv6 Address Text Representation &lt;<link url='http://tools.ietf.org/html/rfc5952'>http://tools.ietf.org/html/rfc5952</link>&gt;.</note>" >
@ -670,6 +671,7 @@ THE SOFTWARE.
<!ENTITY stoxcore "<span class='ref'><strong><link url='http://tools.ietf.org/html/draft-ietf-stox-core'>draft-ietf-stox-core</link></strong></span> <note>Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Addresses and Error Conditions &lt;<link url='http://tools.ietf.org/html/draft-ietf-stox-core'>http://tools.ietf.org/html/draft-ietf-stox-core</link>&gt;.</note>" > <!ENTITY stoxcore "<span class='ref'><strong><link url='http://tools.ietf.org/html/draft-ietf-stox-core'>draft-ietf-stox-core</link></strong></span> <note>Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Addresses and Error Conditions &lt;<link url='http://tools.ietf.org/html/draft-ietf-stox-core'>http://tools.ietf.org/html/draft-ietf-stox-core</link>&gt;.</note>" >
<!ENTITY tcprobust "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-tcpm-tcpsecure'>Improving TCP's Robustness to Blind In-Window Attacks</link></span> <note>Improving TCP's Robustness to Blind In-Window Attacks &lt;<link url='http://tools.ietf.org/html/draft-ietf-tcpm-tcpsecure'>http://tools.ietf.org/html/draft-ietf-tcpm-tcpsecure</link>&gt;. Work in progress.</note>" > <!ENTITY tcprobust "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-tcpm-tcpsecure'>Improving TCP's Robustness to Blind In-Window Attacks</link></span> <note>Improving TCP's Robustness to Blind In-Window Attacks &lt;<link url='http://tools.ietf.org/html/draft-ietf-tcpm-tcpsecure'>http://tools.ietf.org/html/draft-ietf-tcpm-tcpsecure</link>&gt;. Work in progress.</note>" >
<!ENTITY turn "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-behave-turn'>TURN</link></span> <note>Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) &lt;<link url='http://tools.ietf.org/html/draft-ietf-behave-turn'>http://tools.ietf.org/html/draft-ietf-behave-turn</link>&gt;. Work in progress.</note>" > <!ENTITY turn "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-behave-turn'>TURN</link></span> <note>Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) &lt;<link url='http://tools.ietf.org/html/draft-ietf-behave-turn'>http://tools.ietf.org/html/draft-ietf-behave-turn</link>&gt;. Work in progress.</note>" >
<!ENTITY turn-rest "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-rtcweb-turn-rest'>A REST API for Access to TURN Services</link></span> <note>A REST API For Access To TURN Services &lt;<link url='http://tools.ietf.org/html/draft-ietf-rtcweb-turn-rest'>http://tools.ietf.org/html/draft-ietf-rtcweb-turn-rest</link>&gt;. Work in progress.</note>" >
<!ENTITY xmppoverwebsocket "<span class='ref'><link url='https://datatracker.ietf.org/doc/draft-ietf-xmpp-websocket/'>XMPP Over WebSocket</link></span> <note>An XMPP Sub-protocol for WebSocket &lt;<link url='https://datatracker.ietf.org/doc/draft-ietf-xmpp-websocket/'>https://datatracker.ietf.org/doc/draft-ietf-xmpp-websocket/</link>&gt;. Work in progress.</note>" > <!ENTITY xmppoverwebsocket "<span class='ref'><link url='https://datatracker.ietf.org/doc/draft-ietf-xmpp-websocket/'>XMPP Over WebSocket</link></span> <note>An XMPP Sub-protocol for WebSocket &lt;<link url='https://datatracker.ietf.org/doc/draft-ietf-xmpp-websocket/'>https://datatracker.ietf.org/doc/draft-ietf-xmpp-websocket/</link>&gt;. Work in progress.</note>" >
<!ENTITY bundle "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation/'>Multiplexing Negotiation Using Session Description Protocol (SDP) Port Numbers</link></span> <note>Multiplexing Negotiation Using Session Description Protocol (SDP) Port Numbers &lt;<link url='http://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation/'>http://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation/</link>&gt;. Work in progress.</note>" > <!ENTITY bundle "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation/'>Multiplexing Negotiation Using Session Description Protocol (SDP) Port Numbers</link></span> <note>Multiplexing Negotiation Using Session Description Protocol (SDP) Port Numbers &lt;<link url='http://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation/'>http://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation/</link>&gt;. Work in progress.</note>" >