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

chen.ran@zte.com.cn Mon, 20 July 2020 09:11 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 3C7583A0916; Mon, 20 Jul 2020 02:11:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level:
X-Spam-Status: No, score=-1.917 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, URIBL_BLOCKED=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 P3wFn6L2mYjT; Mon, 20 Jul 2020 02:11:32 -0700 (PDT)
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 362203A0915; Mon, 20 Jul 2020 02:11:32 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id BA9E13756782CEAF74AA; Mon, 20 Jul 2020 17:11:22 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl1.zte.com.cn with SMTP id 06K9B7I8072614; Mon, 20 Jul 2020 17:11:07 +0800 (GMT-8) (envelope-from chen.ran@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid203; Mon, 20 Jul 2020 17:11:07 +0800 (CST)
Date: Mon, 20 Jul 2020 17:11:07 +0800 (CST)
X-Zmail-TransId: 2afb5f155fab85360efb
X-Mailer: Zmail v1.0
Message-ID: <202007201711070262824@zte.com.cn>
In-Reply-To: <d37cd591d1864972b17b225f41cab4bc@huawei.com>
References: 202007161719327112195@zte.com.cn, d37cd591d1864972b17b225f41cab4bc@huawei.com
Mime-Version: 1.0
From: <chen.ran@zte.com.cn>
To: <jie.dong@huawei.com>
Cc: <james.n.guichard@futurewei.com>, <spring@ietf.org>, <spring-chairs@ietf.org>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 06K9B7I8072614
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/BMwz9sZgNfBGejPrQovO6YSel78>
Subject: Re: [spring] =?utf-8?q?WG_Adoption_Callfordraft-dong-spring-sr-for-e?= =?utf-8?q?nhanced-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: Mon, 20 Jul 2020 09:11:35 -0000

Hi Jie,


IMO, the essence of the problem is that an identifier should be introduced to manage and maintain virtual network resources,  not whether it is necessary to allocate resource related SIDs , because the current SR architecture already supports resource related SIDs allocation, there is no limit to that. For example, service SID (compuated resource related), Node/Adjacency SID(topological resource related), etc. Especially, SRv6 SID encourages programming anything. Can we say that these SIDs have no resource meaning?


Thus, draft-dong-spring-sr-for-enhanced-vpn does not introduce any new content on the existing SR architecture.






For identifier to manage and maintain virtual network resources, draft-peng-teas-network-slicing firstly to introduce a new identifier (AII) in the network to unifiedly identify the topology, computing and storage resource. Before that, other existing identities only focus on topology resources.






Just for topology related resource, Segment Routing with MTR/Flex-algo/AII all support the division of multiple topological resource, and already support allocatoin of SID per MT-ID/algorithm/AII. Especially for link resource, the bandwidth of the same link can be subdivided into multiple resources. 


If these subdivided resources exist in the form of sub-interface resources, L2-bundles(rfc8668) provides the method to assign adjacency-SID for members, In other words, the allocation of member adjacency SID has already been aware of these subdivided resources, each sub-interface has its own link attributes (bandwidth, delay, etc.). 


If there are no sub-interface, the link can also be shared by multiple virtual networks to allocate multiple adjacency SIDs. Under the existing SR architecture, draft-peng-teas-network-slicing and draft-peng-lsr-algorithm-related-adjacency-sid have already described the allocation of adjacency SID per AII and algorithm.






Obviously, the above SR with MTR/Flex-algo/AII are all complete solutions, including control plane extensions and forwarding mechanisms, and they need not make any changes to the SR architecture.


I wonder according to draft-dong-spring-sr-for-enhanced-vpn, what can we do under its guidance, or what we can't do without this draft? 






Regards,


Ran







原始邮件



发件人:Dongjie(Jimmy) <jie.dong@huawei.com>
收件人:陈然00080434;james.n.guichard@futurewei.com <james.n.guichard@futurewei.com>;spring@ietf.org <spring@ietf.org>rg>;
抄送人:spring-chairs@ietf.org <spring-chairs@ietf.org>rg>;
日 期 :2020年07月16日 19:50
主 题 :RE: [spring] WG Adoption Callfordraft-dong-spring-sr-for-enhanced-vpn




Hi Ran,


 


Thanks for your comments. While I don’t quite get your point of objection.  Perhaps you have some misunderstanding about the relationship of the
 drafts mentioned.


 


RFC 8402 introduced the topology and service semantics of SR SID, this document proposed to add resource semantics to SIDs. Then MT or Flex-Algo
 are control plane mechanism for the distribution of topology-specific SIDs. The relationship with these documents are described in this draft.


        


My reading of draft-peng in LSR and TEAS is that they may provide an option of control plane extensions for the resource-aware SIDs defined in this
 document, which just proves that the enhancement in this document is in the right direction, and more work based on it could be done in relevant WGs.


 


Thus my suggestion would be to have the SR enhancement adopted in SPRING first, then more discussion about its control plane could happen in other
 WGs as the next step.  


 


Hope this helps.


 


Best regards,


Jie


 




From: spring [mailto:spring-bounces@ietf.org]On Behalf Of chen.ran@zte.com.cn
Sent: Thursday, July 16, 2020 5:20 PM
To: james.n.guichard@futurewei.com; spring@ietf.org
Cc: spring-chairs@ietf.org
Subject: Re: [spring] WG Adoption Call fordraft-dong-spring-sr-for-enhanced-vpn




 

Dear WG,


I don't support WG adoption.


It is not a new idea for each Virtual Network to have its own SIDs.


e.g. The earlist description of the SID be allocated per flex-algorithm and related metric


 information was in draft-hegdeppsenak-isis-sr-flex-algo-00(2017.7.17) (now is draft-ietf-isis-sr-flex-algo) . 


The earlist description of the SID be allocated per MT was in draft-filsfils-spring-segment-routing-04(2014.7.3)


(now is RFC8402 ), and draft-peng-lsr-network-slicing-00(2019.2.25) describe the


SID be allocated per AII(alias alice).  For slice resources,https://tools.ietf.org/html/draft-peng-teas-network-slicing-03  


induced slice-id(AII) for slice resources management, and can differentiate them (e.g. L2 link or L3 interface,


section 7 ), and how to compute SR-BE or SR-TE path according to AII combined with other criteria.


 


Regards,


Ran

 


-----Original Message-----
From: spring <spring-bounces@ietf.org> On Behalf Of James Guichard
Sent: Wednesday, July 15, 2020 8:17 PM
To: spring@ietf.org
Cc: spring-chairs@ietf.org
Subject: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn

Dear WG:

  

This email begins a 2 week WG adoption call for https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/ <https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/>  ending Wednesday 29th July 2020.  

  

Please speak up if you support or oppose adopting this document into the WG. Please also provide comments/reasons for that support (or lack thereof). Silence will not be considered consent.

  

Thanks!

  

Jim, Joel & Bruno

  

  

  


_______________________________________________
spring mailing list
spring@ietf.org