Re: [Teas] [Teas-ns-dt] Various terms for transport portion of a network slicing

Eric Gray <ewgray2k@gmail.com> Wed, 30 September 2020 13:33 UTC

Return-Path: <ewgray2k@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CFCF3A09B0; Wed, 30 Sep 2020 06:33:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 FsgJkUYB1MA0; Wed, 30 Sep 2020 06:33:06 -0700 (PDT)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43AD03A0983; Wed, 30 Sep 2020 06:33:06 -0700 (PDT)
Received: by mail-qt1-x829.google.com with SMTP id g3so1130538qtq.10; Wed, 30 Sep 2020 06:33:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=qcqY2lXKYeA2T9lridqhpOYGggs0pqvKPGhHayoAZVI=; b=FyoN7WEdh65FQJh5Ql1FO2N9kSRPvLnM7x5aLC3V1dqruOdwOa91D8LfRrgqYj/TND OnPAFKCx6pYtCSHxZ8IBr1gdCWNy5REu7IXXPmlLaLtr2ivxJ/iLtI+wBgLztwpEa01e dgUbOf2+J6/2cUR/Y6cof0/4Mfc6S373qx0brqEgHvgZjLvXPrMww5TSCDjEKgSZNWMd f1kcs7XmXJ5+76b0ZLRPEG/JpTcVmVAx9Wyh+Gd83KBLWTzkYTZNDo8VAM4wKOzY2Ldx FYm7LAtYFlE/LJQbAq97iDADQ64YmHpXpW2zUOmPZ6wS4dgS4jyMJRgf/XdvfyZ0q8mi xrog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=qcqY2lXKYeA2T9lridqhpOYGggs0pqvKPGhHayoAZVI=; b=Bhfmbi9bzYc5sVvohKQZ18ptMHfXa3qVYk5uJxsBTDNcyEd9aGmiA8MBUmpTiAsNX+ r7PG2lyfrjHWUdOg+flWUjWL9GSj+XJ2cPkopGEqMmHSMVe8hF8iHRF0GhX7OAGSNQSc iQiHHhpCXc8BMB1gjRap8sSRFKE4Iy5UfVcUzSohbQKCfF4JGv0a5kgAXe3u1A2F8Vz1 FhE2ZKJ/2ivz3pxVQmkXhGN+FtUqUe6RaSXU33OE4vuqqTROt+O9BTmQaHALSrtYCTY9 jHzDdL/YYPSdumTH0NNERZMr7+v9cVewP/91O8L7xDOQ31TrMTGQiQKLtEfJQFpPFWGu 6ZRQ==
X-Gm-Message-State: AOAM531wm70L9+Jwdju2w0A7fTuicQk+JJWABhRK5IZFHn+4PaQsYY9I A7UK7WNeBMz+/WUj2aB4iLI=
X-Google-Smtp-Source: ABdhPJzIv2qvgJSWNHv96XDoNtmdaDnrIzdQm8Po0XJhkYrEGLFeargIt8qMSIAHcpCWWnnSmdCsug==
X-Received: by 2002:ac8:7388:: with SMTP id t8mr2215916qtp.187.1601472785224; Wed, 30 Sep 2020 06:33:05 -0700 (PDT)
Received: from ?IPv6:2601:85:4680:3329:49e7:f672:f431:32a0? ([2601:85:4680:3329:49e7:f672:f431:32a0]) by smtp.gmail.com with ESMTPSA id 192sm2127346qkm.110.2020.09.30.06.33.03 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Sep 2020 06:33:04 -0700 (PDT)
From: Eric Gray <ewgray2k@gmail.com>
Message-Id: <C3EBECEA-B5EC-4EB7-8D58-9FA0379A93A8@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F77F242A-5139-4238-AD99-8B45AD06484F"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 30 Sep 2020 09:33:02 -0400
In-Reply-To: <BYAPR13MB24371FAE02EB8312A0418716D9320@BYAPR13MB2437.namprd13.prod.outlook.com>
Cc: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>, Lou Berger <lberger@labn.net>, "BRUNGARD, DEBORAH A" <db3546@att.com>, Vishnu Pavan Beeram <vishnupavan@gmail.com>, TEAS WG <teas@ietf.org>, "teas-ns-dt@ietf.org" <teas-ns-dt@ietf.org>
To: Kiran Makhijani <kiranm@futurewei.com>
References: <3C917BB8-A27B-48E8-8AB5-4674B9892E60@nokia.com> <A19434CC-A9E0-47E6-A6E5-36DA8EDCEC89@gmail.com> <51179B7E-C2CE-4794-A74B-38068E36CB25@nokia.com> <001DC659-3BC7-4344-B8BA-C9C74F1D58A9@gmail.com> <BYAPR13MB24371FAE02EB8312A0418716D9320@BYAPR13MB2437.namprd13.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/Ynnnskxqg8FVzbQVL8ErUznk6Wc>
Subject: Re: [Teas] [Teas-ns-dt] Various terms for transport portion of a network slicing
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Sep 2020 13:33:17 -0000

