BGP Operations and Security
draft-ietf-grow-bgpopsecupd-15
| Document | Type |
Expired Internet-Draft
(grow WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tobias Fiebig , Nick Hilliard | ||
| Last updated | 2026-10-09 (Latest revision 2026-04-07) | ||
| Replaces | draft-fiebig-grow-bgpopsecupd | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Consensus: Waiting for Write-Up | |
| Associated WG milestone |
|
||
| Document shepherd | Job Snijders | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | paolo@ntt.net, job@bsd.nl |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Border Gateway Protocol (BGP) is a critical component in the Internet to exchange routing information between network domains. It is important to understand the security and reliability requirements that can and should be met to prevent accidental or intentional routing disturbances. Previously, security considerations for BGP have been described in RFC7454 / BCP194. Since the publication of RFC7454, changes in operational practice have taken place, which are partially conflicting with the advice given in RFC7454. This document obsoletes RFC7454, and provides less implementation-specific best practices, with the goal of being less prone to becoming outdated or conflicting with changed operational practices.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)