Re: [Teas] FW: New Version Notification for draft-nsdt-teas-ietf-network-slice-definition-00.txt

Adrian Farrel <adrian@olddog.co.uk> Wed, 28 October 2020 16:20 UTC

Return-Path: <adrian@olddog.co.uk>
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 A887C3A010A; Wed, 28 Oct 2020 09:20:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 L2vt6jWvI4FS; Wed, 28 Oct 2020 09:20:32 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 A7E2D3A0112; Wed, 28 Oct 2020 09:20:30 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id 09SGKQZR030210; Wed, 28 Oct 2020 16:20:26 GMT
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2179822042; Wed, 28 Oct 2020 16:20:26 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS id 0B84B22044; Wed, 28 Oct 2020 16:20:26 +0000 (GMT)
Received: from LAPTOPK7AS653V (81-174-211-216.pth-as4.dial.plus.net [81.174.211.216]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 09SGKOWF005595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 28 Oct 2020 16:20:25 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Kiran Makhijani'" <kiranm@futurewei.com>, <teas-ns-dt@ietf.org>, "'TEAS WG'" <teas@ietf.org>
References: <160334637666.17176.15293064565481905957@ietfa.amsl.com> <BYAPR13MB2437223D535F2ACC294A8FEAD91D0@BYAPR13MB2437.namprd13.prod.outlook.com> <005401d6a84f$76d21310$64763930$@olddog.co.uk> <BYAPR13MB24376B12958519181BDEF237D9170@BYAPR13MB2437.namprd13.prod.outlook.com>
In-Reply-To: <BYAPR13MB24376B12958519181BDEF237D9170@BYAPR13MB2437.namprd13.prod.outlook.com>
Date: Wed, 28 Oct 2020 16:20:24 -0000
Organization: Old Dog Consulting
Message-ID: <062c01d6ad46$3e2ef8b0$ba8cea10$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHgC41I55FYvxoDOgxM9N1MOiaQcQJLYPYuAYCg3mQB2wzWH6ltO3ug
Content-Language: en-gb
X-Originating-IP: 81.174.211.216
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25754.001
X-TM-AS-Result: No--28.962-10.0-31-10
X-imss-scan-details: No--28.962-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25754.001
X-TMASE-Result: 10--28.962300-10.000000
X-TMASE-MatchedRID: pS5owHKhBO2yoI+bK8UPQmmpWpGzPzJdaMmm586o4gBIXJo+eGm+FHgW t5DwssvI5JR7iYrWWS9N7v5eVNBbmvnVY0DWsTq3nMQdNQ64xfepXdWa4gU0S7T/vLTYpUnMcqD dkIibZdHf5wnq0pNQ1eI3TeEX0p58DvmmHfPKDDUzxdO2BTO20+Nk6PrhzRD2IlxOowKJvsXFSC smzalJ/Gr8oEHqFO0os/V3IKtzjqyTDlsGaeU3mFzIUxHqXB+QC/ExpXrHizwcNByoSo036Qzrb STTmWqb8N5Old8DoGO6Jjcl3s7Fnbl7A3O5D6aX5Qo03mEdwAErftG2Z0stzug3wNKii1r5EYKg ogWnjPO8JJvjqeYFtrfhL1mA+RaMOpPA8Ci9bQTyKt/vA0HdKPNYK2IEj4Nx2+Avsq/zL0F9TEB 5StD0vdcNqFK7tWlhyZFdAOAQ4c6B7muvZbKCIoVMtEwAWsdcNr21mij50Nsz988bphElUX3kR6 l0wGIGesLKOnHkV3IQcEWJjhzpZNa8OeUKtpU/mOFnGEL0JOPdu0VUNP0QV5m9G0XmuNWvHZGTP 9sxpjDjDo8FoO8h18Nsw3rqH4H4Q9x1CLc+xtpOX8UITKJPHiBP+xe0Zet/nkYuW9OJethXoYnJ E8t84uByqm2JX7QDkJ/2H+NycvHii4GtpKvX35E2Q1oQGbBkQ5p+5M7kril/KM1eVsG+dHY+oFb rqO/J23eOzBZakZcjEpJdZ5B2HQqbmS3v1dsxFyB4e9PL2K59LQinZ4QefL6qvLNjDYTwzz3jeh zenex88Plw9Yn01z+d0CWdalxjFpG8QcMOW5kXeuQCqIxled934/rDAK3zUc1+O1X9AzE=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/NW6WZDefDX-BEpeNUNND3a424yU>
Subject: Re: [Teas] FW: New Version Notification for draft-nsdt-teas-ietf-network-slice-definition-00.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, 28 Oct 2020 16:20:35 -0000

Thanks Kiran,

It is getting markedly better.
I'll wait for Jie, Luis, and Jeff before I look at the draft again.

A

-----Original Message-----
From: Kiran Makhijani <kiranm@futurewei.com> 
Sent: 28 October 2020 15:53
To: adrian@olddog.co.uk; teas-ns-dt@ietf.org; 'TEAS WG' <teas@ietf.org>
Subject: RE: [Teas] FW: New Version Notification for
draft-nsdt-teas-ietf-network-slice-definition-00.txt

Thanks Adrian, 
According to authors the current text in this document is just enough to
provide clarity on the IETF network slice concept. 
I remember you wanted current section 5 to be removed but we felt it's
important and pruned it quite a bit - we will further combine section 5 and
10 to define end-to-end slices relationship and the structure in one place. 
Other than that, we are waiting for revision on isolation contribution from
Jie, Luis, and Jeff.  

Yes, end-to-end slicing will need quite a bit of explanation but minimal
description here is also important to show the scope of IETF network slices
in the broader concept. 

I hope that the mailing list this time agrees that it is a reasonable
terminology-set. 
-Kiran


> -----Original Message-----
> From: Adrian Farrel <adrian@olddog.co.uk>
> Sent: Thursday, October 22, 2020 1:44 AM
> To: Kiran Makhijani <kiranm@futurewei.com>om>; teas-ns-dt@ietf.org; 'TEAS WG'
> <teas@ietf.org>
> Subject: RE: [Teas] FW: New Version Notification for draft-nsdt-teas-ietf-
> network-slice-definition-00.txt
> 
> Kiran, all,
> 
> I want to thank the authors of this draft for their work and for
listening.
> This version of the draft is a *substantial* improvement.
> 
> Of course, I still have some issues I'd like to work through. Some of my
concerns
> are "just" language usage where the choice of words or phrasing means
> something that I don't think the authors intend. Other concerns are about
the
> details. But all in all, this is going in the right direction.
> 
> I still think there is too much text in this definitions document. I think
that is a
> natural result of having several documents in the pipe at the same time.
There
> is explanation of how things work and hang together that, in my opinion,
> should relocate to other documents - maybe the framework, maybe dedicated
> applicability statements. For example, I can see value in a document
explaining
> how IETF network slices fit into the models of "end-to-end network slices"
as
> conceived in other SDOs.
> 
> Best,
> Adrian
> 
> -----Original Message-----
> From: Teas <teas-bounces@ietf.org> On Behalf Of Kiran Makhijani
> Sent: 22 October 2020 07:12
> To: teas-ns-dt@ietf.org; TEAS WG <teas@ietf.org>
> Subject: [Teas] FW: New Version Notification for
draft-nsdt-teas-ietf-network-
> slice-definition-00.txt
> 
> Hello Teas and teas-ns-dt,
> FYI: Please find new version of  IETF network slices (previously called
transport
> slices) definition document.
> 
> This is still a work in progress document but several comments and
feedback
> received till now have been addressed. We want to share updates so far and
> look forward to further comments and discussion.
> 
> Thanks
> -Authors
> 
> -----Original Message-----
> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
> Sent: Wednesday, October 21, 2020 11:00 PM
> To: Kiran Makhijani <kiranm@futurewei.com>om>; Luis Contreras
> <luismiguel.contrerasmurillo@telefonica.com>om>; Reza Rokui
> <reza.rokui@nokia.com>om>; Shunsuke Homma
> <shunsuke.homma.ietf@gmail.com>om>; Jeff Tantsura <jefftant.ietf@gmail.com>om>;
> Luis M. Contreras <luismiguel.contrerasmurillo@telefonica.com>
> Subject: New Version Notification for
> draft-nsdt-teas-ietf-network-slice-definition-00.txt
> 
> 
> A new version of I-D, draft-nsdt-teas-ietf-network-slice-definition-00.txt
> has been successfully submitted by Kiran Makhijani and posted to the IETF
> repository.
> 
> Name:		draft-nsdt-teas-ietf-network-slice-definition
> Revision:	00
> Title:		Definition of IETF Network Slices
> Document date:	2020-10-21
> Group:		Individual Submission
> Pages:		17
> URL:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ie
> tf.o
> rg%2Farchive%2Fid%2Fdraft-nsdt-teas-ietf-network-slice-definition-
> 00.txt&amp
> ;data=04%7C01%7Ckiranm%40futurewei.com%7C80aac7efa01d43e055d208d
> 8764fa8e5%7C
> 0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637389431798734419%7
> CUnknown%7CTW
> FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC
> I6Mn0%3D
> %7C2000&amp;sdata=7wm50bc73lEQm0WsZuuDrtMBr0hhmz3dUsSHLUji5r8
> %3D&amp;reserve
> d=0
> Status:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatra
> cke
>
r.ietf.org%2Fdoc%2Fdraft-nsdt-teas-ietf-network-slice-definition%2F&amp;data
> =04%7C01%7Ckiranm%40futurewei.com%7C80aac7efa01d43e055d208d8764f
> a8e5%7C0fee8
> ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637389431798734419%7CUnk
> nown%7CTWFpbGZ
> sb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn
> 0%3D%7C20
> 00&amp;sdata=diwg0Oe8QVWtuRFoP21aAAN%2FQ046hCe%2F1DI5vNgOH08
> %3D&amp;reserved
> =0
> Htmlized:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatra
> cke
> r.ietf.org%2Fdoc%2Fhtml%2Fdraft-nsdt-teas-ietf-network-slice-
> definition&amp;
> data=04%7C01%7Ckiranm%40futurewei.com%7C80aac7efa01d43e055d208d8
> 764fa8e5%7C0
> fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637389431798734419%7C
> Unknown%7CTWF
> pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI
> 6Mn0%3D%
> 7C2000&amp;sdata=H%2BuJYcBjXiSrz1raGpMrRthMlWHAAjvdZIQuOcAp1YE%3
> D&amp;reserv
> ed=0
> Htmlized:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ie
> tf
> .org%2Fhtml%2Fdraft-nsdt-teas-ietf-network-slice-definition-
> 00&amp;data=04%7
> C01%7Ckiranm%40futurewei.com%7C80aac7efa01d43e055d208d8764fa8e5%
> 7C0fee8ff2a3
> b240189c753a1d5591fedc%7C1%7C1%7C637389431798744414%7CUnknown
> %7CTWFpbGZsb3d8
> eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
> %7C2000&am
> p;sdata=ZMr1EeR5CXXBvuPd0SndoJYxehAdgAmmaLkEz%2BkXrXE%3D&amp;re
> served=0
> 
> 
> Abstract:
>    This document provides a definition of the term "IETF Network Slice"
>    for use within the IETF and specifically as a reference for other
>    IETF documents that describe or use aspects of network slices.
> 
>    The document also describes the characteristics of an IETF network
>    slice, related terms and their meanings, and explains how IETF
>    network slices can be used in combination with end-to-end network
>    slices or independent of them.
> 
> 
> 
> 
> 
> 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.ie
> tf.org%2Fmailman%2Flistinfo%2Fteas&amp;data=04%7C01%7Ckiranm%40futu
> rewei.com%7C6dad12e7b3d147f151ce08d876669af2%7C0fee8ff2a3b240189c
> 753a1d5591fedc%7C1%7C0%7C637389530342292715%7CUnknown%7CTWFp
> bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6
> Mn0%3D%7C1000&amp;sdata=KTwJI1b62%2BemHwnZjOgc8v446%2Bgxhl8N3
> Gy4QP6BdU0%3D&amp;reserved=0