Re: [Teas] FW: New Version Notification for draft-king-teas-applicability-actn-slicing-06.txt

Kiran Makhijani <kiranm@futurewei.com> Wed, 22 July 2020 01:45 UTC

Return-Path: <kiranm@futurewei.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 925773A0819 for <teas@ietfa.amsl.com>; Tue, 21 Jul 2020 18:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level:
X-Spam-Status: No, score=-2.09 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 QFoCe9PaSRsN for <teas@ietfa.amsl.com>; Tue, 21 Jul 2020 18:44:58 -0700 (PDT)
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-eopbgr690100.outbound.protection.outlook.com [40.107.69.100]) (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 D09933A080B for <teas@ietf.org>; Tue, 21 Jul 2020 18:44:58 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=C1IsgYmBGn+H93oxHAUuxcPptwOSqBoHYElbvRnEGbF82JKCIlPaZh3EvCj3eW72ZnpkRZUKMt4IjCaJXt/DJ84GHk26GXpOTpbbY/WpergVW6q5Z9KwOqcg4X2VFGt+3sPCAkQnSkH2ae0lzz0oNpSlTDpldGhidargMlH/Yj/+/5Y/+X0gcItavNSaCBTdRK17/dPd70tR2HkgB38YPAetT63UVpnQpQq031ZqPPFKiIs4W4VlASa93DqqI0xpCVV+Bz1e6AVho1lcwUGT0T6askjID6Om5rS+yvytzvngIgTFLTAb0eA9Ef2yfhxh94nCZevwPoC7QxKOISY45A==
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=LUQzrBlYjy58ATIIkksL667v8rXvPxpm1C3RrjGiqv8=; b=R3DQTlZmyeiZBAVvQ4iJ6BpPL9R72gIQ/eW67P5m0KUSisBh0XoY5mL+2sWSlUabBiFgven7jZluX2kax72vL4FWt1EzkvvLKCic6NYikZNPw627YWcKyL8HAGljSDGeFcKt+PxWU/5/bC+1oAmMgrdzKoHtJO0kkgoCiCZOtSu55pLR3zKa2wfqOtKG8kCjegm8tWdBZzVTwbwJE6Qx9yhqdoRZF8euW9ASLy98LgJBrxKVcvPAawHWCqir5ZvIlOQLgMorpDovNs2jEB1HZnvRNETETl1EEFd9RnXHeM/1HC3W+pOCIaPEZKk030Gnfa72BBjx+iMbvT4IIJjrfA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=LUQzrBlYjy58ATIIkksL667v8rXvPxpm1C3RrjGiqv8=; b=Oxkxk60KsAwu72hpCb83DotgSFcKqqzEv7vlKbyAT8Lhdq0TXFihuMscXCEpDx+aKdX0Qbj1awN/QhpaH5wPwlpkPy+svILFqiWJcni7tSTyf9xmdE7rps2SgoeQqaG5kprlrCjR4cNT0QKYacQlLuHL+rmavPY4IkbEHCyZXsE=
Received: from BYAPR13MB2437.namprd13.prod.outlook.com (2603:10b6:a02:cb::23) by BY5PR13MB3239.namprd13.prod.outlook.com (2603:10b6:a03:184::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.18; Wed, 22 Jul 2020 01:44:56 +0000
Received: from BYAPR13MB2437.namprd13.prod.outlook.com ([fe80::4596:6de4:d7fe:66ee]) by BYAPR13MB2437.namprd13.prod.outlook.com ([fe80::4596:6de4:d7fe:66ee%3]) with mapi id 15.20.3216.018; Wed, 22 Jul 2020 01:44:55 +0000
From: Kiran Makhijani <kiranm@futurewei.com>
To: "dk@danielking.net" <dk@danielking.net>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] FW: New Version Notification for draft-king-teas-applicability-actn-slicing-06.txt
Thread-Index: AQJxGDC4suh2J78pwwWz9frRtQUvKafROWJggAwcZMA=
Date: Wed, 22 Jul 2020 01:44:55 +0000
Message-ID: <BYAPR13MB2437D103F2A6ABCA8E73667ED9790@BYAPR13MB2437.namprd13.prod.outlook.com>
References: <159466961105.19498.16921497402746412452@ietfa.amsl.com> <000001d659b5$f021d4f0$d0657ed0$@danielking.net>
In-Reply-To: <000001d659b5$f021d4f0$d0657ed0$@danielking.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: danielking.net; dkim=none (message not signed) header.d=none;danielking.net; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [67.188.27.49]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1402372a-3b68-4eab-9d92-08d82de0d5fa
x-ms-traffictypediagnostic: BY5PR13MB3239:
x-microsoft-antispam-prvs: <BY5PR13MB3239A71418E8351F1EE39E0DD9790@BY5PR13MB3239.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 8cKQ1oWXCVcSrVL9RmQInTSetg+fGPozmw7AXQ1ElsjNijRiUKS941J8rSIc5BKRAtrL/VxpQgvCF/UI/ZWBTUSc146WtP4/ZsPkuH1j5GWRuwq67Q3hCVYQKe9I3X93hgoja9WbDnnXND/40wNIx/JFl6EV9B+xgCqhlOggQo9Drxgd2wSwx1KzMB9k6swh2UxlrbZBrTb7b0wAgLKdWsMl4Drt3GiZfcDfU0cBpQ8FUoudmjTf7h3P6MRGGFmQ0wCySRTVOVXf5Yfc8usCh+SBFZpJwg8gPlQ8PPgaeVU4dmhh70Jj1mWVd4j1p1AYuiF/DqBGa7i9kk28BYlQ3FewMlYg8WGpv6lGdBhbHeg5GqN9lwh6gA2N48k8tbfTrNwMN3vpqHIgrn9KSD9qX6FQbm+vcSfFgPnnuaiDO3PbW/w3LdGTi24DuDdfHMSNYSmGvQy2nWYAPtRMxFQSHFuB8BNe4tgqBnP4YXn4x9c=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR13MB2437.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(39850400004)(136003)(366004)(346002)(376002)(396003)(52536014)(33656002)(5660300002)(966005)(45080400002)(71200400001)(8936002)(478600001)(8676002)(9686003)(66574015)(55016002)(66556008)(53546011)(76116006)(66446008)(66476007)(64756008)(26005)(2906002)(15650500001)(110136005)(316002)(7696005)(83080400001)(66946007)(186003)(86362001)(83380400001)(6506007); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: 9MY6Iei9cvAYjWpkFWzJw6IJDXJcJh6pR39SfCIS3kCh4Y7gW57nRJv9kgJPa8AG6d+XGoQbAjVikdtrK1GNK3u5o85X1lH8jPQKnXmxhzlfTuNQ5htVAzINsVjz4d8iAaZa8p5ZfWPqaENFTBZg6/z0vfz3B72QC7T3u+w2BvjOxYOgksmi+UaD5fWn36Mwa1NY+fmBdIESe7cjGMG/lt3C+H9uGVEF2Ds3DXlNwcwP1IKs4RBCu53ScYmin9+TZO1KWdnAAmuTxT/ZuYcyviSzmCmrSPxJGp37ifX1Fkv5vRqS47rAYrcwn7Z+bd4UPC9yTtdJ1FvzcIbAydl1ps8xprpts9Jwj/bJFjaoCyEf3+RtPou6MYDAGpNLGrIpptt7ED3oou2xlty5ecXtyK7YO6NCp0Bu0U+T/JPXcCyiCC5zcY9tML/a0dkUKvnqzK+yi+7Sc3l+eK/gDU7Fo/LJcF5CywDfV3CKbZ4qN3s=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR13MB2437.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1402372a-3b68-4eab-9d92-08d82de0d5fa
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jul 2020 01:44:55.7631 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Y9LvYQcbIjeXYt/txyL/lylusOIS4anXUH3pgm78BZWhMz6Oqt7sUgn55ortRMAAkm4gEdJzNQ7Lh6A+7jk+QA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR13MB3239
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/SS-IxjiXPhYW99y-Oho3YgS7RB4>
Subject: Re: [Teas] FW: New Version Notification for draft-king-teas-applicability-actn-slicing-06.txt
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, 22 Jul 2020 01:45:01 -0000

Hi Dan, 
I'd like to share few thoughts form my reading of this document, mostly for clarifications:

- First thing that strikes me is: the things before chapter 3 are not related to ACTN only, and is common information that will benefit all. I'd strongly encourage to give broader relevance to requirements section.

- Out of curiosity, why do you define Resource and Infrastructure resource separately when you don't use them later in the document?

- In terminology part defining network slice as an agreement is an interesting choice (difficult for me to get used to), but since this is an ACTN world, why not call it a client network?

- I could only follow delivery model 3.2.3 in relation to transport slices. Could not grasp relevance of section 3.2.1 and 3.2.2 - are they not transport slices? 

- Even in 3.2.4, I understand the text explains the  mappings of Lx-service-models to ACTN but beyond that relationship to slices is not clear. This is very important and crux of ACTN applicability to slices. If you followed nsdt discussion, we were asked to remove it as an example of SBI. Because service models are consumer's view of the network. So if you explain relationship in terms of interface and use, that would be very useful.

- I can not differentiate between the usage of term network slice transport slice: - which one should be used when?  In nsdt we have a notion of higher-level orchestrator that interfaces with transport controller so it is not a problem there.

- one thing missing is a ACTN framework to TS-framework comparison.

This is a good contribution. I hope to see better alignment in time..
Thanks
Kiran

> -----Original Message-----
> From: Teas <teas-bounces@ietf.org> On Behalf Of dk@danielking.net
> Sent: Tuesday, July 14, 2020 1:08 AM
> To: teas@ietf.org
> Subject: [Teas] FW: New Version Notification for draft-king-teas-applicability-
> actn-slicing-06.txt
> 
> Greetings TEAS,
> 
> For your reading pleasure we recently updated our ACTN applicability to
> network slicing I-D.
> 
> Applicability of Abstraction and Control of Traffic Engineered Networks (ACTN)
> to TE Network Slicing
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatr
> acker.ietf.org%2Fdoc%2Fhtml%2Fdraft-king-teas-applicability-actn-
> slicing&amp;data=02%7C01%7Ckiranm%40futurewei.com%7Cc25b2df4f9f04f
> ca662e08d827cd28b9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7
> C637303109400397496&amp;sdata=4Eyq1sAw7Ow0MpVHiTvFFpMXLNmsILG
> pYD54SImHAAw%3D&amp;reserved=0
> 
> The tldr version, we updated the document to point to a candidate YANG
> model for transport network slicing (draft-wd-teas-transport-slice-yang). We
> also fixed some NITs and identified some additional/future work.
> 
> As always we would love to hear from the WG participants. Did you find the I-D
> useful, not so useful, are we on the right track, what is missing? All feedback
> acknowledged and gratefully received.
> 
> See you (virtually) soon.
> 
> BR, Dan.
> 
> -----Original Message-----
> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
> Sent: 13 July 2020 20:47
> To: Haomian Zheng <zhenghaomian@huawei.com>om>; John Drake
> <jdrake@juniper.net>et>; Daniel King <daniel@olddog.co.uk>
> Subject: New Version Notification for draft-king-teas-applicability-actn-slicing-
> 06.txt
> 
> 
> A new version of I-D, draft-king-teas-applicability-actn-slicing-06.txt
> has been successfully submitted by Daniel King and posted to the IETF
> repository.
> 
> Name:		draft-king-teas-applicability-actn-slicing
> Revision:	06
> Title:		Applicability of Abstraction and Control of Traffic Engineered
> Networks (ACTN) to TE Network Slicing
> Document date:	2020-07-13
> Group:		Individual Submission
> Pages:		17
> URL:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.i
> etf.org%2Finternet-drafts%2Fdraft-king-teas-applicability-actn-slicing-
> 06.txt&amp;data=02%7C01%7Ckiranm%40futurewei.com%7Cc25b2df4f9f04f
> ca662e08d827cd28b9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7
> C637303109400397496&amp;sdata=Jx8IyUCQJ0RTzGWs%2F4tLuGbBbgJBUfb
> 2aX5gAcu7bA4%3D&amp;reserved=0
> Status:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatr
> acker.ietf.org%2Fdoc%2Fdraft-king-teas-applicability-actn-
> slicing%2F&amp;data=02%7C01%7Ckiranm%40futurewei.com%7Cc25b2df4f9
> f04fca662e08d827cd28b9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C
> 0%7C637303109400407495&amp;sdata=aVfyA15howACcW%2BkLZAH%2B2I
> ORFAZEJtC5ANlZigy8Vk%3D&amp;reserved=0
> Htmlized:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.i
> etf.org%2Fhtml%2Fdraft-king-teas-applicability-actn-slicing-
> 06&amp;data=02%7C01%7Ckiranm%40futurewei.com%7Cc25b2df4f9f04fca6
> 62e08d827cd28b9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C6
> 37303109400407495&amp;sdata=6yWCeXEujIPIT8KaTLCXfiJvRstVQjTbj2FzXgr
> 6i6Q%3D&amp;reserved=0
> Htmlized:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatr
> acker.ietf.org%2Fdoc%2Fhtml%2Fdraft-king-teas-applicability-actn-
> slicing&amp;data=02%7C01%7Ckiranm%40futurewei.com%7Cc25b2df4f9f04f
> ca662e08d827cd28b9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7
> C637303109400407495&amp;sdata=ziekTnqxE9LwTHLwqa2cUgYSiCDnBkY5U
> 6xZexajf2A%3D&amp;reserved=0
> Diff:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.i
> etf.org%2Frfcdiff%3Furl2%3Ddraft-king-teas-applicability-actn-slicing-
> 06&amp;data=02%7C01%7Ckiranm%40futurewei.com%7Cc25b2df4f9f04fca6
> 62e08d827cd28b9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C6
> 37303109400407495&amp;sdata=2FhfHfo7mFzcO1KAwi9dBYDChLaGjHpI3xp
> H624UZi8%3D&amp;reserved=0
> 
> Abstract:
>    Network abstraction is a technique that can be applied to a network
>    domain that utilizes a set of policies to select network resources
>    and obtain a view of potential connectivity across the network.
> 
>    Network slicing is an approach to network operations that builds on
>    the concept of network abstraction to provide programmability,
>    flexibility, and modularity.  It may use techniques such as Software
>    Defined Networking (SDN) and Network Function Virtualization (NFV) to
>    create multiple logical or virtual networks, each tailored for a set
>    of services share the same set of requirements.
> 
>    Abstraction and Control of Traffic Engineered Networks (ACTN) is
>    described in RFC 8453.  It defines an SDN-based architecture that
>    relies on the concept of network and service abstraction to detach
>    network and service control from the underlying data plane.
> 
>    This document outlines the applicability of ACTN to transport network
>    slicing in a Traffic Engineering (TE) network that utilizes IETF
>    technology.  It also identifies the features of network slicing not
>    currently within the scope of ACTN, and indicates where ACTN might be
>    extended.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> 
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.i
> etf.org%2Fmailman%2Flistinfo%2Fteas&amp;data=02%7C01%7Ckiranm%40fu
> turewei.com%7Cc25b2df4f9f04fca662e08d827cd28b9%7C0fee8ff2a3b240189
> c753a1d5591fedc%7C1%7C0%7C637303109400407495&amp;sdata=i1CyZvff
> WC%2B%2FwsbL3CkQ3T8LOuFw7wN3Kbb9UxLcexo%3D&amp;reserved=0