Maximum Transmission Unit Extended Community for BGP-4
draft-zeng-idr-bgp-mtu-extension-02

 
Document Type Expired Internet-Draft (individual)
Last updated 2012-09-09 (latest revision 2012-03-08)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-zeng-idr-bgp-mtu-extension-02.txt

Abstract

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.

Authors

Qing Zeng (zengqing@huawei.com)
Jie Dong (jie.dong@huawei.com)

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