<remark><p>Added more detailed information about the solution element; removed the suggestion element since the solution element can be used by both reporting entities and receiving entities; added notes about processing of incident reports by receiving entities.</p></remark>
<remark><p>Initial published version.</p></remark>
</revision>
<revision>
<version>0.0.3</version>
<date>2009-04-30</date>
<initials>psa</initials>
<remark><p>Per Council feedback, moved server rosters to a separate specification.</p></remark>
</revision>
<revision>
<version>0.0.2</version>
<date>2009-04-27</date>
<initials>psa/fj</initials>
<remark><p>Refactored XML format; added elements for sub-categories, locations, related incidents, solutions, and suggestions.</p></remark>
</revision>
<revision>
<version>0.0.1</version>
<date>2009-04-13</date>
<initials>ah/fj/psa/mr/mw</initials>
<remark><p>First draft.</p></remark>
</revision>
</header>
<section1topic='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>An incident report consists of an XMPP &MESSAGE; stanza containing an <incident/> child element that includes an 'id' attribute whose value is a UUID as described in &rfc4122;. An example is shown below. A server deployment SHOULD send incident reports only to peer servers that it trusts, for example peers that are in its "server roster" as described in &xep0267;.</p>
<examplecaption="An incident report"><![CDATA[
<messagefrom='jabber.org'to='im.flosoft.biz'>
<incidentxmlns='urn:xmpp:incident:0'
id='BA51A035-7710-4558-9BBF-34838A4C5B24'>
<description>
<discuss>
<admin>stpeter@jabber.org</admin>
<muc>operators@conference.jabber.org</muc>
</discuss>
<info>
<category>muc</category>
<type>presence</type>
<type>long-messages</type>
</info>
<locs>
<loc>jdev@conference.jabber.org</loc>
<loc>jabber@conference.jabber.org</loc>
</locs>
<rels>
<rel>133BCE2E-E669-4ECE-B0F8-766B9E65630D</rel>
</rels>
<severity>2</severity>
<source>
<jids>
<jid>abuser@abuse.lit</jid>
<jid>loser@abuse.lit</jid>
</jids>
</source>
<textxml:lang='en'>lots of MUC spammers from abuse.lit!</text>
<time>
<begin>2009-04-13T19:05:20Z</begin>
<end>2009-04-13T19:27:22Z</end>
<report>2009-04-13T19:31:07Z</report>
</time>
</description>
</incident>
</message>
]]></example>
<p>The defined children of the <description/> element are as follows:</p>
<tablecaption='<description/> children'>
<tr>
<th>Element Name</th>
<th>Description</th>
</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>
</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>
</tr>
<tr>
<td><locs/></td>
<td>The place or places on the XMPP network where the incident has occurred (such as a multi-user chat room, a publish-subscribe service, or a general XMPP server), each contained in a separate <loc/> element.</td>
</tr>
<tr>
<td><rels/></td>
<td>The IDs of one or more incidents to which this incident might be related, each contained in a separate <rel/> element.</td>
</tr>
<tr>
<td><severity/></td>
<td>The seriousness of the problem, from 5 (least serious) to 1 (most serious).</td>
<td>The IPv4 or IPv6 address (optionally including port) and JabberID where the incident originated (multiple instance of each source type can be included).</td>
<td>A natural-language description of the event. This element SHOULD possess an 'xml:lang' attribute. Multiple <text/> elements MAY be included, each with a different 'xml:lang' value.</td>
</tr>
<tr>
<td><time/></td>
<td>The time when the incident began and ended (include an empty <end/> element if the incident is still happening) and, optionally, was reported. The dates MUST conform to the DateTime profile specified in &xep0082;</td>
<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>
<section1topic='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>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>This specification defines the following XML namespace:</p>
<ul>
<li>urn:xmpp:incident:0</li>
</ul>
<p>Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
