RFC 6192: Protecting the Router Control Plane
In plain English — editorial summary, not part of the RFC
This memo provides a method for protecting a router's control plane from undesired or malicious traffic. In this approach, all legitimate router control plane traffic is identified. Once legitimate traffic has been identified, a filter is deployed in the router's forwarding plane. That filter prevents traffic not specifically identified as legitimate from reaching the router's control plane, or rate-limits such traffic to an acceptable level. Note that the filters described in this memo are applied only to traffic that is destined for the router, and not to all traffic that is passing through the router. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6192
- Published
- March 2011
- Authors
- D. Dugal; C. Pignataro; R. Dunn
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5575Dissemination of Flow Specification RulesObsoleted
August 2009
- RFC 6092Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet ServiceCurrent
January 2011
- RFC 4890Recommendations for Filtering ICMPv6 Messages in FirewallsCurrent
May 2007
- RFC 8519YANG Data Model for Network Access Control Lists (ACLs)Current
March 2019
- RFC 9288Recommendations on the Filtering of IPv6 Packets Containing IPv6 Extension Headers at Transit RoutersCurrent
August 2022
- RFC 5661Network File System (NFS) Version 4 Minor Version 1 ProtocolObsoleted
January 2010
- RFC 5397WebDAV Current Principal ExtensionCurrent
December 2008
- RFC 4768Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 NamingCurrent
December 2006
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?