XEP-0377: Spam Reporting

Abstract: This document specifies a mechanism by which users can report spam and other abuse to a server operator or other spam service.
Author:Sam Whited
Copyright:© 1999 – 2017 XMPP Standards Foundation. SEE LEGAL NOTICES.
Type:Standards Track
Last Updated:2016-05-25

WARNING: This Standards-Track document is Experimental. Publication as an XMPP Extension Protocol does not imply approval of this proposal by the XMPP Standards Foundation. Implementation of the protocol described herein is encouraged in exploratory implementations, but production systems are advised to carefully consider whether it is appropriate to deploy implementations of this protocol before it advances to a status of Draft.

Table of Contents

1. Introduction
2. Discovering Support
3. Payload
4. Use with the Blocking Command
5. Implementation Notes
6. Internationalization Considerations
7. Security Considerations
8. IANA Considerations
9. XMPP Registrar Considerations
    9.1. Protocol Namespaces
    9.2. Namespace Versioning
    9.3. Abuse Reporting Registry
    9.4. Abuse Reporting Reasons
10. XML Schema
11. Acknowledgements

    A: Document Information
    B: Author Information
    C: Legal Notices
    D: Relation to XMPP
    E: Discussion Venue
    F: Requirements Conformance
    G: Notes
    H: Revision History

1. Introduction

Many spam and abuse prevention techniques rely on users being able to report other users who are sending unwanted messages, or specific instances of abuse. Blocking Command (XEP-0191) [1] allows users to block spammers, but does not provide a mechanism for them to report a reason for the block to the server operator. This specification extends the blocking command to optionally provide an abuse report.

2. Discovering Support

Entities that support Service Discovery (XEP-0030) [2] and abuse reporting MUST respond to service discovery requests with a feature of 'urn:xmpp:reporting:0' and with a feature for each reason supported by the responding entity as described in the relavant specifications. Eg. a response from a server that supports reporting and understands the abuse and spam reasons defined later in this specification might look like the following:

Example 1. Service discovery information response

<iq from='shakespeare.lit'
  <query xmlns='http://jabber.org/protocol/disco#info'>
    <feature var='urn:xmpp:reporting:0'/>
    <feature var='urn:xmpp:reporting:reason:abuse:0'/>
    <feature var='urn:xmpp:reporting:reason:spam:0'/>

3. Payload

The payload for reporting abuse to the server takes the form of a <report/> qualified by the 'urn:xmpp:reporting:0' namespace (see Namespace Versioning regarding the possibility of incrementing the version number). Report payloads are reusable and MUST NOT be sent without first being wrapped in a stanza.

Example 2. The most basic report payload

<report xmlns="urn:xmpp:reporting:0" />

Abuse reports MAY include a reason for the report and servers MUST tolerate unknown XML elements in a report without making assumptions about the semantic meaning of unknown elements.

This document defines the following reasons for a report:

Used for reporting a JID that is sending unwanted messages.
Used for reporting general abuse.

Clients MUST include only one reason per report.

Reports MAY contain a user provided message explaining or providing context about the reason for the report. See also the Internationalization Considerations section of this document.

Example 3. Report with optional reason and text

<report xmlns="urn:xmpp:reporting:0">
  <text xml:lang="en">
    Never came trouble to my house like this.

4. Use with the Blocking Command

To send a report, a report payload MAY be inserted into an <item/> node sent as part of a request to block a spammer as defined in Blocking Command (XEP-0191) [1]. For example:

Example 4. Report sent with blocking command

<iq from='juliet@capulet.com/chamber' type='set' id='block1'>
  <block xmlns='urn:xmpp:blocking'>
    <item jid='romeo@montague.net'>
      <report xmlns="urn:xmpp:reporting:0">

Servers that receive a blocking command with a report MUST block the JID or return an error just as they would if no report were present. Servers then MAY take other actions based on the report, however, such actions are outside the scope of this document.

5. Implementation Notes

Clients that support sending reports as part of the blocking command SHOULD expose interfaces to both block a JID without reporting it as abusive, and to block and report a JID.

