mirror of https://github.com/moparisthebest/xeps
0.3
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3629 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre
parent
68e2a6c43a
commit
d7c5de1caa
44
xep-0268.xml
44
xep-0268.xml
|
|
@ -46,6 +46,12 @@
|
|||
<email>mwild1@gmail.com</email>
|
||||
<jid>mwild1@jaim.at</jid>
|
||||
</author>
|
||||
<revision>
|
||||
<version>0.3</version>
|
||||
<date>2009-11-17</date>
|
||||
<initials>psa</initials>
|
||||
<remark><p>Added security considerations; defined schema.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.2</version>
|
||||
<date>2009-06-05</date>
|
||||
|
|
@ -79,7 +85,7 @@
|
|||
</header>
|
||||
|
||||
<section1 topic='Introduction' anchor='intro'>
|
||||
<p>As XMPP technologies have been deployed more widely, the open XMPP network has become a more significant target for attacks. This specification defines ways for XMPP server deployments to share information with each other and therefore handle such attacks in a more real-time fashion. In particular, it defines a format for sharing incident reports among XMPP server deployments. (For some related considerations, see &rfc2350;, &rfc3067;, and &rfc5070;.)</p>
|
||||
<p>As XMPP technologies have been deployed more widely, the open XMPP network has become a more significant target for attacks. This specification defines ways for XMPP server deployments to share information with each other and therefore to handle such attacks in a more real-time fashion. In particular, it defines a format for sharing incident reports among XMPP server deployments. (For some related considerations, see &rfc2350;, &rfc3067;, and &rfc5070;.)</p>
|
||||
</section1>
|
||||
|
||||
<section1 topic='Incident Reports' anchor='reports'>
|
||||
|
|
@ -130,11 +136,11 @@
|
|||
</tr>
|
||||
<tr>
|
||||
<td><discuss/></td>
|
||||
<td>This element contains the JID of the server admin who generated the incident report (<admin/>), as well as a &xep0045; room where the incident can be discussed (<muc/>).</td>
|
||||
<td>The JID of the server admin who generated the incident report (<admin/>), as well as a &xep0045; room where the incident can be discussed (<muc/>).</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><info/></td>
|
||||
<td>Structured information about the incident. The defined values of the <category/> and <type/> elements shall be provided via a registry. It is envisioned that the <category/> values shall be "muc" for &xep0045; incidents, "pubsub" for &xep0060; incidents, "reg" for account registration (&xep0077;) incidents, and "stanzas" for general XMPP traffic incidents.</td>
|
||||
<td>Structured information about the incident. The defined values of the <category/> and <type/> elements shall be provided via a registry. It is envisioned that the <category/> values shall be "muc" for &xep0045; incidents, "pubsub" for &xep0060; incidents, "reg" for account registration (&xep0077;) incidents, and "stanzas" for general XMPP incidents.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><locs/></td>
|
||||
|
|
@ -164,7 +170,7 @@
|
|||
</section1>
|
||||
|
||||
<section1 topic='Incident Solutions' anchor='solutions'>
|
||||
<p>If the reporting entity determines a solution to the problem or a receiving entity has a suggested solution to the problem, it SHOULD send out a revised incident report containing a <solution/> element (or the reporting entity can include a solution in its initial report). The solution element can include any of the elements defined for the <description/> element, such as the <ip/> element (since the XMPP server of a source JID might know the IP address and port of the connected entity).</p>
|
||||
<p>If the reporting entity determines a solution to the problem or a receiving entity has a suggested solution to the problem, it SHOULD send out a revised incident report containing a <solution/> element (alternatively, the reporting entity can include a solution in its initial report). The solution element can include any of the elements defined for the <description/> element, such as the <ip/> element (since the XMPP server of a source JID might know the IP address and port of the connected entity).</p>
|
||||
<example caption="An incident solution"><![CDATA[
|
||||
<message from='jabber.org' to='im.flosoft.biz'>
|
||||
<incident xmlns='urn:xmpp:incident:0'
|
||||
|
|
@ -183,17 +189,20 @@
|
|||
</incident>
|
||||
</message>
|
||||
]]></example>
|
||||
<p>Further definition of the <solution/> element will be provided in a future version of this specification.</p>
|
||||
</section1>
|
||||
|
||||
<section1 topic='Processing of Incident Reports' anchor='processing'>
|
||||
<p>Unless explicitly configured to do so, a receiving server SHOULD NOT automatically modify its configuration based on receipt of an incident report, even from a trusted server, but instead SHOULD prompt the human administrator(s) so that they can take appropriate action.</p>
|
||||
<p>Unless explicitly configured to do so, a receiving server SHOULD NOT automatically modify its configuration based on receipt of an incident report, even from a trusted server, but instead SHOULD prompt the human administrators so that they can take appropriate action.</p>
|
||||
<p>A receiving server MAY accept incident reports from peers that are not on its "trust list", but SHOULD treat such reports with caution and provide them to the human administrator(s) of the server.</p>
|
||||
<p>A receiving server MAY forward reports that it receives to other servers it trusts.</p>
|
||||
</section1>
|
||||
|
||||
<section1 topic='Security Considerations' anchor='security'>
|
||||
<p>To follow.</p>
|
||||
<p>This technology is designed to help mitigate attacks on the XMPP network. However, incident reporting is itself vulnerable to the following attacks:</p>
|
||||
<ul>
|
||||
<li>False reports could lead a server to deny service to legitimate users or peer servers (see also &xep0205;). To help mitigate such attacks, a server SHOULD treat with caution any incident reports that it might receive from untrusted entities.</li>
|
||||
<li>If traffic between two servers is not protected using Transport Layer Security (TLS), a passive eavesdropper could gain access to incident reports and therefore adjust its behavior in response. To prevent such attacks, servers SHOULD use TLS.</li>
|
||||
</ul>
|
||||
</section1>
|
||||
|
||||
<section1 topic='IANA Considerations' anchor='iana'>
|
||||
|
|
@ -214,7 +223,26 @@
|
|||
</section1>
|
||||
|
||||
<section1 topic='XML Schema' anchor='schema'>
|
||||
<p>To follow.</p>
|
||||
<code><![CDATA[
|
||||
<?xml version='1.0' encoding='UTF-8'?>
|
||||
|
||||
<xs:schema
|
||||
xmlns:xs='http://www.w3.org/2001/XMLSchema'
|
||||
targetNamespace='urn:xmpp:incident:0'
|
||||
xmlns='urn:xmpp:incident:0'
|
||||
elementFormDefault='qualified'>
|
||||
|
||||
<xs:element name='incident'>
|
||||
</xs:element>
|
||||
|
||||
<xs:simpleType name='empty'>
|
||||
<xs:restriction base='xs:string'>
|
||||
<xs:enumeration value=''/>
|
||||
</xs:restriction>
|
||||
</xs:simpleType>
|
||||
|
||||
</xs:schema>
|
||||
]]></code>
|
||||
</section1>
|
||||
|
||||
</xep>
|
||||
|
|
|
|||
Loading…
Reference in New Issue