[Teas] Slice as a Service : Response of IETF Network slice coauthors to TEAS mailing list

Adrian Farrel <adrian@olddog.co.uk> Thu, 04 March 2021 18:19 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 C05D03A13B0 for <teas@ietfa.amsl.com>; Thu, 4 Mar 2021 10:19:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id j0SPCWBCnNOi for <teas@ietfa.amsl.com>; Thu, 4 Mar 2021 10:19:12 -0800 (PST)
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 286A73A13AC for <teas@ietf.org>; Thu, 4 Mar 2021 10:19:11 -0800 (PST)
Received: from vs1.iomartmail.com (vs1.iomartmail.com []) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id 124IJ7sj008993; Thu, 4 Mar 2021 18:19:07 GMT
Received: from vs1.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id 09C702203D; Thu, 4 Mar 2021 18:19:07 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown []) by vs1.iomartmail.com (Postfix) with ESMTPS id E85322203C; Thu, 4 Mar 2021 18:19:06 +0000 (GMT)
Received: from LAPTOPK7AS653V ([]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 124IJ55I029334 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 4 Mar 2021 18:19:06 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'TEAS WG' <teas@ietf.org>
Cc: 'Shunsuke Homma' <s.homma0718@gmail.com>, 'Jeff Tantsura' <jefftant.ietf@gmail.com>, 'Kiran Makhijani' <kiranm@futurewei.com>, "'Luis M. Contreras'" <contreras.ietf@gmail.com>
Date: Thu, 04 Mar 2021 18:19:05 -0000
Organization: Old Dog Consulting
Message-ID: <00b201d71122$dd464850$97d2d8f0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B3_01D71122.DD470BA0"
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AdcRItnRlgJjMYDXS32uGKciK4tmGQ==
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--20.493-10.0-31-10
X-imss-scan-details: No--20.493-10.0-31-10
X-TMASE-Result: 10--20.493400-10.000000
X-TMASE-MatchedRID: fuZ11Ac8DpwTEJKeyObgP3FPUrVDm6jtkYC3rjkUXRJ623gwrBldgL3n vEDn2bXpeiIJKNTp1LDCElfQbzj/Y5qEo+48iI7uJdOcBmSEp+UZskwWqoib3Ag2kgWdt3qaJxu QLWshpjrdvO9TrNr2cG4FPqjeI4cukw5bBmnlN5jghYcEpSUypmTcElmE8+OMHk+0rK2TDq6Jzv yP4u0tgOBAYff9fVPjV4Hy8jOGoWT3uvD+1Bkl7TQ60lWQoG0rKVrLOZD1BXSsaBVGMabQl+//v bMLiEkV0+0G7io/4HWtQ57zuXEmXBWVVkGuW6Jr3zSg/bkXzGld5/m3qrxFzEqa6TyhyXvPk/W3 dqvyXNMLwTxkKC1upZfrKASrZ1Stu4AM1i3aFvZHKdPCX1liHlTizEWrqKARCgNjqBgJU5M/Sly sU74QwzmCoROg0mm31vAWquN+Nu7NhpzQcEKpPRz2MDiYujy5qa+0bGZ+s5mRmBpkPchPVfFBLq yzMQ6aziCmu04/U+jQACPgtyOvxRRR9/GzeUaYi+m1DDPm2yJ9itonZum4Xpd9j+WYn72G1BoO0 FXL0siPJcLvI+dniBQAXi4Ga9GRHxPMjOKY7A+DGx/OQ1GV8gM5kYUazKEVsOzOncrmCoN8ihDm ybMVFkzgPxyJ5sPoOtGfDh16yoPPj0glKRhCFb+MEbJz+dTR
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/j3ocuoD8J7bD-D7cXxI-6ZQ8uRo>
Subject: [Teas] Slice as a Service : Response of IETF Network slice coauthors to TEAS mailing list
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: Thu, 04 Mar 2021 18:19:15 -0000

Thanks to the pen-holders for trying to progress this discussion.


I wonder whether we should separate the discussions into separate threads? As we discuss the different points it’ll get messy unless we do that.


I’ve changed the subject line for the issue I want to call out.


> IETF network slice as a Service

> The co-authors agree with the mailing list suggestion to treat the IETF network 

> slice as  a service. 

> In summary, an IETF Network Slice Service contains multiple endpoints (see

> discussion below for endpoint), multiple connections and multiple SLOs. 

> This is aligned with the mailing list. In consequence we propose to add

> “Service” to the text  in the draft defining what an IETF network slice is.


I don’t think this is an either/or. I think we have “a slice as perceived by the consumer/customer” and “a slice as operated by the operator of the underlay network”. This is very similar to how VPNs are discussed.


So, yes, lets have a description of a “network slice service”. But I think we have to start with a general description of a “network slice”. The former is how the consumer/customer perceives the slice. The latter is what is really going on: the resources and capabilities of the operator’s network are being selectively partitioned to provide the service.