[Idr] FW: New Version Notification for draft-li-idr-sr-policy-path-mtu-03.txt

"Chengli (Cheng Li)" <chengli13@huawei.com> Wed, 06 November 2019 13:29 UTC

Return-Path: <chengli13@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1F5512010C for <idr@ietfa.amsl.com>; Wed, 6 Nov 2019 05:29:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EKZccmtH4WhP for <idr@ietfa.amsl.com>; Wed, 6 Nov 2019 05:29:19 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 9720412089D for <idr@ietf.org>; Wed, 6 Nov 2019 05:29:19 -0800 (PST)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 796582E57C609860C958 for <idr@ietf.org>; Wed, 6 Nov 2019 13:29:17 +0000 (GMT)
Received: from lhreml712-chm.china.huawei.com (10.201.108.63) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 6 Nov 2019 13:29:16 +0000
Received: from lhreml712-chm.china.huawei.com (10.201.108.63) by lhreml712-chm.china.huawei.com (10.201.108.63) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 6 Nov 2019 13:29:17 +0000
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by lhreml712-chm.china.huawei.com (10.201.108.63) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Wed, 6 Nov 2019 13:29:16 +0000
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.172]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0439.000; Wed, 6 Nov 2019 21:29:08 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: 'idr wg' <idr@ietf.org>
Thread-Topic: New Version Notification for draft-li-idr-sr-policy-path-mtu-03.txt
Thread-Index: AQHVkjv/omz2zOIOIUG4bJfkVdTwcqd+IvsA
Date: Wed, 06 Nov 2019 13:29:08 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB02781A93@dggeml529-mbx.china.huawei.com>
References: <157278143529.13518.8813781234419670363.idtracker@ietfa.amsl.com>
In-Reply-To: <157278143529.13518.8813781234419670363.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.185.75]
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/OEM4CFay_FGpsPL4lotdJWcn3OY>
Subject: [Idr] FW: New Version Notification for draft-li-idr-sr-policy-path-mtu-03.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: Wed, 06 Nov 2019 13:29:21 -0000

Hi IDRers,

We submitted a new revision of draft-li-idr-sr-policy-path-mtu-03.txt.

This document defines extensions to BGP to distribute path MTU information within SR policies.
Because in SR, PMTU is not available due to not signaling protocol. But PMTU is needed for checking the packet size exceeds the PMTU or not.

Since the content is stable and mature, also, Huawei is implementing, we request for WG review and adoption.

Any comments and questions are welcome! 

Thanks,
Cheng




-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Sunday, November 03, 2019 7:44 PM
To: Ahmed El Sawaf <aelsawaf.c@stc.com.sa>; YongQing Zhu <zhuyq.gd@chinatelecom.cn>; Yongqing Zhu <zhuyq.gd@chinatelecom.cn>; Chengli (Cheng Li) <chengli13@huawei.com>; Lizhenbin <lizhenbin@huawei.com>
Subject: New Version Notification for draft-li-idr-sr-policy-path-mtu-03.txt


A new version of I-D, draft-li-idr-sr-policy-path-mtu-03.txt
has been successfully submitted by Cheng Li and posted to the IETF repository.

Name:		draft-li-idr-sr-policy-path-mtu
Revision:	03
Title:		Segment Routing Path MTU in BGP
Document date:	2019-11-03
Group:		Individual Submission
Pages:		8
URL:            https://www.ietf.org/internet-drafts/draft-li-idr-sr-policy-path-mtu-03.txt
Status:         https://datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-mtu/
Htmlized:       https://tools.ietf.org/html/draft-li-idr-sr-policy-path-mtu-03
Htmlized:       https://datatracker.ietf.org/doc/html/draft-li-idr-sr-policy-path-mtu
Diff:           https://www.ietf.org/rfcdiff?url2=draft-li-idr-sr-policy-path-mtu-03

Abstract:
   Segment Routing is a source routing paradigm that explicitly
   indicates the forwarding path for packets at the ingress node.  An SR
   policy is a set of candidate SR paths consisting of one or more
   segment lists with necessary path attributes.  However, the path
   maximum transmission unit (MTU) information for SR path is not
   available in the SR policy since the SR does not require signaling.
   This document defines extensions to BGP to distribute path MTU
   information within SR policies.

                                                                                  


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