Expert Review for Incident Object Description Exchange Format (IODEF) Extensions in IANA XML Registry
draft-ietf-mile-iodef-xmlreg-01

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    mile mailing list <mile@ietf.org>,
    mile chair <mile-chairs@tools.ietf.org>
Subject: Protocol Action: 'Expert Review for IODEF Extensions in IANA XML Registry' to Proposed Standard (draft-ietf-mile-iodef-xmlreg-01.txt)

The IESG has approved the following document:
- 'Expert Review for IODEF Extensions in IANA XML Registry'
  (draft-ietf-mile-iodef-xmlreg-01.txt) as Proposed Standard

This document is the product of the Managed Incident Lightweight Exchange
Working Group.

The IESG contact persons are Sean Turner and Stephen Farrell.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-mile-iodef-xmlreg/

Ballot Text

Technical Summary

'Expert Review for IODEF Extensions in IANA XML Registry' (draft-ietf-mile-iodef-xmlreg) specifies restrictions on additions to the subset of the IANA XML Namespace and Schema registries, to require Expert Review for extensions to the Incident Object Description Exchange Format (IODEF).  IODEF is specified in RFC5070.

Working Group Summary

The document requires and expert review on IODEF extensions, very straightforward from the WG perspective.

Document Quality

Yes, there are several implementations of RFC5070 and extensions.  This document does not specify anything that requires implementation, just requires an expert review on any new extensions.

Personnel

Kathleen Moriarty is the Document Shepherd.
Sean Turner is the Responsible Area Director.


IANA Note

Please note that this document is assigning an *additional* expert.  There's no expectation that this expert will be an XML expert.  This will mean there are two designated experts: one for the XML schema and one for the IODEF.  We'll need to somehow clearly identify this in the registry.

RFC Editor Note