RFC 6545: Real-time Inter-network Defense (RID)
In plain English — editorial summary, not part of the RFC
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. Service 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. This document obsoletes RFC 6045. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6545
- Published
- April 2012
- Authors
- K. Moriarty
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 84
- Also known as
- —
- Obsoletes:
- RFC 6045
Topics
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 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 6542Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Channel Binding Hash AgilityCurrent
March 2012
- RFC 6560One-Time Password (OTP) Pre-AuthenticationCurrent
April 2012
- RFC 6520Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) Heartbeat ExtensionUpdated
February 2012
- RFC 6595A Simple Authentication and Security Layer (SASL) and GSS-API Mechanism for the Security Assertion Markup Language (SAML)Current
April 2012
- RFC 6613RADIUS over TCPUpdated
May 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?