[Idr] Re： 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]

wangjl50 <wangjl50@chinatelecom.cn> Fri, 27 September 2019 01:45 UTC

HMM_SOURCE_IP: 172.18.0.80:44835.1118499336
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.78?logid-FB5515E67EAF4B21B45583EBC4C18785 (unknown [172.18.0.80]) by chinatelecom.cn (HERMES) with SMTP id 253A72800B6; Fri, 27 Sep 2019 09:45:04 +0800 (CST)
X-189-SAVE-TO-SEND: 71069678@chinatelecom.cn
Received: from ([172.18.0.80]) by App0022 with ESMTP id FB5515E67EAF4B21B45583EBC4C18785 for shares@ndzh.com; Fri Sep 27 09:45:07 2019
X-Transaction-ID: FB5515E67EAF4B21B45583EBC4C18785
X-filter-score: filter<0>
X-Real-From: wangjl50@chinatelecom.cn
X-Receive-IP: 172.18.0.80
X-MEDUSA-Status: 0
Date: Fri, 27 Sep 2019 09:45:04 +0800
From: wangjl50 <wangjl50@chinatelecom.cn>
To: shares <shares@ndzh.com>, idr <idr@ietf.org>
References: <20190925100655689125227@chinatelecom.cn>, <f5sj2t-z2ave6y3n5mmqaxuso-umbbue-cgr5cp18ve20-waefj-iwiydfbtmao4-ah1nng3ke77c-igaa33-9jo94f-e7fuca-r8u231a3r0ln46r9ah-tho9nnz7yc7z-79xs0a-fzf07kkyjc5xh9hods.1569390909366@email.android.com>, <20190925140543100911237@chinatelecom.cn>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.12.322[cn]
Mime-Version: 1.0
Message-ID: <2019092620313102674116@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart627177468777_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/TI3ZwqGxeXxIIYrP_X49crxTM8I>
Subject: [Idr] Re： 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 <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: Fri, 27 Sep 2019 01:45:16 -0000

Support the adoption. 

Best regards,
Jianglong Wang

From: Susan Hares
Date: 2019-09-18 00:35
To: 'idr wg'
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

[Idr] Re： Adoption: draft-li-idr-bgp-ls-sr-policy… wangjl50