Sign in
Version 5.13.0, 2015-03-25
Report a bug

Maximum Transmission Unit Extended Community for BGP-4

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2012-09-09 (latest revision 2012-03-08)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:


Proper functioning of path Maximum Transmission Unit (MTU) discovery [RFC1191] requires that IP routers have knowledge of the MTU for each link to which they are connected. As MPLS progresses, [RFC3988] specifies extensions to LDP in support of LDP LSP MTU discovery. For the LSP created using Border Gateway Protocol (BGP) [RFC3107], it does not have the ability to signal the path MTU to the ingress Label Switching Router (LSR). In the absence of this functionality, the MTU for the BGP LSP must be statically configured by network operators or by equivalent off-line mechanisms. This document defines the MTU Extended Community for BGP in support of BGP LSP MTU discovery.


Qing Zeng <>
Jie Dong <>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)