JSON binding of IODEF
draft-takahashi-mile-jsoniodef-01

Document Type Replaced Internet-Draft (individual)
Last updated 2017-09-27
Replaced by draft-ietf-mile-jsoniodef
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mile-jsoniodef
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-takahashi-mile-jsoniodef-01.txt

Abstract

RFC 7970 [RFC7970] 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.

Authors

Takeshi Takahashi (takeshi_takahashi@nict.go.jp)
Mio Suzuki (mio@nict.go.jp)

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