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 068C912011B for ; Wed, 25 Sep 2019 01:56:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.889 X-Spam-Level: X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] 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 kLNNpNVmDlAd for ; Wed, 25 Sep 2019 01:56:12 -0700 (PDT) Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.223]) by ietfa.amsl.com (Postfix) with ESMTP id ACC50120129 for ; Wed, 25 Sep 2019 01:56:10 -0700 (PDT) HMM_SOURCE_IP: 172.18.0.48:44028.2017113401 HMM_ATTACHE_NUM: 0000 HMM_SOURCE_TYPE: SMTP Received: from clientip-120.88.10.9?logid-186E698D1D274183ABE341C3349C5DBD (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 563D3280095 for ; Wed, 25 Sep 2019 16:56:04 +0800 (CST) X-189-SAVE-TO-SEND: 44093218@chinatelecom.cn Received: from ([172.18.0.48]) by App0024 with ESMTP id 186E698D1D274183ABE341C3349C5DBD for idr@ietf.org; Wed Sep 25 16:56:05 2019 X-Transaction-ID: 186E698D1D274183ABE341C3349C5DBD X-filter-score: filter<0> X-Real-From: chenhuan6@chinatelecom.cn X-Receive-IP: 172.18.0.48 X-MEDUSA-Status: 0 Date: Wed, 25 Sep 2019 16:56:02 +0800 From: "chenhuan6@chinatelecom.cn" To: "idr@ietf.org" References: <016601d56d75$e3756320$aa602960$@ndzh.com>, <20190923090020974231159@chinatelecom.cn>, <20190923164940832052191@chinatelecom.cn>, <20190925095649404552223@chinatelecom.cn>, <20190925103617200737229@chinatelecom.cn>, <20190925143633227040238@chinatelecom.cn> X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7.2.12.322[cn] Mime-Version: 1.0 Message-ID: <20190925165501706541245@chinatelecom.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart255366856621_=----" Archived-At: Subject: Re: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt [9/17 to 10/1/2019] 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: Wed, 25 Sep 2019 08:56:16 -0000 This is a multi-part message in MIME format. ------=_001_NextPart255366856621_=---- Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 U3VwcG9ydCB0aGUgV0cgYWRvcHRpb24gb2YgdGhlIHR3byBkcmFmdHMgYXMgdGhlIGNvLWF1dGhv ci4NClBhdGggU2VnbWVudCBwcm92aWRlcyB0aGUgaWRlbnRpZmljYXRpb24gb2YgdGhlIFNSIHBh dGguIEl0IHdpbGwgYmUgdXNlZnVsIGZvciBTUiBkZXBsb3ltZW50Lg0KQW5kIHRoZW4sIG9wZXJh dG9yIGNhbiBkbyB0aGUgU1IgcGVyZm9ybWFuY2UgbWVhc3VyZW1lbnQgYW5kIFNSIE9BTS4NCkJH UC1MUyBpcyBwb3B1bGFyIGZvciB0aGUgcm91dGVyLiBJdCdzIHdlbGNvbWUgdG8gdXNlIEJHUCBl eHRlbnNpb25zIGZvciB0aGUgUGF0aCBTZWdtZW50LCBhbmQgdGhlbiB0aGUgZGVwbG95bWVudCBp cyBlYXN5Lg0KQmVzdCByZWdhcmRzLg0KICBIVUFOQU4gQ0hFTu+8iOmZiOWNjuWNl++8iQ0KDQoN CkRhdGEgQ29tbXVuaWNhdGlvbiBSZXNlYXJjaCBEZXBhcnRtZW50DQpHdWFuZ2RvbmcgUmVzZWFy Y2ggSW5zdGl0dXRlIG9mIENoaW5hIFRlbGVjb20gQ28uLEx0ZC4NClRlbO+8mjAyMC0zODYzLTkz NDYNClBI77yaMTMzLTE2MDktNzE2Mw0KUVHvvJoxNzMzNTgzNw0KTWFpbO+8mmNoZW5odWFuNkBj aGluYXRlbGVjb20uY24gDQogDQpGcm9tOiBTdXNhbiBIYXJlcw0KRGF0ZTogMjAxOS0wOS0xOCAw MDozNQ0KVG86ICdpZHIgd2cnDQpTdWJqZWN0OiBbSWRyXSBBZG9wdGlvbjogZHJhZnQtbGktaWRy LWJncC1scy1zci1wb2xpY3ktcGF0aC1zZWdtZW50LTAzLnR4dCBhbmQgZHJhZnQtbGktc3ItcG9s aWN5LXBhdGgtc2VnbWVudC0wMS50eHQgWzkvMTcgdG8gMTAvMS8yMDE5XQ0KVGhpcyBiZWdpbnMg YSAyIHdlZWsgV0cgQWRvcHRpb24gY2FsbCB0d28gcmVsYXRlZCBkcmFmdHMgWzkvMTcgdG8gMTAv MS8yMDE5XSANCsK3ICAgICAgICAgZHJhZnQtbGktYmdwLWxzLXNyLXBvbGljeS1wYXRoLXNlZ21l bnQtMDMudHh0IGFuZCANCsK3ICAgICAgICAgZHJhZnQtbGktaWRyLXNyLXBvbGljeS1wYXRoLXNl Z21lbnQtMDEudHh0LiANCiANCllvdSBjYW4gYWNjZXNzIHRoZXNlIHR3byBkcmFmdHMgYXQgdGhl IGZvbGxvd2luZyBsb2NhdGlvbjogDQogDQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2Rv Yy9kcmFmdC1saS1pZHItYmdwLWxzLXNyLXBvbGljeS1wYXRoLXNlZ21lbnQvDQogDQpodHRwczov L2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1saS1pZHItc3ItcG9saWN5LXBhdGgtc2Vn bWVudC8NCiANClRoZSBhdXRob3JzIGhhdmUgcG9pbnRlZCBvdXQgdGhhdCB0aGUgYWRvcHRpb24g b2YgdGhpcyANCmRyYWZ0IHNpbmNlIHRoZSBmb2xsb3dpbmcgIFNSLU1QTFMgUGF0aCBTZWdtZW50 IGRyYWZ0IGhhcyBiZWVuIGFkb3B0ZWQ6IA0KIA0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1s L2RyYWZ0LWlldGYtc3ByaW5nLW1wbHMtcGF0aC1zZWdtZW50LTAwDQogDQpQbGVhc2UgY29uc2lk ZXIgdGhlIGZvbGxvd2luZyBxdWVzdGlvbnMgaW4geW91ciByZXNwb25zZXM/IA0KIA0KMSkgICAg ICBTaG91bGQgdGhpcyBTUiBQb2xpY3kgdGVjaG5vbG9neSBiZSBpbmNsdWRlZCBpbiBCR1AgZm9y IFNSLU1QTFMgDQogDQpTcHJpbmcgaGFzIGFkb3B0ZWQgdGhlIGRyYWZ0LCBidXQgSURSIGNhbiBw cm92aWRlIGZlZWRiYWNrIA0KdG8gc3ByaW5nIGFib3V0IHB1dHRpbmcgdGhpcyB0ZWNobm9sb2d5 IGluIEJHUC4NCiANCjIpICAgICAgSXMgdGhpcyB0ZWNobm9sb2d5IGEgZ29vZCB3YXkgdG8gaW1w bGVtZW50IHRoZSByZXF1aXJlZCANCkZlYXR1cmVzIGluIEJHUD8gDQogDQozKSAgICAgIElzIHRo aXMgdGVjaG5vbG9neSByZWFkeSBmb3IgYWRvcHRpb24/IA0KIA0KNCkgICAgICBEbyB5b3UgaGF2 ZSBhbnkgY29uY2VybnMgYWJvdXQgYWRvcHRpbmcgdGhpcyB0ZWNobm9sb2d5PyANCiANCiANCkNo ZWVycywgU3VzYW4gSGFyZXMgDQo= ------=_001_NextPart255366856621_=---- Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable = =0A

Support the WG adoption of&nbs= p;the two drafts as the co-author.

Path Segment provides the identification of th= e SR path. It will be useful for SR deployment.

And= then, operator can do the SR performance measurement and SR OAM.

BGP-LS is popular for the router. It's w= elcome to use BGP extensions for the Path Segment, and then the deployment= is easy.

Best regards.

=0A
  HUANAN CHEN=EF=BC=88=E9=99=88=E5= =8D=8E=E5=8D=97=EF=BC=89
=
<= /span>

Data Communication Research Department
Guangdong Research Institute of China Telec= om Co.,Ltd.
Tel=EF=BC=9A020-3863= -9346
PH=EF=BC=9A133-1609-7163
QQ=EF=BC=9A17335837
Mail=EF=BC=9Achenhuan6@chinatelecom.cn <= /div>
=0A
 
Date:=  2019-09-18 00:35
Subject: [Idr] Adoption: draft-li-idr-bgp-ls-s= r-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt [9= /17 to 10/1/2019]

This begins a 2 we= ek WG Adoption call two related drafts [9/17 to 10/1/2019]

=

=C2=B7    &nbs= p;    draft-l= i-bgp-ls-sr-policy-path-segment-03.txt and

=C2=B7       &n= bsp; draft-li-idr-sr-policy-= path-segment-01.txt.

 =

You can access these two drafts at th= e following location:

 = ;

https://datatracker.ietf.org/doc/draft-li-id= r-bgp-ls-sr-policy-path-segment/

 

https://datatracker.ietf.org/doc/draf= t-li-idr-sr-policy-path-segment/

 

The authors have point= ed out that the adoption of this

draft since the following  SR-MPLS Path Segment draft has been adopt= ed:

 

 

Please consider the following questions in your responses? <= o:p>

 

1) = ;     Should th= is SR Policy technology be included in BGP for SR-MPLS

 

Spring has adopted the draft, but IDR can p= rovide feedback

to spring about putting this technology in BGP.

 

2)    &nbs= p; Is this technology a good way to= implement the required

Features in BGP?

 

3)      Is this technology ready for adoption? =

 

4)      Do you have any concerns about adopting this technology?

 

 

C= heers, Susan Hares

=0A
=
=0A
=0A
=0A
=0A
=0A ------=_001_NextPart255366856621_=------