RFC 4451: BGP MULTI_EXIT_DISC (MED) Considerations
In plain English — editorial summary, not part of the RFC
The BGP MULTI_EXIT_DISC (MED) attribute provides a mechanism for BGP speakers to convey to an adjacent AS the optimal entry point into the local AS. While BGP MEDs function correctly in many scenarios, a number of issues may arise when utilizing MEDs in dynamic or complex topologies. This document discusses implementation and deployment considerations regarding BGP MEDs and provides information with which implementers and network operators should be familiar. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4451
- Published
- March 2006
- Authors
- D. McPherson; V. Gill
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 13
- 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 4264BGP WedgiesCurrent
November 2005
- RFC 4098Terminology for Benchmarking BGP Device Convergence in the Control PlaneCurrent
June 2005
- RFC 4486Subcodes for BGP Cease Notification MessageUpdated
April 2006
- RFC 4278Standards Maturity Variance Regarding the TCP MD5 Signature Option (RFC 2385) and the BGP-4 SpecificationCurrent
January 2006
- RFC 4277Experience with the BGP-4 ProtocolCurrent
January 2006
- RFC 4276BGP-4 Implementation ReportCurrent
January 2006
- RFC 4275BGP-4 MIB Implementation SurveyCurrent
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?