BGP Security Requirements
draft-ietf-rpsec-bgpsecrec-10
| Document | Type |
Expired Internet-Draft
(rpsec WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Blaine Christian , Tony Tauber | ||
| Last updated | 2015-10-14 (Latest revision 2008-11-03) | ||
| 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 (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | David Ward | ||
| 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, the Border Gateway Protocol, is critical to the proper operation of large-scale internetworks, both public and private. While securing the information transmitted between two BGP speakers is a relatively easy technical matter, securing BGP, as a routing system, is more complex. This document describes a set of requirements for securing BGP and the routing information carried within BGP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)