Re: [Teas-ns-dt] New Version Notification for draft-nsdt-teas-transport-slice-definition-00.txt

Eric Gray <eric.gray@ericsson.com> Mon, 18 November 2019 11:02 UTC

Return-Path: <eric.gray@ericsson.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 CBF5D1208F1 for <teas-ns-dt@ietfa.amsl.com>; Mon, 18 Nov 2019 03:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 a4ZDdbcdbpkM for <teas-ns-dt@ietfa.amsl.com>; Mon, 18 Nov 2019 03:02:13 -0800 (PST)
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-eopbgr720053.outbound.protection.outlook.com [40.107.72.53]) (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 7A2E6120908 for <teas-ns-dt@ietf.org>; Mon, 18 Nov 2019 03:02:13 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RJSZcNYHD8aYsn3K5RAz7GVqZR7mtj9ac0cAccpV25bqq/KO88BKK6gIpGCeMx84QtP9ouhN7gfTDT551+H91Y95ra3/fOGKOaB6nY6DIp3lx+xxUtNAmANlRjNAahTDH+WLEfkO80DHw5P0q1WLQWL0+Xwvp/nZGDiaEzjFTqb0fNQzMoMFZ+k1ImU585YdspfyuAJpKa3qZYAreHXu0r70cV2+2WO71EaufjfK28+9lwNvJdROnc2x4UvdC2suTs3f1cbBBUrgPS9N6phBuzVliY92G2XToEdP7zSmhh0tYQmXjYj19UPZ9KlS7spQCxhY6uj3GkYyvCkVNmC1og==
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=CLC8i98MsZi4W0fOcfE9Cx6z9+av1c0l/R97AnYTj/8=; b=fiDc/gMnrFRe4QvD/cNMwOQgtnpP+/QMO92Bes6ZqSXmtpJMYSBZ7Lp4itvyzGlwZAtHHm1S4vboF294CZF6pc0uGIMJloXwGwERg0YLR5r8rbQrmRVM9E4Lmc5AWJVPLKuuAvIv/bHjlNYIVTKoQK6YBs7TqF8zj4DMVE2LSjy2bDE5JqNAg01lJpzZtHM6Zvq3crKX/WitCuUSr+QEnZ1UVtPDqMZlYSGmZoyp5pswGWC3GM2BmBN3rBK3RxFIVTRpgtWCExD0s+V5MU9P3vv/lTTYF/OKdE6orBOi3POkMsrVIkT/5An2WCuvTh41WltnCDAFItXEEVJnl0EI1Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CLC8i98MsZi4W0fOcfE9Cx6z9+av1c0l/R97AnYTj/8=; b=eI3AvjpoFqvZhFC16d8GXsjTtCCOQuAXeAMtJHji33khnWCUqBPmZvIlYmM6ib6EmKwPa8Gp32t1taAN5u35kD4vK8JqW0eduBAvDErg5daZKlgUR1+6gxE3ebiHd9HlBWh5uosH6FGAyc64ovo1EJ/kAXZkNPLhc8yl562qlrE=
Received: from BN8PR15MB2644.namprd15.prod.outlook.com (20.179.138.27) by BN8PR15MB2819.namprd15.prod.outlook.com (20.179.138.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.20; Mon, 18 Nov 2019 11:02:09 +0000
Received: from BN8PR15MB2644.namprd15.prod.outlook.com ([fe80::b850:e5a7:20fa:ca1d]) by BN8PR15MB2644.namprd15.prod.outlook.com ([fe80::b850:e5a7:20fa:ca1d%3]) with mapi id 15.20.2451.029; Mon, 18 Nov 2019 11:02:09 +0000
From: Eric Gray <eric.gray@ericsson.com>
To: Jari Arkko <jari.arkko=40ericsson.com@dmarc.ietf.org>, "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
CC: "teas-ns-dt@ietf.org" <teas-ns-dt@ietf.org>
Thread-Topic: New Version Notification for draft-nsdt-teas-transport-slice-definition-00.txt
Thread-Index: AQHVklpLKKG5Sn/KnEiSeO9D/3tQ5qeIVfGQgAADRoCAAU5WwIADQTkAgAK0pwCAATtbIA==
Date: Mon, 18 Nov 2019 11:02:08 +0000
Message-ID: <BN8PR15MB2644E91D9A072994C876CF18974D0@BN8PR15MB2644.namprd15.prod.outlook.com>
References: <157279398342.13436.8646176235211541803.idtracker@ietfa.amsl.com> <A221C2A6-52D7-4865-B814-6A2D2D9066BA@nokia.com> <BN8PR15MB26441D2FCC74FA4947D25F0E97760@BN8PR15MB2644.namprd15.prod.outlook.com> <A1A20161-CDBA-4ABE-ABF3-4BAF3F4DA543@nokia.com> <BN8PR15MB264495EA8D8B0AD33229139F97700@BN8PR15MB2644.namprd15.prod.outlook.com> <DB80ECD2-1A7D-45FE-8372-FD5A1175B5B1@nokia.com> <42EC79B8-51D0-429E-9A21-B6F1B6A7DABC@ericsson.com>
In-Reply-To: <42EC79B8-51D0-429E-9A21-B6F1B6A7DABC@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=eric.gray@ericsson.com;
x-originating-ip: [108.178.151.98]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6b33ea03-7ada-45fc-72c7-08d76c16c1be
x-ms-traffictypediagnostic: BN8PR15MB2819:
x-microsoft-antispam-prvs: <BN8PR15MB2819C2823F57E3E608F05A1C974D0@BN8PR15MB2819.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0225B0D5BC
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(39850400004)(366004)(346002)(376002)(396003)(51914003)(189003)(199004)(54896002)(9686003)(4326008)(99286004)(64756008)(66446008)(8676002)(86362001)(52536014)(66476007)(81156014)(81166006)(256004)(76116006)(7110500001)(3846002)(14444005)(66946007)(6116002)(2906002)(8936002)(66556008)(33656002)(55016002)(486006)(44832011)(53546011)(25786009)(6306002)(478600001)(6506007)(476003)(2420400007)(14454004)(790700001)(15650500001)(11346002)(446003)(6436002)(102836004)(26005)(76176011)(7696005)(186003)(6246003)(229853002)(5660300002)(110136005)(7736002)(316002)(74316002)(66066001)(71190400001)(71200400001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN8PR15MB2819; H:BN8PR15MB2644.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: J08QZBm2deEd4EfjlK+pLQu666dxdyn46azUoug5kITsfAC8FKDIq7zXSeIMEK08tI3ywF+Xvz+U4jf1sfLtZjlNAJALmZJeLXqR4n4+HN+XcWWq83WVhHT0llEORPnT7n8R71hJcmvMcu9pbR6xpuRLrazS2Hzf3xohBZxuswizdNs7ehYDel/omMzQau9azgOqg7ZGIKtelekRi/fAQLqRWTBI4+CUjx0q9QHlm2L8NRADUFrAi49Crk0zuzzwUKMFhJmM582KKtdyzHr6wzOwozWZpR1l0OgPYmeCD0MacR0YsjqmMPm4XVe+hbMeB3bQy2fU/0d32Y19cqCqmfEeJ3f0S3LwzFmb88bp2k+9/au2RreMrU8ruKo35KjInacp/ifGZItZeo6HC6Ziotu5rWovjNeCt1BD8F/ILB35waQgFO7WK971p6CloEv+
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BN8PR15MB2644E91D9A072994C876CF18974D0BN8PR15MB2644namp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6b33ea03-7ada-45fc-72c7-08d76c16c1be
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Nov 2019 11:02:08.9500 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 5QSUKJmy+b5dxfrteGFgtYdvhKZDkMue1O6dSsLnshGMijulzDO1aPm3l2mCJzZAcbxvw2nT9t1S8rG4iMHwEw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR15MB2819
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-ns-dt/nOsigp4LusvU5CYGyJ0YKx_elFM>
Subject: Re: [Teas-ns-dt] New Version Notification for draft-nsdt-teas-transport-slice-definition-00.txt
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: Mon, 18 Nov 2019 11:02:16 -0000

The biggest issue I have with the use of SLA is that – from my understanding of the work in the IETF to date – the concept of a “service level agreement” is quite foreign.  It represents a contract for a service between a service provider and a service consumer (or subscriber).

We could spend quite a lot of time – time better used in other (more IETF-relevant) pursuits – on the finer details of this sort of contractual arrangement.

From the perspective of the folks who are defining both the technology, and its control, what we are more likely to be concerned with is the parameters that make up the relevant service details – not the instrument that gives both a subscriber and a provider legal recourse to recover perceived damages as a result of a failure to provide working technology and controls.

From: Teas-ns-dt <teas-ns-dt-bounces@ietf.org> On Behalf Of Jari Arkko
Sent: Sunday, November 17, 2019 3:07 AM
To: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com>
Cc: teas-ns-dt@ietf.org
Subject: Re: [Teas-ns-dt] New Version Notification for draft-nsdt-teas-transport-slice-definition-00.txt


Thanks for the discussion.



I reviewed the definition again today, and have some comments/suggestions.



First off, there’s overall quite a bit of material in the draft overall. Sometimes it is useful to nail down a concept in few words familiar to networking geeks even outside the mobile network space, and leave examples and use cases and mapping to interesting other things (such as 5G) to other documents. That might benefit understanding from others… we can talk about how we want to convey the final definitions once we’re done.



Secondly, I’d still love to polish the compactness of the definition a bit, to base it on fundamental concept. How about this:



OLD:

A Transport Slice is an abstract network topology connecting different network functions (NFs) with appropriate isolation and a specific Service Level Agreement (SLA) described in terms of shared or dedicated network resources. In other words, a transport slice is a group of connections that connect various NFs in the network to achieve some specific SLA for a customer as shown in Figure-2.

NEW:

A Transport Slice is an abstract network topology connecting different network functions (NFs) with a specific Service Level Agreement (SLA) described in terms of expected network service. The SLA can include characteristics such as guaranteed bandwidth or latency, requirements on the use of physically separate equipment, etc.

Jari