[Teas] New Slicing revision: I-D Action: draft-ietf-teas-ietf-network-slices-01.txt

Adrian Farrel <adrian@olddog.co.uk> Fri, 16 April 2021 10:39 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 997683A205C for <teas@ietfa.amsl.com>; Fri, 16 Apr 2021 03:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.782
X-Spam-Status: No, score=0.782 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAY_BE_FORGED=2.699, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id F5hGcPTB2_Hf for <teas@ietfa.amsl.com>; Fri, 16 Apr 2021 03:39:34 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.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 4B8C63A205B for <teas@ietf.org>; Fri, 16 Apr 2021 03:39:34 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com []) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id 13GAdRwR028750; Fri, 16 Apr 2021 11:39:27 +0100
Received: from vs3.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id CC6502203D; Fri, 16 Apr 2021 11:39:26 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown []) by vs3.iomartmail.com (Postfix) with ESMTPS id B75DE2203A; Fri, 16 Apr 2021 11:39:26 +0100 (BST)
Received: from LAPTOPK7AS653V (74.197.bbplus.pte-ag1.dyn.plus.net [] (may be forged)) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id 13GAdPoX018998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 16 Apr 2021 11:39:26 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <teas@ietf.org>
Cc: <adrian@olddog.co.uk>
Date: Fri, 16 Apr 2021 11:39:26 +0100
Organization: Old Dog Consulting
Message-ID: <001001d732ac$c61a6020$524f2060$@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: AdcyrMGYgkzgz1b8SvWxYh0b6ILPeQ==
Content-Language: en-gb
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--18.476-10.0-31-10
X-imss-scan-details: No--18.476-10.0-31-10
X-TMASE-Result: 10--18.476300-10.000000
X-TMASE-MatchedRID: 2IBMc5ux2bPovmVP2LXWkXFPUrVDm6jtiRPU6vvejXIiXE6jAom+xdAy F09xseMF4EBh9/19U+P2RwMbpf7fkh+zr4ZrJWTdWWHths31oxtZbM2hfH4YXkCVoJv7NVAfB9E fC4OZGMz4DaEjUREg7QBzTalPgdQv9EH0bSIeT7nece0aRiX9Whik1Pp+6bs1AkSnL4YTrqFe9t X9WdS/Su2ZvS5nsJCPaMV6Fi9hlY+31FyZGcEodaNT4eJsLoMr6grWy6/Bur5rvf5eVgMu7Oy1U Uv/teRoiny2mY9r3u0sYi0ZdAdpzt+nkmoyBAmZmOFnGEL0JONuTKBinxl/uoVquVYFwXAm6HbD 2UCOudSG6dqEhHWyS8jVo0MIoldQRPK4qobd9zsZSUX8zcPGny3ExqBs33885DJ1FS+XdBNhu4k wNv/c0bg2zPRNbetc7g6B4WJLTOXuNO1zKrjbZkI4eS9mV4/ssdlGINmgngU8cwBuO6HB30qdVW Wu3Vopm+UTNeyODYnwZfFVvDo3PNJCetfwBKiFjrVn4cme+w5R3sGN+j7mNAJaHYtz8RhJCDKLx u18IKoCvMPZ/yI7M7RYyCSqCpPEOzeHE5CffKtO8qlnOXFSz2sb8DMbj1PYmb0bRea41a82KJc0 6SjQW5qvf1vJTZ68ZN6H4UE7wzFTattrga832NMrcx6d6fiW9wXxnluKnXuSt8TaoHcbIj+wkmu 9F8TU+h3BHlgemEkCABdcsis79cqHIZzMU5PjIAjxomarSPBdSt9kxxIQnmjliw+xvItdblsbMX lEtupFFrjTpX9jDMtpj/RkI+vmfDDFL+oKuV6eAiCmPx4NwLTrdaH1ZWqCpvI8UZOf47hcRgd0H R6VpXQdJ7XfU86e4kYXbobxJbLnIzRzWS2P0w==
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/S406Qkl_c5ZtjlIRZkfh33_Ci84>
Subject: [Teas] New Slicing revision: I-D Action: draft-ietf-teas-ietf-network-slices-01.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: Fri, 16 Apr 2021 10:39:39 -0000


In this revision, I have tidied the text. That involved:
- Fixing inconsistent editorial standards between the source documents
- Some more minor editorials
- Moving a couple of sections around
- Collapsing a little duplication arising from pulling text from two places
- Removing cross-references between the source documents
- Removing the tagging of the source material

In doing so, there were two small paragraphs that didn't seem to belong.
These can be seen in the Appendix.

ACTION: All: Please shout if you believe this text should not be deleted.

While this document is now in a condition that can be reviewed and commented
on, I propose to make some suggestions to reduce and consolidate the text. I
will bring these to the list as separate threads (some have already been
seen on the list, but we should make the proposed changes clear). They will

- Discussion of realisation.
  This should be a discussion of architectural realisation, not of
underlying technologies.
  Currently we have:
   - a large section on ACTN
   - a couple of references to VPN+
   - no mention of the architecture underlying
  I already suggested (on list) a way to reduce the ACTN text, but it has
since been
  proposed to me that all discussion of realisation of the architecture can
be best
  achieved with brief paragraphs and references. I will propose text.

- Isolation and "unmeasurable SLOs"
  This has long been a contentious topic. I think we had reached a bit of a
  in the definitions draft, but doing the merge has caused me to re-read it
and I am
  uneasy. I will be making a text suggestion to clarify the purpose and
meaning of the
  section on isolation, and that will depend on us also clarifying the
description of
  "directly measurable SLOs" and "indirectly measurable SLOs. 

- Revisiting the definition of a network slice
  This is obviously pretty core to our work! John Drake previously sent a
suggestion to
  the list (2021-04-03). This caused a bit of discussion and raises a number
of points.
  I plan to try to tease out the various points to see whether we can agree
  Separately and then come up with new definitions text. This may be a good
  For our first telechat on the document.
ACTION: Chairs: Decide what the rules are for having telechat meetings for
this document.


-----Original Message-----
From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of
Sent: 16 April 2021 11:19
To: i-d-announce@ietf.org
Cc: teas@ietf.org
Subject: I-D Action: draft-ietf-teas-ietf-network-slices-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts
This draft is a work item of the Traffic Engineering Architecture and
Signaling WG of the IETF.

        Title           : Framework for IETF Network Slices
        Authors         : Adrian Farrel
                          Eric Gray
                          John Drake
                          Reza Rokui
                          Shunsuke Homma
                          Kiran Makhijani
                          Luis M. Contreras
                          Jeff Tantsura
	Filename        : draft-ietf-teas-ietf-network-slices-01.txt
	Pages           : 33
	Date            : 2021-04-16

   This document describes network slicing in the context of networks
   built from IETF technologies.  It defines the term "IETF Network
   Slice" and establishes the general principles of network slicing in
   the IETF context.

   The document discusses the general framework for requesting and
   operating IETF Network Slices, the characteristics of an IETF Network
   Slice, the necessary system components and interfaces, and how
   abstract requests can be mapped to more specific technologies.  The
   document also discusses related considerations with monitoring and

   This document also provides definitions of related terms to enable
   consistent usage in other IETF documents that describe or use aspects
   of IETF Network Slices.

The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at:

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.

Internet-Drafts are also available by anonymous FTP at:

I-D-Announce mailing list
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt