RFC 4264: BGP Wedgies
In plain English — editorial summary, not part of the RFC
It has commonly been assumed that the Border Gateway Protocol (BGP) is a tool for distributing reachability information in a manner that creates forwarding paths in a deterministic manner. In this memo we will describe a class of BGP configurations for which there is more than one potential outcome, and where forwarding states other than the intended state are equally stable. Also, the stable state where BGP converges may be selected by BGP in a non-deterministic manner. These stable, but unintended, BGP states are termed here "BGP Wedgies". This memo provides information for the Internet community.
Document record
- Document ID
- RFC4264
- Published
- November 2005
- Authors
- T. Griffin; G. Huston
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4384BGP Communities for Data CollectionCurrent
February 2006
- RFC 4098Terminology for Benchmarking BGP Device Convergence in the Control PlaneCurrent
June 2005
- RFC 4451BGP MULTI_EXIT_DISC (MED) ConsiderationsCurrent
March 2006
- RFC 4272BGP Security Vulnerabilities AnalysisCurrent
January 2006
- RFC 4273Definitions of Managed Objects for BGP-4Current
January 2006
- RFC 4274BGP-4 Protocol AnalysisCurrent
January 2006
- RFC 4275BGP-4 MIB Implementation SurveyCurrent
January 2006
- RFC 4276BGP-4 Implementation ReportCurrent
January 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?