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

"Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com> Fri, 04 September 2020 14:16 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 2E2203A0BD4; Fri, 4 Sep 2020 07:16:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_IMAGE_RATIO_08=0.001, 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 MkPnF7rs2GP6; Fri, 4 Sep 2020 07:16:31 -0700 (PDT)
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (mail-mw2nam10on2125.outbound.protection.outlook.com [40.107.94.125]) (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 5B9363A0BD3; Fri, 4 Sep 2020 07:16:30 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=K5+8Bt/Nui38Iox1loYmycv2vpxOMGRdfqWD6SB9vvv3BM5eGjiOSHaGucAe79ACWRu81SdAYNixHD9KsyxHOOywqJzUWO42FtkQ0U9OauFwwH5bTdXZgqA+RzazfgjDlyz2YRAtkYresiG7m+4cGNdYHQxDwUjoxVRpHTZGXvvVGw7SeoMRpgmf9qA9krMvuGTWbD8OzrF3dijiVyJrPCOMLMmuP/GoXMAEgSIdx0mhsyILCuRFmssH6FFPrCHvpCj4YGT/y1R2lUwpkGaWUj4n9uvOnVVYoN5aVHI0hr1RghRL8jsHX4+WW4OYzISKZVI5aaA7xxgqEbx1KcUL+Q==
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=kRfOrbVbQHopbDpTK1/VqCLoH34aQRRf1tin4XrIayE=; b=TbCXRFKcx9TLZIjuRhY+3wVX+aVnHGvcNk206UbCgkLLULIovwt239GBBiabTplr/IuUlM1bhTQEGcNWmxY0dG+ncJg+wo0u7DF8iorQkCEUv4x4EAz8QoZox5OF6TngWrxKp71to1ocGolEtqbxNp3S8sPYM92Ug/kMem37AgKhT66NKkwtu0Q0DyeFh3Ucc569sdVvb28/wU+EMsb+d6W7bi6/BtEtud03KfFrhuodIKp2nFaRv6ngos8+eV3+LPbeg5toSlT16k5wIASL9WemTFvYu9KFPw6LOm2ciSqU+z6Wz4ISaxYMvBo9BlNVX+pDGOHaVqY67HHdqNliMw==
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=kRfOrbVbQHopbDpTK1/VqCLoH34aQRRf1tin4XrIayE=; b=ACs1Pj5PXaZ6TbiFFeIC6aYFidCCQcBO8Zdq3duh5SXwuCEWSg+RR9kmkJMtvHhXMyveU0LhQSoTTfGr7PgX6vbFIOHg1lxYwwmxbbuzjXed7IGCVHtGR0fdzHRTN36SCiwG3pxiurkbSE6qZvrf+9ZYZJoloa4z3XYvOXUhPS0=
Received: from DM6PR08MB6331.namprd08.prod.outlook.com (2603:10b6:5:1ee::8) by DM5PR0801MB3672.namprd08.prod.outlook.com (2603:10b6:4:7e::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3326.25; Fri, 4 Sep 2020 14:16:28 +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.017; Fri, 4 Sep 2020 14:16:28 +0000
From: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
To: 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>, 'Vishnu Pavan Beeram' <vishnupavan@gmail.com>, 'TEAS WG' <teas@ietf.org>, "'BRUNGARD, DEBORAH A'" <db3546@att.com>
CC: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
Thread-Topic: Why term transport slice? [Teas] WG adoption - draft-nsdt-teas-transport-slice-definition
Thread-Index: AQHWgsX63GErIr9JAECVKqmtq/XJjw==
Date: Fri, 4 Sep 2020 14:16:28 +0000
Message-ID: <EBB5115F-1EF4-4F07-88FB-C5598A640D74@nokia.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: futurewei.com; dkim=none (message not signed) header.d=none;futurewei.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: 0b2b1844-4f39-402f-4bd1-08d850dd1d58
x-ms-traffictypediagnostic: DM5PR0801MB3672:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <DM5PR0801MB3672C3CD97103BABF66C6B819F2D0@DM5PR0801MB3672.namprd08.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 2Xb0UJNxs/XZ7C1KixkIPijtGIxazqhGMG+kyFAIlUXfj/wRmOpXG1kyX+AAuspoD1xUMFMN1toFDsuFkbtt9u0uYxPgGXIM/3jP2J1yX7vVQTdPjNOS/iUwFQTSkrHdsAf86zcXdKX68YN9Cp4dTub0Ehb7MbaTI6K1rNvfS4QOqMNQ4NRkh7cYWZUi9AZAXWf+OZn1y2XIs6CZjiSbzEzAcsee6ZbAEBj6KB9jJ6n0zVS0mOzXyZpjFSczANZ/+xBZkispw/ZJRuiOoh0uRumfJC2KKft56vCQX6/CuowaCv2ffNFDylqYFwhuVXdvwidhPgrHkZs4y74REIZdzb8tnWL6YK3nXZpFouLrGhElTRBNQ5z3fPf+JC7JRI8IW+4+vC5fPRBgLlWZbUtJfw==
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)(366004)(376002)(136003)(346002)(39860400002)(396003)(6506007)(66556008)(478600001)(66946007)(5660300002)(76116006)(64756008)(66476007)(66576008)(66446008)(99936003)(110136005)(91956017)(2906002)(186003)(26005)(966005)(86362001)(316002)(4326008)(8936002)(107886003)(71200400001)(6512007)(2616005)(8676002)(36756003)(33656002)(83380400001)(166002)(6486002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: bE7Ru0p/eR1YoNxR7vUFVm5y/1QK0DGkWnhPm3MqeUHVxSzZ+jmwsBxnGZOD/s52Vj4XYbNAmVN1o1/8YE3/AsDeEnhmK4Pe750EKPstshFqyJrk1OWPtp9iGuf5LuamCTBm8PdJVC+iZLM5udMr6eFmr0t8cWhWKUzENiiJXzTEt8n9YBNpHty5Ips22gbUZZiiGsbrWPKjChqjfdUYKE6ifWF5UbHNxrSucI2K/XSJLfKbuzm9XyXeiR5uv9b9tNSi7cFO/XZlUTTr6pzctjqX8f2tIAFMZOMTuLdk8rm9abMMZvsUp+E5fSF1DGwipJMM9EDh+m2jAEngAHd2tuZEMKtlOAe1/cMGNfDL9lZdaESZVyTpFuL1CF5E8m0aQvEG//w7lI3Lz7xve1EagkIEmAMGqUmH0idYFXD4nbZVt/R3gSnjlZ77oUuS3pZ+yNsM0zDRV2avrPm0b+Ieybt9/zKjlsZgDv4uPZS+HLZh5iAubVVQP8NKY4GyqiU9wB5p7WbEUk4O0UwEr43vPGBmerpMS3gGzwjW9Hdw1xqCL3d680+hkB3LUn6Sh+v3EVmxZ8py6itZoGcZ99mgQlNHM2aD5s1CT/+e4ewYhdkaLhOx8OGlEgIQQzIUmfBwg15CI5imoE1gbOhj9xBPjw==
Content-Type: multipart/related; boundary="_005_EBB5115F1EF44F0788FBC5598A640D74nokiacom_"; 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: 0b2b1844-4f39-402f-4bd1-08d850dd1d58
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Sep 2020 14:16:28.1702 (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: ztDu4h76WN8pwE01B46AY6gvcVD+Bt82dDArHsvNkFXIsHAeFMcLeZsMz6EB31Y0KpvSJohB3IUGA3wvEUY8gA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR0801MB3672
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/GvCsWwDTekSHhW_WmmegfFn7Dw8>
Subject: [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: Fri, 04 Sep 2020 14:16:35 -0000

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.)

[cid:image001.png@01D682A4.71E94A10]

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



  *   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

According to the picture below,  the reference of transport portion of a network slice  is referred by “Transport network supporting connectivity’

[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



  *   3GPP: See Figure 4.9.3.1 of TR 28.801 and  http://www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G

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