From de1c5cd36f7948350613658b191652f8180b6a11 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 13 May 2008 02:31:01 +0000 Subject: [PATCH] 0.8 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1843 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0186.xml | 39 ++++++++++++++++++++++++++------------- 1 file changed, 26 insertions(+), 13 deletions(-) diff --git a/xep-0186.xml b/xep-0186.xml index 9fff3553..66d43153 100644 --- a/xep-0186.xml +++ b/xep-0186.xml @@ -20,11 +20,16 @@ XEP-0018 - XEP-0126 None NOT YET ASSIGNED &stpeter; + + 0.7 + 2008-05-12 + psa +

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.

 + 0.6 2007-09-05 @@ -78,9 +83,9 @@

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:

-

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 XEP-0018 and XEP-0126.

+

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 XEP-0018 and provide a more client-friendly approach to invisibility than XEP-0126.

The requirements for invisible mode are straightforward:

@@ -101,7 +106,7 @@ ]]> -

If the server supports the protocol defined herein, it MUST return a feature of "http://www.xmpp.org/extensions/xep-0186.html#ns" &NSNOTE;.

+

If the server supports the protocol defined herein, it MUST return a feature of "urn:xmpp:tmp:invisible" &NSNOTE;.

... - + ... @@ -117,12 +122,12 @@

A client SHOULD complete this service discovery process before sending initial presence to its server.

-

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 <invisible/> element qualified by the 'http://www.xmpp.org/extensions/xep-0186.html#ns' namespace &NSNOTE;.

+

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 <invisible/> element qualified by the 'urn:xmpp:tmp:invisible' namespace &NSNOTE;.

- + ]]>

If the server can successfully process the invisibility command, it MUST return an IQ-result.

@@ -145,12 +150,12 @@

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.

 -

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 <visible/> element qualified by the 'http://www.xmpp.org/extensions/xep-0186.html#ns' namespace &NSNOTE;.

+

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 <visible/> element qualified by the 'urn:xmpp:tmp:invisible' namespace &NSNOTE;.

- + ]]>

If the server can successfully process the visibility command, it MUST return an IQ-result.

@@ -167,15 +172,23 @@

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).

 + +

A server MAY use the same backend data store for invisibility mode as defined herein and &xep0016; as used for invisibility (see XEP-0126). 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.

+ -

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).

+

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:

+
    +
  • 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;.
    • +
  • 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.
    • +
  • If a contact sends a Last Activity 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.
    • +

No interaction with &IANA; is required as a result of this document.

 -

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 ®ISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.

+

Until this specification advances to a status of Draft, its associated namespace shall be "urn:xmpp:tmp:invisible"; upon advancement of this specification, the ®ISTRAR; 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.

 @@ -184,8 +197,8 @@