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

"Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com> Fri, 12 February 2021 14:51 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 A052F3A1705 for <teas@ietfa.amsl.com>; Fri, 12 Feb 2021 06:51:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.15
X-Spam-Level:
X-Spam-Status: No, score=-2.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, 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 cK1faLRvvlPg for <teas@ietfa.amsl.com>; Fri, 12 Feb 2021 06:51:34 -0800 (PST)
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (mail-dm6nam11on2118.outbound.protection.outlook.com [40.107.223.118]) (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 56E883A1706 for <teas@ietf.org>; Fri, 12 Feb 2021 06:51:34 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GKloAOsqp89//f1Ff/kPZ46U9HuQs9gHRpIW8OxJYe02aiQhrARSbQMHLSTP5mRSwqqUkcAoHMsiZdlk8yby7AOMEraItShYueWcG7WZ7eQammVhEHUxhnEz4oHt7baN98KytBOMhpX7pRXBOEa5boHwuFA9z5iaQzySOIbEDWp8sBCoAzFVevjPnJ5BAF60cY/EurJuiSRjh6a50skY1v84Ep+bnqijorZm3nUXEYYx5d6SamszKY+CpFL1ASRKt4Ul+b5nt05uyg2CKIeInC2OEbbylLjNzHY158MY5lbPCOsb6vQrlrF3bVoHvK6HLyFEqYgAIDid6QGa1rQnvA==
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=EqXB5sGu2NpQx/zuSona/+VPfcFSlNHxeewND+eh1do=; b=QIl+m0Uktwz34ICgUPrXD68dTWxuAz1PzjLIfeiKPs5KmaTIGPqI7/fSD+oEkQxvb6bAwxp8YK822lwVuNpAaYAo2GnmbB4l0j7LzhZiqFsU+DQApea7kvJBK+FvtfruCzunuT/FCUmVVbJlXySZLSnMBf+4n3s7fG23cWOwyPqQDSh/J+PJEZ753U71boskhP6qdsGyAsMxzwREeVJitGVS0+NkNsZS2k319MMMsWEdKloKzwhcYlpOXCcegduSEXNbcdhh5C3XfFxMyBjzh/Txro5Bz8G/ljGG3rpc2J0rEbaOs7ZDFXmLMrizmnCqtw/X9P0WoC7OjWv7hKx3pQ==
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=EqXB5sGu2NpQx/zuSona/+VPfcFSlNHxeewND+eh1do=; b=ZKHuqlj76Z+4mHWbh9cljH1Ly54vzACkxnplj01NybFHtYOj5ak+xigi7MFnm4PYW1A0R1/DyJdNkDdRawLJERyKSBLY4IAxhBN2OdHYQM9pVNogkR9W5EfIUhHkmMawwtIoWpbHw68FoIM/ILfMETmDRe5IuxV6Pny29ZmrK3s=
Received: from BN6PR08MB2707.namprd08.prod.outlook.com (2603:10b6:404:c0::10) by BN7PR08MB3905.namprd08.prod.outlook.com (2603:10b6:406:83::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.29; Fri, 12 Feb 2021 14:51:30 +0000
Received: from BN6PR08MB2707.namprd08.prod.outlook.com ([fe80::bcda:a2e1:1f5d:b93f]) by BN6PR08MB2707.namprd08.prod.outlook.com ([fe80::bcda:a2e1:1f5d:b93f%3]) with mapi id 15.20.3846.034; Fri, 12 Feb 2021 14:51:30 +0000
From: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] network Slice Endpoint in draft-ietf-teas-ietf-network-slice-definition-00
Thread-Index: AQHXAU6MGsRAiRcW2UaOBIHvlkPf7Q==
Date: Fri, 12 Feb 2021 14:51:30 +0000
Message-ID: <3F1804FC-E9EB-41AE-A0F6-EABA1010D7D6@nokia.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> <61180F49-A511-458A-B6AA-96E4C3BBA0A1@nokia.com> <56d8b5c3-5a94-ec85-2950-cadb18676ebd@joelhalpern.com> <83CF461D-A00B-45B0-BC90-6059ECDA9F95@nokia.com> <64a28682-022b-9ac1-2bfb-ebe2f1b26b5e@joelhalpern.com>
In-Reply-To: <64a28682-022b-9ac1-2bfb-ebe2f1b26b5e@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.45.21011103
authentication-results: joelhalpern.com; dkim=none (message not signed) header.d=none;joelhalpern.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: a4d8854d-e79d-4183-6e56-08d8cf65aec0
x-ms-traffictypediagnostic: BN7PR08MB3905:
x-microsoft-antispam-prvs: <BN7PR08MB390537F5FC5FD6F25AD65E3A9F8B9@BN7PR08MB3905.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: QHiri08vDcjOlsDSIah7c6/2wxQT1Yz3tSlur1LwRUjNxeM3xehklMC7SlPDUfBUxQAYswpiucYFJe3fo+8kSRSdEvE+Ew2L54S4POp5cSfZ5hPyD2/4nrQ4YUqbwd20CJd/JBexdmM2iF+tY86rqkt8VEOXD6eUUIqiELGk+bAeIyNHuSShMYgaCxgFnXlT2J46O8DpF4uvfVIJh7KYchhN+nSIyn03tF2bVJ6QNC/S6uxb75Ku+e6K6/bTsXlgGPXLLoYrvhpw0WPiv+jAgeWzRc5S3/uKviD1TIyR3L4svlLxxmln/M2J9YZ51+6jG6ejBscFWLMx5ZejoImW245IfDaI1hdkE6bWoFvnjr8AkqrNinN34+eRawBBSx63OPa1XwbBPkFJuK36r2Shgku/jZTHT8txLzUcnuNHWO2uBGPxb61VKvwliOGL8v2CwabR6WI2+FAO7ettxtnwwHdCY1X4cgrd9p8CTF3/K9j+5uGnJMztdy63WoIse5IWR6n0CQcLFuYULhaXMe7zKwTKpglu57wkzlm07rqF2p8mfONPwDjxvNq23E01nsyrFW6fOyE1KIXd3QfCG70CxqXUaZw4+4Buyco2BWiI/PjOb2om47+LF4yfSaSIxL4uNoTkN53OPWGHxuyNgrU2qQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN6PR08MB2707.namprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39860400002)(396003)(136003)(366004)(346002)(376002)(5660300002)(26005)(110136005)(83380400001)(76116006)(64756008)(66946007)(66446008)(66556008)(66476007)(91956017)(2616005)(966005)(2906002)(6486002)(8936002)(36756003)(53546011)(478600001)(316002)(6512007)(86362001)(186003)(6506007)(33656002)(71200400001)(8676002)(45980500001)(559001)(579004); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: =?utf-8?B?NkFzcis5N0UrQm4yNmwvenJTbFEyZ2RIZE83L0ZsSGpDMUdPR2VxREJVQ0NO?= =?utf-8?B?ZGU2NVBkYUM5OHNZaUJpTk9mcmlBRXI4U0wvV1pxc2x4T2VuSkZJbFZqSUxP?= =?utf-8?B?S05wMU9ic0JVUzhFclRlUVFlc0Q2cmo2eXlmcEpwYitxQjFWekhPSEhKNlQ5?= =?utf-8?B?Q0JhTGt1QnVZWFdLYm03RW42V2xrWW1XZktoMm5qS2RDeGh0ZVRLSll1czVH?= =?utf-8?B?clYzV2RkZi92cllGMC9YYk1WT1k3SW51OXBMblp0RDVlYnFCVFM2eWNRMWdG?= =?utf-8?B?a1BLY2hWU0g0OXA4MmtnaldqUDdRT0lOUThXS2pVRkJJZDEvMllMQkZ4ajBw?= =?utf-8?B?OUkvMk5PU2dOakRvbEF0aDlnc1F1M1h4V0NRTzQzNHYzK3RwUzViTWhtdlZH?= =?utf-8?B?VUJRUTByWWRXMVdHQTFYK0FXNXhaeU1pdEl0ckZueC85L2xqQ1Q5Nm85YzJT?= =?utf-8?B?YTJzRE12QjNTajBFa2JhWFJ3TmhGbFJvcmhKM2xodWFBTi9zUkdyQ1VpdG93?= =?utf-8?B?ZTR4cnRndG5mclBlakhHT24vRkRTbkNBVklKM0dCRWJnT3czSDRsbGREWVpS?= =?utf-8?B?Z0ZBNG9OQlk1NEVFUG1EU1JpSGJKbHpuODRndU5JaUpMd1UrLzVva0NaZlhV?= =?utf-8?B?a0NOSjFFU3ZXNU54VnVZNmoybjFJTzkrL2src1NvNTljK2kvZWdJQXhvTC93?= =?utf-8?B?a29uUHc4YWNJT2pjdWVHd3dqaXhpL21VNDZrSWJLemVEV0RYOHdxeElIY2hw?= =?utf-8?B?RFNmS1EyL3QvSEd1TUV6MkFlemtDSEVrNUx6QVc0SGlYWFNGTE5COWhlb0ht?= =?utf-8?B?a0M3WUJFNkIwemc1RkxDNFhsbmx5ZEpTYksySFJ1NWtsbEtJZExYV1NlK09U?= =?utf-8?B?WUlwTmh6bjNocnRiNjFQbTc1UkttL3lZbGZuOTF2czUzNFV3YUl5RlJSYndT?= =?utf-8?B?WjIvSG5haENMZHFlQXIraWtWOEYrRnZXdU5vRHNTNUg1T21pMXljdmlHdzBy?= =?utf-8?B?UGFCaVdOcEhvSTZJYWg5S3lwRUdtaU16ejNFdEUvcGVyUTJiU0hjQXh1a0h0?= =?utf-8?B?L1ZwK2VWVkVyeUdONm1jd09xQWFzZy9ycURyTXAxdGpTc0JtN1dDRzdxNlFy?= =?utf-8?B?WnB4Z3NBUVRvclBZNG1wM2JKVnlHcG5yWGd0MUxEUU5EZkQ3djhQQ0lQSzlK?= =?utf-8?B?cEd6RERkR1hVMHB5TjRzYlo3djhjczIxSUFQME8yeDdLUFljSTZKVjBaays1?= =?utf-8?B?VzA2MHdqVVZZR2xGTFl1SkthWGpEck9uTDlzN21GSk9mdGdXbmdjWFJCbUZY?= =?utf-8?B?TjhJMUg2ZlBaZTlYTWdQTmM4ZnkzbnF4K1RUK2dVT0JpOW1hNFEyTkZRU05O?= =?utf-8?B?bk9SUHcwV0N3UDFGOHRiVFJkQUNydm1RMzhnK043VWZyYnQ2c3ZvQ1ZhdmJz?= =?utf-8?B?R1VudGwvL3cxU291VlRmZ3AzVytTZGRLQ1JRd0xvUEhKcGV2MWM2Z2xya0FO?= =?utf-8?B?N29YazJsd2YrZnlZM2lNR0lwYVVobC9RUk1ibGVTTlg2MFZ6RmtoY1R6N1RE?= =?utf-8?B?dDY4R1NJN3NoVGIyQUdqTHJVTUJMdEVTQklLbUNDRzdBNkhoQUJsVnZaT3JM?= =?utf-8?B?V1U2VUVIQVA3WnVyWGRzRlh6YW5rbjJDOVhTS1MvZXRDclpyZ1RHNHFIZkk2?= =?utf-8?B?RUpydkliZGdSak80NGgzS01PWE00RnJrQUNLeEsrR2phODdQUzhWR085Qmtr?= =?utf-8?Q?SPEL+omt/Pkm0zDLpxOfkFkZn1gnw+dN4Fod3BF?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_3F1804FCE9EB41AEA0F6EABA1010D7D6nokiacom_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN6PR08MB2707.namprd08.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a4d8854d-e79d-4183-6e56-08d8cf65aec0
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Feb 2021 14:51:30.0589 (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: ddfJKHvsE792OT8zixBfXtItrB+rT4SDJF8CvagCayCJ6vYaImxQ7FIsRpNffGZVcAmSxy3WGpiU17G47yRAQQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR08MB3905
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/uSJp3Wo3rQiQ5phEVHpqD8ypHuo>
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 14:51:38 -0000

Joel,



Please see section 4.3.2.1. Layer 3 and Layer 2 Encapsulations where the sentence start with If the AN or CN could support MPLS,….

It shows that the traffic from AN or CN (i.e. RAN or Core Network) might be MPLS.



Reza





On 2021-02-12, 9:43 AM, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:



    Reza, I looked at that paper.  I do not see anything in there that

    addresses the inconsistency I am calling out below.



    Yours,

    Joel



    On 2/12/2021 9:09 AM, Rokui, Reza (Nokia - CA/Ottawa) wrote:

    > Joel,

    >

    > There are some discussions on this topic for 5G for example. See the

    > following draft:

    >

    >   * draft-geng-teas-network-slice-mapping-02

    >

    > Reza

    >

    > On 2021-02-10, 12:41 PM, "Joel Halpern Direct"

    > <jmh.direct@joelhalpern.com> wrote:

    >

    >      In every case I know of (which is I grant not every case) the non-IP

    >

    >      packet is still a packet.  It is generally delivered to the service

    >

    >      provider as an Ethernet packet (since that is the only other kind of

    >

    >      packet we actually deal with.)

    >

    >      I do not know of any operator who trusts his customer to put an MPLS

    >

    >      label on a packet which the operator will use for switching.  (The

    >

    >      closest I know of is when the operator actually controls the CPE.

    > Which

    >

    >      is clearly not what you are describing.)

    >

    >      If you have another use case in mind, it would be very helpful if you

    >

    >      would explain it in more detail.

    >

    >      Yours,

    >

    >      Joel

    >

    >      On 2/10/2021 11:42 AM, Rokui, Reza (Nokia - CA/Ottawa) wrote:

    >

    >      > See inline please.

    >

    >      >

    >

    >      > Cheers,

    >

    >      >

    >

    >      > Reza

    >

    >      >

    >

    >      > *From: *John E Drake <jdrake@juniper.net>

    >

    >      > *Date: *Wednesday, February 10, 2021 at 11:21 AM

    >

    >      > *To: *Reza Rokui <reza.rokui@nokia.com>om>, "adrian@olddog.co.uk"

    >

    >      > <adrian@olddog.co.uk>uk>, "'Joel M. Halpern'" <jmh@joelhalpern.com>om>,

    >

    >      > "teas@ietf.org" <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> *On Behalf Of * Rokui, Reza

    > (Nokia

    >

    >      > - CA/Ottawa)

    >

    >      > *Sent:* Wednesday, February 10, 2021 7:39 AM

    >

    >      > *To:* adrian@olddog.co.uk; 'Joel M. Halpern' <jmh@joelhalpern.com>om>;

    >

    >      > teas@ietf.org

    >

    >      > *Cc:* Rokui, Reza (Nokia - CA/Ottawa) <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./*

    >

    >      >

    >

    >      > [Reza] Disagree. There are use-cases where the traffic to transport

    >

    >      > network is not IP and is Labeled-packets.

    >

    >      >

    >

    >      > 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://www.ietf.org/mailman/listinfo/teas>

    >

    >      >

    >

    >      >      _______________________________________________

    >

    >      >

    >

    >      >      Teas mailing list

    >

    >      >

    >

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

    >

    >      >

    >

    >      > https://www.ietf.org/mailman/listinfo/teas

    >

    >      > <https://www.ietf.org/mailman/listinfo/teas>

    >

    >      >

    >

    >      >

    >

    >      > _______________________________________________

    >

    >      > Teas mailing list

    >

    >      > Teas@ietf.org

    >

    >      > https://www.ietf.org/mailman/listinfo/teas

    >

    >      >

    >

    >

    > _______________________________________________

    > Teas mailing list

    > Teas@ietf.org

    > https://www.ietf.org/mailman/listinfo/teas

    >