[Idr] I-D Action: draft-ietf-idr-bgp-ls-link-mtu-12.txt
internet-drafts@ietf.org Thu, 21 May 2026 02:02 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@mail2.ietf.org
Received: from [10.244.11.249] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 82AEBF216AF4; Wed, 20 May 2026 19:02:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779328952; bh=ldNvGWP22TGAYWYWBisevfjoVawxwFMIBpN+MXwTFcY=; h=From:To:Cc:Subject:Reply-To:Date; b=IV5fc84NajMW5BRaulSBfgQ2OgM8HtPyOfuT+NSRIe3SczvE9yMtMJDCPJqBqC1EP kfjC1RDGWbvdJpIXkibyx3RXr4KzYQVcOuLSf5NLk1VRE8usFqEHvzOa/zJskLySp1 9iLFG0W2tdZQ4NdFzov6aZOWDYp+K/KzWsEDvGJE=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.65.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <177932895235.1103.9565510052860886829@dt-datatracker-6995bf6b4c-lv9zr>
Date: Wed, 20 May 2026 19:02:32 -0700
Message-ID-Hash: YXRTOTDJJ5QTE7G5LHKOYXGE2V32YD7W
X-Message-ID-Hash: YXRTOTDJJ5QTE7G5LHKOYXGE2V32YD7W
X-MailFrom: internet-drafts@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: idr@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-ls-link-mtu-12.txt
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/7TYH3LDEPl7gfMxaRGRZP3wCGMk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>
Internet-Draft draft-ietf-idr-bgp-ls-link-mtu-12.txt is now available. It is a
work item of the Inter-Domain Routing (IDR) WG of the IETF.
Title: Signaling Maximum Transmission Unit (MTU) using BGP-LS
Authors: Yongqing Zhu
Zhibo Hu
Shuping Peng
Robbins Mwehaire
Name: draft-ietf-idr-bgp-ls-link-mtu-12.txt
Pages: 9
Dates: 2026-05-20
Abstract:
Segment Routing (SR) leverages the source routing paradigm, which can
be directly applied to the MPLS architecture and IPv6 architecture,
with a new type of routing header. Since multiple labels or SRv6
SIDs are pushed in the packets, it is more likely that the packet
size exceeds the path MTU of SR tunnel. However, SR uses the IGP as
the routing protocol and does not support the negotiation of the Path
MTU.
BGP Link State (BGP-LS) describes a mechanism by which link-state and
TE information can be collected from networks and shared with
external components using the BGP routing protocol. This document
specifies the extensions to BGP-LS to carry MTU information of link.
The centralized controller (PCE/SDN) calculates the Path MTU while
completing the service path calculation based on the information
transmitted by the BGP-LS.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-link-mtu/
There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ls-link-mtu-12
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-idr-bgp-ls-link-mtu-12
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
- [Idr] I-D Action: draft-ietf-idr-bgp-ls-link-mtu-… internet-drafts