Protecting The Router Control Plane
draft-dugal-opsec-protect-control-plane-02
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2010-07-06 (latest revision 2010-02-23) | ||
| Replaced by | draft-ietf-opsec-protect-control-plane | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-opsec-protect-control-plane | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-dugal-opsec-protect-control-plane-02.txt
Abstract
This memo provides a method for protecting a router's control plane from undesired or malicious traffic. In this approach, all legitimate control plane traffic is identifed. Once legitimate traffic has been identified, a filter is deployed on the router's forwarding plane. That filter prevents traffic not specifically identified as legitimate from reaching the router's control plane.
Authors
David Dugal
(ddugal@juniper.net)
Carlos Pignataro
(cpignata@cisco.com)
Rodney Dunn
(rodunn@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)