Skip to main content

JSON representation of IODEF

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Author Takeshi Takahashi
Last updated 2016-12-10 (Latest revision 2016-06-08)
Replaced by draft-ietf-mile-jsoniodef, draft-ietf-mile-jsoniodef, RFC 8727
RFC stream (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


RFC5070-bis provides XML-based data representation on incident information, but the use of the IODEF data model is not limited to XML. JSON representation is sometimes preferred since it is easy to handle from certain programming environments. This draft represents the IODEF data model in JSON. Note that this 00 version draft is prepared for the purpose of encouraging discussion on the need for JSON representation.


Takeshi Takahashi

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)