Skip to main content

Protecting the Router Control Plane
RFC 6192

Revision differences

Document history

Date By Action
2020-01-21
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This memo provides a method for protecting a router's control plane from undesired or malicious traffic. …
Received changes through RFC Editor sync (changed abstract to '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.')
2015-10-14
(System) Notify list changed from opsec-chairs@ietf.org, draft-ietf-opsec-protect-control-plane@ietf.org to (None)
2014-12-05
(System) Posted related IPR disclosure: Cisco's Statement of IPR Related to RFC 6192
2011-03-31
Cindy Morgan State changed to RFC Published from RFC Ed Queue.
2011-03-31
Cindy Morgan [Note]: 'RFC 6192' added
2011-03-30
(System) RFC published