Re: [Teas] network Slice Endpoint in draft-ietf-teas-ietf-network-slice-definition-00
"Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com> Wed, 10 February 2021 18:10 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 DA1DA3A114C for <teas@ietfa.amsl.com>; Wed, 10 Feb 2021 10:10:05 -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=unavailable 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 fsOaQEEQ-wnh for <teas@ietfa.amsl.com>; Wed, 10 Feb 2021 10:10:03 -0800 (PST)
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2107.outbound.protection.outlook.com [40.107.220.107]) (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 34AA83A1154 for <teas@ietf.org>; Wed, 10 Feb 2021 10:10:03 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LWUE6k/k8LIPtTxUGzTN+H+kdgV6NHCCa9HdhZ0Sbl+N2/wEdGzT77l3skuBXjHpuCTo19EhPCkRlkeeTZVDPZFplV7QJatNivbknO1ni2OXDJ4k+GxNsf0hPj/hcT2EXuvsM7D+HElje22Sp89Qj2/aqbWzbHrLTFU/+F9lekZUXWvidEttD6oldSPY4wqHc9m2YPLVYBY5jQuBhHtpdd6ipCYQxlaJb77k/2OrFFL85iyFNT+uo+0j4r7ioutzoICFh2xw6qfZ6EkoHRt9YTr2x4d2YUJyd0ssvXFHmEc6viILwiH1fa6l/TmfDzHqDNalex3WStcOdVRF+smhFQ==
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=SyM0X3BoiwNdR785tcJApdWWpoll7h5wnYsO4egShRk=; b=erT9/E/Tl/uo5gWZmZUA6ZMjFaNRnhtzGpFJvdBbAb2Nin+Z1oi939+7ULlCak1TpL2vtjnIJYYfDOk/wNsfTdU3/qW2+SiKkvEDQqCNgIQ3D9hS75cwpkOXmE8KWhBo37ERrfe1g/Ppw6FaPbAQWAZQhO50WPpQ7ZEkgSmun1gz6n5xzBrEOLITZVJ3j+uccfvGXkmFD20qnUREoFiRcTmUer/z66guFkn7z7LjCGKDCC7K+qNAOd8Q4PNCyUwwptUsHiDO7VFSCPDKOzsskMk/psjTrMKktTQnqE/VFJCrcP84PwunQ/C+xcUHDWfEPz4YkrXHnU9M0b8K1NxbMA==
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=SyM0X3BoiwNdR785tcJApdWWpoll7h5wnYsO4egShRk=; b=xw0eO46NnlE6tKrpIrToO7nIPEiPy53TU68ZedtqxhfsTUwKE0f0WlMSn5treOJtg7ACqHzWdGeRCyjN7wxQSPHzXCILDwN/Ceo+5EO3gAB0NMEgYDJfSUxnKDBEN9oY7N5hy5iFzYYMQ3pInKKOy2rWh4+MnZ2NPW8GpZJB9AM=
Received: from MWHPR08MB2718.namprd08.prod.outlook.com (2603:10b6:300:bb::15) by CO2PR0801MB2325.namprd08.prod.outlook.com (2603:10b6:102:11::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3825.20; Wed, 10 Feb 2021 18:09:58 +0000
Received: from MWHPR08MB2718.namprd08.prod.outlook.com ([fe80::3065:4348:5ec:9ce6]) by MWHPR08MB2718.namprd08.prod.outlook.com ([fe80::3065:4348:5ec:9ce6%10]) with mapi id 15.20.3846.027; Wed, 10 Feb 2021 18:09:58 +0000
From: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org>, "'Joel M. Halpern'" <jmh@joelhalpern.com>, "teas@ietf.org" <teas@ietf.org>
CC: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
Thread-Topic: [Teas] network Slice Endpoint in draft-ietf-teas-ietf-network-slice-definition-00
Thread-Index: AQHW/9fxcsd/2g9Cb02oeWSji1if9g==
Date: Wed, 10 Feb 2021 18:09:58 +0000
Message-ID: <8874DB35-E818-4B87-A628-94C853972E48@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> <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:
user-agent: Microsoft-MacOutlook/16.45.21011103
authentication-results: olddog.co.uk; dkim=none (message not signed) header.d=none;olddog.co.uk; 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: 1d4df225-9c5c-4b15-f45b-08d8cdef13c2
x-ms-traffictypediagnostic: CO2PR0801MB2325:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <CO2PR0801MB2325EC24965194F52B50BA779F8D9@CO2PR0801MB2325.namprd08.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: gVk6U2aVOY4+BOgpSnhiZqWVHUDDVbi3eInlNkesGsWTr9XYfS6TPfPkEkBdT9XtvMHgkmbrrsMt0ptgoz1feM30uHusTJkJ9C4CLBzDRhGee4N00zCLRCE51Qs5SGmJ/sSoAXQ9nEwKsVuv1Pn1EBqsX477Khrf/SGx4YbNtp0H81umMCHUrFDnd4BWfoc2mh87+9IzfcDN1RJjNubBVq/KTBf++kpzwR2uFmuJQtX3W2wy1+wV6KANmKYaSdgIE/geZGY5cwT/Bnd3E0pHx/y90N4gX+IVx+j4mbV9uFHAwh8LDd67qgmVL9QJInb6o8Sr57xPRQ3aDjWtW/11r71oydwIcHoZcEpQdTlPPDIfZ87bnSVBigSNAQP7l2qr/AcN/c3B42yECUuu+rlQCChQQIQRXPbfFdxe1C3O/J0X3Sv8iN8y00dS1SLsadQ/e4OwpuMyZvGTPVE4ItjR8g/OZjhhGKRvp5vgasm/EEJuSu/aKrlZwjX6PRoWDltJnS4iJ+IpBZ09YguS1IFt+EUyCun+Y37ZgNzxFJdmQjVe9v4bGk/oex3d4biQU/Wr518HpiNg2x0lDoQkrXR5b2yXPvFU4C3V/6N5Kuj2zzv9cRp+O3sgRY/s+YF43sH0PtGxLW8Rt3MIQtXi43PyzQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MWHPR08MB2718.namprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(136003)(39860400002)(346002)(396003)(376002)(366004)(8936002)(36756003)(66946007)(66556008)(66476007)(64756008)(2616005)(66446008)(76116006)(5660300002)(107886003)(86362001)(478600001)(6512007)(71200400001)(91956017)(83380400001)(8676002)(6486002)(4326008)(316002)(9326002)(33656002)(2906002)(6506007)(53546011)(166002)(966005)(110136005)(186003)(26005)(45980500001); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: bmENqtLUxBCtjSSMzkweA3NW/AMgP3RuiX9MCArjUAP59uCf2Ug00xSE2mrNfOZ7X/L2HtcNm4ZdOQ7sCQePnlLKT1Yr9B0iHzA/nqMX7Zlj4k39Iqx0MoWM7bxm/zFwY6rdilPHe12fJtwJ469YjhoGezS+LcM+Ma5NKOMFXg+PTdc7Pq4KIZPAQJbPNtCtCBczzkaei8Mvulhup5xBrVN2lI758gvi2D1p6yv15HjyWA0L+7PWX8TpchP24kLhhGe/8Iw8EUVim4kD4837R+0lRSPx7rH4/2vi8ggu3sJn3IPX+UZgRVrLoH7wNQfMtcNVHQai7lzKClDAifcaTlCLiyBi3lbR7Fp7bwcv8ZAhoIsvdPgffHkR4IuPOOgWPjjOCnQT4d7ajZT+bGHx3q+L9WdYQWTcxKFZW/fiHJVZzz5h5oreTGKbXUQMa9OIorixm0BvOUPVY4Kl1wGri5xP+xXV4IKp8phnIm5XCsfPOGR67t052KfM3LicP+xv+OHBRyajofuOqqtkd5133RCpWEhBwcsIi071tG/b5WZ16Z4rWJz0y+W5FUlwS2e0ghMH4FhD92v0gSyQcGbuTimqPiwrPVtd6ZjR32ovgFOw9sQpjachgjYyysB6915BQ+g9yegvvkxH5rvs8pG/kkejc1mtJl94BHU/MuN5DmxxOB1ytJRNWw4Q5EMgeg2moVUkPoSzliukaImdoWh4SpkAuJ1YFvKwiMReNHhFm/OpUt8fbnlkAiz9kHT7IBdsbDciH/P3RQaiei7Gi4ra2VQz9b6Ff8bgw2AXlALuEoK0HhNf9zcYA430qSkBArj5UBUCcLc2ZSqkctQVSLx27BrX7IUI+QkZVePnVPBq0Bl0VDHjBe15GnGm/RdpWm+rxWYDUItF9fBo7ExgHvLbY93v9yq7rtkDi3fIhvStr8TAvgOqSznxsXy23yJYRoLxYj4YzshNeS1S5enlYE+Q8yO6OG1KzsADAbsy1eQxBWpS87MszU6X7qzAghEGU2CFFj4r005Gi9m+V1qp5GWWsni9h7tf2p/vtXwvnfYCTsl3+rnVNh1g2kJ+DvY4MFcz3caZ8tCKoSYg6KVvGO7U1r2dwxsQQtgYWsg1/2s0wPDvH3opceh/ErQ9UvBOsg33bZW1kwNkvMNCaZZnUxYf+j5tNwR00Ym5gXgzGE3Z8CxlM79+dtPZn9YAexr+BWaqTve83VL+6V7ns4TXb8jJCNYDOFKM2XyR6g/zdcuF6TcK5AWo9ltamAV/Owt/M27g73QMu+WMsLo0E9DheBeNQqISi3alBnDwsEKBxbsFHCTzy2Mjk8fmheeE1LR1MJAF
Content-Type: multipart/alternative; boundary="_000_8874DB35E8184B87A62894C853972E48nokiacom_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MWHPR08MB2718.namprd08.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1d4df225-9c5c-4b15-f45b-08d8cdef13c2
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Feb 2021 18:09:58.4606 (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: mVYci2gvbF9HFyXjvNjq+j1fqPHQjhznBviOTJYjpBpIfbzexGaffybg1kCH5/H/AJV/r+l98iaLg23HSgdlww==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO2PR0801MB2325
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/IicmR-T7-IEN0nLWywzZ3dpNTj4>
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: Wed, 10 Feb 2021 18:10:06 -0000
Hi Adrian, My comment is inlined. Reza From: Adrian Farrel <adrian@olddog.co.uk> Organization: Old Dog Consulting Reply-To: "adrian@olddog.co.uk" <adrian@olddog.co.uk> Date: Wednesday, February 10, 2021 at 12:29 PM To: 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org>, Reza Rokui <reza.rokui@nokia.com>, "'Joel M. Halpern'" <jmh@joelhalpern.com> Cc: "teas@ietf.org" <teas@ietf.org> Subject: RE: [Teas] network Slice Endpoint in draft-ietf-teas-ietf-network-slice-definition-00 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. [Reza] this picture might be useful but without referring to PE and CE. IMO it is not applicable to our discussion since IETF network slice is technology-agnostic. 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? [Reza] In Definition draft the co-authors intentionally did not use term “Service” since this term is overloaded and anybody can have his own interpretation. So, IETF network slice is a group of connections between multiple endpoints which are realized in the operator’s transport network using any L0/L1/L2/L3 services/tunnels. Note that the transport network might either be IP/MPLS or other technologies (e.g. PON) Connections, tunnels, links all have end points. Services have “service delivery points” and “access points”. Or is a slice a type of network (virtual or logical or sliced)? Networks have “edges” and “access points”. [Reza] Good point Adrian. All these are related to “IETF Network Slice REALIZATION”. So any L0/L1/L2/L3 services/tunnels used to realize the IETF network slice will have its own access point, endpoints etc. These are different from “IETF Network Slice Endpoints” but obviously there will be a relationship between them. Adrian From: Teas <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>; adrian@olddog.co.uk; 'Joel M. Halpern' <jmh@joelhalpern.com>; 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 _______________________________________________ Teas mailing list Teas@ietf.org<mailto:Teas@ietf.org> https://www.ietf.org/mailman/listinfo/teas
- [Teas] network Slice Endpoint in draft-ietf-teas-… Joel M. Halpern
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Adrian Farrel
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Rokui, Reza (Nokia - CA/Ottawa)
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Joel M. Halpern
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Rokui, Reza (Nokia - CA/Ottawa)
- Re: [Teas] network Slice Endpoint in draft-ietf-t… John E Drake
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Rokui, Reza (Nokia - CA/Ottawa)
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Adrian Farrel
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Joel Halpern Direct
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Rokui, Reza (Nokia - CA/Ottawa)
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Kiran Makhijani
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Uma Chunduri
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Rokui, Reza (Nokia - CA/Ottawa)
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Rokui, Reza (Nokia - CA/Ottawa)
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Joel M. Halpern
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Rokui, Reza (Nokia - CA/Ottawa)
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Joel M. Halpern
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Rokui, Reza (Nokia - CA/Ottawa)
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Joel M. Halpern
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Adrian Farrel
- Re: [Teas] network Slice Endpoint in draft-ietf-t… John E Drake
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Uma Chunduri
- Re: [Teas] network Slice Endpoint in draft-ietf-t… mohamed.boucadair
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Joel M. Halpern
- Re: [Teas] network Slice Endpoint in draft-ietf-t… mohamed.boucadair
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Joel M. Halpern
- Re: [Teas] network Slice Endpoint in draft-ietf-t… mohamed.boucadair
- Re: [Teas] network Slice Endpoint in draft-ietf-t… John E Drake
- Re: [Teas] network Slice Endpoint in draft-ietf-t… tom petch
- Re: [Teas] network Slice Endpoint in draft-ietf-t… John E Drake
- Re: [Teas] network Slice Endpoint in draft-ietf-t… mohamed.boucadair
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Daniele Ceccarelli
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Kiran Makhijani
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Rokui, Reza (Nokia - CA/Ottawa)
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Greg Mirsky
- Re: [Teas] network Slice Endpoint in draft-ietf-t… mohamed.boucadair
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Joel M. Halpern
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Rokui, Reza (Nokia - CA/Ottawa)
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Eric Gray
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Luis M. Contreras
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Joel M. Halpern
- Re: [Teas] network Slice Endpoint in draft-ietf-t… mohamed.boucadair
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Luis M. Contreras
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Young Lee
- Re: [Teas] network Slice Endpoint in draft-ietf-t… mohamed.boucadair
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Young Lee
- Re: [Teas] network Slice Endpoint in draft-ietf-t… John E Drake
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Adrian Farrel
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Dongjie (Jimmy)
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Gyan Mishra
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Shunsuke Homma
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Joel M. Halpern
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Gyan Mishra
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Shunsuke Homma
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Gyan Mishra
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Ogaki, Kenichi
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Shunsuke Homma
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Adrian Farrel
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Gyan Mishra
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Shunsuke Homma
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Gyan Mishra
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Gyan Mishra
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Shunsuke Homma
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Gyan Mishra
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Shunsuke Homma
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Gyan Mishra
- Re: [Teas] network Slice Endpoint in draft-ietf-t… John E Drake
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Joel M. Halpern
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Tarek Saad
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Greg Mirsky
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Adrian Farrel
- Re: [Teas] network Slice Endpoint in draft-ietf-t… John E Drake
- Re: [Teas] network Slice Endpoint in draft-ietf-t… LUIS MIGUEL CONTRERAS MURILLO
- Re: [Teas] network Slice Endpoint in draft-ietf-t… John E Drake
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Tarek Saad
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Tarek Saad
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Adrian Farrel
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Krzysztof Szarkowicz
- Re: [Teas] network Slice Endpoint in draft-ietf-t… John E Drake
- Re: [Teas] network Slice Endpoint in draft-ietf-t… John E Drake
- Re: [Teas] network Slice Endpoint in draft-ietf-t… mohamed.boucadair
- Re: [Teas] network Slice Endpoint in draft-ietf-t… Krzysztof Szarkowicz
- Re: [Teas] network Slice Endpoint in draft-ietf-t… mohamed.boucadair