6. Internationalization Considerations

If one or more <text/> elements are present they SHOULD include 'xml:lang' attributes specifying the natural language of the XML character data.

7. Security Considerations

This document introduces no additional security considerations above and beyond those defined in the documents on which it depends.

8. IANA Considerations

This document requires no interaction with the Internet Assigned Numbers Authority (IANA) [3].

9. XMPP Registrar Considerations

9.1 Protocol Namespaces

This specification defines the following XML namespace:

Upon advancement of this specification from a status of Experimental to a status of Draft, the XMPP Registrar [4] shall add the foregoing namespace to the registry located at <https://xmpp.org/registrar/disco-features.html>, as described in Section 4 of XMPP Registrar Function (XEP-0053) [5].

9.2 Namespace Versioning

If the protocol defined in this specification undergoes a revision that is not fully backwards-compatible with an older version, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of XEP-0053.

9.3 Abuse Reporting Registry

The XMPP Registrar shall maintain a registry of abuse report reasons. All abuse report reason registrations shall be defined in separate specifications (not in this document). Application types defined within the XEP series MUST be registered with the XMPP Registrar, resulting in protocol URNs of the form "urn:xmpp:reporting:reason:name:X" (where "name" is the registered name of the reason and "X" is a non-negative integer).

In order to submit new values to this registry, the registrant shall define an XML fragment of the following form and either include it in the relevant XMPP Extension Protocol or send it to the email address <registrar@xmpp.org>:

  <name>The name of the abuse report reason.</name>
  <desc>A natural-language summary of the reason.</desc>
    The document in which the report reason is specified.

9.4 Abuse Reporting Reasons

This specification defines the following abuse reporting reasons:

Upon advancement of this specification from a status of Experimental to a status of Draft, the XMPP Registrar [4] shall add the following definition to the abuse reporting reasons registry, as described in this document:

  <desc>Used to report a JID that was sending spam messages.</desc>

  <desc>Used to report general abuse that is not covered by a more specific reason.</desc>

10. XML Schema

An XML schema will be added before this specification moves to draft status.

11. Acknowledgements

Thanks to the participants of the XMPP Summit 20 in Austin, TX who discussed this XEP: specifically to Waqas Hussain, Kevin Smith, Lance Stout, and Matthew Wild. A special thanks to Daniel Wisnewski for giving the presentation that kicked off the anti-abuse work.


Appendix A: Document Information

Series: XEP
Number: 0377
Publisher: XMPP Standards Foundation
Status: Experimental
Type: Standards Track
Version: 0.1.0
Last Updated: 2016-05-25
Approving Body: XMPP Council
Dependencies: XMPP Core, XMPP IM, XEP-0191
Supersedes: None
Superseded By: None
Source Control: HTML
This document in other formats: XML  PDF

Appendix B: Author Information

Sam Whited

Email: sam@samwhited.com
JabberID: sam@samwhited.com
URI: https://blog.samwhited.com/

Appendix C: Legal Notices


This XMPP Extension Protocol is copyright © 1999 – 2017 by the XMPP Standards Foundation (XSF).


Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.

Disclaimer of Warranty

## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##

Limitation of Liability

In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.

IPR Conformance

This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA).

Appendix D: Relation to XMPP

The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.

Appendix E: Discussion Venue

The primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.org> discussion list.

Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.

Errata can be sent to <editor@xmpp.org>.

Appendix F: Requirements Conformance

The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".

Appendix G: Notes

1. XEP-0191: Blocking Command <https://xmpp.org/extensions/xep-0191.html>.

2. XEP-0030: Service Discovery <https://xmpp.org/extensions/xep-0030.html>.

3. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.

4. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>.

5. XEP-0053: XMPP Registrar Function <https://xmpp.org/extensions/xep-0053.html>.

Appendix H: Revision History

Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/

Version 0.1.0 (2016-05-25)

Initial version approved by the Council.


Version 0.0.1 (2016-05-21)

First draft.