RFC 5070: The Incident Object Description Exchange Format
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7970.
Current document in this lineage: RFC 7970 — The Incident Object Description Exchange Format Version 2
In plain English — editorial summary, not part of the RFC
The Incident Object Description Exchange Format (IODEF) defines a data representation that provides a framework for sharing information commonly exchanged by Computer Security Incident Response Teams (CSIRTs) about computer security incidents. This document describes the information model for the IODEF and provides an associated data model specified with XML Schema. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5070
- Published
- December 2007
- Authors
- R. Danyliw; J. Meijer; Y. Demchenko
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 92
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 5070 (2007)
- RFC 6685 (2012)
- RFC 7970 (2016) ✓
Read the full history of The Incident Object Description Exchange Format Version 2 →
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7203An Incident Object Description Exchange Format (IODEF) Extension for Structured Cybersecurity InformationCurrent
April 2014
- RFC 6546Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLSCurrent
April 2012
- RFC 6045Real-time Inter-network Defense (RID)Obsoleted
November 2010
- RFC 6046Transport of Real-time Inter-network Defense (RID) MessagesObsoleted
November 2010
- RFC 2350Expectations for Computer Security Incident ResponseCurrent
June 1998
- RFC 5080Common Remote Authentication Dial In User Service (RADIUS) Implementation Issues and Suggested FixesCurrent
December 2007
- RFC 5081Using OpenPGP Keys for Transport Layer Security (TLS) AuthenticationObsoleted
November 2007
- RFC 5083Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content TypeCurrent
November 2007
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?