[Teas] First version merged slicing draft [Was: I-D Action: draft-ietf-teas-ietf-network-slices-00.txt]

Adrian Farrel <adrian@olddog.co.uk> Thu, 15 April 2021 09:44 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 D071D3A188E for <teas@ietfa.amsl.com>; Thu, 15 Apr 2021 02:44:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.783
X-Spam-Status: No, score=0.783 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAY_BE_FORGED=2.699, RCVD_IN_DNSWL_BLOCKED=0.001, 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 jZ0n5tbMD52H for <teas@ietfa.amsl.com>; Thu, 15 Apr 2021 02:44:25 -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 459993A188C for <teas@ietf.org>; Thu, 15 Apr 2021 02:44:25 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com []) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id 13F9iMYH016513 for <teas@ietf.org>; Thu, 15 Apr 2021 10:44:22 +0100
Received: from vs2.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id 47C1A22044 for <teas@ietf.org>; Thu, 15 Apr 2021 10:44:21 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown []) by vs2.iomartmail.com (Postfix) with ESMTPS id 32A2722042 for <teas@ietf.org>; Thu, 15 Apr 2021 10:44:21 +0100 (BST)
Received: from LAPTOPK7AS653V (74.197.bbplus.pte-ag1.dyn.plus.net [] (may be forged)) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 13F9iJck003287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <teas@ietf.org>; Thu, 15 Apr 2021 10:44:20 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <teas@ietf.org>
Date: Thu, 15 Apr 2021 10:44:18 +0100
Organization: Old Dog Consulting
Message-ID: <001d01d731db$e8c59260$ba50b720$@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: Adcx2+YqQW1Ic7+nSVmiQeFzyZv2kw==
Content-Language: en-gb
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--19.809-10.0-31-10
X-imss-scan-details: No--19.809-10.0-31-10
X-TMASE-Result: 10--19.808700-10.000000
X-TMASE-MatchedRID: bg+cX/QuSVbovmVP2LXWkXFPUrVDm6jtiRPU6vvejXJYjwH7MZdcVHch tJI6MELjT/dBt9e2zw/2RwMbpf7fkg4AByEthGnRcTwOmq5GKdChp756/rM6Ugp+tuYb4NtQN8Z 7BplvPfTZM1UPpfeKYQUqLEtQk2boaWPqw6Sbal4m2C2fR2e+B1HewY36PuY0R64C5ZrYJjRuni JOkZD09CYxz8zvRVbyr5KMpzU/ScQIasXPlctLdC0x8J2DopENCRjsEqumlCkruUVdHizCWX+YL BuR+SHBlC0f6BOUR6+y80F6YLj3JXt7SyPco45M48SQ1JLtjzYWUg/hm489yFcn81OBopCmq7wH q+Q+2VUoYBK68Mm4PYRbKc8p/pvE3Eg/7BaS8ZH4FqzGb25nh8/rSr8VfmGwy5JfHvVu9It12pJ YHv90h80RRdX/v/XP+/pwMY/89aO1Z0c2mubs9m5eAiqrqZDKx3x+XnIcCMRYbPLopoBzQiBhQ6 yz+UaYLgJkCc+p3AmUyDB0GLlwbb9jX++auvv+FcK/QGNGRL06En2bnefhoOytS7m1HlRoSiDeF P1/+gLbgfxR9ePGrJAQMOcfVw6qrpj4RCOlBrjH9K2ZqHQWln0tCKdnhB58vqq8s2MNhPDPPeN6 HN6d7M3o0JwlpIFPC24oEZ6SpSkgbhiVsIMQKxZ5+8y352uC
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/BSNkGqsCkRZDZEj57H-_l7UaT0M>
Subject: [Teas] First version merged slicing draft [Was: I-D Action: draft-ietf-teas-ietf-network-slices-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: Thu, 15 Apr 2021 09:44:28 -0000


According to the Pledge...

Here is the -00 that just pulls in all of the text from the two contributing

My next step is to rationalise this a bit to avoid duplication and make sure
the sections are in the right order.

Comments are, of course, welcome, but maybe focus on just the editorial work
rather than the technical content (there'll be plenty of time for that

Hoping to have the -01 within a week.


-----Original Message-----
From: Teas <teas-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: 15 April 2021 01:29
To: i-d-announce@ietf.org
Cc: teas@ietf.org
Subject: [Teas] I-D Action: draft-ietf-teas-ietf-network-slices-00.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-00.txt
	Pages           : 35
	Date            : 2021-04-14


   This memo discusses setting up special-purpose network connections
   using existing IETF technologies.  These connections are called IETF
   network slices for the purposes of this memo.  The memo discusses the
   general framework for this setup, the necessary system components and
   interfaces, and how abstract requests can be mapped to more specific
   technologies.  The memo also discusses related considerations with
   monitoring and security.

   This memo is intended for discussing interfaces and technologies.  It
   is not intended to be a new set of concrete interfaces or
   technologies.  Rather, it should be seen as an explanation of how
   some existing, concrete IETF VPN and traffic-engineering technologies
   can be used to create IETF network slices.  Note that there are a
   number of these technologies, and new technologies or capabilities
   keep being added.  This memo is also not intended presume any
   particular technology choice.


   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.

The IETF datatracker status page for this draft is:

There are also htmlized versions 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:

Teas mailing list