IETF Logo Mail Archive

Re: [Teas-ns-dt] Definition of transport network slicing

"Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com> Wed, 16 October 2019 13:56 UTC

Return-Path: <reza.rokui@nokia.com>
X-Original-To: teas-ns-dt@ietfa.amsl.com
Delivered-To: teas-ns-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84CE8120026 for <teas-ns-dt@ietfa.amsl.com>; Wed, 16 Oct 2019 06:56:53 -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_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 1tWBm7Y2t6bn for <teas-ns-dt@ietfa.amsl.com>; Wed, 16 Oct 2019 06:56:50 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on072f.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe02::72f]) (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 E4D7B12001E for <teas-ns-dt@ietf.org>; Wed, 16 Oct 2019 06:56:48 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gZmbVHJko8qCyUnqCgHVpoAcmHxIdh8tqXq4FVY91xPQrjlybPjksledBo4j48Fx4MAToPn/sJ80oIZBlIOaEKGspPQroUchtO/MJ0TqnJLi60/s6h34bTlkV6+iO/NHNmGMKkDTY3HYrbEmRUogFELxCkc2RENNtjGh/BLRBS6ifBKCKlkjc51MfZz2SaJESLYxvRhHW2zBZH8o/xzpnoS+cB84c3dU1EocO5zeqTS+8HR1cJtMshYTIziL4/+cRn2a2DQmpEQ5s+BajzugtFNbYN/YyPpe3qmMcYbNtKgJe875q7Nwnh0HwYCiwRAevy/+mvbeyBD5L/uumm+UBA==
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=adpHHSuiAUJ7YIBP0p4R77jGTW7OXmMg0jRUOwzDsck=; b=Zevvp1cHLX3daBvfnuPb4fvoWAoiDgYRC3REZ+1q86VBnJLeuOqu0BDosrb9Mpv8shSWXLgcNUEOw+PATtjjPsm2qSAlTRVBitoqGjcsZazdYdxq3FqtudHYn1+r+vrkHGRei4cVGaMwbS2ARwqzA9V9P7IUomv/Bliszz7sMh+YEFinrKYFfHD73GPKjlZSipa93smOQsIpRQ96VETzTg9Z/DypaYNRONjykszpFmQ0xEEtK4U2LR+2RyupfUjjjuB0vKnupM7s4dEoBHstVbnKWSHrTc3toiboQ3MJhY+FYl+UzGrqB7iAyUDwlAuBtva9viJ6tiZq4DUFnQFfGg==
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=adpHHSuiAUJ7YIBP0p4R77jGTW7OXmMg0jRUOwzDsck=; b=vewVielcl9sqSyz/bMUn0zfEP70GoeZscXm4OuZQouKMERw0s9CoaqFyzXu7Eicr9nIngo07c+QFpXe9tcAzgDeS62Y7oezIZacrklA64ESwWmcEZVoHmdPmlyiINXNu8kCtFGvtUetw21BoVeCDT9NgbIM7gkjNaPR7uIKRO6c=
Received: from AM0PR07MB6098.eurprd07.prod.outlook.com (20.178.112.202) by AM0PR07MB6292.eurprd07.prod.outlook.com (10.186.172.79) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.13; Wed, 16 Oct 2019 13:56:44 +0000
Received: from AM0PR07MB6098.eurprd07.prod.outlook.com ([fe80::1dbf:15af:851e:15ee]) by AM0PR07MB6098.eurprd07.prod.outlook.com ([fe80::1dbf:15af:851e:15ee%4]) with mapi id 15.20.2347.021; Wed, 16 Oct 2019 13:56:44 +0000
From: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "teas-ns-dt@ietf.org" <teas-ns-dt@ietf.org>
CC: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
Thread-Topic: [Teas-ns-dt] Definition of transport network slicing
Thread-Index: AQHVhCmLNkwDr32fR0W4Hi17u6EzmA==
Date: Wed, 16 Oct 2019 13:56:44 +0000
Message-ID: <23F39B19-B3FE-4F67-BCB2-4C4891A591AB@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1d.0.190908
authentication-results: spf=none (sender IP is ) smtp.mailfrom=reza.rokui@nokia.com;
x-originating-ip: [131.228.32.174]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6c687824-0157-46fa-a115-08d75240adee
x-ms-office365-filtering-ht: Tenant
x-ms-traffictypediagnostic: AM0PR07MB6292:
x-ms-exchange-purlcount: 1
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <AM0PR07MB62926E979CAAD37CE97074659F920@AM0PR07MB6292.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0192E812EC
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(346002)(136003)(366004)(396003)(376002)(199004)(189003)(229853002)(26005)(66946007)(256004)(8676002)(76116006)(66616009)(733005)(5660300002)(66446008)(14454004)(66476007)(66556008)(64756008)(6116002)(6436002)(91956017)(606006)(186003)(8936002)(102836004)(99936001)(66066001)(53546011)(6506007)(81166006)(81156014)(86362001)(4326008)(3846002)(6306002)(110136005)(6486002)(236005)(54896002)(476003)(99286004)(6512007)(36756003)(107886003)(2906002)(478600001)(966005)(2616005)(25786009)(58126008)(6246003)(71200400001)(71190400001)(316002)(33656002)(861006)(7736002)(2501003)(486006); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR07MB6292; H:AM0PR07MB6098.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: kubPChIH1z5P1qitJKkjU30bukgfP6jDkU5Kn4xBxW2WEr6W0UEvng9udW0ft0LfzfO1PruUE1hUvkxx/kExTPInrbCvLRiLjTMfC0fWmQBOQuDG0U4nYBzjlB6GWVdC3MT8QGIIh9muop4bz5G4VoeQNoND6awCECq3Vqwe4kzWMJgMaE2TAnQhuiLoFFb6XQksMlRZ+ILeoVOF3Y6AoLGd9kv/umztRsvbiRTdp/9YYKJ598kvgU0gtKSPe2sl7EGkIua5l9/IuTVuUKSz5p4i0D9sM/E9ja9PyNYzkJSJpgkshddJ640SvOpo4ntTdwHGEuZkHG9NNOh/PLU/VSir550cK4sePel3LyvjTJbfoBuTQ/VN2W2/jCeel8ButRsB6gt7Few3as7h5Llws+Ua9Pchnx0xAzoBOFV83igT1GKv3Rf7KC4Y5nzoJKAl3o1zRlAoiBFo0q+QNQL7TQ==
Content-Type: multipart/related; boundary="_004_23F39B19B3FE4F67BCB24C4891A591ABnokiacom_"; type="multipart/alternative"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6c687824-0157-46fa-a115-08d75240adee
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Oct 2019 13:56:44.4676 (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: dFnpsnsc6ixpntlNnnaYWFlrng/2jfTxmeYc35PSgEppAyQZAoxBWaM4ET2+nApVBcJDSLivKnmulQtJsvfYnQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB6292
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-ns-dt/Luke3erU5134bMJtrbqTM1qUQ2A>
Subject: Re: [Teas-ns-dt] Definition of transport network slicing
X-BeenThere: teas-ns-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TEAS Network Slicing Design Team <teas-ns-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas-ns-dt>, <mailto:teas-ns-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas-ns-dt/>
List-Post: <mailto:teas-ns-dt@ietf.org>
List-Help: <mailto:teas-ns-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas-ns-dt>, <mailto:teas-ns-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2019 13:56:54 -0000

Hi Jie and all,

Your definition is correct. However, the following is my view. Please add comments.

In general a transport slice has a definition and a realization (aka implementation). The transport slice definition is whatever Jie mentioned below and I rephrase it here. i.e.

  *   Transport slice definition: A set of connections each with appropriate isolation and specific Service Level Agreement (SLA).

However an transport slice has an implementation (or realization) as well. To clarify, let’s have an example.
The following picture shows the most complex 5G network (i.e. Cloud RAN where it contains fronthaul, midhaul and backhaul networks. In this picture there are 4 different transport slices for a single E2E network slice.

Each of transport slices 1 to 4 has an implementation which potentially has different technologies and different techniques. For example, the transport slice 3 can be realized on IP network using L3VPN or VPN+ or any other techniques to satisfy certain SLAs. The fact is that we can realize the transport slice 3 using different techniques but the regardless of that, the definition of the transport slice 3 does not change (which is connectivity of CUs to Core network).

Another example is the transport slice 2 in midhaul which its definition is connectivity between DUs to CUs. In majority of  deployments, this transport slice will be realized using PON technique or IP VPNs. Again regardless of implementation, the transport slice 2’s definition is DUs to CUs connectivity with certain SLAs.

If needed, I can present a few slides during our call on Oct 17th.

Cheers,
Reza


[cid:image001.png@01D58457.A0B90980]



From: Teas-ns-dt <teas-ns-dt-bounces@ietf.org> on behalf of "Dongjie (Jimmy)" <jie.dong@huawei.com>
Date: Monday, October 14, 2019 at 5:57 PM
To: "teas-ns-dt@ietf.org" <teas-ns-dt@ietf.org>
Subject: [Teas-ns-dt] Definition of transport network slicing

Hi,

As one of the action points of the design team conference call in last week, we will discuss and give the definition of transport network slicing. Here I’d like to reference the definition in https://tools.ietf.org/html/draft-ietf-teas-enhanced-vpn-03 as the starting point:

“A transport network slice is a virtual (logical) network with a particular network topology and a set of shared or dedicated network resources, which are used to provide the network slice consumer with the required connectivity, appropriate isolation and specific Service Level Agreement (SLA). “

Please feel free to provide your comments and suggestions.

Best regards,
Jie

v2.23.0 | Report a Bug | By Email