[mile] JSON representation of IODEF (FW: New Version Notification for draft-takahashi-mile-jsoniodef-00.txt)

["Takeshi Takahashi" <[e-mail]>]

Hello all,

In the Yokohama meeting, we had discussion on the JSON representation of IODEF.
Since rfc5070-bis is about to be published as an RFC, I would like to push this discussion again.
For this purpose, I've created its JSON representation draft.

https://datatracker.ietf.org/doc/draft-takahashi-mile-jsoniodef/

The conversion from XML to JSON is very simple, but some classes that exist only for the purpose of semantically grouping subjects could be omitted depending on the discussion. (e.g., Flow class and Record class)

If anybody is interested in authoring or co-authoring this draft, please feel free to contact me.
I would appreciate that very much.
The current draft is prepared for the purpose of raising discussion and checking any interests from potential authors/co-authors.

Thank you, and kind regards.
Take



> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]]
> Sent: Wednesday, June 8, 2016 6:08 PM
> To: Takeshi Takahashi
> Subject: New Version Notification for
> draft-takahashi-mile-jsoniodef-00.txt
> 
> 
> A new version of I-D, draft-takahashi-mile-jsoniodef-00.txt
> has been successfully submitted by Takeshi Takahashi and posted to the IETF
> repository.
> 
> Name:		draft-takahashi-mile-jsoniodef
> Revision:	00
> Title:		JSON representation of IODEF
> Document date:	2016-06-08
> Group:		Individual Submission
> Pages:		58
> URL:
> https://www.ietf.org/internet-drafts/draft-takahashi-mile-jsoniodef-00
> .txt
> Status:
> https://datatracker.ietf.org/doc/draft-takahashi-mile-jsoniodef/
> Htmlized:
> https://tools.ietf.org/html/draft-takahashi-mile-jsoniodef-00
> 
> 
> Abstract:
>    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.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat