The Incident Object Description Exchange Format Version 2
draft-ietf-mile-rfc5070-bis-26

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: rdd@cert.org, mile-chairs@tools.ietf.org, takeshi_takahashi@nict.go.jp, Kathleen.Moriarty.ietf@gmail.com, mile-chairs@ietf.org, "The IESG" <iesg@ietf.org>, mile@ietf.org, draft-ietf-mile-rfc5070-bis@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'The Incident Object Description Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-bis-25.txt)

The IESG has approved the following document:
- 'The Incident Object Description Exchange Format v2'
  (draft-ietf-mile-rfc5070-bis-25.txt) as Proposed Standard

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

The IESG contact persons are Stephen Farrell and Kathleen Moriarty.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-mile-rfc5070-bis/

Ballot Text

Technical Summary

   The Incident Object Description Exchange Format (IODEF) defines a
   data representation for security incident reports and cyber
   indicators commonly exchanged by operational security teams for
   mitigation and watch and warning.  This document describes an updated
   information model for the IODEF and provides an associated data model
   specified with XML Schema.  This new information and data model
   obsoletes [RFC5070]

Working Group Summary

   There was good consensus on the draft from the WG.  The updates were managed using the datatracker ticketing system and updates were confirmed on list.   

Document Quality

   There are several implementations which are documented in an implementation report to follow.  The XML expert for IODEF performed their review already and others checked the XML to UML, myself included.  The internationalization was checked as well.

Personnel

  Takeshi Takahashi is the Document Shepherd and Kathleen Moriarty is 
  the Responsible Area Director
'The IANA Expert(s) for the registries in this document are Takeshi Takahashi and Roman Danyliw.'

IANA Note

  Registry updates require expert review per RFC5226.

RFC Editor Note