moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-27 03:32:16 -05:00
Code Issues Releases Wiki Activity

superseded by XEP-0268

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3640 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-11-18 17:39:11 +00:00
parent a196befa55
commit 09aa17b952
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
xep-0161.xml
View File

@ -7,7 +7,7 @@
<xep> <xep>
<header> <header>
<title>Abuse Reporting</title> <title>Abuse Reporting</title>
<abstract>This document specifies an XMPP protocol extension for reporting abusive XMPP stanzas.</abstract> <abstract>This document specifies an XMPP protocol extension for reporting abusive XMPP stanzas. NOTE: This specification has been superseded by XEP-0268.</abstract>
&LEGALNOTICE; &LEGALNOTICE;
<number>0161</number> <number>0161</number>
<status>Deferred</status> <status>Deferred</status>
@ -20,7 +20,9 @@
<spec>XEP-0030</spec> <spec>XEP-0030</spec>
</dependencies> </dependencies>
<supersedes/> <supersedes/>
<supersededby/> <supersededby>
<spec>XEP-0268</spec>
</supersededby>
<shortname>NOT_YET_ASSIGNED</shortname> <shortname>NOT_YET_ASSIGNED</shortname>
&stpeter; &stpeter;
<revision> <revision>
@ -56,6 +58,7 @@
</header> </header>
<section1 topic='Introduction' anchor='intro'> <section1 topic='Introduction' anchor='intro'>
<p>NOTE: This specification has been superseded by &xep0268;.</p>
<p>Unfortunately, not all XMPP entities are well-behaved -- they may send spam of various kinds, harrass chat rooms, generate large amounts of traffic, etc. Currently, if an XMPP entity (the "attacker") sends abusive stanzas to another XMPP entity (the "victim"), there is no way for the victim or the victim's server to inform the attacker's server that the attacker is generating abusive traffic. In current practice, the victim's server may have no choice but to terminate the server-to-server connection rather than continue to accept the abusive traffic.</p> <p>Unfortunately, not all XMPP entities are well-behaved -- they may send spam of various kinds, harrass chat rooms, generate large amounts of traffic, etc. Currently, if an XMPP entity (the "attacker") sends abusive stanzas to another XMPP entity (the "victim"), there is no way for the victim or the victim's server to inform the attacker's server that the attacker is generating abusive traffic. In current practice, the victim's server may have no choice but to terminate the server-to-server connection rather than continue to accept the abusive traffic.</p>
<p>This situation is far from desirable. Therefore, this specification defines several protocol functions that can help to discourage abuse on the XMPP network:</p> <p>This situation is far from desirable. Therefore, this specification defines several protocol functions that can help to discourage abuse on the XMPP network:</p>
<ol> <ol>