Aligned document with the IETF guidelines for defining extensions to IODEF; defined several more IODEF NodeRole categories; added schema for the JID element; noted that the JID element might be moved to a separate specification.
If the recipient is able to process the report, it MUST return an &IQ; stanza of type "result"; if not, it MUST return an &IQ; stanza of type "error" (error handling will be defined in a future version of this specification).
+This document defines the following IODEF extensions, described in accordance with the guidelines in &miletemplate;.
+This specification defines an extended Contact role of "chatroom", i.e., a new enumerated value for the Contact@role attribute. This value specifies a text conference where discussion of the incident can take place, e.g., an IRC channel or an XMPP &xep0045; room. Since there are many different chatroom technologies, the address of the chatroom shall be specified as the child of an &ADDITION; element. For XMPP chatrooms, the address is the XML character data of a &JID; element qualified by the 'urn:xmpp:jid:0' namespace.
+Note: Definition of the &JID; element might be moved to a separate specification.
+This specification defines an extended Address category of "xmpp", i.e., a new enumerated value for the Address@category attribute. This value specifies the JabberID of a network entity, in conformance with &rfc6122; or its successor.
+This specification defines several extended NodeRole categories, i.e., new enumerated values for the NodeRole@category attribute:
+This specification defines an AdditionalData element of &JID; qualified by the 'urn:xmpp:jid:0' namespace. The XML character data of this element is a JabberID (i.e., an XMPP address) that conforms to RFC 6122 or its successor.
+Note: Definition of the &JID; element might be moved to a separate specification.
+The <jid/> element qualified by the 'urn:xmpp:incident:2' namespace is a "JID slot" as described in &rfc6122bis;.
+The &JID; element qualified by the 'urn:xmpp:incident:2' namespace is a "JID slot" as described in &rfc6122bis;.
+Note: Definition of the &JID; element might be moved to a separate specification.
This document might require interaction with &IANA; to register various IODEF extension attributes.
+This document might require interaction with &IANA; to register various IODEF extensions, in accordance with draft-ietf-mile-template.
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;.
+Note: Registration of the 'urn:xmpp:jid:0' namespace might be moved to a separate specification.
+
+
-
-
@@ -373,7 +407,24 @@
- ]]>
+ ]]>
+
+ Note: This schema and associated text might be moved to a separate specification.
+
+
+
+
+
+
+
+ ]]>
+