Initial published version.
First draft, split from the incident reporting proposal.
In XMPP, rosters and presence subscriptions have been used to date only among IM users (see &xmppim;). However, nothing prevents the application of these concepts to other XMPP entities, such as components and servers. Given that a presence subscription typically indicates some level of trust in a peer, server deployments can use the sharing of XMPP presence information as a way to indicate that a given server has a trust relationship with a peer server. The server might then share certain kinds of additional information only with trusted peers, for example &xep0268;.
+To establish a trust relationship with a peer, a server shall send a presence subscription request to the peer, just as is done between XMPP users.
+A server MUST NOT send such a presence subscription request unless explicitly requested to do so by the server administrator(s).
+Upon receiving such a presence subscription request, the XMPP server software running at the peer MUST prompt the server administrator(s) to approve the request, rather than automatically approving it. Methods for doing so are out of scope for this specification.
+If the server administrator(s) approve the request, the peer server shall then inform the originating server that the request has been approved.
+The peer SHOULD also send a subscription request to the originating server.
+If an XMPP server implementation supports this usage of presence subscriptions, it MUST keep a list of approved entities, which we denote a "server roster". The implementation MAY use that roster for access control purposes defined in other specifications.
+To follow.
+This document requires no interaction with &IANA;.
+This document requires no interaction with the ®ISTRAR;.
+Initial published version.
Per Council feedback, moved server rosters to a separate specification.
Refactored XML format; added elements for sub-categories, locations, related incidents, solutions, and suggestions.
First draft.
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;.)
+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;.
+The defined children of the <description/> element are as follows:
+| Element Name | +Description | +
|---|---|
| <discuss/> | +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/>). | +
| <info/> | +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. | +
| <locs/> | +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. | +
| <rels/> | +The IDs of one or more incidents to which this incident might be related, each contained in a separate <rel/> element. | +
| <severity/> | +The seriousness of the problem, from 5 (least serious) to 1 (most serious). | +
| <source/> | +The IP address(es) and JabberID(s) where the incident originated. | +
| <text/> | +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. | +
| <time/> | +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; | +
If the reporting entity determines a solution to the problem, it MAY send out a revised incident report containing a <solution/> element.
+Further definition of the <solution/> element will be provided in a future version of this specification.
+If an entity that receives an incident report has a suggested solution to the problem, it MAY send an incident message containing a <suggestion/> element.
+Further definition of the <suggestion/> element will be provided in a future version of this specification.
+To follow.
+This document requires no interaction with &IANA;.
+This specification defines the following XML namespace:
+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;.
+To follow.
+