Hi Jie,
Thanks for you reply.
Please see in-line [PSF]
Regards,
PSF
From: spring [mailto:spring-boun...@ietf.org] On Behalf Of
peng.sha...@zte.com.cn
Sent: Sunday, February 7, 2021 11:53 AM
To: james.n.guich...@futurewei.com
Cc: spring@ietf.org; spring-cha...@ietf.org
Subject: Re: [spring] WG Adoption Call for
draft-dong-spring-sr-for-enhanced-vpn
Hi WG/authors,
I have to point out that the VTN-ID in draft-dong-spring-sr-for-enhanced-vpn is
actually the AII in draft-peng-teas-network-slicing, just a new name. That can
be seen from the evolution of the historical versions of the these two drafts.
[Jie] The VTN (virtual network) concept is introduced in
draft-ietf-teas-enhanced-vpn, which is long before the draft you mentioned.
In control plane, a VTN can be identified by existing control plane IDs, and
VTN-ID is used when multiple VTNs share the same topology. IMO this is
different from what the AII is used for.
[PSF] No, Let's look at the timeline.
[PSF] draft-peng-lsr-network-slicing-00 (February 25, 2019) first discussed the
introduction of slice based identifier in control plane and forwarding plane,
which we call AII.
[PSF] Before that, the previous control plane schemes of Enhanced VPN, such as
draft-dong-lsr-sr-enhanced-vpn-01 (October 22, 2018), have been discussed
always based on MTR ID. You originally think that a slice is an MTR.
[PSF] After that, the later control plane schemes of Enhanced VPN, such as
draft-dong-lsr-sr-enhanced-vpn-02 (November 4, 2019), also discussed the
introduction of slice based identifier in control plane and forwarding plane,
which you call TNSI.
[PSF] In fact, VTN was formally defined till in draft-ietf-teas-enhanced-vpn-05
(2020.2.18). Before that, you mentioned that it is a sub topology that is a
virtual SR network composed of a group of SIDs (with associated resources).
However, it does not describe how to create this virtual SR network. That is
the key issue. Note that the so-called "using a set of SIDs to form a virtual
SR network" is putting the cart before the horse. My means is that, for
example, people can create Flex-algo plane based on the key ID, i.e, algorithm
with its related FAD, while SID per algorithm is just an attribute of the
created Flex-algo plane. Nobody knows how the Flex-algo plane is created just
according to "a set of SIDs per algorithm".
[PSF] Anyway, what I mentioned is a slice based ID introduced in the control
and forwarding plane, but you mention VTN concept, they are NOT the same thing.
Once the slice based ID is introduced, it can be used to distinguish which
slice the service belongs to, and that is not related with whether different
slice can or not share the same topology.
I draw your attention to draft draft-peng-teas-network-slicing which analyzes
in detail the reasons for the introduction of slice identifier (AII) in the
network, and maintains the resource partition of each slice and the allocation
of SID per AII in the network. All this happened before
draft-dong-spring-sr-for-enhanced-vpn.
[Jie] If you follow the SPRING WG closely, you would know that the first
version of draft-dong-spring-sr-for-enhanced-vpn was submitted in March 2018,
which is one and a half year earlier than the draft you mentioned.
And if you want people to read or discuss another draft, you could start a
thread in the WG which the draft belongs to.
[PSF] Sure, but it seems that it has no substance mechanism to create the
virtual SR network? You might say "using a set of SIDs to form a virtual SR
network", that is putting the cart before the horse IMO.
In addition, the idea that multiple slices share the same virtual topology
(such as flex-algo) is also copied from draft-bestbar-teas-ns-packet, which can
significantly reduce the state in the network, especially without maintaining
SPT per slice, which means that multiple SIDs per slice can share the
forwarding action of SPT per VN and at the same time can do resource guarantee
by SID per slice (or slice-id in packet).
[Jie] The mechanism of multiple VTNs sharing the same topology was first
described in draft-dong-teas-enhanced-vpn-vtn-scalability one year ago in Feb
2020. Further discussion about the scalability optimizations in that document
will happen in the TEAS WG.
[PSF] Thanks for clarification for this point. draft-bestbar-spring-scalable-ns
clearly desribed that multiple per slice Prefix-SIDs (Slice Prefix-SIDs) can be
assigned for the same prefix such that they all share the same IGP computed
path over one topology and optimized for one algorithm to allow the steering of
traffic to the same prefix along a path but over different network slices. If
that is exactly what did draft-dong-teas-enhanced-vpn-vtn-scalability(5.1.
Control Plane Optimization) want to do, I suggest adding an explicit
description similar as draft-bestbar-spring-scalable-ns.
Best regards,
Jie
Thus, from a purely technical point of view, I see no reason for this document
to be adopted.
Regards,
PSF
原始邮件
发件人：JamesGuichard
收件人：spring@ietf.org;
抄送人：spring-cha...@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
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
