Security Requirements for Routing Protocols
draft-puig-rpsec-generic-requirements-02
| Document | Type |
Expired Internet-Draft
(rpsec WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jean-Jacques Puig , Mohammed Achemlal , Emanuele Jones , Danny R. McPherson | ||
| Last updated | 2004-04-20 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Routing protocols are subject to threats and attacks that can harm individual users or network operations as a whole. This document describes a generic set of security requirements for routing protocols and routing systems.
Authors
Jean-Jacques Puig
Mohammed Achemlal
Emanuele Jones
Danny R. McPherson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)