[Idr] FW: New Version Notification for draft-zhu-idr-bgp-ls-path-mtu-04.txt

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Mon, 10 August 2020 06:41 UTC

Return-Path: <pengshuping@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 7117F3A141A; Sun, 9 Aug 2020 23:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id HJKa46mmtQh4; Sun, 9 Aug 2020 23:41:52 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 842223A0E8B; Sun, 9 Aug 2020 23:41:52 -0700 (PDT)
Received: from lhreml719-chm.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 9293B9C8E3A0DA56D0EB; Mon, 10 Aug 2020 07:41:50 +0100 (IST)
Received: from lhreml719-chm.china.huawei.com ( by lhreml719-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 10 Aug 2020 07:41:50 +0100
Received: from DGGEML405-HUB.china.huawei.com ( by lhreml719-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Mon, 10 Aug 2020 07:41:50 +0100
Received: from DGGEML532-MBX.china.huawei.com ([]) by dggeml405-hub.china.huawei.com ([]) with mapi id 14.03.0487.000; Mon, 10 Aug 2020 14:41:43 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "idr@ietf.org" <idr@ietf.org>
CC: "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Thread-Topic: New Version Notification for draft-zhu-idr-bgp-ls-path-mtu-04.txt
Thread-Index: AQHWbsorPkbY8uy6t0mfdoUZfSUxIqkwtt/w
Date: Mon, 10 Aug 2020 06:41:43 +0000
Message-ID: <4278D47A901B3041A737953BAA078ADE19274CD2@DGGEML532-MBX.china.huawei.com>
References: <159703175291.14024.7598117612296708735@ietfa.amsl.com>
In-Reply-To: <159703175291.14024.7598117612296708735@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/yK_etrYrS1PrMRRea20qBB1uVd0>
Subject: [Idr] FW: New Version Notification for draft-zhu-idr-bgp-ls-path-mtu-04.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Aug 2020 06:41:58 -0000

Dear IDR folks, 

We have updated the draft, https://tools.ietf.org/html/draft-zhu-idr-bgp-ls-path-mtu-04. 

Thank all the colleagues who have commented on this draft during my presentation in IETF108. We have addressed all the comments in this new version. Please review. 

Since we have agreed that this is a nice feature to have, we would like to ask the WG to adopt this draft. 

Thank you!

Best regards, 

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, August 10, 2020 11:56 AM
To: Huzhibo <huzhibo@huawei.com>om>; Robbins Mwehaire <Robbins.Mwehair@mtn.com>om>; Yongqing Zhu <zhuyq8@chinatelecom.cn>cn>; Robbins Mwehair <robbins.mwehair@mtn.com>om>; Pengshuping (Peng Shuping) <pengshuping@huawei.com>
Subject: New Version Notification for draft-zhu-idr-bgp-ls-path-mtu-04.txt

A new version of I-D, draft-zhu-idr-bgp-ls-path-mtu-04.txt
has been successfully submitted by Shuping Peng and posted to the IETF repository.

Name:		draft-zhu-idr-bgp-ls-path-mtu
Revision:	04
Title:		BGP-LS Extensions for Advertising Path MTU
Document date:	2020-08-10
Group:		Individual Submission
Pages:		9
URL:            https://www.ietf.org/internet-drafts/draft-zhu-idr-bgp-ls-path-mtu-04.txt
Status:         https://datatracker.ietf.org/doc/draft-zhu-idr-bgp-ls-path-mtu/
Htmlized:       https://tools.ietf.org/html/draft-zhu-idr-bgp-ls-path-mtu-04
Htmlized:       https://datatracker.ietf.org/doc/html/draft-zhu-idr-bgp-ls-path-mtu
Diff:           https://www.ietf.org/rfcdiff?url2=draft-zhu-idr-bgp-ls-path-mtu-04

   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.  The centralized
   controller (PCE/SDN) completes the service path calculation based on
   the information transmitted by the BGP-LS and delivers the result to
   the Path Computation Client (PCC) through the PCEP or BGP protocol.

   Segment Routing (SR) leverages the source routing paradigm, which can
   be directly applied to the MPLS architecture with no change on the
   forwarding plane and applied to the IPv6 architecture, with a new
   type of routing header, called SRH.  The SR uses the IGP protocol as
   the control protocol.  Compared to the MPLS tunneling technology, the
   SR does not require additional signaling.  Therefore, the SR does not
   support the negotiation of the Path MTU.  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.

   This document specifies the extensions to BGP Link State (BGP-LS) to
   carry maximum transmission unit (MTU) messages of link.  The PCE/SDN
   calculates the Path MTU while completing the service path calculation
   based on the information transmitted by the BGP-LS.


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat