BGP Connection Collision Avoidance
draft-chen-bgp-avoid-collision-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2003-09-16 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-chen-bgp-avoid-collision-00.txt
Abstract
To simplify the BGP session bringup logic, in this document we propose a revision that allows a BGP speaker to play only the active or the passive role in establishing a BGP connection with another BGP speaker. A BGP speaker determines whether it will play the active or passive role based on the AS numbers and/or the peering addresses involved.
Authors
Enke Chen
(enkechen@cisco.com)
Jenny Yuan
(jenny@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)