1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-28 04:02:20 -05:00

Support OTRv3 only and remove feature subelements

This commit is contained in:
Sam Whited 2015-08-30 11:05:33 -05:00 committed by Matthew A. Miller
parent 81cefd2e88
commit 50e058ee03

View File

@ -61,18 +61,24 @@
<p> <p>
If an entity supports OTR it MUST advertise the fact by returning a If an entity supports OTR it MUST advertise the fact by returning a
feature of 'urn:xmpp:otr:0' &VNOTE; in response to a &xep0030; feature of 'urn:xmpp:otr:0' &VNOTE; in response to a &xep0030;
information request. It MUST also include '&lt;version&gt;' elements for information request. This indicates support for OTRv3 as defined by
each version of the OTR protocol that is supported. Eg. an entity which <i><link url='https://otr.cypherpunks.ca/Protocol-v3-4.0.0.html'>
supports OTR versions 2 and 3 might include the following feature in its Off-the-Record Messaging Protocol version 3
disco info list: </link></i>
<note>
(Accessed 2015-08-30). "Off-the-Record Messaging Protocol version 3"
&lt;<link url='https://otr.cypherpunks.ca/Protocol-v3-4.0.0.html'>
https://otr.cypherpunks.ca/Protocol-v3-4.0.0.html
</link>&gt;
</note>.
<example caption='Disco response'><![CDATA[ <example caption='Disco response'><![CDATA[
<feature var='urn:xmpp:otr:0'> <feature var='urn:xmpp:otr:0' />
<version>2</version>
<version>3</version>
</feature>
]]></example> ]]></example>
</p> </p>
<p>
If older versions of OTR are required, they may be discovered out of band
using OTRs built in mechanism which is beyond the scope of this document.
</p>
</section1> </section1>
<section1 topic='Security Considerations' anchor='security'> <section1 topic='Security Considerations' anchor='security'>
<p> <p>