[Idr] 回复: FW: 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]

"licong.bri@chinatelecom.cn" <licong.bri@chinatelecom.cn> Tue, 15 October 2019 04:18 UTC

Return-Path: <licong.bri@chinatelecom.cn>
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 A8CA2120018 for <idr@ietfa.amsl.com>; Mon, 14 Oct 2019 21:18:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 i_0q_TepdHLB for <idr@ietfa.amsl.com>; Mon, 14 Oct 2019 21:18:47 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.227]) by ietfa.amsl.com (Postfix) with ESMTP id 2AE61120048 for <idr@ietf.org>; Mon, 14 Oct 2019 21:18:45 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.80:34582.1997499030
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.78?logid-177982820D8B4780A16646DF832838E8 (unknown [172.18.0.80]) by chinatelecom.cn (HERMES) with SMTP id A73FE280092 for <idr@ietf.org>; Tue, 15 Oct 2019 12:18:35 +0800 (CST)
X-189-SAVE-TO-SEND: licong.bri@chinatelecom.cn
Received: from ([172.18.0.80]) by App0022 with ESMTP id 177982820D8B4780A16646DF832838E8 for idr@ietf.org; Tue Oct 15 12:18:38 2019
X-Transaction-ID: 177982820D8B4780A16646DF832838E8
X-filter-score: filter<0>
X-Real-From: licong.bri@chinatelecom.cn
X-Receive-IP: 172.18.0.80
X-MEDUSA-Status: 0
Date: Tue, 15 Oct 2019 12:18:31 +0800
From: "licong.bri@chinatelecom.cn" <licong.bri@chinatelecom.cn>
To: idr <idr@ietf.org>
References: <016601d56d75$e3756320$aa602960$@ndzh.com>, <C7C2E1C43D652C4E9E49FE7517C236CB02741095@dggeml529-mbx.china.huawei.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.10.151[cn]
Mime-Version: 1.0
Message-ID: <2019101512182981901122@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart230125702345_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/js3Wokr2GiAJyi6VETihFnakt9s>
Subject: [Idr] =?gb2312?b?u9i4tDogRlc6ICBBZG9wdGlvbjogZHJhZnQtbGktaWRy?= =?gb2312?b?LWJncC1scy1zci1wb2xpY3ktcGF0aC1zZWdtZW50LTAzLnR4dCBhbmQgZHJh?= =?gb2312?b?ZnQtbGktc3ItcG9saWN5LXBhdGgtc2VnbWVudC0wMS50eHQgWzkvMTcgdG8g?= =?gb2312?b?MTAvMS8yMDE5XQ==?=
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: Tue, 15 Oct 2019 04:18:51 -0000

Support these two drafts

Best Regards,
Cong Li
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Wednesday, September 18, 2019 12:35 AM
To: 'idr wg' <idr@ietf.org>
Subject: [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]
 
This begins a 2 week WG Adoption call two related drafts [9/17 to 10/1/2019] 
・         draft-li-bgp-ls-sr-policy-path-segment-03.txt and 
・         draft-li-idr-sr-policy-path-segment-01.txt. 
 
You can access these two drafts at the following location: 
 
https://datatracker.ietf.org/doc/draft-li-idr-bgp-ls-sr-policy-path-segment/
 
https://datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-segment/
 
The authors have pointed out that the adoption of this 
draft since the following  SR-MPLS Path Segment draft has been adopted: 
 
https://tools.ietf.org/html/draft-ietf-spring-mpls-path-segment-00
 
Please consider the following questions in your responses? 
 
1)      Should this SR Policy technology be included in BGP for SR-MPLS 
 
Spring has adopted the draft, but IDR can provide feedback 
to spring about putting this technology in BGP.
 
2)      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? 
 
 
Cheers, Susan Hares