The Requirements for Secure Routing
draft-chen-secure-routing-requirements-01
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Meiling Chen , Li Su | ||
| Last updated | 2023-09-10 (Latest revision 2023-03-09) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Both ISPs and users have put forward requirements for secure routing, the scenarios are analyzed in the draft draft-chen-secure-routing- use-cases. This draft analyzes the functions required to implement secure routing. Attack detection and users security requirements translateion are out of scope.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)