moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-24 10:12:19 -05:00
Code Issues Releases Wiki Activity

0.8

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1843 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2008-05-13 02:31:01 +00:00
parent 6782945240
commit de1c5cd36f
1 changed files with 26 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
xep-0186.xml
View File

@ -20,11 +20,16 @@
</dependencies>
<supersedes>
<spec>XEP-0018</spec>
<spec>XEP-0126</spec>
</supersedes>
<supersededby>None</supersededby>
<shortname>NOT YET ASSIGNED</shortname>
&stpeter;
<revision>
<version>0.7</version>
<date>2008-05-12</date>
<initials>psa</initials>
<remark><p>Added note about integration with privacy lists; removed XEP-0126 from list of protocols that this specification supersedes; changed temporary namespace to conform to XMPP Registrar procedures; copied several security considerations from XEP-0126.</p></remark>
</revision>
<revision>
<version>0.6</version>
<date>2007-09-05</date>
@ -78,9 +83,9 @@
<p>Some instant messaging implementations of the Jabber/XMPP protocols have long supported the ability for IM users to be online but appear invisible. The existing protocols for doing so are:</p>
<ul>
<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>
<li><p>&xep0126; -- this protocol is a somewhat complicated use of &xep0016; for the temporary purpose of appearing invisible rather than the intended purpose of permanently blocking communications; however, the invisible command defined herein can provide a client-friendly interface to the same data store used for privacy lists.</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 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>
<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 protocol described in <cite>XEP-0018</cite> and provide a more client-friendly approach to invisibility than <cite>XEP-0126</cite>.</p>
</section1>
<section1 topic='Requirements' anchor='req'>
<p>The requirements for invisible mode are straightforward:</p>
@ -101,7 +106,7 @@
<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" &NSNOTE;.</p>
<p>If the server supports the protocol defined herein, it MUST return a feature of "urn:xmpp:tmp:invisible" &NSNOTE;.</p>
<example caption='Service discovery response'><![CDATA[
<iq from='bilbo@tolkien.lit/shire'
id='disco1'
@ -109,7 +114,7 @@
type='get'>
<query xmlns='http://jabber.org/protocol/disco#info'>
...
<feature var='http://www.xmpp.org/extensions/xep-0186.html#ns'/>
<feature var='urn:xmpp:tmp:invisible'/>
...
</query>
</iq>
@ -117,12 +122,12 @@
<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 &NSNOTE;.</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 'urn:xmpp:tmp:invisible' namespace &NSNOTE;.</p>
<example caption='Invisible command'><![CDATA[
<iq from='bilbo@tolkien.lit/shire'
id='inv1'
type='set'>
<invisible xmlns='http://www.xmpp.org/extensions/xep-0186.html#ns'/>
<invisible xmlns='urn:xmpp:tmp:invisible'/>
</iq>
]]></example>
<p>If the server can successfully process the invisibility command, it MUST return an IQ-result.</p>
@ -145,12 +150,12 @@
<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 &NSNOTE;.</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 'urn:xmpp:tmp:invisible' namespace &NSNOTE;.</p>
<example caption='Visible command'><![CDATA[
<iq from='bilbo@tolkien.lit/shire'
id='vis1'
type='set'>
<visible xmlns='http://www.xmpp.org/extensions/xep-0186.html#ns'/>
<visible xmlns='urn:xmpp:tmp:invisible'/>
</iq>
]]></example>
<p>If the server can successfully process the visibility command, it MUST return an IQ-result.</p>
@ -167,15 +172,23 @@
<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='Integration With Privacy Lists' anchor='priv'>
<p>A server MAY use the same backend data store for invisibility mode as defined herein and &xep0016; as used for invisibility (see <cite>XEP-0126</cite>). If so, the server MUST update the relevant privacy lists on behalf of the user when the client requests initiation or termination of invisible mode.</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>It is possible to leak presence while in invisible mode (for example, by sending a message, IQ, or presence stanza to a contact). A client SHOULD warn a user before allowing the client to generate any outbound traffic and MUST NOT respond to IQ requests received from entities with which it has not initiated communications while in invisible mode (e.g., by sending messages, IQs, or directed presence).</p>
<p>It is important to recognize that invisibility can be defeated without the use of privacy lists, intelligent stanza handling by the server, and an awareness of context on the part of a client. For example:</p>
<ul>
<li>If a user attempts to send a message, IQ, or presence stanza to a contact, the user may inadvertently leak his or her presence; therefore the client SHOULD warn the user before allowing the user to generate any outbound traffic, including "is-composing" events as defined in &xep0085;.</li>
<li>If a user usually logs in as the same resource (e.g., "Home"), a contact can send an IQ request to that resource's full JID using &xep0012;, &xep0030;, &xep0090;, or &xep0092; and receive a reply, thus providing information that reveals the user's availability.</li>
<li>If a contact sends a <cite>Last Activity</cite> request to the user's bare JID, the user's server normally would reveal information about the user's availability; however, while the user is in invisible mode the server MUST return a &unavailable; error to such contacts.</li>
</ul>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>
<p>No interaction with &IANA; is required as a result of this document.</p>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='ns'>
<p>Until this specification advances to a status of Draft, its associated namespace shall be "http://www.xmpp.org/extensions/xep-0186.html#ns"; upon advancement of this specification, the &REGISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>Until this specification advances to a status of Draft, its associated namespace shall be "urn:xmpp:tmp:invisible"; upon advancement of this specification, the &REGISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;. The namespace "urn:xmpp:invisible" is requested, and is thought to be unique.</p>
</section2>
</section1>
<section1 topic='XML Schema' anchor='schema'>
@ -184,8 +197,8 @@
<xs:schema
xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='http://www.xmpp.org/extensions/xep-0186.html#ns'
xmlns='http://www.xmpp.org/extensions/xep-0186.html#ns'
targetNamespace='urn:xmpp:tmp:invisible'
xmlns='urn:xmpp:tmp:invisible'
elementFormDefault='qualified'>
<xs:element name='invisible' type='empty'/>