Operational Requirements for Enhanced Error Handling Behaviour in BGP-4
draft-ietf-grow-ops-reqs-for-bgp-error-handling-07
| Document | Type | Expired Internet-Draft (grow WG) | |
|---|---|---|---|
| Last updated | 2015-10-14 (latest revision 2014-11-09) | ||
| Stream | IETF | ||
| Intended RFC status | Informational | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Reviews | |||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Joel Jaeggli | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-grow-ops-reqs-for-bgp-error-handling-07.txt
Abstract
BGP-4 is utilised as a key intra- and inter-Autonomous System routing protocol in modern IP networks. The failure modes as defined by the original protocol standards are based on a number of assumptions around the impact of session failure. Numerous incidents both in the global Internet routing table and within Service Provider networks have been caused by strict handling of a single invalid UPDATE message causing large-scale failures in one or more Autonomous Systems. This memo describes the current use of BGP-4 within Service Provider networks, and outlines a set of requirements for further work to enhance the mechanisms available to a BGP-4 implementation when erroneous data is detected. Whilst this document does not provide specification of any standard, it is intended as an overview of a set of enhancements to BGP-4 to improve the protocol's robustness to suit its current deployment.
Authors
Rob Shakir (rob.shakir@bt.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)