Hi Chongfeng, Thanks for your valuable comments. The term “IETF network slice” was chosen by the network slicing design team in TEAS WG, after many discussion in both the design team and the WG. This document tries to align with the terminology there.
I also agree that the terms in different SDOs needs to be aligned, or the relationship and mapping between different terms could be defined. Best regards, Jie From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: Friday, May 14, 2021 5:18 PM To: Dongjie (Jimmy) <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [spring] A new draft on Segment Routing for End-to-End IETF network slicing Hi，Jie， I think this work is useful and support its progress in spring or other WGs. However, I have some concerns about the term of "IETF slicing”, from the perspective of operator, the terms of “IETF slicing” and “3GPP slicing” may be confusing, there should be a universal set of terms of slicing across different SDOs, even they may cover different sections or layers of the network system. What’s your opinion? Best regards Chongfeng 2021年5月14日 下午4:10，Dongjie (Jimmy) <[email protected]<mailto:[email protected]>> 写道： Hi WG, Recently we published a new draft on Segment Routing for End-to-End IETF Network Slicing: https://datatracker.ietf.org/doc/html/draft-li-spring-sr-e2e-ietf-network-slicing It introduces the new SRv6 behaviors and SR-MPLS BSIDs to enable the mapping and concatenation of multi-domain IETF network slices. This document is aligned with the framework for end-to-end IETF network slicing as described in draft-li-teas-e2e-ietf-network-slicing. Your review and comments are welcome. Best regards, Jie _______________________________________________ spring mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/spring
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
