Re: [Teas] Why term transport slice? WG adoption - draft-nsdt-teas-transport-slice-definition

Young Lee <younglee.tx@gmail.com> Sat, 05 September 2020 04:35 UTC

Return-Path: <younglee.tx@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 CBF173A121C; Fri, 4 Sep 2020 21:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level:
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 3TZt9sOnKQop; Fri, 4 Sep 2020 21:35:32 -0700 (PDT)
Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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 897873A0E14; Fri, 4 Sep 2020 21:35:31 -0700 (PDT)
Received: by mail-il1-x12d.google.com with SMTP id a8so2410769ilk.1; Fri, 04 Sep 2020 21:35:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LChVIkqzws5Z2v94sIQemFsHT8NL6fNax52Hex5pKMA=; b=XL3ZPr/iJ36Ik4gnz4TkxU/A5RDKhXKimkRqMHcuHOoCco9gmKF3wYbZdqKERH9TnB dv0YGDH6YHDCH39hA21Ed/12oa6V0LTcO9zNDkbeuGVVd7x4wCdFbySaGKCasi2Kzill XFDXxY8yWSUJ5xW/iWfuR9UlHYNIVneAcgTkuLU6v67ABrCF8UXm2fh9seNfSj7DBFKP XP5jkMt+c4ZrOv8He0t4sY2gEiqwNz7vsDx7g0ZO2nGeszyWDafvV2UtIVTjThXm6+ou WwM0fgT71xQCn48wr7Qwwe9C0oT2NG5vMv7s1aXyjILYyNr+a8wHYd2IsxgRtsXmiX1b qnZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LChVIkqzws5Z2v94sIQemFsHT8NL6fNax52Hex5pKMA=; b=ZDeZF89Ep1xVTash1buckNG3u3twACvtaW5T7eAMr/xk4HYcB5aLPJEOkz5gr/LzPM M17oDipXvrdG1+aFZV2pfPxO8rT/t3l4+RlNy2jssZXcHt08F/6q+G8czXOGco3WcTkK CIXG6EJDjuQXbt8i4wQ1Q66hdpJAu3blPomJUsCS4w/lB5aLN7BKEEKvZsCzEUxjMYeT +DgC/KjTlVbep2DhSRPrREj+0K3u2aWZdH8iir5QyXjmQhOp2kCnSq6yMBlYm/ltehCJ RZFa1pO+EEIJTJYrMBU0WkpAy9Za4PXqWFKw2Nq7rqHt2LOkxbXUv/ZinD9ObJ3QQuzP kchA==
X-Gm-Message-State: AOAM531TmSyrjUeLnb7HZQbjtOEwe+uK0xMpZZyBARFkfkUQ9MUsn/lB v+BMANsZfCgjaOK9BJYR/QK4qUaW2JCFwMhOXtk=
X-Google-Smtp-Source: ABdhPJwShzc+Kbmpd4tIGPZrJdfqNL3H5O6XM9bwPrMVRl3ultjUcrJ8i5SFD9uamcXFQUYpyWOaWrD0DWBCbx3ZfHA=
X-Received: by 2002:a92:9986:: with SMTP id t6mr10796917ilk.28.1599280530143; Fri, 04 Sep 2020 21:35:30 -0700 (PDT)
MIME-Version: 1.0
References: <EBB5115F-1EF4-4F07-88FB-C5598A640D74@nokia.com> <DM5PR05MB33881A3CE266B2B38A6D29C0C72D0@DM5PR05MB3388.namprd05.prod.outlook.com>
In-Reply-To: <DM5PR05MB33881A3CE266B2B38A6D29C0C72D0@DM5PR05MB3388.namprd05.prod.outlook.com>
From: Young Lee <younglee.tx@gmail.com>
Date: Sat, 5 Sep 2020 13:35:17 +0900
Message-ID: <CAGHSPWM0fvoh_vKWsKGtaCkc11UHgysi2_oSJ95UqKv7S785+Q@mail.gmail.com>
To: John E Drake <jdrake=40juniper.net@dmarc.ietf.org>
Cc: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>, Kiran Makhijani <kiranm@futurewei.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, Eric Gray <ewgray2k@gmail.com>, Igor Bryskin <i_bryskin=40yahoo.com@dmarc.ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>, "EXT-vishnupavan@gmail.com" <vishnupavan@gmail.com>, TEAS WG <teas@ietf.org>, "BRUNGARD, DEBORAH A" <db3546@att.com>
Content-Type: multipart/related; boundary="000000000000e5ddce05ae8983d8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/NRskTgn1vGSFClCg94VqbLf1TK0>
Subject: Re: [Teas] Why term transport slice? WG adoption - draft-nsdt-teas-transport-slice-definition
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: Sat, 05 Sep 2020 04:35:35 -0000

