forked from xsf/xeps
-
Notifications
You must be signed in to change notification settings - Fork 0
/
xep-0076.xml
116 lines (116 loc) · 5.64 KB
/
xep-0076.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
]>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
<header>
<title>Malicious Stanzas</title>
<abstract>This document defines an XMPP protocol extension for flagging malicious stanzas.</abstract>
&LEGALNOTICE;
<number>0076</number>
<status>Active</status>
<type>Humorous</type>
<sig>Standards</sig>
<dependencies>
<spec>XMPP Core</spec>
<spec>RFC 3514</spec>
</dependencies>
<supersedes/>
<supersededby/>
<shortname>evil</shortname>
&stpeter;
&hildjj;
<revision>
<version>1.0</version>
<date>2003-04-01</date>
<initials>psa</initials>
<remark><p>April Fools!</p></remark>
</revision>
</header>
<section1 topic='Introduction'>
<p>&rfc3514;, published just today (2003-04-01), defines a mechanism for specifying the "evil bit" in IPv4 in order to determine if a packet was sent with malicious intent. In Section 5 ("Related Work") of that RFC, reference is made to complementary mechanisms for other forms of evil such as IPv6 support and the application/evil MIME type. Because the &XSF; desires to maintain compliance with protocols developed by core Internet standards bodies, the current document defines a complementary mechanism for XMPP support of evil.</p>
</section1>
<section1 topic='Requirements and Approach'>
<p>There are three basic XMPP stanza types that may be sent within XML streams:</p>
<ul>
<li><message/> -- a "push" medium for sending information to other entities.</li>
<li><presence/> -- a "broadcast" medium for publishing information to entities that have subscribed to an entity's availability status.</li>
<li><iq/> -- a "request-response" medium for executing basic but structured transactions with other entities.</li>
</ul>
<p>Any one of the foregoing data elements can be used with malicious intent. Therefore a generalized mechanism is needed. Because XML namespaces are used within XMPP to properly scope data, this document proposes a new namespace ('http://jabber.org/protocol/evil') to implement the desired functionality.</p>
</section1>
<section1 topic='Use Cases'>
<section2 topic='Evil Messages'>
<p>If an evil entity sends an evil message, it MUST include an appropriately namespaced extension in the message stanza:</p>
<example caption='Evil Entity Sends Evil Message'><![CDATA[
<message
from='iago@shakespeare.lit/pda'
to='emilia@shakespeare.lit/mobile'>
<body>
I told him what I thought, and told no more
Than what he found himself was apt and true.
</body>
<evil xmlns='http://jabber.org/protocol/evil'/>
</message>
]]></example>
</section2>
<section2 topic='Evil Presence'>
<p>If an evil entity sends evil presence information, it MUST include an appropriately namespaced extension in the presence stanza:</p>
<example caption='Evil Entity Sends Evil Presence'><![CDATA[
<presence from='iago@shakespeare.lit/pda'>
<show>dnd</show>
<status>Fomenting dissension</status>
<evil xmlns='http://jabber.org/protocol/evil'/>
</presence>
]]></example>
</section2>
<section2 topic='Evil IQs'>
<p>If an evil entity provides evil information in an IQ exchange, it MUST include an appropriately namespaced extension in the IQ stanza:</p>
<example caption='Evil Entity Sends Evil Message'><![CDATA[
<iq from='iago@shakespeare.lit/pda'
id='evil1'
to='emilia@shakespeare.lit/mobile'>
<query xmlns='jabber:iq:version'>
<name>Stabber</name>
<version>666</version>
<os>FiendOS</os>
</query>
<evil xmlns='http://jabber.org/protocol/evil'/>
</iq>
]]></example>
</section2>
</section1>
<section1 topic='Determining Support' anchor='disco'>
<p>Evil entities MUST advertise their support for this protocol in their responses to &xep0030; information ("disco#info") requests by returning a feature of "http://jabber.org/protocol/evil":</p>
<example caption='A disco#info query'><![CDATA[
<iq from='emilia@shakespeare.lit/mobile'
id='disco1'
to='iago@shakespeare.lit/pda'
type='get'>
<query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>
]]></example>
<example caption='A disco#info response'><![CDATA[
<iq from='iago@shakespeare.lit/pda'
id='disco1'
to='emilia@shakespeare.lit/mobile'
type='result'>
<query xmlns='http://jabber.org/protocol/disco#info'>
<feature var='http://jabber.org/protocol/evil'/>
</query>
</iq>
]]></example>
<p>In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.</p>
</section1>
<section1 topic='Security Considerations'>
<p>Because the 'http://jabber.org/protocol/evil' namespace flags an XML stanza as malicious, it is critically important that an entity appropriately process an XML stanza that contains the evil extension. Mission-critical applications SHOULD ignore any stanzas tagged with the evil extension. Evil servers MAY pass through evil stanzas unmodified. Really evil servers MAY silently delete the evil extension. Entities that are evil to the core SHOULD support channel-level evil as defined in RFC 3514, since this document defines per-stanza evil only.</p>
</section1>
<section1 topic='IANA Considerations'>
<p>This document requires no interaction with &IANA;.</p>
</section1>
<section1 topic='XMPP Registrar Considerations'>
<p>The ®ISTRAR; shall register the 'http://jabber.org/protocol/evil' namespace as a result of this document.</p>
</section1>
</xep>