Privacy lists

1. Introduction

Almost all types of Instant Messaging (IM) applications have found it necessary to develop some method for a user to block the receipt of messages and packets from other users (the rationale for such blockage depends on the needs of the individual user). This document defines a flexible method for communications blocking.

Pratiquement toutes les types d'applications de Messagerie Instantanée (IM) ont eu la nécessité de développer des méthodes pour qu'un utilisateur puisse bloquer la réception de messages et paquets d'autres utilisaetgurs (la raison d'un tel "filtrage" dépend des besoins de l'utilisateur individuel).

Note: The protocol specified herein MAY be used in conjunction with Simple Communications Blocking [1]; see XEP-0191 for details.

2. Protocol This section has been copied without modification from Section 10 of RFC 3921 [2], with the exception of the message stanza handling rule in the Blocked Entity Attempts to Communicate with User subsection.

Most instant messaging systems have found it necessary to implement some method for users to block communications from particular other users (this is also required by sections 5.1.5, 5.1.15, 5.3.2, and 5.4.10 of RFC 2779 [3]. In XMPP this is done by managing one's privacy lists using the 'jabber:iq:privacy' namespace.

Server-side privacy lists enable successful completion of the following use cases:

Retrieving one's privacy lists. Adding, removing, and editing one's privacy lists. Setting, changing, or declining active lists. Setting, changing, or declining the default list (i.e., the list that is active by default). Allowing or blocking messages based on JID, group, or subscription type (or globally). Allowing or blocking inbound presence notifications based on JID, group, or subscription type (or globally). Allowing or blocking outbound presence notifications based on JID, group, or subscription type (or globally). Allowing or blocking IQ stanzas based on JID, group, or subscription type (or globally). Allowing or blocking all communications based on JID, group, or subscription type (or globally). Note: Presence notifications do not include presence subscriptions, only presence information that is broadcasted to entities that are subscribed to a user's presence information. Thus this includes presence stanzas with no 'type' attribute or of type='unavailable' only