Return-Path: 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 B1C1D3A1396 for ; Fri, 3 Apr 2020 00:53:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 hzDhKqzwdZDf for ; Fri, 3 Apr 2020 00:53:15 -0700 (PDT) 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 F18453A1395 for ; Fri, 3 Apr 2020 00:53:14 -0700 (PDT) Received: from lhreml705-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 9344D3498047EB769786 for ; Fri, 3 Apr 2020 08:53:13 +0100 (IST) Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Fri, 3 Apr 2020 08:53:12 +0100 Received: from DGGEMM423-HUB.china.huawei.com (10.1.198.40) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Fri, 3 Apr 2020 08:53:12 +0100 Received: from DGGEMM529-MBS.china.huawei.com ([169.254.14.174]) by dggemm423-hub.china.huawei.com ([10.1.198.40]) with mapi id 14.03.0487.000; Fri, 3 Apr 2020 15:53:08 +0800 From: Huzhibo To: Susan Hares , 'IDR List' Thread-Topic: [Idr] WG Adoption - draft-li-idr-sr-policy-path-mtu-03.txt - 2 Week WG adoption call (3/30 - 4/13) Thread-Index: AdYGjhUttAt3lPHsTfmnpSciWcUkAAC/aB4Q Date: Fri, 3 Apr 2020 07:53:08 +0000 Message-ID: <06CF729DA0D6854E8C1E5121AC3330DFAF5D9355@dggemm529-mbs.china.huawei.com> References: <01a201d6068f$c1f3aaf0$45db00d0$@ndzh.com> In-Reply-To: <01a201d6068f$c1f3aaf0$45db00d0$@ndzh.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.108.202.126] Content-Type: multipart/alternative; boundary="_000_06CF729DA0D6854E8C1E5121AC3330DFAF5D9355dggemm529mbschi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: [Idr] =?gb2312?b?tPC4tDogIFdHIEFkb3B0aW9uIC0gZHJhZnQtbGktaWRy?= =?gb2312?b?LXNyLXBvbGljeS1wYXRoLW10dS0wMy50eHQgLSAyIFdlZWsgV0cgYWRvcHRp?= =?gb2312?b?b24gY2FsbCAoMy8zMCAtIDQvMTMp?= X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2020 07:53:17 -0000 --_000_06CF729DA0D6854E8C1E5121AC3330DFAF5D9355dggemm529mbschi_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 VHJhZGl0aW9uYWwgTVBMUyB1c2VzIHRoZSBMRFAgLyBSU1ZQIHByb3RvY29sIHRvIG9idGFpbiB0 aGUgUGF0aCBNVFUuIFNlZ21lbnQgUm91dGluZyByZW1vdmVzIHRoZSBMRFAgLyBSU1ZQIHByb3Rv Y29sIGFuZCByZXF1aXJlcyBhIG5ldyBtZWNoYW5pc20gdG8gY2FsY3VsYXRlIHRoZSBQYXRoIE1U VS4NClN1cHBvcnQgQWRhcHRpb24uDQoNClRoYW5rcw0KDQpaaGlibyBIdQ0KDQq3orz+yMs6IElk ciBbbWFpbHRvOmlkci1ib3VuY2VzQGlldGYub3JnXSC0+rHtIFN1c2FuIEhhcmVzDQq3osvNyrG8 5DogMjAyMMTqM9TCMzDI1SAyMDozNg0KytW8/sjLOiAnSURSIExpc3QnIDxpZHJAaWV0Zi5vcmc+ DQrW98ziOiBbSWRyXSBXRyBBZG9wdGlvbiAtIGRyYWZ0LWxpLWlkci1zci1wb2xpY3ktcGF0aC1t dHUtMDMudHh0IC0gMiBXZWVrIFdHIGFkb3B0aW9uIGNhbGwgKDMvMzAgLSA0LzEzKQ0KDQpUaGlz IGJlZ2lucyBhIDIgd2VlayBXRyBhZG9wdGlvbiBjYWxsIGZvciBkcmFmdC1saS1pZHItc3ItcG9s aWN5LXBhdGgtbXR1LTAzLnR4dA0KDQpZb3UgY2FuIHZpZXcgdGhpcyBkcmFmdCBhdDoNCmh0dHBz Oi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWxpLWlkci1zci1wb2xpY3ktcGF0aC1t dHUvDQoNClRoaXMgZHJhZnQgZGlzdHJpYnV0ZXMgcGF0aCBtYXhpbXVtIHRyYW5zbWlzc2lvbiB1 bml0IGZvciB0aGUNClNSIHBvbGljeSB2aWEgQkdQLg0KDQpBbnkgZGlzY3Vzc2lvbiByZWdhcmRp bmcgb24gd2hldGhlciBvbmUgZGVzaXJlcw0KU1IgUG9saWN5IHNob3VsZCBiZSBjbGVhcmx5IGRp c3Rpbmd1aXNoZWQgZnJvbSB0aGUNClRlY2huaWNhbCBkaXNjdXNzaW9ucyBvbiB0aGUgbWVjaGFu aXNtcyB0byBwYXNzIFNSIHBvbGljeSBNVFUuDQoNClRoZSBxdWVzdGlvbnMgZm9yIHRoZSBwZW9w bGUgdG8gZGlzY3VzcyBvbiB0aGlzIGRyYWZ0IGFyZToNCg0KMSkgSXMgdGhlcmUgYSBuZWVkIGZv ciB0aGlzIG1lY2hhbmlzbSBpbiBuZXR3b3JrcyB1c2luZw0KICAgICAgICBNUExTLVNSIG9yIFNS LVY2IGFuZCBTUiBwb2xpY3k/DQoNCjIpIEFyZSB0aGVyZSBhbnkgZXJyb3IgaGFuZGxpbmcgaXNz dWVzIGJlc2lkZXMgd2hhdCBpcyBiZWluZw0KICAgICBUYWtlbiBjYXJlIG9mIGluIFJGQzc3NTJi aXMtMDMudHh0DQoNCjMpIERvIHlvdSB0aGluayB0aGlzIGRyYWZ0IGlzIHJlYWR5IHRvIGJlIGFk b3B0ZWQ/DQogICAgIEluIHRoaXMgY2F0ZWdvcnksIHBsZWFzZSBsaXN0IGFueSBjb25jZXJucyB5 b3UgaGF2ZQ0KICAgICByZWdhcmRpbmcgYWRvcHRpb24uICBUaGlzIGNhdGVnb3J5IGNhbiBpbmNs dWRlDQogICAgIGdlbmVyYWwgY29uY2VybnMgYWJvdXQgQkdQLUxTLCBNUExTLVNSLA0KICAgIFNS LVY2LCBhbmQgU1ItUG9saWN5Lg0KDQpDaGVlcnMsIFN1ZSBIYXJlcw0KDQoNCg0KDQoNCg== --_000_06CF729DA0D6854E8C1E5121AC3330DFAF5D9355dggemm529mbschi_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Traditional MPLS uses the LDP / RSVP protocol to obtain the Path = MTU. Segment Routing removes the LDP / RSVP protocol and requires a new mec= hanism to calculate the Path MTU.

