RFC 6046: Transport of Real-time Inter-network Defense (RID) Messages
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6546.
Current version: RFC 6546 — Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLS
In plain English — editorial summary, not part of the RFC
The Incident Object Description Exchange Format (IODEF) defines a common XML format for document exchange, and Real-time Inter-network Defense (RID) defines extensions to IODEF intended for the cooperative handling of security incidents within consortia of network operators and enterprises. This document specifies a transport protocol for RID based upon the passing of RID messages over HTTP/TLS (Transport Layer Security). This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6046
- Published
- November 2010
- Authors
- K. Moriarty; B. Trammell
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 6546
Topics
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 6045Real-time Inter-network Defense (RID)Obsoleted
November 2010
- RFC 5941Sharing Transaction Fraud DataCurrent
August 2010
- RFC 5070The Incident Object Description Exchange FormatObsoleted
December 2007
- RFC 7203An Incident Object Description Exchange Format (IODEF) Extension for Structured Cybersecurity InformationCurrent
April 2014
- RFC 7495Enumeration Reference Format for the Incident Object Description Exchange Format (IODEF)Current
March 2015
- RFC 7970The Incident Object Description Exchange Format Version 2Current
November 2016
- RFC 8134Management Incident Lightweight Exchange (MILE) Implementation ReportCurrent
May 2017
- RFC 8600Using Extensible Messaging and Presence Protocol (XMPP) for Security Information ExchangeCurrent
June 2019
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?