1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-10-31 15:35:07 -04:00
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@842 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-05-16 22:35:41 +00:00
parent d8e341eb93
commit 5a603999e0
2 changed files with 4 additions and 4 deletions

View File

@ -10,7 +10,7 @@
<abstract>This document defines a DNS TXT Resource Record format for use in discovering alternative methods of connecting to an XMPP server.</abstract> <abstract>This document defines a DNS TXT Resource Record format for use in discovering alternative methods of connecting to an XMPP server.</abstract>
&LEGALNOTICE; &LEGALNOTICE;
<number>0156</number> <number>0156</number>
<status>Experimental</status> <status>Proposed</status>
<type>Standards Track</type> <type>Standards Track</type>
<sig>Standards</sig> <sig>Standards</sig>
<approver>Council</approver> <approver>Council</approver>

View File

@ -10,7 +10,7 @@
<abstract>This document defines an XMPP protocol extension for sending pings over XML streams.</abstract> <abstract>This document defines an XMPP protocol extension for sending pings over XML streams.</abstract>
&LEGALNOTICE; &LEGALNOTICE;
<number>0199</number> <number>0199</number>
<status>Experimental</status> <status>Proposed</status>
<type>Standards Track</type> <type>Standards Track</type>
<sig>Standards</sig> <sig>Standards</sig>
<approver>Council</approver> <approver>Council</approver>
@ -55,7 +55,7 @@
<p>The XMPP ping protocol is extremely simple:</p> <p>The XMPP ping protocol is extremely simple:</p>
<ol> <ol>
<li>The pinging entity sends an IQ-get containing a &lt;ping/&gt; element qualified by the 'http://www.xmpp.org/extensions/xep-0199.html#ns' namespace &NSNOTE;.</li> <li>The pinging entity sends an IQ-get containing a &lt;ping/&gt; element qualified by the 'http://www.xmpp.org/extensions/xep-0199.html#ns' namespace &NSNOTE;.</li>
<li>The pinged entity returns either an IQ-result (if it supports the namespace) or an IQ-error (if it does not). <note>The pinged entity MAY ignore the IQ (i.e., return neither a result nor an error) if doing so would reveal its presence information to an entity that is not authorized to view that information; this mainly applies to client-to-client pings.</note></li> <li>The pinged entity returns either an IQ-result (if it supports the namespace) or an IQ-error (if it does not). (See the <link url='#security'>Security Considerations</link> regarding leaks of presence information in the context of pings sent to clients.)</li>
</ol> </ol>
</section1> </section1>
<section1 topic='Use Cases' anchor='usecases'> <section1 topic='Use Cases' anchor='usecases'>
@ -214,7 +214,7 @@
]]></example> ]]></example>
</section1> </section1>
<section1 topic='Security Considerations' anchor='security'> <section1 topic='Security Considerations' anchor='security'>
<p>A pinged entity MAY ignore the IQ (i.e., return neither a result nor an error) if doing so would reveal its presence information to an entity that is not authorized to view that information; this mainly applies to client-to-client pings.</p> <p>A pinged entity MAY ignore the IQ (i.e., return neither a result nor an error) if doing so would reveal its presence (network availability) information to an entity that is not authorized to view that information; this mainly applies to pings sent to clients (where the response would reveal client availability) but may apply to other entities as well.</p>
</section1> </section1>
<section1 topic='IANA Considerations' anchor='iana'> <section1 topic='IANA Considerations' anchor='iana'>