RFC 6685: Expert Review for Incident Object Description Exchange Format (IODEF) Extensions in IANA XML Registry
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
This document specifies restrictions on additions to the subset of the IANA XML Namespace and Schema registries, to require Expert Review for extensions to Incident Object Description Exchange Format (IODEF). [STANDARDS-TRACK]
Document record
- Document ID
- RFC6685
- Published
- July 2012
- Authors
- B. Trammell
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 3
- 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
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6684Guidelines and Template for Defining Extensions to the Incident Object Description Exchange Format (IODEF)Current
July 2012
- RFC 8134Management Incident Lightweight Exchange (MILE) Implementation ReportCurrent
May 2017
- RFC 6680Generic Security Service Application Programming Interface (GSS-API) Naming ExtensionsCurrent
August 2012
- RFC 6678Requirements for a Tunnel-Based Extensible Authentication Protocol (EAP) MethodCurrent
July 2012
- RFC 6677Channel-Binding Support for Extensible Authentication Protocol (EAP) MethodsCurrent
July 2012
- RFC 6696EAP Extensions for the EAP Re-authentication Protocol (ERP)Current
July 2012
- RFC 6697Handover Keying (HOKEY) Architecture DesignCurrent
July 2012
- RFC 6698The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSAUpdated
August 2012
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?