RFC 6045: Real-time Inter-network Defense (RID)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6545.
Current version: RFC 6545 — Real-time Inter-network Defense (RID)
In plain English — editorial summary, not part of the RFC
Network security incidents, such as system compromises, worms, viruses, phishing incidents, and denial of service, typically result in the loss of service, data, and resources both human and system. Network providers and Computer Security Incident Response Teams need to be equipped and ready to assist in communicating and tracing security incidents with tools and procedures in place before the occurrence of an attack. Real-time Inter-network Defense (RID) outlines a proactive inter-network communication method to facilitate sharing incident handling data while integrating existing detection, tracing, source identification, and mitigation mechanisms for a complete incident handling solution. Combining these capabilities in a communication system provides a way to achieve higher security levels on networks. Policy guidelines for handling incidents are recommended and can be agreed upon by a consortium using the security recommendations and considerations. RID has found use within the international research communities, but has not been widely adopted in other sectors. This publication provides the specification to those communities that have adopted it, and communities currently considering solutions for real-time inter-network defense. The specification may also accelerate development of solutions where different transports or message formats are required by leveraging the data elements and structures specified here. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6045
- Published
- November 2010
- Authors
- K. Moriarty
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 75
- Also known as
- —
- Obsoleted by:
- RFC 6545
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 6046Transport of Real-time Inter-network Defense (RID) MessagesObsoleted
November 2010
- RFC 6546Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLSCurrent
April 2012
- 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
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?