[Teas] What's in draft-ietf-teas-ietf-network-slices-08.txt

Adrian Farrel <adrian@olddog.co.uk> Sun, 06 March 2022 22:02 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 587F33A0D3F for <teas@ietfa.amsl.com>; Sun, 6 Mar 2022 14:02:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 GHBrVzK1XlDa for <teas@ietfa.amsl.com>; Sun, 6 Mar 2022 14:02:23 -0800 (PST)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (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 EFE103A0C7F for <teas@ietf.org>; Sun, 6 Mar 2022 14:02:22 -0800 (PST)
Received: from vs4.iomartmail.com (vs4.iomartmail.com [10.12.10.122]) by mta7.iomartmail.com (8.14.7/8.14.7) with ESMTP id 226M2Jh0013375 for <teas@ietf.org>; Sun, 6 Mar 2022 22:02:19 GMT
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 84A724604A for <teas@ietf.org>; Sun, 6 Mar 2022 22:02:19 +0000 (GMT)
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 784D146043 for <teas@ietf.org>; Sun, 6 Mar 2022 22:02:19 +0000 (GMT)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs4.iomartmail.com (Postfix) with ESMTPS for <teas@ietf.org>; Sun, 6 Mar 2022 22:02:19 +0000 (GMT)
Received: from LAPTOPK7AS653V ([85.255.233.217]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.7/8.14.7) with ESMTP id 226M2IEQ012519 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <teas@ietf.org>; Sun, 6 Mar 2022 22:02:18 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: teas@ietf.org
Date: Sun, 06 Mar 2022 22:02:17 -0000
Organization: Old Dog Consulting
Message-ID: <0e3b01d831a5$d9127520$8b375f60$@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: AdgxpdRaJZVBrLBpSie8djmEaBqVsA==
Content-Language: en-gb
X-Originating-IP: 85.255.233.217
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-8.6.0.1018-26756.003
X-TM-AS-Result: No--26.903-10.0-31-10
X-imss-scan-details: No--26.903-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-8.6.1018-26756.003
X-TMASE-Result: 10--26.903400-10.000000
X-TMASE-MatchedRID: cPu9AiD5JXwZnuop9luYIN5x7RpGJf1a2qPQi8vc9bKpFMAdzAAQJ0Ij Ip4EpSqCApknKNqCQYMmJ3J3qUIlPiSBigu/eRn2fb/LeMmmtRB2ZYwNBqM6IvmrkkH6JvZBMX6 RlGNkucKr1jKm0SUrl09t13CqwBy8XtsGnSgA6qpOKksNozKUfZc2qBokXYfiMGqHura0AtG95i YVgizGV9A0cse87b4T4mvIgB4Ef0f51WNA1rE6t2MugLQMu2GXRealVAhocE+/K9mCmWrmBlaGr AOmqLgexnkmNVxPuc4igRw+EUgtq0C8jypqzPK2ovaPAM40SOHQ2dRRUyVMphJocwn93gES81oS Kb4F9XBFFrjTpX9jDPxumwmMXNEFBXY0oXpqJ16DpW5ZeDjLZCJIyemE7blFmtpNozJnXaujxYy RBa/qJX3mXSdV7KK4kVrCU883ln5TptoDfp6JrMRB0bsfrpPIqxB32o9eGclVaBFytIQUtw==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/CB0FXS-NNvjJYYtjQxMUt_s2SfM>
Subject: [Teas] What's in draft-ietf-teas-ietf-network-slices-08.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: Sun, 06 Mar 2022 22:02:28 -0000

There is nothing quite like reviewing your own work to make you feel old and
tired.

This revision includes:
- comments from John Mulloley
- updates are careful reviews by me and John Drake

The only think left in my buffer is "It might be nice to include some worked
examples." I have a sketch of one from Med, and a few thoughts of what I
could include, but do we really need them? I'd welcome your thoughts, but
you might get asked to provide text!

Otherwise, I think the time between now and IETF-113 should be open season
for review comments. We can discuss anything big at the IETF meeting and
then (possibly) be ready for WG last call shortly after.

Best,
Adrian

-----Original Message-----
From: Teas <teas-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: 06 March 2022 21:57
To: i-d-announce@ietf.org
Cc: teas@ietf.org
Subject: [Teas] I-D Action: draft-ietf-teas-ietf-network-slices-08.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
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
                          John Drake
                          Reza Rokui
                          Shunsuke Homma
                          Kiran Makhijani
                          Luis M. Contreras
                          Jeff Tantsura
	Filename        : draft-ietf-teas-ietf-network-slices-08.txt
	Pages           : 42
	Date            : 2022-03-06

Abstract:
   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
   security.

   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:
https://datatracker.ietf.org/doc/draft-ietf-teas-ietf-network-slices/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-teas-ietf-network-slices-08.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-ietf-network-slices-08


Internet-Drafts are also available by rsync at
rsync.ietf.org::internet-drafts


_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas