No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-0377.xml 8.8KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247
  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM 'xep.ent'>
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>Spam Reporting</title>
  10. <abstract>
  11. This document specifies a mechanism by which users can report spam and other
  12. abuse to a server operator or other spam service.
  13. </abstract>
  14. &LEGALNOTICE;
  15. <number>0377</number>
  16. <status>Deferred</status>
  17. <type>Standards Track</type>
  18. <sig>Standards</sig>
  19. <approver>Council</approver>
  20. <dependencies>
  21. <spec>XMPP Core</spec>
  22. <spec>XMPP IM</spec>
  23. <spec>XEP-0191</spec>
  24. </dependencies>
  25. <supersedes/>
  26. <supersededby/>
  27. <shortname>NOT_YET_ASSIGNED</shortname>
  28. &sam;
  29. <revision>
  30. <version>0.2</version>
  31. <date>2017-09-11</date>
  32. <initials>XEP Editor (jwi)</initials>
  33. <remark>Defer due to lack of activity.</remark>
  34. </revision>
  35. <revision>
  36. <version>0.1.0</version>
  37. <date>2016-05-25</date>
  38. <initials>ssw</initials>
  39. <remark><p>Initial version approved by the Council.</p></remark>
  40. </revision>
  41. <revision>
  42. <version>0.0.1</version>
  43. <date>2016-05-21</date>
  44. <initials>ssw</initials>
  45. <remark><p>First draft.</p></remark>
  46. </revision>
  47. </header>
  48. <section1 topic='Introduction' anchor='intro'>
  49. <p>
  50. Many spam and abuse prevention techniques rely on users being able to report
  51. other users who are sending unwanted messages, or specific instances of
  52. abuse. &xep0191; allows users to block spammers, but does not provide a
  53. mechanism for them to report a reason for the block to the server operator.
  54. This specification extends the blocking command to optionally provide an
  55. abuse report.
  56. </p>
  57. </section1>
  58. <section1 topic='Discovering Support' anchor='disco'>
  59. <p>
  60. Entities that support &xep0030; and abuse reporting MUST respond to service
  61. discovery requests with a feature of 'urn:xmpp:reporting:0' and with a
  62. feature for each reason supported by the responding entity as described in
  63. the relavant specifications. Eg. a response from a server that supports
  64. reporting and understands the abuse and spam reasons defined later in this
  65. specification might look like the following:
  66. </p>
  67. <example caption="Service discovery information response"><![CDATA[
  68. <iq from='shakespeare.lit'
  69. id='ku6e51v3'
  70. to='kingclaudius@shakespeare.lit/castle'
  71. type='result'>
  72. <query xmlns='http://jabber.org/protocol/disco#info'>
  73. <feature var='urn:xmpp:reporting:0'/>
  74. <feature var='urn:xmpp:reporting:reason:abuse:0'/>
  75. <feature var='urn:xmpp:reporting:reason:spam:0'/>
  76. </query>
  77. </iq>]]></example>
  78. </section1>
  79. <section1 topic='Payload' anchor='payload'>
  80. <p>
  81. The payload for reporting abuse to the server takes the form of a
  82. &lt;report/&gt; qualified by the 'urn:xmpp:reporting:0' namespace &VNOTE;.
  83. Report payloads are reusable and MUST NOT be sent without first being
  84. wrapped in a stanza.
  85. </p>
  86. <example caption='The most basic report payload'><![CDATA[
  87. <report xmlns="urn:xmpp:reporting:0" />]]></example>
  88. <p>
  89. Abuse reports MAY include a reason for the report and servers MUST tolerate
  90. unknown XML elements in a report without making assumptions about the
  91. semantic meaning of unknown elements.
  92. </p>
  93. <p>
  94. This document defines the following reasons for a report:
  95. </p>
  96. <dl>
  97. <di>
  98. <dt>&lt;spam/&gt;</dt>
  99. <dd>Used for reporting a JID that is sending unwanted messages.</dd>
  100. </di>
  101. <di>
  102. <dt>&lt;abuse/&gt;</dt>
  103. <dd>Used for reporting general abuse.</dd>
  104. </di>
  105. </dl>
  106. <p>
  107. Clients MUST include only one reason per report.
  108. </p>
  109. <p>
  110. Reports MAY contain a user provided message explaining or providing context
  111. about the reason for the report. See also the
  112. <link url='#i18n'>Internationalization Considerations</link> section of this
  113. document.
  114. </p>
  115. <example caption='Report with optional reason and text'><![CDATA[
  116. <report xmlns="urn:xmpp:reporting:0">
  117. <text xml:lang="en">
  118. Never came trouble to my house like this.
  119. </text>
  120. <spam/>
  121. </report>]]></example>
  122. </section1>
  123. <section1 topic='Use with the Blocking Command' anchor='blocking'>
  124. <p>
  125. To send a report, a report payload MAY be inserted into an &lt;item/&gt;
  126. node sent as part of a request to block a spammer as defined in &xep0191;.
  127. For example:
  128. </p>
  129. <example caption='Report sent with blocking command'><![CDATA[
  130. <iq from='juliet@capulet.com/chamber' type='set' id='block1'>
  131. <block xmlns='urn:xmpp:blocking'>
  132. <item jid='romeo@montague.net'>
  133. <report xmlns="urn:xmpp:reporting:0">
  134. <abuse/>
  135. </report>
  136. </item>
  137. </block>
  138. </iq>]]></example>
  139. <p>
  140. Servers that receive a blocking command with a report MUST block the JID or
  141. return an error just as they would if no report were present. Servers then
  142. MAY take other actions based on the report, however, such actions are
  143. outside the scope of this document.
  144. </p>
  145. </section1>
  146. <section1 topic='Implementation Notes' anchor='impl'>
  147. <p>
  148. Clients that support sending reports as part of the blocking command SHOULD
  149. expose interfaces to both block a JID without reporting it as abusive, and
  150. to block and report a JID.
  151. </p>
  152. </section1>
  153. <section1 topic='Internationalization Considerations' anchor='i18n'>
  154. <p>
  155. If one or more &lt;text/&gt; elements are present they SHOULD include
  156. 'xml:lang' attributes specifying the natural language of the XML character
  157. data.
  158. </p>
  159. </section1>
  160. <section1 topic='Security Considerations' anchor='security'>
  161. <p>
  162. This document introduces no additional security considerations above and
  163. beyond those defined in the documents on which it depends.
  164. </p>
  165. </section1>
  166. <section1 topic='IANA Considerations' anchor='iana'>
  167. <p>This document requires no interaction with &IANA;.</p>
  168. </section1>
  169. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  170. <section2 topic='Protocol Namespaces' anchor='registrar-ns'>
  171. <p>This specification defines the following XML namespace:</p>
  172. <ul>
  173. <li>urn:xmpp:reporting:0</li>
  174. </ul>
  175. <p>
  176. Upon advancement of this specification from a status of Experimental to
  177. a status of Draft, the &REGISTRAR; shall add the foregoing namespace to
  178. the registry located at &DISCOFEATURES;, as described in Section 4 of
  179. &xep0053;.
  180. </p>
  181. </section2>
  182. <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
  183. &NSVER;
  184. </section2>
  185. <section2 topic='Abuse Reporting Registry' anchor='registrar-reporting'>
  186. <p>
  187. The XMPP Registrar shall maintain a registry of abuse report reasons.
  188. All abuse report reason registrations shall be defined in separate
  189. specifications (not in this document). Application types defined within
  190. the XEP series MUST be registered with the XMPP Registrar, resulting in
  191. protocol URNs of the form "urn:xmpp:reporting:reason:name:X" (where
  192. "name" is the registered name of the reason and "X" is a non-negative
  193. integer).
  194. </p>
  195. &REGPROCESS;
  196. <code>
  197. <![CDATA[<reason>
  198. <name>The name of the abuse report reason.</name>
  199. <urn>urn:xmpp:reporting:reason:{name}:{ver}</urn>
  200. <desc>A natural-language summary of the reason.</desc>
  201. <doc>
  202. The document in which the report reason is specified.
  203. </doc>
  204. </reason>]]></code>
  205. </section2>
  206. <section2 topic='Abuse Reporting Reasons' anchor='registrar-reasons'>
  207. <p>This specification defines the following abuse reporting reasons:</p>
  208. <ul>
  209. <li>urn:xmpp:reporting:reason:spam:0</li>
  210. <li>urn:xmpp:reporting:reason:abuse:0</li>
  211. </ul>
  212. <p>
  213. Upon advancement of this specification from a status of Experimental to
  214. a status of Draft, the &REGISTRAR; shall add the following definition to
  215. the abuse reporting reasons registry, as described in this document:
  216. </p>
  217. <code><![CDATA[
  218. <reason>
  219. <name>Spam</name>
  220. <urn>urn:xmpp:reporting:reason:spam:0</urn>
  221. <desc>Used to report a JID that was sending spam messages.</desc>
  222. <doc>XEP-0377</doc>
  223. </reason>]]></code>
  224. <code><![CDATA[
  225. <reason>
  226. <name>Abuse</name>
  227. <urn>urn:xmpp:reporting:reason:abuse:0</urn>
  228. <desc>Used to report general abuse that is not covered by a more specific reason.</desc>
  229. <doc>XEP-0377</doc>
  230. </reason>]]></code>
  231. </section2>
  232. </section1>
  233. <section1 topic='XML Schema' anchor='schema'>
  234. <p>
  235. An XML schema will be added before this specification moves to draft
  236. status.
  237. </p>
  238. </section1>
  239. <section1 topic='Acknowledgements' anchor='acknowledgements'>
  240. <p>
  241. Thanks to the participants of the XMPP Summit 20 in Austin, TX who
  242. discussed this XEP: specifically to Waqas Hussain, Kevin Smith, Lance
  243. Stout, and Matthew Wild. A special thanks to Daniel Wisnewski for giving
  244. the presentation that kicked off the anti-abuse work.
  245. </p>
  246. </section1>
  247. </xep>