RFC 5004: Avoid BGP Best Path Transitions from One External to Another
In plain English — editorial summary, not part of the RFC
In this document, we propose an extension to the BGP route selection rules that would avoid unnecessary best path transitions between external paths under certain conditions. The proposed extension would help the overall network stability, and more importantly, would eliminate certain BGP route oscillations in which more than one external path from one BGP speaker contributes to the churn. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5004
- Published
- September 2007
- Authors
- E. Chen; S. Sangli
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5065Autonomous System Confederations for BGPUpdated
August 2007
- RFC 4893BGP Support for Four-octet AS Number SpaceObsoleted
May 2007
- RFC 4781Graceful Restart Mechanism for BGP with MPLSCurrent
January 2007
- RFC 4761Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and SignalingUpdated
January 2007
- RFC 4760Multiprotocol Extensions for BGP-4Updated
January 2007
- RFC 4724Graceful Restart Mechanism for BGPUpdated
January 2007
- RFC 5292Address-Prefix-Based Outbound Route Filter for BGP-4Current
August 2008
- RFC 4659BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPNCurrent
September 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?