RFC 8727: JSON Binding of the Incident Object Description Exchange Format
In plain English — editorial summary, not part of the RFC
The Incident Object Description Exchange Format (IODEF) defined in RFC 7970 provides an information model and a corresponding XML data model for exchanging incident and indicator information. This document gives implementers and operators an alternative format to exchange the same information by defining an alternative data model implementation in JSON and its encoding in Concise Binary Object Representation (CBOR).
Document record
- Document ID
- RFC8727
- Published
- August 2020
- Authors
- T. Takahashi; R. Danyliw; M. Suzuki
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 88
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8600Using Extensible Messaging and Presence Protocol (XMPP) for Security Information ExchangeCurrent
June 2019
- RFC 8935Push-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 8936Poll-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 8417Security Event Token (SET)Current
July 2018
- RFC 8414OAuth 2.0 Authorization Server MetadataCurrent
June 2018
- RFC 8392CBOR Web Token (CWT)Current
May 2018
- RFC 9101The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)Current
August 2021
- RFC 8134Management Incident Lightweight Exchange (MILE) Implementation ReportCurrent
May 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?