Re: [Teas] Network Slicing design team definitions- transport slice

"Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com> Tue, 01 September 2020 18:17 UTC

Return-Path: <reza.rokui@nokia.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 B34063A0E88 for <teas@ietfa.amsl.com>; Tue, 1 Sep 2020 11:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 PohhEibPbYhQ for <teas@ietfa.amsl.com>; Tue, 1 Sep 2020 11:17:07 -0700 (PDT)
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (mail-mw2nam10on2134.outbound.protection.outlook.com [40.107.94.134]) (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 A53EA3A0E7F for <teas@ietf.org>; Tue, 1 Sep 2020 11:17:06 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=l2yDQa9jvvxtQTB1qtBjfqlct81ZKvsfHqoatrCjdDR2lof5G0xqoKQ6Pzop/3tS+atAPNBuzXtH9otuPCkIWqQ6sdewOqP9bzrJSVUCyFK8DkOOrVwNjeOYlm2UAepKxJ8L1DTdqtXI5If2tlAq2Aq7isfgREvNrZBMXv7VK4Cnvizs/GPQHON2xQLEiVnUYS7T3PlMnDY1RxtC8l0VCCPJD9jORqq8boTrWFFicy6FQ/nEAcnXQVcFHIx7duWaq8m/kelwk++DpsjEbxaOZECnE2aoTN5bCd7BYcGgn1H9Lod7vCBUi0TcHOPQkUjrWd0HCt5wtySO8Gmg2V2QyA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ROg6hzrB4IW+MC2zT/CFwX7+SKsoX+oLNy6zFr8lG7k=; b=bLT0tNhdegGyknfQytH89fZ75+mjPqdLwEi+cw5K6VRRyZtN47YMFmLCPV9KFiSQgA+FNn+RbJ2er9gf6cBXUVPWhy0tIZ4fy9r091LqGhIpmjw/JYgG6hH5x3IRI8d04Ry0uA7ZIt/WAxrzhbm+aWh26/4Yc/4fujSFOaZjNbGs6z+QxUfbDi4JE7JRi8eBQUVbfzheNZZ5WbzGEeKfqFIQ5MKp4NvFF8fU5js+vG8k3JAdGvm1vB+lu1bSQSp0Ha81gzUltmtmDTBcjXiR78rwtp5sBoiAzKsPULgD8NHUosRcxNdkDDoLwlQ/ipPzwK5RGhXsi5sMj0SVdgVYug==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ROg6hzrB4IW+MC2zT/CFwX7+SKsoX+oLNy6zFr8lG7k=; b=c0VhmD8YporH9/9vRZGGPNK23CsAMaPjI2bz5kMreTL1zIjtbTyN61JP9IYhbZ1CuExd8rASbhLQ27JxL20VDfXw6ezmq4w3hJT4BJ97h+ja4m/1UVVxGwbr25YxhafQnpT7GVntW4ip38d5VLdHOS2d7Eeoymwi/KwJDyzVIWA=
Received: from DM6PR08MB6331.namprd08.prod.outlook.com (2603:10b6:5:1ee::8) by DM6PR08MB4121.namprd08.prod.outlook.com (2603:10b6:5:83::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3326.23; Tue, 1 Sep 2020 18:17:04 +0000
Received: from DM6PR08MB6331.namprd08.prod.outlook.com ([fe80::b1d0:ed5:8e69:c77d]) by DM6PR08MB6331.namprd08.prod.outlook.com ([fe80::b1d0:ed5:8e69:c77d%5]) with mapi id 15.20.3348.015; Tue, 1 Sep 2020 18:17:04 +0000
From: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
To: Young Lee <younglee.tx@gmail.com>, "BRUNGARD, DEBORAH A" <db3546@att.com>, TEAS WG <teas@ietf.org>
CC: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
Thread-Topic: [Teas] Network Slicing design team definitions- transport slice
Thread-Index: AQHWgIwYofZbO4F5OUCURNQco+xweQ==
Date: Tue, 1 Sep 2020 18:17:04 +0000
Message-ID: <A6B4274F-E7E2-45F6-A63E-C3EFD018F0C3@nokia.com>
References: <70af45b0bdf54f418ad83fcb65906f4a@att.com> <CAGHSPWM0mnm_ky2wPVS4fFKpe91nNCBJvWbHtoZVm=-cDA79jg@mail.gmail.com>
In-Reply-To: <CAGHSPWM0mnm_ky2wPVS4fFKpe91nNCBJvWbHtoZVm=-cDA79jg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.40.20081000
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=nokia.com;
x-originating-ip: [24.246.4.36]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 96469fa1-5fce-48e9-53a0-08d84ea33aa0
x-ms-traffictypediagnostic: DM6PR08MB4121:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <DM6PR08MB41218404CCA2A2379A13E3309F2E0@DM6PR08MB4121.namprd08.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: KfS+iFLXcdHMW8GOoGBnHt27y7UtbbjHP+L2QymOEZCvIwBnFltLjrt4vNn6G3VgxWtjcefgnG7E5n7AIQsn2FU7LOsigUs5mNIpaQIq29FozB6LooEifqnHe/1BaoE5FNBiU7Vk9JYCNtfkssleuootb6tGUIAUgSJ7GXLxJYqli5PrnI8glULNyqzDHOeIjUxl4iGpIYnSTkLlVhujNusVA2o5o5qf8/RwjPpDKeQE5I16jeXUUGEq1bSrS20kPGjUTnHMl6fyW8mYyS6tQ0Vn9KTJ9YGdLlCvBtqvwxQtsEu6w/f3LWub7UTflzP8ye2TctqN6ScQs9vBZjfbIrYG8xT+XqxctkRhK+kQlr+GLpIa7EMA0pk4zBhIYUte9SCN4SpKZgadtlw/G6S7Hw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR08MB6331.namprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(136003)(396003)(346002)(366004)(39860400002)(376002)(5660300002)(71200400001)(966005)(8676002)(26005)(110136005)(2616005)(36756003)(8936002)(6506007)(86362001)(66476007)(66946007)(91956017)(2906002)(186003)(316002)(6512007)(66446008)(4326008)(107886003)(66556008)(76116006)(6486002)(99936003)(53546011)(83380400001)(166002)(64756008)(66616009)(33656002)(478600001); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: /d/8pmLH4PcfOrU+9bgEFVg+GdAId3XeZVOuDeHDe0hTAyjI7amzT83UCU+S1X6vPWzcn/A6Gd72ppbYuX1PaTPjG0wQmQ/aB7Cxf+W/BtVTj3xGgz+H+EaTZViFTtoStZxjJjfC5Y1xhu5C2kJf4IuzGsqbAI4uaOJfeOj1zz6Tk030JPU4u+UxWFwmXFEfDYg+GHfeEwHBvVENz0QskvlZcbwZFYoq3Wu4KRYgiAJWY+a7ORHV2tXCnO3vtCtg0ViysBWzJzxtNuNTL1s/V92WM9C6JAvt8oTnMnawZsC+cHSTb2HYAHjPm0+jW1LHN6zFqhPw216DDPjbf8joS2QLAB9jLp1cuHKTQ857KudgaUB7SjnWCBKlfkDqT5Tt2fZS6Pg+GHUI3kdQQ0O5rQfAbPa+Kn6bnK0HR335pt8z2LSWWv6teo9yX7SCZYE4IwwX1KjIDLQl9/g7Q6Ja4m5QmVEdOgPoeNdZAuAVcOLi5ibifTf7ojZ5IGiudD9dptxliAMD/Wz+mPqiZIudRiu7Pr2EpQd1ZkwieL8x4LYFFiNK2oKVYfYTVjcZcu2FoxtmovVJ0or9tfa6i/XJyaiMeJZ5kAFcoEpoJVC7JMxADARt4X3SFbaA5JJXJU8RdBRrd058TNjPZ46RaLvHdw==
Content-Type: multipart/related; boundary="_004_A6B4274FE7E245F6A63EC3EFD018F0C3nokiacom_"; type="multipart/alternative"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR08MB6331.namprd08.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 96469fa1-5fce-48e9-53a0-08d84ea33aa0
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Sep 2020 18:17:04.2170 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Yf2+ss+Wa4jc0V+D7nq8565wlz38X/EYff09QNjK+LyPXvjfQoRqgIMNra4YcHJRx/8ildP1Vp4UQzL5kgJt4g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR08MB4121
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/z-9VSDR6YU9_GVGepuyFrHqHidM>
Subject: Re: [Teas] Network Slicing design team definitions- transport slice
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: Tue, 01 Sep 2020 18:17:10 -0000

All,

Please note that 3GPP does not use the term “RAN Slice” or “Core slice”. Instead they use term “Slice Subnet”.
Please refer to the following 3GPP documents for example for more info:


  *   TS 28.531
  *   TR 28.801

Also see the following (taken from http://www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G).
The term NSI is for Network Slice instance and term NSSI is for Network Slice Subnet instance. As the picture shows, 3GPP does not differentiate between RAN and Core, all are called NSSI
The draft’s co-authors did not use the term “subnet” because at IETF this term (i.e. IP Subnet) has very clear meaning and using it in context of network slicing is confusing.

Also since the work at IETF is not just for 5G, we use the term “Transport slice”. If the use case is 5G, we also used RAN and Core Slices instead of NSSI to remove any confusion.


[cid:image001.png@01D6806A.8E70BC90]


From: Teas <teas-bounces@ietf.org> on behalf of Young Lee <younglee.tx@gmail.com>
Date: Tuesday, September 1, 2020 at 10:56 AM
To: "BRUNGARD, DEBORAH A" <db3546@att.com>
Cc: TEAS WG <teas@ietf.org>
Subject: Re: [Teas] Network Slicing design team definitions- transport slice

Hi Deborah,

I also am wondering where ' transport slicing' came from. 3GPP uses network slicing in the following three subnets: RAN, CN, and TN; and accordingly it uses RAN slicng, CN slicing  and TN slicing.

There is always prefix "Network" is associated with slicing whether it is RAN, CN, or TN.

As you pointed out, when RFC 8453 was developed in TEAS WG, we originally used the term Transport Network Slicing, but later this term was replaced with Traffic Engineered (TE) Network slicing.

Transport slicing is a bit orphanish. It should be either TE network slicing or Transport network slicing. In TEAS WG, TE network slicing might be more consistent with RFC 8453. Just for your reference, the following terminology has been defined in RFC 8453:


TE Network Slicing:  In the context of ACTN, a TE network slice is a

      collection of resources that is used to establish a logically

      dedicated virtual network over one or more TE networks.  TE

      network slicing allows a network operator to provide dedicated

      virtual networks for applications/customers over a common network

      infrastructure.  The logically dedicated resources are a part of

      the larger common network infrastructures that are shared among

      various TE network slice instances, which are the end-to-end

      realization of TE network slicing, consisting of the combination

      of physically or logically dedicated resources.

Thanks.
Young



2020년 9월 1일 (화) 오후 11:31, BRUNGARD, DEBORAH A <db3546@att.com<mailto:db3546@att.com>>님이 작성:
Hi,
(speaking as an individual)

Picking up on Jari’s comment “sometimes people want to use labels that are a bit more imprecise, but I think we should strive to avoid such labels as much as we can”, can you give more background on the choice of the term “transport slice”?

I noted while you have text on the use of “transport” by 3GPP as specifying a very specific sub-network in the radio network (which excludes the handoff to the rest of the network), you referenced RFC5921 (MPLS-TP) for the term “transport”.

There was a long thread of mail on ACTN, RFC8453, to move away from the term “transport” to “TE networks” which was agreed to be more specific/appropriate for TEAS. Considering IETF is already using the term “network slicing” (including TEAS RFC8453) and 3GPP use of the term, I don’t understand the use of “transport” in this document.

Considering IETF already uses the term “network slice” and 3GPP uses the term (and all the industry SDOs), I am concerned we will be confusing the industry, especially as “transport” is an imprecise term for TEAS work. Is this work a subset and scoped only to the 3GPP “transport” cloud (and implied use of MPLS-TP)? Or is it planned to be generic (for all TE networks)?

Deborah
(speaking as individual)
_______________________________________________
Teas mailing list
Teas@ietf.org<mailto:Teas@ietf.org>
https://www.ietf.org/mailman/listinfo/teas