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

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

Return-Path: <adrian@olddog.co.uk>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 70B843A0BDC; Wed, 28 Oct 2020 12:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id jjHkQTefzrib; Wed, 28 Oct 2020 12:24:43 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com []) (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 33E013A0BDB; Wed, 28 Oct 2020 12:24:42 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com []) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id 09SJObja006065; Wed, 28 Oct 2020 19:24:37 GMT
Received: from vs3.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id E47432203D; Wed, 28 Oct 2020 19:24:36 +0000 (GMT)
Received: from asmtp3.iomartmail.com (unknown []) by vs3.iomartmail.com (Postfix) with ESMTPS id CE0792203A; Wed, 28 Oct 2020 19:24:36 +0000 (GMT)
Received: from LAPTOPK7AS653V (81-174-211-216.pth-as4.dial.plus.net []) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 09SJOZl6027097 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 28 Oct 2020 19:24:36 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Joel M. Halpern'" <jmh@joelhalpern.com>, "'Kiran Makhijani'" <kiranm@futurewei.com>, <teas-ns-dt@ietf.org>, "'TEAS WG'" <teas@ietf.org>
Date: Wed, 28 Oct 2020 19:24:35 -0000
Organization: Old Dog Consulting
Message-ID: <065401d6ad5f$f90856e0$eb1904a0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0655_01D6AD5F.F90A2BA0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdatX1BLaMZCVkrFTCyXOjAUHkxR0w==
Content-Language: en-gb
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--26.333-10.0-31-10
X-imss-scan-details: No--26.333-10.0-31-10
X-TMASE-Result: 10--26.332500-10.000000
X-TMASE-MatchedRID: 0uBW4KZo6nbovmVP2LXWkXFPUrVDm6jttwAS5aedRei2TkeS9tjW4yMn HClP1IKbfmDk9kX3dCiURMo5LLQQ1J9vFrcDXJOnJrUxoq6hvw+/OTsD3tyjecv2Plvg6rT9Xbw +gpsOp4orJlO7hPPvNpFwU58M6hoSaBevM/eurMckO5bN+/P8x/EAlAseOuhvLraGNlLRahh2PD tE/uRnJPwkG7zUirW/4Tp1OMnl6hU6OXeDanhdcFyuZHgmvm5ofYrr1p9yfCp5t7W19HpOSLBjZ rYHdK0C129HBY8eHi8TXOtSVUj2Nv85GCR7+Gth9m9PbNihg7AL8TGleseLPEhcmj54ab4UJ+9k zW+GmbQb44BbUzEQ3AI5mAfN2gbbQSNhggaMa/colijkrg/WpMgRBOWHX9AxrSZr8U2Z6jy6PD0 Fdea44EW8B0Xg/2eSLm2LgrpTgTBEuBaftj2asFn1SWwc/kqZib37+ozdvcEKfrbmG+DbUNNZnq bwOWHjGIr2zyxIm4wOHK0R2yV1TtseFraHPsIf4h8r8l3l4eaPSNdj1JMyAcu+4EUKZ3vmkR56H /GDiv3Yu/vxGDNvca0Pj/9cOH4s3jdcci4U9LIk/b03uBR3UC58R61qYYYEH5kZy/EQbgR/EHDF oghOjws59GYHXmGqsOhGbFb19LCEOKkbzZMhHKbib7rubANvLMFGpdF2SNOHOZaHHVPl19PUmLp wpHLWjZP/00Gx0AXDbMN66h+B+EPcdQi3PsbaTl/FCEyiTx4gT/sXtGXrf55GLlvTiXrYV6GJyR PLfOLgcqptiV+0A5Cf9h/jcnLx4ouBraSr19+eAiCmPx4NwGmRqNBHmBve1B0Hk1Q1KyJGNS8BP La+j6ebHCxzBV4TKzfM9B6IRt7+efAnnZBiL0OAfBu/XeE8Hw1FadiMrDxhfyxQKdeNx0n/no8+ E1Kp6BnaXf9+/82sSv8nosi0bjOqzMbcA4rp14bz/zlZxqYrw5W8m2rXhM5NGJhSMTA/
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/6KL0ajoPYsMBYUVsy3pdlD12hU8>
Subject: [Teas] Isolation : 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 19:24:48 -0000

Hi Joel,


I wish we were not waiting to hear from the isolation trio on their proposal.


Nevertheless, I think it is worth looking at the text in Kiran's latest version. It goes, I think, some way to addressing your legitimate concerns about the concept of isolation.


*	Firstly, it observes that isolation is mainly the property of not being negatively impacted by other slices/services.


*	The it notes that the demand for isolation may be met by conformance to other SLOs.


*	And finally it separates isolation as an SLO from isolation as a realisation technique. 


While this continues to include the term ‘isolation’, it looks to me like a reasonable foundation for showing what is meant.


It’s tough for Kiran as she is trying to negotiate a line between those who want to discuss isolation and want it to be an integral part of slicing and those who want isolation to be totally left out of the draft.




-----Original Message-----

From: Joel M. Halpern <jmh@joelhalpern.com> 

Sent: 28 October 2020 17:16

To: adrian@olddog.co.uk; '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


Hmmm.  I had understood something slightly different.   I may well have 


I thought we would adopt as a WG document a document with place-holders 

for things like isolation.  Then folks could see if they could come up 

with something to fill those holes that the WG would accept during teh 

WG work on the document.  If we reached the end, and could not fill 

those gaps, then we would see if we could agree to remove the 

placeholder sections.





On 10/28/2020 12:20 PM, Adrian Farrel wrote:

> 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


>> %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


> _______________________________________________

> Teas mailing list

> Teas@ietf.org

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