moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 23:28:51 -05:00
Code Issues Releases Wiki Activity

0.6

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1204 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-09-06 02:21:46 +00:00
parent c6b7d2c337
commit 28b99fc69f
1 changed files with 43 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
xep-0186.xml
View File

@ -18,10 +18,19 @@
<spec>XMPP IM</spec>
<spec>XEP-0030</spec>
</dependencies>
<supersedes>None</supersedes>
<supersedes>
<spec>XEP-0018</spec>
<spec>XEP-0126</spec>
</supersedes>
<supersededby>None</supersededby>
<shortname>NOT YET ASSIGNED</shortname>
&stpeter;
<revision>
<version>0.6</version>
<date>2007-09-05</date>
<initials>psa</initials>
<remark><p>Clarified that this specification is intended to supersede XEP-0018 and XEP-0126; added several additional examples.</p></remark>
</revision>
<revision>
<version>0.5</version>
<date>2007-01-30</date>
@ -71,7 +80,7 @@
<li><p>&xep0018; -- this protocol is not compatible with &xmppcore; and &xmppim;, and the speciifcation does not provide reliable documentation of the protocol in use since many server implementations support presence of type "invisible" but not presence of type "visible".</p></li>
<li><p>&xep0126; -- this protocol is in many ways a mis-use of privacy lists for the temporary purpose of appearing invisible rather than the intended purpose of permanently blocking communications.</p></li>
</ul>
<p>In order to provide a standards-compliant protocol that can be used in the long term, this document defines an IQ-based protocol that enables an IM user to "go invisible" and "go visible" at will within the context of a given session.</p>
<p>In order to provide a standards-compliant protocol that can be used in the long term, this document defines an IQ-based protocol that enables an IM user to become "invisible" and "visible" at will within the context of a given session. This protocol is intended to supersede the protocols described in <cite>XEP-0018</cite> and <cite>XEP-0126</cite>.</p>
</section1>
<section1 topic='Requirements' anchor='req'>
<p>The requirements for invisible mode are straightforward:</p>
@ -85,13 +94,19 @@
<section2 topic='Discovering Support' anchor='disco'>
<p>In order for a client to discover whether its server supports the protocol defined herein, it MUST send a &xep0030; information request to the server:</p>
<example caption='Service discovery request'><![CDATA[
<iq from='bilbo@tolkien.lit/shire' to='tolkien.lit' type='get' id='disco1'>
<iq from='bilbo@tolkien.lit/shire'
id='disco1'
to='tolkien.lit'
type='get'>
<query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>
]]></example>
<p>If the server supports the protocol defined herein, it MUST return a feature of "http://www.xmpp.org/extensions/xep-0186.html#ns":</p>
<p>If the server supports the protocol defined herein, it MUST return a feature of "http://www.xmpp.org/extensions/xep-0186.html#ns" &NSNOTE;.</p>
<example caption='Service discovery response'><![CDATA[
<iq from='bilbo@tolkien.lit/shire' to='tolkien.lit' type='get' id='disco1'>
<iq from='bilbo@tolkien.lit/shire'
id='disco1'
to='tolkien.lit'
type='get'>
<query xmlns='http://jabber.org/protocol/disco#info'>
...
<feature var='http://www.xmpp.org/extensions/xep-0186.html#ns'/>
@ -102,18 +117,22 @@
<p>A client SHOULD complete this service discovery process before sending initial presence to its server.</p>
</section2>
<section2 topic='User Becomes Invisible' anchor='invisible'>
<p>In order for a client to go invisible, it shall send an IQ-set with no 'to' address (thus handled by the user's server) containing an &lt;invisible/&gt; element qualified by the 'http://www.xmpp.org/extensions/xep-0186.html#ns' namespace:</p>
<p>In order for a client to go invisible, it shall send an IQ-set with no 'to' address (thus handled by the user's server) containing an &lt;invisible/&gt; element qualified by the 'http://www.xmpp.org/extensions/xep-0186.html#ns' namespace &NSNOTE;.</p>
<example caption='Invisible command'><![CDATA[
<iq type='set' id='inv1'>
<iq from='bilbo@tolkien.lit/shire'
id='inv1'
type='set'>
<invisible xmlns='http://www.xmpp.org/extensions/xep-0186.html#ns'/>
</iq>
]]></example>
<p>If the server can successfully process the invisibility command, it MUST return an IQ-result:</p>
<p>If the server can successfully process the invisibility command, it MUST return an IQ-result.</p>
<example caption='Invisible command is successful'><![CDATA[
<iq type='result' id='inv1'/>
<iq to='bilbo@tolkien.lit/shire'
id='inv1'
type='result'/>
]]></example>
<p>(Standard XMPP stanza errors apply; see <cite>RFC 3920</cite> and &xep0086;.)</p>
<p>If the client enters invisible mode after having previously sent undirected presence with no 'type' attribute (e.g., after sending initial presence), the server MUST send &UNAVAILABLE; presence from the client's resource to all contacts who would receive unavailable presence if the client sent &UNAVAILABLE;.</p>
<p>If the client enters invisible mode after having previously sent undirected presence with no 'type' attribute (e.g., after sending initial presence), the server MUST send &UNAVAILABLE; presence from the specified resource to all contacts who would receive unavailable presence if the client sent &UNAVAILABLE;.</p>
<p>While the client is in invisible mode, the server:</p>
<ol start='1'>
<li><p>MUST NOT broadcast presence notifications as a result of receiving any subsequent undirected presence notifications from the client.</p></li>
@ -126,17 +145,26 @@
<p>If after sending directed presence the client then sends &UNAVAILABLE;, the server MUST deliver that unavailable presence only to the entities to which the client sent directed presence after going invisible.</p>
</section2>
<section2 topic='User Becomes Visible' anchor='visible'>
<p>In order for a client to become visible again, it shall send an IQ-set with no 'to' address (thus handled by the user's server) containing a &lt;visible/&gt; element qualified by the 'http://www.xmpp.org/extensions/xep-0186.html#ns' namespace:</p>
<p>In order for a client to become visible again, it shall send an IQ-set with no 'to' address (thus handled by the user's server) containing a &lt;visible/&gt; element qualified by the 'http://www.xmpp.org/extensions/xep-0186.html#ns' namespace &NSNOTE;.</p>
<example caption='Visible command'><![CDATA[
<iq type='set' id='vis1'>
<iq from='bilbo@tolkien.lit/shire'
id='vis1'
type='set'>
<visible xmlns='http://www.xmpp.org/extensions/xep-0186.html#ns'/>
</iq>
]]></example>
<p>If the server can successfully process the visibility command, it MUST return an IQ-result:</p>
<p>If the server can successfully process the visibility command, it MUST return an IQ-result.</p>
<example caption='Visible command is successful'><![CDATA[
<iq type='result' id='vis1'/>
<iq to='bilbo@tolkien.lit/shire'
id='vis1'
type='result'/>
]]></example>
<p>When the client becomes visible, the server MUST treat that state as equivalent to an active session before receiving initial presence from the client. It is the responsibility of the client to send an undirected presence notification to the server, which the server MUST broadcast to all entities who would normally receive presence broadcasts from the client (as well as any other entities to which the client sent directed presence while invisible).</p>
<p>When the client becomes visible, the server MUST treat that state as equivalent to an active session before receiving initial presence from the client.</p>
<p>It is the responsibility of the client to send an undirected presence notification to the server.</p>
<example caption='Client sends presence'><![CDATA[
<presence from='bilbo@tolkien.lit/shire'/>
]]></example>
<p>The server then MUST broadcast that presence to all entities who would normally receive presence broadcasts from the client (as well as any other entities to which the client sent directed presence while invisible).</p>
</section2>
</section1>
<section1 topic='Security Considerations' anchor='security'>