1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-10 11:25:00 -05:00

XEP-0260: Fix broken ICE-TCP ref

This commit is contained in:
Sam Whited 2016-05-17 09:09:49 -05:00
parent 45960060ed
commit b92a2b7a23

View File

@ -36,6 +36,12 @@
<email>klaus.hartke@googlemail.com</email> <email>klaus.hartke@googlemail.com</email>
<jid>nx@jabber.org</jid> <jid>nx@jabber.org</jid>
</author> </author>
<revision>
<version>1.0.1</version>
<date>2016-05-17</date>
<initials>ssw</initials>
<remark><p>Fix broken ICE-TCP reference.</p></remark>
</revision>
<revision> <revision>
<version>1.0</version> <version>1.0</version>
<date>2011-09-23</date> <date>2011-09-23</date>
@ -459,7 +465,7 @@ priority = (2^16)*(type preference) + (local preference)
</section1> </section1>
<section1 topic='Fallback Methods' anchor='fallback'> <section1 topic='Fallback Methods' anchor='fallback'>
<p>If the SOCKS5 Bytestreams negotiation fails, the parties might want to "fall back" to another transport. Currently the transport of last resort for a streaming exchange is &xep0047; as described for Jingle in &xep0261;, however if other transport methods are defined in the future (e.g. &ice-tcp;) then clients could fall back to those methods instead of IBB. The protocol flow for fallback from S5B to IBB is as follows.</p> <p>If the SOCKS5 Bytestreams negotiation fails, the parties might want to "fall back" to another transport. Currently the transport of last resort for a streaming exchange is &xep0047; as described for Jingle in &xep0261;, however if other transport methods are defined in the future (e.g. &rfc6544;) then clients could fall back to those methods instead of IBB. The protocol flow for fallback from S5B to IBB is as follows.</p>
<code><![CDATA[ <code><![CDATA[
Romeo Juliet Romeo Juliet
| | | |