Hi,

I agree with John. This is a good point. There are a mutiplicity of
"customers/consumers" that would like to consume the "services" IETF/TEAS
provides, and 3GPP is one of the customers that may be interested in
fulfiling its TN subnet requirements for eMBB or uRLLC network slice types.

But there are other customers that TEAS ACTN supports among which are L1VPN
for DCI, IP service providers that need a leased line between two end
points, etc, let alone L2/3 VPN customers that need TE networks, and
enhanced VPN.

TEAS ACTN effort has been to fulfill the common requirements coming from a
plethora of diverse customers.

What about non-TE? As Igor nicely put in another email thread, ACTN VN/ TE
Yang models can still be used as they provide all necessary basic
components (non-TE specific) such as end points, service policies, sharing
properties, etc. All components in YANG models can be made optional so all
TE components can be skipped if there is a need for that.

Regards,
Young






2020년 9월 5일 (토) 오전 12:15, John E Drake <jdrake=40juniper.net@dmarc.ietf.org>님이
작성:

> Hi,
>
>
>
> ‘Network slice’.  As Adrian points out, this is the term that has been
> used in the IETF for quite some;  it is used in RFCs 8453, 8568, and 8578,
> as well as the preponderance of I-Ds on this topic.  Even if another term
> was correct, and I don’t think that, trying to use a term other than
> ‘network slice’ will continue to cause tremendous confusion.  I.e.,
> changing terms is akin to closing the barn door after the horse has bolted.
>
>
>
> As I noted yesterday, and throughout the **Network Slicing** design team
> meetings, I think it is up to an application that uses IETF network slices
> as components to indicate where in its design these IETF network slices
> fit.  I.e., IETF network slices are being designed for use by a
> multiplicity of applications and trying to make our terminology congruent
> with this one application is problematic.
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
>
>
> Juniper Business Use Only
>
> *From:* Teas <teas-bounces@ietf.org> *On Behalf Of * Rokui, Reza (Nokia -
> CA/Ottawa)
> *Sent:* Friday, September 4, 2020 10:16 AM
> *To:* Kiran Makhijani <kiranm@futurewei.com>om>; adrian@olddog.co.uk; 'Eric
> Gray' <ewgray2k@gmail.com>om>; 'Igor Bryskin' <i_bryskin=
> 40yahoo.com@dmarc.ietf.org>gt;; 'TEAS WG Chairs' <teas-chairs@ietf.org>rg>;
> EXT-vishnupavan@gmail.com <vishnupavan@gmail.com>om>; 'TEAS WG' <
> teas@ietf.org>gt;; 'BRUNGARD, DEBORAH A' <db3546@att.com>
> *Cc:* Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com>
> *Subject:* [Teas] Why term transport slice? WG adoption -
> draft-nsdt-teas-transport-slice-definition
>
>
>
> *[External Email. Be cautious of content]*
>
>
>
> All,
>
>
>
> Thanks for all feedbacks.
>
>
>
> Let’s step back and address these questions: *How and why the authors’ of
> the draft chose the term “Transport Slice”?*
>
>
>
> Before formation of the TEAS WG NSDT, there were lots of discussions and
> drafts to address the role of IETF for network slicing. Those discussion
> and drafts tried to address the network slicing  from different
> perspectives but in most cases they had one thing in common, they started
> by discussion the network slicing but at the end they really meant the
> Transports portion of the network slice. In other words, although the name
> of the draft and discussion was network slicing, but they just talked about
> Transport portion.  In other hand, the term network slice and Transport
> portion of a network slice were used interchangeably.
>
>
>
> After creation of the NSDT, we collectively thoughts that the first order
> of business is to clarify this. So, the “draft definition” started. The
> following are the reasons:
>
>
>
> Reason 1)
>
> The first reason for this draft is to make very clear distinction between
> a network slice (defined for example by 3GPP) and transport portion of a
> network slice.
>
> In our opinion it is essential to make a clear distinction between *network
> slice* and *transport portion of a network slice*. They are NOT the same
> since a network slice contain the transport portion.
>
> The picture below was outcome of that discussion. In summary, a network
> slice is an end-to-end context and depends on the used case (i.e 5G, DCI,
> etc), it might contain a few other components (i.e. RAN, Transport, Core
> etc.)
>
>
>
>
>
> Reason 2)
>
> We just established the fact that an end-to-end network slice is different
> from transport portion of the network slice. The next question is that what
> the definition of the Transport portion of a network slice is.
>
> This is fully discussed in draft but in summary the transport portion of a
> network slice describes the CONNECTIVITY between various endpoints. Our
> definition is aligned with MEF and 3GPP.
>
>    - MEF uses the same definition for Transport portion of the network
>    slice”. See Section 5.3 of following white paper
>
>
>    -
>       https://wiki.mef.net/display/CESG/Slicing+for+Shared+5G+Fronthaul+and+Backhaul+-+White+Paper
>       <https://urldefense.com/v3/__https:/wiki.mef.net/display/CESG/Slicing*for*Shared*5G*Fronthaul*and*Backhaul*-*White*Paper__;KysrKysrKysr!!NEt6yMaO-gk!RwBHv_fQ5XdrftEX2118w7OUiQg2mu-eHcRobC4KGZ-EPaqW2EcKPWfQ_6Dp7hs$>
>
>
>
>    - This is aligned with 3GPP. See Figure 4.9.3.1 of TR 28.801 and
>    http://www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G
>    <https://urldefense.com/v3/__http:/www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G__;!!NEt6yMaO-gk!RwBHv_fQ5XdrftEX2118w7OUiQg2mu-eHcRobC4KGZ-EPaqW2EcKPWfQECxLoTI$>
>
> According to the picture below,  the reference of transport portion of a
> network slice  is referred by “Transport network supporting connectivity’
>
> [image: cidimage001.png@01D6806A.8E70BC90]
>
>
>
>
>
> Reason 3)
>
> The next question is that which term shall be used for ‘Transport portion
> of an end-to-end network slice”?
>
>
>
>    - MEF uses the term “Transport Slice”. See Figure 17 of following
>    white paper
>
>
>    -
>       https://wiki.mef.net/display/CESG/Slicing+for+Shared+5G+Fronthaul+and+Backhaul+-+White+Paper
>       <https://urldefense.com/v3/__https:/wiki.mef.net/display/CESG/Slicing*for*Shared*5G*Fronthaul*and*Backhaul*-*White*Paper__;KysrKysrKysr!!NEt6yMaO-gk!RwBHv_fQ5XdrftEX2118w7OUiQg2mu-eHcRobC4KGZ-EPaqW2EcKPWfQ_6Dp7hs$>
>
>
>
>    - 3GPP: See Figure 4.9.3.1 of TR 28.801 and
>    http://www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G
>    <https://urldefense.com/v3/__http:/www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G__;!!NEt6yMaO-gk!RwBHv_fQ5XdrftEX2118w7OUiQg2mu-eHcRobC4KGZ-EPaqW2EcKPWfQECxLoTI$>
>
> They do not directly address the transport portion of a network slice.
> They do not have a term for this. They mainly address the 5G RAN and 5G
> Core. As shown in the picture above, the reference of transport is phrase
> “Transport network supporting connectivity”.
>
>
>
>    - >From IETF point of view, these are potential choices for Transport
>    portion of a network slice:
>
>
>    - Network slice: This for sure is NO. Reason 1) clearly shows that we
>    shall not use term “Network slice” for transport portion. This is not
>    correct.
>    - Use 3GPP phrase: “Transport network supporting connectivity”
>    - Use the phrase “Transport portion of the Network Slice”
>    - Use term “Transport Network Slice”
>    - Use term “Transport Slice”
>    - Adrian, Igor, Deborah and others, is there any other suggestion? If
>    so, please add
>
>
>
> From the above choices, the draft authors uses the term “Transport Slice”
> but not the “Transport Network Slice” to make sure we implicitly stating
> that Network Slice and Transport part are different.
>
> Having said that, authors are open to suggestion. Please suggest your term.
>
>
>
>
>
> *Reza *
>
>
>
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>