Re: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn

chen.ran@zte.com.cn Tue, 09 February 2021 03:54 UTC

Return-Path: <chen.ran@zte.com.cn>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5188F3A10CB; Mon, 8 Feb 2021 19:54:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 w2cqa7y0X_ox; Mon, 8 Feb 2021 19:54:44 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 CA26D3A10BD; Mon, 8 Feb 2021 19:54:35 -0800 (PST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id 3755EC71D3C76879DA34; Tue, 9 Feb 2021 11:54:33 +0800 (CST)
Received: from njxapp04.zte.com.cn ([10.41.132.203]) by mse-fl2.zte.com.cn with SMTP id 1193sSmm012100; Tue, 9 Feb 2021 11:54:28 +0800 (GMT-8) (envelope-from chen.ran@zte.com.cn)
Received: from mapi (njxapp05[null]) by mapi (Zmail) with MAPI id mid203; Tue, 9 Feb 2021 11:54:27 +0800 (CST)
Date: Tue, 09 Feb 2021 11:54:27 +0800
X-Zmail-TransId: 2afd602207735ac152a9
X-Mailer: Zmail v1.0
Message-ID: <202102091154279621309@zte.com.cn>
In-Reply-To: <MN2PR13MB42061AD1E295598F1F2726BDD2BB9@MN2PR13MB4206.namprd13.prod.outlook.com>
References: MN2PR13MB42061AD1E295598F1F2726BDD2BB9@MN2PR13MB4206.namprd13.prod.outlook.com
Mime-Version: 1.0
From: chen.ran@zte.com.cn
To: james.n.guichard@futurewei.com, spring@ietf.org, spring-chairs@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 1193sSmm012100
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/cttVy09H4vCYAIR90aldVmOASKM>
Subject: Re: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2021 03:54:52 -0000

Hi WG,



 


What are the advantages of this draft compared with other drafts? (such as draft-bestbar-spring-scalable-ns, draft-peng-lsr-network-slicing),and is it just explain the concept of virtual SR network beyond the concept of resource-aware SID? 


Many people are thinking about how to realize slicing in the network and made many contributions. Although I am originally a co-author of draft draft-peng-lsr-network-slicing, I think so far draft-bestbar-spring-scalable-ns, comparatively speaking, is to grasp the essence of the problem, and have a complete thoughts.






So, I do not think draft-dong-spring-sr-for-enhanced-vpn is now ready to become a working group draft.






Best Regards,


Ran







原始邮件



发件人:JamesGuichard
收件人:spring@ietf.org;
抄送人:spring-chairs@ietf.org;
日 期 :2021年01月27日 19:47
主 题 :[spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn


_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

 

Dear WG:


 


This message starts a 2 week WG adoption call for https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/ ending February 10th 2021.


 


After review of the document please indicate support (or not) for WG adoption to the mailing list and if you are willing to work on the document, please state this explicitly. This gives the chairs an indication of the energy level of people in the working group willing to work on this document. Please also provide comments/reasons for your support (or lack thereof) as this is a stronger way to indicate your (non) support as this is not a vote.


 


Thanks!


 


Jim, Bruno & Joel