Re: [Teas] FW: The word "transport"

Eric Gray <eric.gray@ericsson.com> Fri, 01 May 2020 17:54 UTC

Return-Path: <eric.gray@ericsson.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 B75753A18CC; Fri, 1 May 2020 10:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.82
X-Spam-Level:
X-Spam-Status: No, score=-2.82 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.82, 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=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 eLlc3DAyH60L; Fri, 1 May 2020 10:53:57 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-eopbgr770040.outbound.protection.outlook.com [40.107.77.40]) (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 9C8103A18CD; Fri, 1 May 2020 10:53:55 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GXxnZVkIVYY4H0ltTli0oJU4pWoU9lmbwQI64LdECPJn3vJTJyR89DOmMNJ1qU5LARF3YNvK/KEDWRNw1nt6QER7ZeFkSu7NPQD2X3mYDIT8GzmtRg69biyttplcCbNHeieyfc95U7aK9en2MfFg2dFDTSvYIbKcfl/VtHAWE0UXZznhMUKpu09l1My+wfdPUXWoThF+ZcwRCQMe+/3lNBNuzk6MsITJdMBt7r5zGnZ8SRSwD4+owDk5p6vsxbgfGPA8jqEU1Xu94iWit5lFKPLmZKM+zqiQRnxHLis0sxMO5umu+A6p1ndz7zVhuCxKdW6cpNHzz5Ip37Jd2g1YAA==
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=TiKYDSNKRSMkSQLPDSXRlkn5lRFpE/E8+D/Y6V1gKEI=; b=KW5ATuMm3/SEL20SglvFU/pzFMdFDYq/s0x2omBUe3r9HxTiVhCyBLMESqvxWthbCDIsHcOZZFWkadyl1BNjF+cQ15Ur9gz1aQ3hffo0Z9khfUeGRIaO5TCKC7eVxCbeO3hj2ICsyLYMWeA55JZchS9eNlIIJEjwOa+osrWL5Uin6N00mGFZFrus1O1smkcAxIrQWItL8LTxSPpcdIISpE1jNtonpYZS13+/OclFFpB0NWCtc1YjuJn5wRTQDRZzpnnQ4Ps/+8TnI9Q6xNzqOdEvbQ1JPjTq7CcdxU/aqb/ur1InsMrsAMQSJJmlM1qUSUi8qQv8QMXS3bjAIrg7yw==
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=TiKYDSNKRSMkSQLPDSXRlkn5lRFpE/E8+D/Y6V1gKEI=; b=PAD6wb/YcrJLpZDst9ICLU1Ix2kfjAbrUnXv7WqOrwPwZdk52/NhxiyiOX5551x86L9qcxs2kg9qEz6amcmjSWGO90hWhCWczOnenELl4B4+neT2m1bQ0ygcep+xyf2GEalThYjrmRNCb4ki7HTGypqUXGYWirErORJzVu2rSgQ=
Received: from MN2PR15MB3103.namprd15.prod.outlook.com (2603:10b6:208:f9::10) by MN2PR15MB3583.namprd15.prod.outlook.com (2603:10b6:208:1b9::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2958.20; Fri, 1 May 2020 17:53:46 +0000
Received: from MN2PR15MB3103.namprd15.prod.outlook.com ([fe80::6464:3ca7:6309:c725]) by MN2PR15MB3103.namprd15.prod.outlook.com ([fe80::6464:3ca7:6309:c725%6]) with mapi id 15.20.2937.028; Fri, 1 May 2020 17:53:46 +0000
From: Eric Gray <eric.gray@ericsson.com>
To: John E Drake <jdrake@juniper.net>, "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org>, "teas@ietf.org" <teas@ietf.org>, "teas-ns-dt@ietf.org" <teas-ns-dt@ietf.org>
Thread-Topic: [Teas] FW: The word "transport"
Thread-Index: AQHWH87RVhjoZk4pGk+CGNiwWxctJKiTXk+QgAACOgCAAADwgIAAAQoAgAAEcICAABfQsA==
Date: Fri, 1 May 2020 17:53:46 +0000
Message-ID: <MN2PR15MB3103F3FCDA52F17AFD95DD1D97AB0@MN2PR15MB3103.namprd15.prod.outlook.com>
References: <036501d61f26$01756f20$04604d60$@olddog.co.uk> <DM5PR05MB33881A76688021C9B05EA556C7AA0@DM5PR05MB3388.namprd05.prod.outlook.com> <03ef01d61f9a$2f5850f0$8e08f2d0$@olddog.co.uk> <A02167A2-4AA6-4522-A6E8-8D9157BEB3F4@nokia.com> <044101d61fc5$1656bd50$430437f0$@olddog.co.uk> <C974BCBC-BDD7-4A01-AED7-30926BC72987@nokia.com> <MN2PR15MB3103FCC7BCA3C126C1F11C8797AB0@MN2PR15MB3103.namprd15.prod.outlook.com> <0A0B7870-40F7-43B2-964B-E0A408D0B844@nokia.com> <DM5PR05MB33883A5B6547F2297BDF6EFDC7AB0@DM5PR05MB3388.namprd05.prod.outlook.com> <1120E99B-CF3C-4FEE-9EBB-CE807CCC62F1@nokia.com> <DM5PR05MB3388B66471C5AB0E877F5C14C7AB0@DM5PR05MB3388.namprd05.prod.outlook.com>
In-Reply-To: <DM5PR05MB3388B66471C5AB0E877F5C14C7AB0@DM5PR05MB3388.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Owner=jdrake@juniper.net; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2020-05-01T16:12:11.4382627Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=Juniper Business Use Only; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Application=Microsoft Azure Information Protection; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=114cea60-6b6c-4101-a2b7-7771ab75951c; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Extended_MSFT_Method=Automatic
authentication-results: juniper.net; dkim=none (message not signed) header.d=none;juniper.net; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [73.248.143.71]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b740fad3-ed4e-4dd6-098e-08d7edf8989c
x-ms-traffictypediagnostic: MN2PR15MB3583:
x-microsoft-antispam-prvs: <MN2PR15MB3583BFB0991C13CE42C0431D97AB0@MN2PR15MB3583.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0390DB4BDA
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: BEhFC8Xxp3eoSeuiR0+WHwUa9I49c797RuvQtSVGl6+xIzYxBg2cw58ol7q1u/99JrglBCmJN0e1cQLtFOsQv0l25xCvWvLEZTIFHroaBnHM/BItgJ1ch57hRJUx6fO4/fWZSqbnO1atnkPw3NpVrIZ+vbipfro23eWGVhDcus3WnCFqG4Xu9bgJ2xhg2LX8/rSwt/VxHR13S9e/DCiEct/Dnpjsy1ZDrOdYMGzoY/trv6cyfJ7n7awaQ01KN9l1ePZrVzOdYhW0dteK/46zHdxMtXAiqHB6Ojhqu88kQZc42Bmt9SMuBwpvN78NzMpOxgrCdnSSisG7WFirNIL+ZzAtbVZ3GFwzTwi5cZDRroFP8qTNfdm5GICAwFMRREY2GG+nA6XYh6Y1/SlKksLJIYf6/u+IkEwshEsL0vR32oK4XtVYs/xYfZXnDl8aroNRYk/lX432G90UKXBehNUQXRF+Z+c/4A5s21l3p3ivfj3FsgvHbLJmYa0OKDLYf4E4XB8d27xilG2PovFtvAmb6w==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR15MB3103.namprd15.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(366004)(376002)(136003)(346002)(39860400002)(396003)(9686003)(55016002)(33656002)(66446008)(64756008)(66476007)(66556008)(66576008)(66946007)(99936003)(478600001)(76116006)(966005)(52536014)(8936002)(8676002)(6506007)(53546011)(86362001)(7696005)(2906002)(44832011)(71200400001)(26005)(186003)(316002)(110136005)(66574012)(5660300002)(30864003)(559001)(579004); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: FkjevURAiFDsUr2Txk93qkU3m5+Tq6ovHT4eF+W+mw50CWGEUU0ON6h6hfdUXfGOAz4KLAEetjBAWKIO5nzULijAG177t98dw4OUjf89nwJ9FsCfAN2vj4vkYSP47jQeMvsbSbbUMCfX1ib6/YuJ3xs0FzyqHI2dgSTrPMz1B6zHIB3r/nFg+5JA+61/jLNxeFQv7PgWn5kZDZDUw5w3lpxHw5vw4wESFRMTmdkUzOaqJnYlqE54sam08b8cOCQ912aFnkqLT5nJ2b1Hkn4W3ajQS9RxNC7MnTCEC2vdjs62odU4+7eKNH7NfdS1Se86WSZYZb8Mv6VaN1kYPMx5XS8J60pK4FxzRoz6Nfe0+ZzxUfBg9bGuE+idfpSYTgNftGHPcpOrbLCPfSbVeEtIv1nAJYnU4ZniP9uXgG66XwMll8UZrmQBA/Fkk3IXM4iPBV6SQbFYODbKVx3wZozaRnzjnulY0WrAr+RIit7Fx6yOrJKYN5/66txzo9aeF2Pos+pSaQjM+E+rflt5baEsnxNc+UuAiTb0KoJbLSJkaK2vS7GVtalfPZkUTov03Tpd0YwPNQI89w0tXoFXTrFTsSZgpqzlaVG6Oa3gEXgV4yRPlH2bcuaC6L8ou7X7e84IHTBcSr08+1JrAR0YhAkOw7D/r7SLaQdZZ0itzowj0YKdmHflIzvt1nakCaYH7/aM3xR6KNtYeNdo7FevUb61dHWug4hNIBA9WO48VjqjobDfKG1y6+Rdbj0LCDqCdn+sjtffDCfcmuTueU1lMuuRS1QZqUY8Zr0OBy3CSrVu6DU=
x-ms-exchange-transport-forked: True
Content-Type: multipart/related; boundary="_006_MN2PR15MB3103F3FCDA52F17AFD95DD1D97AB0MN2PR15MB3103namp_"; type="multipart/alternative"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b740fad3-ed4e-4dd6-098e-08d7edf8989c
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 May 2020 17:53:46.2200 (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: KbSZWxk1jArgETe71WbUFHuklWySyomH2C8NjMh4a9LBJqFQu2sTmFXrefhOGBODVCfchBQPA7pwGfqS5+E13w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR15MB3583
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/3ZD17Y-SfuI4u83eLt15jVeesl8>
Subject: Re: [Teas] FW: The word "transport"
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, 01 May 2020 17:54:02 -0000

Yes, the word “Transport” does carry a lot of baggage – here in the IETF and elsewhere.  Think of it as “baggage transport.” 😊

But that has not stopped us before.  You no doubt know what the “TP” stands for in MPLS-TP.

We cannot rule out use of terms that are pretty much in line with their English language interpretation, just because they are used ambiguously in another context, or in a general context.

I think that – if we were just calling it “Transport” – this would be a serious problem.  But we do not (AFAIK) use this in any context where we do not combine it with “Slicing” and we define “Transport Slicing.” Which should be enough to avoid issues with the fact that the separate terms are ambiguous.

Provided, of course, that it is sufficiently clear what we mean by “Transport Slicing.”

Quite frankly, I find it surprising that we are debating the terminology choices that were made by a design team at the working group level.  It is one thing if it can be argued that the choices are counter-intuitive – though I can think of numerous cases where that has not carried much weight.

What makes sense to discuss at the WG level is whether we define the terminology with sufficient clarity, and then use the terminology as we defined it.

--
Eric

From: John E Drake <jdrake@juniper.net>
Sent: Friday, May 1, 2020 12:12 PM
To: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com>om>; Eric Gray <eric.gray@ericsson.com>om>; adrian@olddog.co.uk; 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org>rg>; teas@ietf.org; teas-ns-dt@ietf.org
Subject: RE: [Teas] FW: The word "transport"
Importance: High

Hi,

That was not my understanding but if that’s true then we are responsible for developing a rather bad term.  As Adrian detailed in his original email, ‘transport’ is a term typically used by other standards bodies and that within the IETF it carries a lot of baggage.

Yours Irrespectively,

John



Juniper Business Use Only
From: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Sent: Friday, May 1, 2020 11:56 AM
To: John E Drake <jdrake@juniper.net<mailto:jdrake@juniper.net>>; Eric Gray <eric.gray@ericsson.com<mailto:eric.gray@ericsson.com>>; adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org<mailto:jdrake=40juniper.net@dmarc.ietf.org>>; teas@ietf.org<mailto:teas@ietf.org>; teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>
Cc: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Subject: Re: [Teas] FW: The word "transport"

[External Email. Be cautious of content]

>>>>> [JD]  This is back to Adrian’s original point, viz, ‘transport slice’ is a term coined by another standards body.

As far as I know there is not any SDO which defines “Transport slice” at least at the time that we wrote the draft. If not so, please provide the reference.
We at IETF started using this term.

Reza

From: John E Drake <jdrake@juniper.net<mailto:jdrake@juniper.net>>
Date: Friday, May 1, 2020 at 11:52 AM
To: Reza Rokui <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>, Eric Gray <eric.gray@ericsson.com<mailto:eric.gray@ericsson.com>>, "adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>" <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>, 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org<mailto:jdrake=40juniper.net@dmarc.ietf.org>>, "teas@ietf.org<mailto:teas@ietf.org>" <teas@ietf.org<mailto:teas@ietf.org>>, "teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>" <teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>>
Subject: RE: [Teas] FW: The word "transport"

Hi,

Comment inline

Yours Irrespectively,

John



Juniper Business Use Only
From: Teas-ns-dt <teas-ns-dt-bounces@ietf.org<mailto:teas-ns-dt-bounces@ietf.org>> On Behalf Of Rokui, Reza (Nokia - CA/Ottawa)
Sent: Friday, May 1, 2020 11:49 AM
To: Eric Gray <eric.gray@ericsson.com<mailto:eric.gray@ericsson.com>>; adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org<mailto:jdrake=40juniper.net@dmarc.ietf.org>>; teas@ietf.org<mailto:teas@ietf.org>; teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>
Cc: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Subject: Re: [Teas-ns-dt] [Teas] FW: The word "transport"

[External Email. Be cautious of content]

>>>>>>>> Possibly it would be better to clarify this in terms of what the IETF does deal with?

I meant that IETF does not address the other aspects of an e2e network slice like RAN and Core slice (aka Other Slices).
A transport slice is just a piece of an e2e network slice. Any reference to “network slice” is not correct since IETF does not deal with Other Slices.

[JD]  This is back to Adrian’s original point, viz, ‘transport slice’ is a term coined by another standards body.

Reza Rokui, Ph.D.
Director, NSP Product Management
Nokia Canada
IP/Optical Network Automation
T:  +1-613-784-1762
M: +1-613-979-6986
600 March Road, Kanata, Ontario, K2K 2E6
Reza.Rokui@Nokia.com<mailto:Reza.Rokui@Nokia.com>


From: Eric Gray <eric.gray@ericsson.com<mailto:eric.gray@ericsson.com>>
Date: Friday, May 1, 2020 at 11:45 AM
To: Reza Rokui <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>, "adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>" <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>, 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org<mailto:jdrake=40juniper.net@dmarc.ietf.org>>, "teas@ietf.org<mailto:teas@ietf.org>" <teas@ietf.org<mailto:teas@ietf.org>>, "teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>" <teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>>
Subject: RE: [Teas] FW: The word "transport"

Possibly it would be better to clarify this in terms of what the IETF does deal with?

The IETF deals with “packetized” (more specifically, where packetization uses IETF defined packet formats) transport of otherwise arbitrary data.

Here you can replace transport with “carrying” – but this is essentially the standard English meaning of transport.

From: Teas-ns-dt <teas-ns-dt-bounces@ietf.org<mailto:teas-ns-dt-bounces@ietf.org>> On Behalf Of Rokui, Reza (Nokia - CA/Ottawa)
Sent: Friday, May 1, 2020 11:38 AM
To: adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org<mailto:jdrake=40juniper.net@dmarc.ietf.org>>; teas@ietf.org<mailto:teas@ietf.org>; teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>
Cc: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Subject: Re: [Teas-ns-dt] [Teas] FW: The word "transport"

Adrian,

>>>>>> I don’t understand “we (IETF) do not deal with network slice”.

Please refer to Figure 4 of the draft.
In summary, an E2E network slice is the logical network from End user X to End use Y and comprises of:

  *   One or more Transport slices (TS)
  *   One or more Other Slices (OS)

Just as an example for “Other Slices”, in 5G these slices are RAN slices and 5G Core Slices.
Referring  this Figure, it is clear that IETF deals with Transport slice which is part of an E2E network slice and “Other slices” are outside scope of IETF.
Please make a clear distinction between Transport Slices and e2e network slices. They are different.
IMHO, any reference to “Network Slice” in IETF drafts means “Transport slice” .

>>>>>>.  Why do we have a “TEAS Network Slicing Design Team”?
Good question. The correct name can be “TEAS Transport Slicing Design Team”

[cid:image002.png@01D61FBF.27168450]

Reza


From: Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>
Organization: Old Dog Consulting
Reply-To: "adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>" <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>
Date: Friday, May 1, 2020 at 10:30 AM
To: Reza Rokui <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>, 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org<mailto:jdrake=40juniper.net@dmarc.ietf.org>>, "teas@ietf.org<mailto:teas@ietf.org>" <teas@ietf.org<mailto:teas@ietf.org>>, "teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>" <teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>>
Subject: RE: [Teas] FW: The word "transport"

Hi Reza,

I don’t understand “we (IETF) do not deal with network slice”.
Why do we have a “TEAS Network Slicing Design Team”?

Cheers,
Adrian

From: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Sent: 01 May 2020 15:13
To: adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org<mailto:jdrake=40juniper.net@dmarc.ietf.org>>; teas@ietf.org<mailto:teas@ietf.org>; teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>
Cc: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Subject: Re: [Teas] FW: The word "transport"

John and all,

This is where I disagree with term “Underlay Network Slice”. It brings lots of other questions since we (IETF) do not deal with network slice as clearly described in our draft.

As I send in another email thread, as per Adrian’s suggestion, we define the term “Transport” as follows and would like to keep the term “Transport Slice”


  *   Definition of term Transport: This term embraces various technologies such as IP, Optical, Ethernet, TDM, etc  that carry packets and traffic and might span multiple administrative domains.

Please provide your suggestion to refine this definition.

Cheers,
Reza

From: Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>
Organization: Old Dog Consulting
Reply-To: "adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>" <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>
Date: Friday, May 1, 2020 at 5:23 AM
To: 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org<mailto:jdrake=40juniper.net@dmarc.ietf.org>>, Reza Rokui <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Cc: "teas@ietf.org<mailto:teas@ietf.org>" <teas@ietf.org<mailto:teas@ietf.org>>
Subject: RE: [Teas] FW: The word "transport"

Yeah, ‘underlay’ seems good because it is a relative term and usefully recursive.

A

From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> On Behalf Of John E Drake
Sent: 30 April 2020 20:59
To: adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'Rokui, Reza (Nokia - CA/Ottawa)' <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Cc: teas@ietf.org<mailto:teas@ietf.org>
Subject: Re: [Teas] FW: The word "transport"

Hi,

How about ‘underlay network slice’?  It’s describing exactly what we are doing and is congruent with the Enhanced VPN draft.

Yours Irrespectively,

John



Juniper Business Use Only
From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> On Behalf Of Adrian Farrel
Sent: Thursday, April 30, 2020 3:32 PM
To: 'Rokui, Reza (Nokia - CA/Ottawa)' <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Cc: teas@ietf.org<mailto:teas@ietf.org>
Subject: [Teas] FW: The word "transport"

[External Email. Be cautious of content]

Reza,

Thanks for forwarding this email.

I appreciate and understand the way that 3GPP use the term “transport”. It makes a lot of sense in the 3GPP context: they are talking about connectivity in their realm, and anything that provides that connectivity (such as an IP network) counts as “transport”.

But we are not the 3GPP and our terminology needs to be consistent. As I noted, we already have multiple meanings of transport:

  *   The transport layer (traditional from the OSI model) that includes TCP, UDP, etc.
  *   Transport networks (a term also used in the ITU-T) that embraces Ethernet, TDM, and optical technologies that carry packets for us. This term is most often seen in CCAMP, TEAS, and PCE.
  *   MPLS-TP (possibly deriving from the ITU-T’s T-MPLS) that refers to the use of MPLS as a technology to build transport networks as described in the previous bullet
  *   Transport as a verb (such as in HTTP) meaning simply ‘to carry’
In the ACTN work, we moved from ‘transport’ to ‘TE’ recognising that ACTN was applicable to any network type where paths could be computed and imposed, and resource partitioned and reserved.

Now, you say Transport networks (which are technology specific) are used to realized “Transport Slices” which would appear to imply that IP cannot be used to realise a transport slice. I don’t know if that is your intention.

You also say They [3GPP] did not define anything related to Transport but you say that immediately under a figure you have copied from 3GPP TS 28.530 that clearly shows transport slices, so that leaves me more than a little confused.

Additionally, you say…
VPN is one of the  solutions to realize the transport slices in IP networks.

…which is fine by me since I am not (here) talking about solutions but services. Actually, I think you would do well to distinguish between VPN as a service and the technologies used to realise a VPN.



Then…

However, The idea of Transport Slice is to allow a high-level system (or consumer or an Orchestrator) to ask for a various connections (i.e. Transport slices)

… This is pretty meaningless the way you have worded it. You have said “the idea of a transport slice is to all a request for transport slices...

across  IP, Optics, PON, Microwave or any combination of these networks. We shall not limit ourselves to IP VPN.

…Yes, indeed. I wonder where the idea of such a limitation came from…

Note that the definition of the Transport slice is technology agnostic.

…I know. It comes from draft-ietf-teas-enhanced-vpn. That originated in draft-king-teas-applicability-actn-slicing. I believe I drafted it…

[snip]

In summary, since the connectivity between various endpoints are across transport network (i.e. IP, Optics, PON, Microware etc.), it is logical to assume the Connections are called Transport Slice.
…which is fine except that you have moved the problem to the definition of “transport network”. The IETF will struggle, I think, with the idea that an IP network is a transport network unless, in the context of these documents, you give a very clear explanation of what these documents mean by that term.

But perhaps we can cut through all of this with some simple clarity. Text to describe the context and meaning of ‘transport’. Since the terminology document has so cheerfully plundered the enhanced VPN framework draft for some text, you might look there (in the Introduction) for suitable context-setting text.

That, of course, leads me to a separate question that I have, which is why the design team is reproducing and/or copying material from an existing WG document rather than working with that document to refine it and/or split it into multiple documents. A different question, but one the chairs might like to comment on.

Best,
Adrian

From: Teas-ns-dt <teas-ns-dt-bounces@ietf.org<mailto:teas-ns-dt-bounces@ietf.org>> On Behalf Of Rokui, Reza (Nokia - CA/Ottawa)
Sent: 30 April 2020 16:23
To: teas@ietf.org<mailto:teas@ietf.org>; teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>
Cc: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Subject: [Teas-ns-dt] FW: The word "transport"

All,

I thought I sent this to TEAS and TEAS-NS-DT team before. Forwarding the response to everyone.

Cheers,
Reza



From: Reza Rokui <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Date: Saturday, April 25, 2020 at 11:37 PM
To: Dhruv Dhody <dhruv.ietf@gmail.com<mailto:dhruv.ietf@gmail.com>>, Jari Arkko <jari.arkko@piuha.net<mailto:jari.arkko@piuha.net>>, "draft-nsdt-teas-transport-slice-definition@ietf.org<mailto:draft-nsdt-teas-transport-slice-definition@ietf.org>" <draft-nsdt-teas-transport-slice-definition@ietf.org<mailto:draft-nsdt-teas-transport-slice-definition@ietf.org>>
Cc: Reza Rokui <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Subject: Re: The word "transport"


Hi all,



Please see inline for some clarifications.



Reza





On 2020-04-24, 1:31 AM, "Dhruv Dhody" <dhruv.ietf@gmail.com<mailto:dhruv.ietf@gmail.com>> wrote:



    Hi Reza,



    I am putting the relevant text here -



    ==



    [14:28:42] <adrianfarrel> I'm getting very confused by everyone

    talking about "transport networks" and "transport slices". Is this

    something coming out of 3GPP?



[Reza] Please note that the “Transport Slice” from IETF point of view is not only limited to 5G network slicing.

5G network slicing is just one use-case of transport slicing as described in Transport Slice definition draft.



Regarding 5G use-case, the following figure is taken from 3GPP TS 28.530 where the “Transport slice” is described as “Connectivity” across transport network.

This is the reason that what has been described in our draft for “Transport Slices” is a set of Connections between various endpoints with certain SLOs.

Note that 3GPP did not define the Transport slice explicitly.



[cid:image001.png@01D61F08.48854020]







    [14:29:06] <adrianfarrel> Seems to me that we (for example, ACTN) went

    through a lot to clarify that "transport network" was sub-IP

    [14:29:17] <adrianfarrel> ...maybe even sub-MPLS

[Reza] Transport networks (which are technology specific) are used to realized “Transport Slices”. Please see draft for more info.



    [14:31:39] <Joel Halpern> "Transport Network" is the industry

    terminology for the network that connects the radio (and related gear)

    to the packet core (and related gear).

    [14:32:03] <Joel Halpern> It is indeed a different usage.  I wish it

    were not overloading.  But they didn't ask me.

    [14:32:47] <Joel Halpern> Which part it refers to in a fixed access

    network is even less clear.



[Reza] The following figure is taken from 3GPP TS 28.530 where it shows various “Transport slices”.

Note that the “Transport Slices” are not only used for RAN to Core. Depends on the deployment, we can have

Transport slices in RAN for midhaul and fronthaul, in 5G Core or for application. All these transport slices are shown below.



] [cid:image003.png@01D61F08.48854020]



    [14:39:54] <adrianfarrel> I understand why 3GPP uses the term. I don't

    understand why we use the term.. We could talk about 'Foobar slices'

    and add one line that says "In the 3GPP, the term 'Transport Slice' is

    used for what we call a 'Foobar Slice'."

[Reza]  Note that 3GPP used the term “slice subnet” when describing it in context of 5G Core and RAN (i.e Core Slice Subnet and RAN Slice Subnet).

They did not define anything related to Transport. As indicated above, 3GPP refer it to “Connectivity”.

We did not want to use Subnet because in IP,  subnet has a very clear definition and using term “Transport Subnet” is completely misleading. So, we chose Transport Slice.

Also since the connectivity between various endpoints are across transport network (i.e. IP, Optics, PON, Microware etc.), it is logical to assume the Connections are called Transport Slice.





    [14:40:18] <adrianfarrel> We *already* have two definitions of

    "transport" in the IETF. We really don't need three

[Reza] Please provide links to these two definition.



    [14:59:00] <adrianfarrel> Well, I picked "foobar' in order to not jump

    immediately to a strawman solution. I think we are talking about

    providing slices as a service across the Internet. Same level of entry

    as a VPN: that is, the consumer provides a packet stream to the

    service entry point, and expects the packets to be delivered to the

    service exit point. Obviously, the consumer of the service may see the

    service as a transport (cf. pseudowires), but we would be 'alarmed' to

    hear a L3VPN described as a 'transport VPN.'

[Reza] VPN is one of the  solutions to realize the transport slices in IP networks.

However, The idea of Transport Slice is to allow a high-level system (or consumer or an Orchestrator) to ask for a various connections (i.e. Transport slices) across  IP, Optics, PON, Microwave or any combination of these networks. We shall not limit ourselves to IP VPN.

Note that the definition of the Transport slice is technology agnostic. For example in 5G you can realize a transpot slice in midhaul (please refer to picture above) which is a set of connections between 5G RAN nodes using PON or Optical connection. In this case there is no IP VPN.

In summary, since the connectivity between various endpoints are across transport network (i.e. IP, Optics, PON, Microware etc.), it is logical to assume the Connections are called Transport Slice.



    Full logs - https://www.ietf.org/jabber/logs/teas/2020-04-23.html<https://protect2.fireeye.com/v1/url?k=d85f249f-86ff9ef1-d85f6404-866038973a15-79480ef04dd7bd36&q=1&e=3885d79e-3893-4913-8634-bfacad730074&u=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fprotect2.fireeye.com%2Fv1%2Furl%3Fk%3Dd4f6bc46-8a560628-d4f6fcdd-86b1886cfa64-dd8e4ff74c5dda87%26q%3D1%26e%3Db15230b3-e6dc-4732-83e3-00354fdc75ae%26u%3Dhttps%2A3A%2A2F%2A2Furldefense.com%2A2Fv3%2A2F__https%2A3A%2A2Fwww.ietf.org%2A2Fjabber%2A2Flogs%2A2Fteas%2A2F2020-04-23.html__%2A3B%2A21%2A21NEt6yMaO-gk%2A21WrvQt2QtERG2EFnE6CPHr8TzNjoFggUjNzUFGwWmlw2KiRSR42MiO2N4YtwhZJI%2A24__%3BJSUlJSUlJSUlJSUlJSUlJQ%21%21NEt6yMaO-gk%21Ss83mQtEVqDRzJaflsjI0IuUspo1qru8LEP6d7EHAVACW_rPFMRhTgGzcd8fvSc%24>



    ==



    More inline..



    On Thu, Apr 23, 2020 at 10:27 PM Rokui, Reza (Nokia - CA/Ottawa)

    <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>> wrote:

    >

    > Hi Dhruv,

    >

    > As far as I remember, we did not have any argument about term "transport". It was agreed that the term "Transport" is suited in context of network slicing.

    > The initial discussion was "Transport network slicing" which later we agreed to remove "network" since it causes confusion since IETF do not cover the e2e network slicing but rather the transport part.

    >

    > I was not clear about Adrian's comment regarding term "transport". IMHO, this term is well suited since it convers any underlying technology for L0 to L3.

    >



    In CCAMP/TEAS circles, the transport network term might not be used

    for L3 (and thus the confusion). And then there are the Transport

    Protocols! Definition draft should include some clarity on what do we

    mean when we say transport network at the least!



    It would be good to get this resolved sooner as we develop multiple

    documents that uses the same terminology!



    Thanks!

    Dhruv



    > Reza

    >

    >

    > On 2020-04-23, 12:35 PM, "Dhruv Dhody" <dhruv.ietf@gmail.com<mailto:dhruv.ietf@gmail.com>> wrote:

    >

    >     Hi,

    >

    >     Adrian gave some comments on jabber about using the word "transport".

    >

    >     During RFC8453 devolpment, this came up where TN in ACTN was transport

    >     networks and it was changed to TE networks to avoid using the

    >     overloaded term "transport".

    >

    >     We need to find a way to justify using this term and maybe describe

    >     this more in the definition draft - and just saying that 3GPP uses

    >     that term may not work I guess!

    >

    >     Was this discussed in the design team earlier, i joined the effort

    >     much later.

    >

    >     Thanks!

    >     Dhruv

    >


Juniper Business Use Only


Juniper Business Use Only


Juniper Business Use Only