mirror of
https://github.com/moparisthebest/xeps
synced 2024-12-25 09:08:52 -05:00
correction per XEP-0115
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1751 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
parent
862556a43a
commit
4dedac3045
15
xep-0174.xml
15
xep-0174.xml
@ -181,7 +181,6 @@ juliet IN TXT "os=PPC Mac OS X Mach-O"
|
||||
juliet IN TXT "phsh=a3839614e1a382bcfebbcf20464f519e81770813"
|
||||
juliet IN TXT "port.p2pj=5562"
|
||||
juliet IN TXT "status=avail"
|
||||
juliet IN TXT "v=1.1.4"
|
||||
juliet IN TXT "vc=CA!"
|
||||
juliet IN TXT "ver=66/0NaeaBKkwk85efJTGmU47vXI="
|
||||
]]></code>
|
||||
@ -291,7 +290,6 @@ _presence._tcp <ttl> SRV <priority> <weight> port-number machine-name.local.
|
||||
<owner> IN <ttl> TXT "phsh=sha1-hash-of-avatar"
|
||||
<owner> IN <ttl> TXT "port.p2pj=5562"
|
||||
<owner> IN <ttl> TXT "status=avail-away-or-dnd"
|
||||
<owner> IN <ttl> TXT "v=entity-capabilities-software-version"
|
||||
<owner> IN <ttl> TXT "vc=capabilities-string"
|
||||
<owner> IN <ttl> TXT "ver=entity-capabilities-identity"
|
||||
]]></code>
|
||||
@ -321,7 +319,6 @@ juliet IN TXT "os=PPC Mac OS X Mach-O"
|
||||
juliet IN TXT "phsh=a3839614e1a382bcfebbcf20464f519e81770813"
|
||||
juliet IN TXT "port.p2pj=5562"
|
||||
juliet IN TXT "status=avail"
|
||||
juliet IN TXT "v=1.1.4"
|
||||
juliet IN TXT "vc=CA!"
|
||||
juliet IN TXT "ver=66/0NaeaBKkwk85efJTGmU47vXI="
|
||||
|
||||
@ -346,7 +343,7 @@ juliet IN TXT "ver=66/0NaeaBKkwk85efJTGmU47vXI="
|
||||
</section1>
|
||||
|
||||
<section1 topic='Discovering Capabilities' anchor='caps'>
|
||||
<p>Because serverless communication does not involve the exchange of XMPP presence, it is not possible to use &xep0115; for capabilities discovery. Therefore, it is RECOMMENDED to instead include the node, hash, and ver TXT records (and OPTIONAL to include the ext and v TXT records). The values of these records MUST be the same as the values for the 'node', 'hash', 'ver', 'ext', 'n', 'os', and 'v' attributes that are advertised for the application in normal XMPP presence (if any) via the Entity Capabilities protocol as described in <cite>XEP-0115</cite>.</p>
|
||||
<p>Because serverless communication does not involve the exchange of XMPP presence, it is not possible to use &xep0115; for capabilities discovery. Therefore, it is RECOMMENDED to instead include the node, hash, and ver TXT records (and OPTIONAL to include the ext TXT record). The values of these records MUST be the same as the values for the 'node', 'hash', 'ver', and 'ext' attributes that are advertised for the application in normal XMPP presence (if any) via the Entity Capabilities protocol as described in <cite>XEP-0115</cite>.</p>
|
||||
</section1>
|
||||
|
||||
<section1 topic='Initiating a Messaging Session' anchor='initiate'>
|
||||
@ -650,16 +647,6 @@ _presence._tcp.local. IN NULL raw-binary-data-here
|
||||
<status>deprecated</status>
|
||||
</record>
|
||||
|
||||
<record>
|
||||
<name>v</name>
|
||||
<desc>
|
||||
The application version; the value of this record MUST be the same
|
||||
as that provided via normal XMPP presence (if applicable) in the 'v'
|
||||
attribute specified in Entity Capabilities (XEP-0115).
|
||||
</desc>
|
||||
<status>optional</status>
|
||||
</record>
|
||||
|
||||
<record>
|
||||
<name>vc</name>
|
||||
<desc>
|
||||
|
Loading…
Reference in New Issue
Block a user