Support Adaption.

 

Thanks

 

Zhibo Hu

 

=B7=A2=BC=FE=C8=CB:= Idr [mailto:idr-bounces@ietf.org] =B4=FA=B1=ED Susan Hares
=B7=A2=CB=CD=CA=B1=BC=E4:= 2020=C4=EA3=D4=C230=C8=D5 20:36
=CA=D5=BC=FE=C8=CB: 'IDR List' <idr@ietf.org>
=D6=F7=CC=E2: [Idr] WG Adoption - draft-li-idr-sr-policy-path-mtu-03.txt - 2 Week WG ad= option call (3/30 - 4/13)

 

This begins a 2 week WG adoptio= n call for draft-li-idr-sr-policy-path-mtu-03.txt

 

You can view this draft at:

https://datatracker.ietf.org= /doc/draft-li-idr-sr-policy-path-mtu/

 

This draft distributes path max= imum transmission unit for the

SR policy via BGP.  <= /o:p>

 

Any discussion regarding on whe= ther one desires

SR Policy should be clearly dis= tinguished from the

Technical discussions on the me= chanisms to pass SR policy MTU.

 

The questions for the people to= discuss on this draft are:

 

1) Is there a need for this mec= hanism in networks using

     &= nbsp;  MPLS-SR or SR-V6 and SR policy?

 

2) Are there any error handling= issues besides what is being

     T= aken care of in RFC7752bis-03.txt

 

3) Do you think this draft is r= eady to be adopted?

     I= n this category, please list any concerns you have

     regard= ing adoption.  This category can include

     g= eneral concerns about BGP-LS, MPLS-SR,

    SR-V6, = and SR-Policy.   

 

Cheers, Sue Hares  

 

 

 

 

 

--_000_06CF729DA0D6854E8C1E5121AC3330DFAF5D9355dggemm529mbschi_--