From 28b99fc69f0e96f243fcc1be9b92c40e0e64530c Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Thu, 6 Sep 2007 02:21:46 +0000 Subject: [PATCH] 0.6 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1204 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0186.xml | 58 ++++++++++++++++++++++++++++++++++++++-------------- 1 file changed, 43 insertions(+), 15 deletions(-) diff --git a/xep-0186.xml b/xep-0186.xml index 2e34cc32..9810b7e5 100644 --- a/xep-0186.xml +++ b/xep-0186.xml @@ -18,10 +18,19 @@ XMPP IM XEP-0030 - None + + XEP-0018 + XEP-0126 + None NOT YET ASSIGNED &stpeter; + + 0.6 + 2007-09-05 + psa +

Clarified that this specification is intended to supersede XEP-0018 and XEP-0126; added several additional examples.

 + 0.5 2007-01-30 @@ -71,7 +80,7 @@

  • &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".

  • &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.

    • -

    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.

    +

    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.

    The requirements for invisible mode are straightforward:

    @@ -85,13 +94,19 @@

    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:

    + ]]> -

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

    +

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

    + ... @@ -102,18 +117,22 @@

    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:

    +

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

    + ]]> -

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

    +

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

    + ]]>

    (Standard XMPP stanza errors apply; see RFC 3920 and &xep0086;.)

    -

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

    +

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

    While the client is in invisible mode, the server:

    1. MUST NOT broadcast presence notifications as a result of receiving any subsequent undirected presence notifications from the client.

      2. @@ -126,17 +145,26 @@

      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:

      +

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

      + ]]> -

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

      +

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

      + ]]> -

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

      +

      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.

      + + ]]> +

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