Re: [Teas] I-D Action: draft-ietf-teas-applicability-actn-slicing-01.txt

Adrian Farrel <adrian@olddog.co.uk> Mon, 07 March 2022 16:59 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 339E73A0D32 for <teas@ietfa.amsl.com>; Mon, 7 Mar 2022 08:59:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 YLdbmpXvOxG0 for <teas@ietfa.amsl.com>; Mon, 7 Mar 2022 08:59:34 -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 1036F3A131E for <teas@ietf.org>; Mon, 7 Mar 2022 08:58:14 -0800 (PST)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta7.iomartmail.com (8.14.7/8.14.7) with ESMTP id 227GwCrJ023403 for <teas@ietf.org>; Mon, 7 Mar 2022 16:58:12 GMT
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E4CF346054 for <teas@ietf.org>; Mon, 7 Mar 2022 16:58:11 +0000 (GMT)
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D8F4546053 for <teas@ietf.org>; Mon, 7 Mar 2022 16:58:11 +0000 (GMT)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs3.iomartmail.com (Postfix) with ESMTPS for <teas@ietf.org>; Mon, 7 Mar 2022 16:58:11 +0000 (GMT)
Received: from LAPTOPK7AS653V ([85.255.233.217]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.7/8.14.7) with ESMTP id 227GwAfc022798 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <teas@ietf.org>; Mon, 7 Mar 2022 16:58:11 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: teas@ietf.org
References: <164667219948.9086.12184430507361762124@ietfa.amsl.com>
In-Reply-To: <164667219948.9086.12184430507361762124@ietfa.amsl.com>
Date: Mon, 07 Mar 2022 16:58:10 -0000
Organization: Old Dog Consulting
Message-ID: <0fa501d83244$87428c40$95c7a4c0$@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: AQK1MT7bqtxZ6xsJ9VH8cL5r61hFqar6Jl2Q
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-26758.001
X-TM-AS-Result: No--13.749-10.0-31-10
X-imss-scan-details: No--13.749-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-8.6.1018-26758.001
X-TMASE-Result: 10--13.749400-10.000000
X-TMASE-MatchedRID: +f/wAVSGjujxIbpQ8BhdbPSG/+sPtZVkdTrzIN6WRwUvfU/riSJXkRwJ bAB37U2pgvRaVUNx1oCSai5O5NiSHoKsC92uhkQmLTHwnYOikQ0cQnDpQ6FX09bGibvVQEMt9K7 5ct/rW8fARsULoJDWyfGfQT0sa5Npuz5caCZL4kiTeuX4xo2DEAT2OEnoCt48oT/LvysjYBhn8j u/LKsy9zbVmGZnPGAkGQ/eZgvPgFBav8PkKeeaZN5x7RpGJf1aC//1TMV5chNLpCLN4NR43nY+o FbrqO/Jh0gbW6ru4xqfY/iJKUhOHB3KilrpmSwSngIgpj8eDcC063Wh9WVqgqbyPFGTn+O4OeLY FhdUjW50HSe131POnuJGF26G8SWypfzLa08EuFBrwX/p4wSBUbXu4SWpX1f7ic8QzDHhYaVITlY AlC7fcEVnp6v5hHbR
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/vJmWYq_2fT-B624a0eHdyzsoj9E>
Subject: Re: [Teas] I-D Action: draft-ietf-teas-applicability-actn-slicing-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: Mon, 07 Mar 2022 16:59:39 -0000

Hi all,

The update here is to tidy the terminology and references as the core
slicing work has progressed.

Cheers,
Adrian

-----Original Message-----
From: Teas <teas-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: 07 March 2022 16:57
To: i-d-announce@ietf.org
Cc: teas@ietf.org
Subject: [Teas] I-D Action:
draft-ietf-teas-applicability-actn-slicing-01.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           : Applicability of Abstraction and Control of
Traffic Engineered Networks (ACTN) to Network Slicing
        Authors         : Daniel King
                          John Drake
                          Haomian Zheng
                          Adrian Farrel
	Filename        : draft-ietf-teas-applicability-actn-slicing-01.txt
	Pages           : 23
	Date            : 2022-03-07

Abstract:
   Network abstraction is a technique that can be applied to a network
   domain to obtain a view of potential connectivity across the network
   by utilizing a set of policies to select network resources.

   Network slicing is an approach to network operations that builds on
   the concept of network abstraction to provide programmability,
   flexibility, and modularity.  It may use techniques such as Software
   Defined Networking (SDN) and Network Function Virtualization (NFV) to
   create multiple logical or virtual networks, each tailored for a set
   of services that share the same set of requirements.

   Abstraction and Control of Traffic Engineered Networks (ACTN) is
   described in RFC 8453.  It defines an SDN-based architecture that
   relies on the concept of network and service abstraction to detach
   network and service control from the underlying data plane.

   This document outlines the applicability of ACTN to network slicing
   in a Traffic Engineering (TE) network that utilizes IETF technology.
   It also identifies the features of network slicing not currently
   within the scope of ACTN, and indicates where ACTN might be extended.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-teas-applicability-actn-slicing/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-teas-applicability-actn-slicing-0
1.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-applicability-actn-slicing
-01


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