BGP Security Requirements
draft-christian-bgpsecrec-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Blaine Christian | ||
| Last updated | 2004-10-25 | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
The security of BGP is critical to the continued health and well being of internetworking. While securing a link between two BGP peers is a relatively easy technical matter, the manner in which to do so is not standard. Additionally, a secure link does not provide security or authentication of the routes updates themselves. In this document, we describe a set of requirements for securing BGP is described, both in the areas of peering relationships and prefix authentication.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)