Skip to main content

BGP MULTI_EXIT_DISC (MED) Considerations
RFC 4451

Revision differences

Document history

Date By Action
2026-05-20
(System) Changed metadata: changed keywords to '['border gateway protocol']' from '[]'
2026-05-20
(System) Metadata update from RFC Editor
2026-05-20
(System) Changed author "V. Gill": changed name from "Vijay Gill" to "V. Gill", changed order from "1" to "2"
2026-05-20
(System)
Changed author "D. McPherson": changed name from "Danny McPherson" to "D. McPherson", changed affiliation from "Arbor Networks" to "Arbor Networks, Inc.", changed order from "0" …
Changed author "D. McPherson": changed name from "Danny McPherson" to "D. McPherson", changed affiliation from "Arbor Networks" to "Arbor Networks, Inc.", changed order from "0" to "1"
2026-05-20
(System) Metadata update from RFC Editor
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'The BGP MULTI_EXIT_DISC (MED) attribute provides a mechanism for BGP speakers to convey to an adjacent …
Received changes through RFC Editor sync (changed abstract to '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.')
2006-03-14
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2006-03-14
Amy Vezza [Note]: 'RFC 4451' added by Amy Vezza
2006-03-10
(System) RFC published