[Idr] 回复: Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/2019]

"Zhuyq" <zhuyq.gd@chinatelecom.cn> Tue, 15 October 2019 09:25 UTC

Return-Path: <zhuyq.gd@chinatelecom.cn>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E5B0B1200B2; Tue, 15 Oct 2019 02:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id c1hYReuAPc2M; Tue, 15 Oct 2019 02:25:48 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn []) by ietfa.amsl.com (Postfix) with ESMTP id 3CB9B120025; Tue, 15 Oct 2019 02:25:47 -0700 (PDT)
Received: from clientip- (unknown []) by chinatelecom.cn (HERMES) with SMTP id ECE69280090; Tue, 15 Oct 2019 17:25:39 +0800 (CST)
X-189-SAVE-TO-SEND: zhuyq.gd@chinatelecom.cn
Received: from ([]) by App0022 with ESMTP id 8C4A7BE571114EB6BE9DDC1EB230472D for idr@ietf.org; Tue Oct 15 17:25:42 2019
X-Transaction-ID: 8C4A7BE571114EB6BE9DDC1EB230472D
X-filter-score: filter<0>
X-Real-From: zhuyq.gd@chinatelecom.cn
X-MEDUSA-Status: 0
From: Zhuyq <zhuyq.gd@chinatelecom.cn>
To: 'Susan Hares' <shares@ndzh.com>, 'idr wg' <idr@ietf.org>, 'SPRING WG List' <spring@ietf.org>
References: <00f901d582ba$f474a230$dd5de690$@ndzh.com>
In-Reply-To: <00f901d582ba$f474a230$dd5de690$@ndzh.com>
Date: Tue, 15 Oct 2019 17:25:35 +0800
Message-ID: <00c701d5833a$843d2840$8cb778c0$@chinatelecom.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C8_01D5837D.92623D00"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGuHv4XFi88tQ8C88VQOUI4EHnoa6eqNrTw
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/GZ8t48cy4_pUVe7plASWMW9OuIc>
Subject: [Idr] 回复: Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to 10/21/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: Tue, 15 Oct 2019 09:25:51 -0000

Support these 2 drafts.

Best regards.

Zhu Yongqing

发件人: Idr <idr-bounces@ietf.org> 代表 Susan Hares
发送时间: 2019年10月15日 2:13
收件人: 'idr wg' <idr@ietf.org>; 'SPRING WG List' <spring@ietf.org>
主题: Re: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt
and draft-li-sr-policy-path-segment-01.txt - 1 week extension [10/14 to


Greetings IDR and Spring WG


The WG Adoption for the two IDR drafts related to IDR received a level
support below the threshold to accept this draft into the IDR WG.  There
were no objection, but there was simply a low level of response. 


This 1 week extension to the Adoption call is to let the members of both the
IDR and SPRING WG comment on whether these drafts have matured enough to be
IDR WG drafts.  On 10/21/2019, the IDR chairs will make a determination of
whether either of these two drafts have enough support to be accepted. 


Thank you,  Susan  Hares

IDR co-chair 


From: Idr [ <mailto:idr-bounces@ietf.org> mailto:idr-bounces@ietf.org] On
Behalf Of Susan Hares
Sent: Tuesday, September 17, 2019 12:35 PM
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: 






The authors have pointed out that the adoption of this 

draft since the following  SR-MPLS Path Segment draft has been adopted: 




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