Hi Kiran.

I am not sure what your “caret arrows” were meant to point to, but - assuming you refer to entire sentence - I am also not sure what “separation” you are referring to.

As has been discussed at length, for the 3GPP use-case/application, the 3GPP view is that what they are asking for is essentially a “transport network slice” and IETF applicability is useful in providing clarification of how applications would use what the IETF has defined.

It may be the case that people in this discussion feel this is obvious, but it is nevertheless usually a good idea to write this sort of thing down for the benefit of people who did not have the privilege of participating in this discussion…

—
Eric

> On Sep 29, 2020, at 3:51 PM, Kiran Makhijani <kiranm@futurewei.com> wrote:
> 
> Hi Eric, 
>  
> In terms of applicability, a 3GPP “transport network slice” consumer would be an “IETF network slice” consumer, unambiguously, when using a service model or NBI defined for that purpose by the IETF.
> ^^^^
> I wonder if this separation is necessary. Don’t consumers sit at a higher level, may ask for RAN-, IETF- or any other network slices? Similarly, IETF-consumer may ask for other slices as well…
> -Kiran
>  
> From: Teas-ns-dt <teas-ns-dt-bounces@ietf.org> On Behalf Of Eric Gray
> Sent: Tuesday, September 29, 2020 12:42 PM
> To: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com>
> Cc: Lou Berger <lberger@labn.net>et>; BRUNGARD, DEBORAH A <db3546@att.com>om>; Vishnu Pavan Beeram <vishnupavan@gmail.com>om>; TEAS WG <teas@ietf.org>rg>; teas-ns-dt@ietf.org
> Subject: Re: [Teas-ns-dt] [Teas] Various terms for transport portion of a network slicing
>  
> Reza,
>  
>              Great!!
>  
>              So this makes the TSC become an “IETF Network Slice controller” - or “IETF NSC” and we should be able to just call that a network slice controller (for brevity) in our documents, once we have stated the intention to do so.
>  
>              In terms of applicability, a 3GPP “transport network slice” consumer would be an “IETF network slice” consumer, unambiguously, when using a service model or NBI defined for that purpose by the IETF.
>  
>              It remains unclear if there would need to be a different matching of names for other applications of an IETF network slice, but that would be an issue to be resolved by whoever wishes to describe applicability of IETF network slices for that (or those) other application(s).  
>  
>              Are there other trickle down name changes to be made?
>  
> —
> Eric
>  
> On Sep 29, 2020, at 3:27 PM, Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com <mailto:reza.rokui@nokia.com>> wrote:
>  
> Eric and all,
>  
> Yes. The term “IETF Network Slice” is acceptable to co-authors.
>  
> Reza
>  
>  
>  
> From: Eric Gray <ewgray2k@gmail.com <mailto:ewgray2k@gmail.com>>
> Date: Tuesday, September 29, 2020 at 3:10 PM
> To: Reza Rokui <reza.rokui@nokia.com <mailto:reza.rokui@nokia.com>>
> Cc: Lou Berger <lberger@labn.net <mailto:lberger@labn.net>>, TEAS WG <teas@ietf.org <mailto:teas@ietf.org>>, Vishnu Pavan Beeram <vishnupavan@gmail.com <mailto:vishnupavan@gmail.com>>, "BRUNGARD, DEBORAH A" <db3546@att.com <mailto:db3546@att.com>>, "teas-ns-dt@ietf.org <mailto:teas-ns-dt@ietf.org>" <teas-ns-dt@ietf.org <mailto:teas-ns-dt@ietf.org>>
> Subject: Re: [Teas] Various terms for transport portion of a network slicing
>  
> Reza,
>  
> Not exactly sure what your mail is concluding.
>  
> Is a “golden middle” the same as an acceptable compromise?  If so, it sounds like we’re saying that we find this term acceptable.
>  
> That would be a good thing.
>  
> —
> Eric
>  
> 
> 
> 
> On Sep 29, 2020, at 2:41 PM, Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com <mailto:reza.rokui@nokia.com>> wrote:
>  
> Hi Lou, Pavan, Deborah and all,
>  
> As per TEAS WG chairs request during the last week’s meeting on network slicing, the co-authors of the definition draft had a few meeting and compiled all the potential terms with their pros and cons in the following table.
> We feel that we captured all the terms suggested by TEAS and NSDT members in mailing lists and during the various meetings. Please let us know if any terms is missing.
>  
> In summary, the co-authors of the draft believe the term “IETF Network Slice” is a golden middle where IETF provides the exact context of any Network slice.
>  
> Cheers,
> Reza (on behalf of all co-authors)
>  
> 
> 
> Various options for transport connectivity term from IETF point of view (without any specific order)
> 
>  
> Term
> Suggested by 
> Pros
> Cons
> 1
> IETF Network Slice
> TEAS chairs
> o It clearly elaborates the scope of technologies addressed with in the IETF leveraging the industry-wide term 'network slice.
> o It is golden middle, where “IETF” provides the exact context to “Network Slice”
> o Acceptable to TEAS WG chairs
> o Acceptable to draft co-authors
> labeling a piece of work with SDO name is not a good idea and IETF has always worked towards wider use, generic solutions, so the name may be restrictive.
> 2
> Transport Slice
> Draft Authors and NSDT
> o ‘Transport network’ is an abstraction of connectivity between the (network) end-points which is technology agnostic.  Well covered by RFC5921.
> 
> o Aligned with other SDO (i.e. MEF)
> See Figure 17 of following white paper
> https://wiki.mef.net/display/CESG/Slicing+for+Shared+5G+Fronthaul+and+Backhaul+-+White+Paper <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.mef.net%2Fdisplay%2FCESG%2FSlicing%2Bfor%2BShared%2B5G%2BFronthaul%2Band%2BBackhaul%2B-%2BWhite%2BPaper&data=02%7C01%7Ckiranm%40futurewei.com%7Cab4fd61ace6b46c2d09d08d864afb631%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637370053140079501&sdata=nvBM5segjpgg29iiPjjOgqe6lvRwjHEgycYfwxoKgoo%3D&reserved=0>	
> As per recent WG adoption poll, it is not accepted
> 3
> Transport network slice
> Draft Authors and some IETF members
> ‘Transport network’ is an abstraction of connectivity between the (network)end-points which is technology agnostic.  Well covered by RFC5921.
> As per recent WG adoption poll, it is not accepted
> 4
> Connectivity Slice
> Draft Authors
> o Since the transport slice is a set of distinct connections, term "Connectivity Slice" is selected
> 
> o Aligned with other SDO (i.e. 3GPP) 
> See Figure 4.9.3.1 of TR 28.801 and  http://www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G <https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.3gpp.org%2FNEWS-EVENTS%2F3GPP-NEWS%2F1951-SA5_5G&data=02%7C01%7Ckiranm%40futurewei.com%7Cab4fd61ace6b46c2d09d08d864afb631%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637370053140089498&sdata=qVnezK0RhH%2BlAQlWrT3Or2%2BEzz8yZU9IuzQ7MkZtC3M%3D&reserved=0>	
> As per TEAS WG chair, connectivity has different meaning at IETF
> 5
> Connectivity Network Slice
> Luis
> The term Network becomes now narrow downed to the reference to connectivity, which is subject of IETF
> As per TEAS WG chair, connectivity has different meaning at IETF
> 6
> Connection Slice
> Luis
> o The term associates the concept of slice to the connection enabling the data transmission among end-points participating of a communication
> o Note – here we could then follow a similar approach to how the VPNs are classified as L2 or L3; I mean L3/L2/(L1?) Connection Slice; if we classify the Connection Slices in that manner, such classification of the Connection Slice types will also help to describe recursiveness or hierarchical (multi-layer) slicing
> o A connection can be established at different levels, including protocols above Layer 3
> o Connection slice can make the people understand that there is a single connection represent a slice (i.e., 1:1) while actually could not be the case (i.e., 1 slice being formed by N connections)
> 7
> Slice Network
> Stewart
> Stewart is coming with some background that a slice is combination of storage, compute and communications (or network). Slice network means an existing network is sliced to serve a particular user-case.
> According to Lou, it has entirely different meaning.
> 8
> Virtual Slice Network (VSN)
> Luis
> o Variant on top of Stewart’s suggestion to link with the evolution of the concept of legacy VPNs
> o The term reminds the idea of logical network per customer focusing on connectivity
> o As before, it could be possible to follow a similar approach to how the VPNs are classified as L2 or L3; I mean L3/L2/(L1?) VSN; also here, such classification of the VSNs can also help to describe recursiveness or hierarchical (multi-layer) slicing in transport
> o There is no specific reference to transport or connectivity, apart of the generic idea of network (which we now is also an overloaded term)
> o Differently from a VPN, which basically is a single instance including a number of locations, a VSN could refer to a set of individual VSNs (e.g., one per network segment). So can be probably confusing. Thus probably it would be needed to add additional terms such as sub-VSN, or VSN-segment, VSN-part, VSN-sub-slice, or alike
> 9
> TE Network slice
> Some TEAS members
> Aligns with same  rationale used for naming ACTN.
> Since not all transport networks are TE enabled, the realization of connectivity might be in a non-TE network. So, this term seems not appropriate
> 10
> Carrier network slice
> Webex/Stewart
> In a generic use of term 'carrier' a carrier slice network carries use-case specific network traffic.
> it may be confusing because it is associated with the infrastructure of telecommunication service providers, i.e., FNO/MNO. Recently, some network operators  deploy COTS servers in their infrastructure for MEC usages, and some readers may expect control of compute and storage  resources is in scope
> 11
> Network slice
> Some IETF members
> An adoption of industry-wide term. While each SDO may look at it differently based on its own set of capabilities, for an end user it is a network slice in a specific technology domain.
> o Since multiple connections are part of a single "Network Slice", it is not a good idea to call each of these connections "Network slice".
> o There is a lack of 'harmonized' definition of network slice. For end customers, message may be confusing on which SDO they should ask for what part. It may lead to duplication of orchestration or APIs, depending upon who is controlling end to end network slice  - is it 3GPP operator, MVNO, ISP, service-integrator, OTT etc... 
> 12
> Data transmission network slice (DTNS)
> Shunsuke 
> Since the transport slice is a set of distinct connections, providing the data transmission, this term might be suitable. 
>  
> 13
> Transmission Network  Slice
> Reza
> Since the transport slice provides the data transmission across transport network, this term might be suitable. 
>  
> 14
> Transmission Slice
> Reza
> Same as "Transmission Network Slice"
>  
>  
>  
>  
> _______________________________________________
> Teas mailing list
> Teas@ietf.org <mailto:Teas@ietf.org>
> https://www.ietf.org/mailman/listinfo/teas <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fteas&data=02%7C01%7Ckiranm%40futurewei.com%7Cab4fd61ace6b46c2d09d08d864afb631%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637370053140089498&sdata=XUvdS67hdORI1INkcIolgIExH8%2FeEdm%2BJ5u0xXmy3Y8%3D&reserved=0>