diff --git a/xep-0186.xml b/xep-0186.xml index 81d7805a..de88ddb3 100644 --- a/xep-0186.xml +++ b/xep-0186.xml @@ -7,11 +7,10 @@
Invisible Command - This document specifies an XMPP-compatible protocol for user invisibility. + This document specifies an XMPP protocol extension for user invisibility. &LEGALNOTICE; 0186 - Deferred - 2014-07-03 + Experimental Standards Track Standards @@ -25,6 +24,12 @@ invisible &stpeter; + + 0.12 + 2017-01-28 + psa +

Added method for specifying server behavior regarding presence probes via new 'probe' attribute; increased the protocol version number from 0 to 1.

 + 0.11 2012-06-27 @@ -106,12 +111,12 @@
-

Some XMPP-based instant messaging systems have long supported the ability for users to be online but to appear invisible. The existing protocols for doing so are:

+

Some XMPP-based instant messaging systems have long supported the ability for users to be online but to appear offline to other users. The existing protocols for this "invisibility" feature 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 protocol described in XEP-0018 and to provide a more client-friendly approach to invisibility than XEP-0126.

+

In order to provide a standards-compliant protocol extension 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.

 @@ -119,34 +124,44 @@
  1. A user can become visible or invisible at any time within an XMPP session.
  2. Invisible mode is active only for the current session; if the user ends that session and starts another session, the invisibility mode set for the previous session does not carry over to the new session.
    3. -
  3. When in invisible mode, a user can send directed presence to particular contacts.
    4. +
  4. When in invisible mode, a user can send messages and directed presence to particular contacts.
 -

In order for a client to go invisible, it sends an IQ-set with no 'to' address (thus handled by the user's server) containing an <invisible/> element qualified by the 'urn:xmpp:invisible:0' namespace &VNOTE;.

- In order for a client to go invisible, it sends an IQ-set with no 'to' address (thus handled by the user's server) containing an <invisible/> element qualified by the 'urn:xmpp:invisible:1' namespace &VNOTE;.

+

The <invisible/> element MUST include a 'probe' attribute, which specifies whether the server shall or shall not send presence probes to entities in the user's roster (thus determining whether the user does or does not automatically receive presence notifications from contacts). This attribute is a boolean &BOOLEANNOTE;, where a logical value of TRUE (lexical value of "true" or "1") indicates that the server shall send presence probes and where a logical value of FALSE (lexical value of "false" or "0") indicates that the server shall not send presence probes. The default logical value is FALSE.

+ - + ]]> -

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

+

Although the default value is false (thus protecting the user from leaking presence information), the client SHOULD always include the 'probe' attribute.

+ + + + ]]> +

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

]]>

(Standard XMPP stanza errors apply; see RFC 6120.)

-

When the client enters invisible mode in the midst of a presence session (i.e., after having previously sent undirected available presence with no 'type' attribute), the server MUST send &UNAVAILABLE; presence from the specified resource to all contacts who would receive unavailable presence if the client sent &UNAVAILABLE;.

-

The following sections define how the server and the client handling of inbound and outbound XML stanzas while the client is invisible.

+

When the client enters invisible mode during a presence session (i.e., after having previously sent undirected available presence with no 'type' attribute), the server MUST send &UNAVAILABLE; from the specified resource to all contacts who would receive unavailable presence if the client itself were to send &UNAVAILABLE;.

+

The following sections define server and client handling of inbound and outbound XML stanzas while the client is invisible.

While the client is in invisible mode, the server:

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

  2. MUST deliver outbound directed presence stanzas generated by the client.

    3. +

  3. MUST generate or not generate outbound presence probes in accordance with the value of the 'probe' attribute.

  4. MUST deliver inbound &PRESENCE; stanzas.

  5. SHOULD deliver inbound &MESSAGE; stanzas whose 'to' address is the bare JID &LOCALBARE; of the user (subject to standard XMPP stanza handling rules from RFC 6120 and RFC 6121).

  6. MUST deliver inbound &MESSAGE; and &IQ; stanzas whose 'to' address is the full JID &LOCALFULL; corresponding to the resource of the client.

    7. @@ -171,59 +186,59 @@ -

    In order for a client to become visible again, it sends an IQ-set with no 'to' address (thus handled by the user's server) containing a <visible/> element qualified by the 'urn:xmpp:invisible:0' namespace &VNOTE;.

    +

    In order for a client to become visible again, it sends an IQ-set with no 'to' address (thus handled by the user's server) containing a <visible/> element qualified by the 'urn:xmpp:invisible:1' namespace &VNOTE;.

    - + ]]>

    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, with one exception: if the client sent directed presence to any entities while in the invisible state, the server MUST treat those entities as under point 2 of Section 4.6.3 of RFC 6121 (i.e., the server MUST ensure that it sends unavailable presence to those entities if the client subsequently goes offline after becoming visible).

    -

    If the user wishes to then send presence to contacts, it is the responsibility of the client to send an undirected available presence notification to the server.

    - If the user wishes to then send presence to all contacts in the roster, it is the responsibility of the client to send an undirected available presence notification to the server.

    + ]]> -

    The server would then broadcast that presence notification to all entities who would normally receive presence broadcasts from the client (the server MAY also send that notification to any entities to which the client sent directed presence while invisible).

    +

    The server would then broadcast that presence notification to all entities who would normally receive presence broadcasts from the client (the server MAY also send that notification to any entities to which the client sent directed presence while invisible, whether or not they are in the user's roster).

    In order for a client to discover whether its server supports the invisible command, it sends a &xep0030; information request to the server:

    ]]> -

    If the server supports the invisible command, it MUST return a feature of "urn:xmpp:invisible:0" &VNOTE;.

    +

    If the server supports the invisible command, it MUST return a feature of "urn:xmpp:invisible:1" &VNOTE;.

    - + ]]> -

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

    +

    A client SHOULD complete this service discovery process before sending initial presence to its server (as specified in &xep0115;, a server can include entity capabilities information in a stream feature, which obviates the need for explicit service discovery as shown above).

     -

    A server MAY use the same backend data store for this invisibility mode as for &xep0016; when 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.

    +

    A server MAY use the same data backend for this invisibility mode as for privacy lists when employed for invisibility (see XEP-0126). If so, the server MUST update the relevant privacy lists on behalf of the user when the client sends an invisible command or a visible command as specified herein.

     -

    No matter how it is implemented, invisibility can be defeated and presence leaks can occur without careful stanza handling on the part of the server and the client. Use of the protocol defined here does not guarantee that presence leaks will not occur, either technically or socially (e.g., if the user reveals his presence to one contact but not another and those contacts are in communication).

    +

    No matter how it is implemented, invisibility can be defeated and presence leaks can occur without careful stanza handling on the part of the server and the client. Use of the protocol defined here does not necessarily prevent presence leaks, either technically or socially (e.g., if the user reveals his presence to one contact but not another and those contacts are in communication).

     @@ -234,7 +249,7 @@

    This specification defines the following XML namespace:

      -
    • urn:xmpp:invisible:0
      • +
    • urn:xmpp:invisible:1

    Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.

     @@ -249,11 +264,22 @@ - + + + + + + + + +