Re: [Teas] network Slice Endpoint in draft-ietf-teas-ietf-network-slice-definition-00

John E Drake <jdrake@juniper.net> Fri, 12 February 2021 16:46 UTC

Return-Path: <jdrake@juniper.net>
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 6BCF43A17A8 for <teas@ietfa.amsl.com>; Fri, 12 Feb 2021 08:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.258
X-Spam-Level:
X-Spam-Status: No, score=-3.258 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net header.b=UEUm4ghm; dkim=pass (1024-bit key) header.d=juniper.net header.b=jCTyb2rY
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 wg0HLhj_Udg3 for <teas@ietfa.amsl.com>; Fri, 12 Feb 2021 08:46:43 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 759853A17A7 for <teas@ietf.org>; Fri, 12 Feb 2021 08:46:43 -0800 (PST)
Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 11CGeJAZ026238; Fri, 12 Feb 2021 08:46:42 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=ZTRFSVRjqbwlT1v0hPZMQNixuIFQf5QCqHEs1n57SUY=; b=UEUm4ghmAogkVamWVdvg+Dzmh5r4EeoDhH4FOi2VbNUmb0JfE3KLNs+XyrKCIv5+wl4s 8yuQoaT5oMrhI1XHc3mvDjUbBJuLThE9dawVofrue5/yGy35yBw9DD34G91LMKbnCCJ1 bl8qer+gdEIUIpNCkdgyKz+IY9LoUwdC86hSX+ZT8Kvvvmoa3HNevDq2PNKKPRYO3NaC 8vLm5xXFf5GI+YjmQ4Zbljuh8aPTBLcEV0WS5DnI6RhWHLTtFyvGZEiqU2AicTf57DMn FzuXWfP1AalCA/5qaJ5UPoGrPoZJYcFHmrKQzcfyOioFj/HjOBtoJsFql/lkQVxfBzIX 6w==
Received: from nam12-mw2-obe.outbound.protection.outlook.com (mail-mw2nam12lp2047.outbound.protection.outlook.com [104.47.66.47]) by mx0b-00273201.pphosted.com with ESMTP id 36hu43v1f6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 12 Feb 2021 08:46:41 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Pt42t7o0qSM1CAxsbkVE5NUCQfUauDHNAOTBuWmevHWN6zIF7JEuMhgqk01Yu3irPZs6OmwNR4DPjEZXo9UdJmU+IBKFksMLZ2hrMPgunL5hkAmRvCOV7IwTesCa6GSyswQxB3kCHXd+YGBZXMGFnE7bCcem/KcB9Q+woaSvI+2YS+7xCklrwgXm1nGlAizv621Vp+wmAVi9ZmBDVfO5nA3xbFG8/y7O6NWgd9oBawQhhqFHA10SUyS3nxUPCWwpopclkRp7MBCg0P3Bh9PalO1AATQXklr99cxxtYNicRZlM56QY2Dm7jN1FkW9zfZBPIo+mSrOm00o8k2X/DPhAA==
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=ZTRFSVRjqbwlT1v0hPZMQNixuIFQf5QCqHEs1n57SUY=; b=mhqWZmchs4vDkXtALMChgFFAHM9mNJNzZpJUiVMqNAvjqxy+wZJAAZgUE5UlorfRpLquKceF0FIlHFCsdJ+/21DfYYw9nbleIBDT77M3DmMZWDaMXCxx7D5t5VrVeSqlEmRE1SL9yTpJuF4FZWbuffBC9Ura06yp6CCbLvG9O1MeYAcX8NuoUFpiz+5c7l46sU8XgeCnY7UNGM9REbV3hKA5KABnOPP6K7PAD60cB1xzRMANnPb7+WZiqKbOggcDs32SJzkJk2GmjKSTe5VYXurktNEf9c8qRAHTu46u3sx6a7GZBHIYQ/onmTY5Tspy6x8ufEsQjvtYY/Q8PYxp8Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZTRFSVRjqbwlT1v0hPZMQNixuIFQf5QCqHEs1n57SUY=; b=jCTyb2rYx8JbZWL3j5hd+Qx6LjsfhZoBXLg0tkW34xovX6ojJfVcklXgimTsigM6YKgslOf2PfyeJeaeIVzAVGaiD8Ue+gTFK2HdlSt0upbT7ltsH5l/4gaGDB+9Vb/qbnbtUFRCyZgWSIOF3rVqxGO8YQGnpm6d+jxCF0VsaiI=
Received: from MN2PR05MB6623.namprd05.prod.outlook.com (2603:10b6:208:e3::23) by BLAPR05MB7412.namprd05.prod.outlook.com (2603:10b6:208:297::5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3868.17; Fri, 12 Feb 2021 16:46:38 +0000
Received: from MN2PR05MB6623.namprd05.prod.outlook.com ([fe80::15d:9352:e16c:49ab]) by MN2PR05MB6623.namprd05.prod.outlook.com ([fe80::15d:9352:e16c:49ab%7]) with mapi id 15.20.3846.029; Fri, 12 Feb 2021 16:46:37 +0000
From: John E Drake <jdrake@juniper.net>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "'Rokui, Reza (Nokia - CA/Ottawa)'" <reza.rokui@nokia.com>, "'Joel M. Halpern'" <jmh@joelhalpern.com>
CC: "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] network Slice Endpoint in draft-ietf-teas-ietf-network-slice-definition-00
Thread-Index: AQHW++D8783XzB8rikeS8cDbgan+4qpKJNwAgAc20ACAAD1MMIAAE86AgAMSUAA=
Date: Fri, 12 Feb 2021 16:46:37 +0000
Message-ID: <MN2PR05MB6623ED37515B1C789DE6E46FC78B9@MN2PR05MB6623.namprd05.prod.outlook.com>
References: <cc3949a4-1e60-7f77-45bd-2470be67d9d5@joelhalpern.com> <022001d6fc0e$4facba70$ef062f50$@olddog.co.uk> <86EF8667-4A3F-463A-BA3E-FE74F4875772@nokia.com> <MN2PR05MB6623EAA3DD2499C095311CDFC78D9@MN2PR05MB6623.namprd05.prod.outlook.com> <048e01d6ffd2$450970f0$cf1c52d0$@olddog.co.uk>
In-Reply-To: <048e01d6ffd2$450970f0$cf1c52d0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.6.0.76
dlp-reaction: no-action
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=true; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2021-02-12T16:46:36Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Method=Standard; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=0633b888-ae0d-4341-a75f-06e04137d755; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=1fb5d099-5249-4f58-80cb-407daa4fab32; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=2
authentication-results: olddog.co.uk; dkim=none (message not signed) header.d=none;olddog.co.uk; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [66.129.241.13]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: f4fc083a-1c2b-49d6-ee29-08d8cf75c3f2
x-ms-traffictypediagnostic: BLAPR05MB7412:
x-microsoft-antispam-prvs: <BLAPR05MB7412D6085E68A0BD9359C253C78B9@BLAPR05MB7412.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: vo+YtlbR3sPu6uv8efvoo6TjdfVtxW+ZW6ix9jWg/0TTR6noZVPNs3v9DlGhXhXhpwTKCxKSsy0wkYVKIOhOrLjwxS/X/h2AuAJIjs3/9rqasJ9U7OL9hOfqMx+j6ubgmmV9l8MBO+WEAnZbZPwfvjB2Lw+Aal65O5w5UumEGnbqTOPyN9L3NZ0/CIt1X/o5fNUkjg9DwOkiP4QiCHwD1i1Oey/nR0J0VchmUvREl58fgGYhLAt6ryCprVQaXkjVxo4IG3Iy7a7F/wIOoapuEjTq+ZAImjxlOAaI5lvDGPFHLLkIv+NTsPWdnUr2VZ6dvWaA5v41xYl+twxXEgiObWLrBI6teg2T1LqKvOgMMYbnQhxiyMEaVP8oKWm1LizvPFEb9atJuQVZgF1plVh9yXC1g/PvDzs2YpDjrVU1Nl3hH4/YceOcYmwiJR9irNMrkat6oLAia9FiO6kHJuj20alYVUwGsa9qjMatmYeHtR9i4KMEhGTCW/M1nD8Wix91j6qnM6FV9V7V7cxwjL6W+lVe/lR1FM16e+TfXxOcoSezFRpnJrFTyTz6Lwu9/IWa83OK5X04FAuAL82B8+GmNwMcGAECEIPfxn84iQ4bmH0=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR05MB6623.namprd05.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(136003)(39860400002)(376002)(346002)(396003)(9326002)(9686003)(166002)(316002)(4326008)(6506007)(53546011)(76116006)(8936002)(86362001)(110136005)(71200400001)(55016002)(7696005)(2906002)(33656002)(83380400001)(52536014)(66946007)(8676002)(26005)(478600001)(64756008)(66556008)(66476007)(966005)(186003)(66446008)(5660300002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: =?utf-8?B?Nzhzck9qU2xvZUc4NjVFSGNsWGNtdVRkc0toNW9wZHBaTHdMWXZjN0U5bUU1?= =?utf-8?B?b2x6d2tpUjFnSGJLSTN1dlZKTTcyZHcrak9lUFI5VzdxaDAxMUh5a1Rac1Bn?= =?utf-8?B?RmNUc1NOb1JmY0Ewc01KdnRmWnIvZjUzNE94SkFzL3FNdEMvSGlpdjQyM2g3?= =?utf-8?B?cEM5QTBvNC9jc01lc1JKM1JkTmYxSjlSL0gwOFRSNW12Sk1Kc2g5MnNCalQ5?= =?utf-8?B?NXVOY01aRWJ6bVZDNmQzWEZBV0Q4SWlmYUxISGZuOE84R1RVYklNV0xyWGxP?= =?utf-8?B?WHdKSGhtRGswa2hWd2VLTk55eXNhcXlwZndJa3h4WWN0K2JjeFJhanVuWm12?= =?utf-8?B?anFOaW4yQVI0Z2RGejArY3N4NytnRUs4anpFREhDWkIzb2ttbFpTNk92b2Np?= =?utf-8?B?a1YxWExIS2M2eGZkcTNXOU5ZdHp1dzJRR084QWNLRjNJak91SjJNeHpjNWJX?= =?utf-8?B?eEcxNUNUUVRuSE5zN0tuMkdETTRQY2thY244Sm91YTFZQzAxd3R1d1F6YkR5?= =?utf-8?B?NSt0K1pCbldESVA0M3VMOTFleE5MaXVubkdBS2h2SEVEbWpubG82TGNOMnk4?= =?utf-8?B?K2VvU2dJVzRLV21oNDFCa3UrVUJJVS94eEN5TWdlZzArZlZmL1FyM0RtTDRG?= =?utf-8?B?QUFVTzgvQmFMMGZNQUhISnVpblJzZGx2ZWVhUU9RTmpjdjNNelZKTDczQ3JY?= =?utf-8?B?K0NWNHRhaWlTZFNjS1pYL3pMN0R1b1NXbjRiNnp0M0ZtNWFzZFNXMHNkOGZ4?= =?utf-8?B?MjJLOGNLdHVCZ1hWeVprRG9FVGNxRnYyRkxwV2lJNnpwd2tsaTBaaEp6MXBQ?= =?utf-8?B?a09KOFZwUElCZUNNWlIvMHU0K1B6WDNrRjdER0lkeUdJa1dNZ2UyMEpJRHBO?= =?utf-8?B?MHNjaWNscUp4WmNoM0JZNEllU2JuMVBONmtvLzg3RjBPbnVKRHJmeW9xV0Uy?= =?utf-8?B?K3YzTGRGdzF2TWkyRnRFTzRIeVFJbjhZQzU3K3cwaU9YcmFaRmllaWNycENz?= =?utf-8?B?cnZoeEQzT3IzbVE5cTF0cklObENNL3RYZld6TGpnWHVkd0hDLzkvVzlsRWlG?= =?utf-8?B?Z0dJZUMrWkR5UFJoUlladnlLT1Z4YUozeUhRUVhwZGkxcXI3M1FyVlZjckp5?= =?utf-8?B?Q1BaU3FsQXJpTmt3TUtiWkkwcUxIVGwrSk9EWlVma2x3VHlFa0EyUmQ1Qjdo?= =?utf-8?B?T05kbnhYeGxuYjIxUkpucldQR0JjeEtBOVNpMXNBWGErRFB2Q2pGWmZRNWV2?= =?utf-8?B?QmZmYjFTSGpHQ3Qvb1RWcXRFUFdxMmoraDc5Q1MyRi9HMTBqTkN4U2g0bWFT?= =?utf-8?B?VFhIUHppQ3BnYmF5MDYxTWFJMVhLeTRtQmVRTGREMElubk9STUJrdDVTN2pn?= =?utf-8?B?OEFNb0JaTmF0MGlVNCtPa2RabTFaU0hrN3JTSzRtMWxqMG16Zk9NRHRUVnFa?= =?utf-8?B?cVllVVU2Tk5HNTF2RDdmbCtZeU9rYmNtemJWQ2tzOWNRWUlGR1hUNm1SOXRF?= =?utf-8?B?amZxNldNQTNUSmZlNHc1d1FJYndyT0EzbXhDMGprdkZmSXpLVzRrdHYzYldU?= =?utf-8?B?V3dRODMwTVVZeUdqaUVpZXJPSDZ4dytYdnY3MU5BMWwxNEJ5ZWVmM2phQ0Jw?= =?utf-8?B?aUFvd01DMWFTVm1lb1NJVm9mTXJwd1lseHBFWmE0NExacERQdDJlbEFmNGd5?= =?utf-8?B?Vk9GQmRSa0ZLSVNSeTZrVk1NNGU0V0NVbzlzQkRJSVFsTU9JYW1aTzJ1Snhr?= =?utf-8?Q?VDb2nwRvxtFAbdFq2dzH4c0fCW7lQgkzc8eE+Dr?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR05MB6623ED37515B1C789DE6E46FC78B9MN2PR05MB6623namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR05MB6623.namprd05.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f4fc083a-1c2b-49d6-ee29-08d8cf75c3f2
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Feb 2021 16:46:37.7127 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: KqyotUPSgH5C5bv+k43FSs/0CvnVACK3Zvvczd6zcGqdkePmbS5hxXZBf6ghHQM9eYssqEYlva13xzALLBzkBA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLAPR05MB7412
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.737 definitions=2021-02-12_05:2021-02-12, 2021-02-12 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 impostorscore=0 suspectscore=0 mlxscore=0 adultscore=0 phishscore=0 spamscore=0 clxscore=1015 bulkscore=0 priorityscore=1501 lowpriorityscore=0 malwarescore=0 mlxlogscore=999 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2102120126
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/vauxNZW5rWG25kudUkCNENvASK8>
Subject: Re: [Teas] network Slice Endpoint in draft-ietf-teas-ietf-network-slice-definition-00
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, 12 Feb 2021 16:46:46 -0000

Hi,

Comments inline

Yours Irrespectively,

John



Juniper Business Use Only
From: Adrian Farrel <adrian@olddog.co.uk>
Sent: Wednesday, February 10, 2021 12:29 PM
To: John E Drake <jdrake@juniper.net>et>; 'Rokui, Reza (Nokia - CA/Ottawa)' <reza.rokui@nokia.com>om>; 'Joel M. Halpern' <jmh@joelhalpern.com>
Cc: teas@ietf.org
Subject: RE: [Teas] network Slice Endpoint in draft-ietf-teas-ietf-network-slice-definition-00

[External Email. Be cautious of content]

Hi all,

In case this discussion is getting heated, can I observe that I find Figure 2 of RFC 3985 hugely useful in this context. Yes, it is only referring to a P2P service and not an MP2MP service, but the same concepts apply and it is likely that all our figures will only show P2P anyway.

You might note that that figure does not use the term “end point” and does this without any loss of meaning. However, whether the terms CE and PE will be applicable for us (probably they are) is up for debate.

[JD]  Almost certainly – it’s the standard IETF terminology

You might also note that the rest of 3985 *does* use the term “endpoint” but it does so only to refer to “tunnel endpoints”.

Let’s step even further back from this.
Is a network slice “connectivity” or does is it a network service?

[JD]  It’s a network service

Connections, tunnels, links all have end points.
Services have “service delivery points” and “access points”.

[JD]  This sounds good to me

Or is a slice a type of network (virtual or logical or sliced)?
Networks have “edges” and “access points”.

Adrian

From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> On Behalf Of John E Drake
Sent: 10 February 2021 16:21
To: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>; adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'Joel M. Halpern' <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com>>; teas@ietf.org<mailto:teas@ietf.org>
Subject: Re: [Teas] network Slice Endpoint in draft-ietf-teas-ietf-network-slice-definition-00

Hi,

Comment inline

Yours Irrespectively,

John



Juniper Business Use Only
From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> On Behalf Of Rokui, Reza (Nokia - CA/Ottawa)
Sent: Wednesday, February 10, 2021 7:39 AM
To: adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'Joel M. Halpern' <jmh@joelhalpern.com<mailto:jmh@joelhalpern.com>>; teas@ietf.org<mailto:teas@ietf.org>
Cc: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Subject: Re: [Teas] network Slice Endpoint in draft-ietf-teas-ietf-network-slice-definition-00

[External Email. Be cautious of content]


Joel and Adrian,



Agreed that there shall be clarity about the endpoints.



                >>>>>> There are traffic endpoints (the sender and receiver of packets), and there are endpoints of the service (the ingress and egress to the slice).

This is correct Adrian.



An “IETF network slice” is between two or more endpoints as outlined in the draft.

In summary, the  IETF network slice is defined  between various device/applications/network functions on multiple “IETF network slice endpoints”.  These are traffic endpoints of the IETF network slice. We refer to them in the draft as “NSE” (IETF Network Slice Endpoints).

In addition , as Adrian mentioned there are endpoints to the realization of the transport slice (i.e. various services/tunnels/paths). I am suggesting to use term “NSI” (IETF Network Slice Ingress).  Please provide your suggestions for NSI if you have any other suggestions.



                >>>> For example, if the service is being

    delivered with MPLS, the Network Slice Endpoint likely cannot put the

    labels on the packet for the MPLS, as it is outside of the IETF network

    Slice.  So we will need yet another layer of classification, and yet

    more interworking.



This is not correct.  Whatever technology is used to realize the IETF network slice must be supported by endpoints. If MPLS is technology of choice, the endpoint must support it in its data-path (and might also support it in its control-plane).



[JD]  This is incorrect.   E.g., in IETF VPNs, the traffic from the CE to the PE is *not* MPLS encapsulated.  It is the PE that does the encapsulation.



Cheers,



Reza



    ------------------Original Message-----------------------



On 2021-02-05, 5:29 PM, "Teas on behalf of Adrian Farrel" <teas-bounces@ietf.org on behalf of adrian@olddog.co.uk<mailto:teas-bounces@ietf.org%20on%20behalf%20of%20adrian@olddog.co.uk>> wrote:



    Ah, the old "endpoint" discussion.



    Yes, Joel is right, we need to disambiguate endpoints from endpoints.

    There are traffic endpoints (the sender and receiver of packets), and there

    are endpoints of the service (the ingress and egress to the slice).



    There is probably a risk that we get sucked in to the wider 5G picture, but

    we need to focus (as Joel says) on the IETF network slice.



    I suggest "source/destination" and "IETF network slice ingress/egress".



    And we can avoid discussion of the wider 5G context, as noted elsewhere in

    the draft, by diverting that material into a dedicated document.



    Cheers,

    Adrian



    -----Original Message-----

    From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> On Behalf Of Joel M. Halpern

    Sent: 05 February 2021 17:04

    To: teas@ietf.org<mailto:teas@ietf.org>

    Subject: [Teas] network Slice Endpoint in

    draft-ietf-teas-ietf-network-slice-definition-00



    Rereading this draft, I realized that I am either confused by or

    disagree with the description of the "Network Slice Endpoint" contianed

    there.





    The endpoint that I think matters is the place where the IETF Network

    Slice Controller starts controlling the QoS and traffic delivery.  The

    Controller doesn't care about the identity of the device outside of that.



    Figure 1 in section 4.2 seems to define that endpoint as the network

    slice realiation endpoint, and describes the network slice endpoint as

    the thing outside the IetF network slice.  This seems counter-productive

    to me.  It complicates teh relationship between the endpoitn and the

    service being abstracted.  For example, if the service is beign

    delivered with MPLS, the Network Slice Endpoint likely can not put the

    labels on the packet for the MPLS, as it is outside of the IETF network

    Slice.  So we will need yet another layer of classification, and yet

    more interworking.

    Further, someone has to get the queueing right for traffic coming out of

    the Network Slice Endpoint.  But it is not part of the IETF Network

    Slice, so we don't have any way to get it right.



    If we define the edge of the space we care about co-incident with the

    edge of the space we influence, things get a lot cleaner.



    Yours,

    Joel



    _______________________________________________

    Teas mailing list

    Teas@ietf.org<mailto:Teas@ietf.org>

    https://www.ietf.org/mailman/listinfo/teas<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/teas__;!!NEt6yMaO-gk!USwujae5c4K64PC5PJd3jKQC-8QgVMQ2vbXzXImhk3Q8K12pHTTKZw2CuDDVyP0$>



    _______________________________________________

    Teas mailing list

    Teas@ietf.org<mailto:Teas@ietf.org>

    https://www.ietf.org/mailman/listinfo/teas<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/teas__;!!NEt6yMaO-gk!USwujae5c4K64PC5PJd3jKQC-8QgVMQ2vbXzXImhk3Q8K12pHTTKZw2CuDDVyP0$>