[Teas] ACTN and Network Slicing in draft-ietf-teas-ietf-network-slice-framework
Adrian Farrel <adrian@olddog.co.uk> Tue, 30 March 2021 08:31 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 344D13A2B5C; Tue, 30 Mar 2021 01:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 2gtCwDdOVWXy; Tue, 30 Mar 2021 01:31:46 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 69ED63A2B5A; Tue, 30 Mar 2021 01:31:43 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id 12U8VeTY016781; Tue, 30 Mar 2021 09:31:40 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7A7162203C; Tue, 30 Mar 2021 09:31:40 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS id 6E73D22046; Tue, 30 Mar 2021 09:31:40 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.2.51]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 12U8Vdgp019418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 Mar 2021 09:31:39 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'TEAS WG' <teas@ietf.org>
Cc: draft-ietf-teas-ietf-network-slice-framework@ietf.org
Date: Tue, 30 Mar 2021 09:31:38 +0100
Organization: Old Dog Consulting
Message-ID: <04fa01d7253f$1af28df0$50d7a9d0$@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: AdclPwWWWhB+9iLTQEq+EpqCtBr+8g==
Content-Language: en-gb
X-Originating-IP: 84.93.2.51
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-26060.005
X-TM-AS-Result: No--7.535-10.0-31-10
X-imss-scan-details: No--7.535-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-26060.005
X-TMASE-Result: 10--7.535500-10.000000
X-TMASE-MatchedRID: kzO89qS42oQaf3p8Lo2lek7yqWc5cVLPpQH4ogtVQP2/md2adk3dRAVF HBHRPrhRS1ayce3yAb4aDx93YrA9C9Uv8ntSEF320XO+Yq6CqgLQVuQgEsWn40Yx760ONDcWM6q QCN8Kquhyavmt8uJW+1zXN1J+me5iRckgR61xVAVpTt57XuqMc/6lpfpte41hzVgwP7ZMYf8KkJ 5fehPoYjYFj1KaPQqMFdgszMOvFpxoWWTS0CIqzv7FEhWgo0y83WFaxVW7M2gjwEWouQA/dYKs6 GJNW8H74LBi6mXnX/tBOjlJ4hTRXF8hjBIn4Ez5TNDKZy5/hvTj6uJZtaDo+1gLks93sG9t4sOl KbR0CgKzhO3QWR/yKYBSMzCkCWTSpanwcPfsn8x0+657dxGJGKIazKtJxIUH40/SLKcn3iziv5O e/FvtDbU8gSYMhf4be2GhLuKy7LQuf8XRo3MpR4t6hZFSx91AE3EgF0+MVuB74JkRCQAITsZLv3 M/59RrUJFtPQDCCPNTTr/+57pMiJ/b/B6A2dBRJmbrB1j4XwqXOVo0UPe9FDT4nNGHFYDrZx+wU PaQDwhHnnKDRBT66Y5FOnAjuzgNnvT6Mk7oJaznjuQQVkVPTfmoZ6x4ZgCU1+OTFqKF59kjqjdF usfoJFc7bdeKsnaLsqOsurV2gaHlRxm3A2wKujl/1fD/GopdyJ1gFgOMhOmLZAVphLW/bSq2rl3 dzGQ1CUAac96l2NnVuxRzSegwtM9oShDT3MPbfDsWZru0I+GErmmViRoGLcC+ksT6a9fy
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/yY6y2qP34gmiTXdoARFVBf4aNiU>
Subject: [Teas] ACTN and Network Slicing in draft-ietf-teas-ietf-network-slice-framework
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: Tue, 30 Mar 2021 08:31:49 -0000
Hi authors of draft-ietf-teas-ietf-network-slice-framework and TEAS WG, I've been looking at the ACTN section in this draft. I think it is good that this draft makes it clear that ACTN is an applicable technology for creating and managing network slices: ACTN is core TEAS mechanism and we should make it available for re-use where possible. However, I think that applying ACTN to network slicing needs more text than it is appropriate to place in this document. You currently have 2 pages out of about 11 pages of text. While I expect the total will grow as more material is added across the document, I also think that adding more substance to the ACTN section would put it completely out of balance. My suggestion is that we: - revise down the ACTN text in this document - make a reference to a separate document to describe the applicability of ACTN I would (obviously?) suggest draft-king-teas-applicability-actn-slicing as the document to be referenced although it will need some work to bring it into line with the terminology work that has been done in TEAS. My suggested edits to this document are: 3.2 OLD Layered virtual connections are comprehensively discussed in IETF documents and are widely supported. See, for instance, GMPLS-based networks ([RFC5212] and [RFC4397]), or ACTN ([RFC8453] and [RFC8454]). The principles and mechanisms associated with layered networking are applicable to IETF network slices. NEW Layered virtual connections are comprehensively discussed in IETF documents and are widely supported. See, for instance, GMPLS-based networks [RFC5212] and [RFC4397], or Abstraction and Control of TE Networks (ACTN) [RFC8453] and [RFC8454]. The principles and mechanisms associated with layered networking are applicable to IETF network slices. END --- 3.5 OLD Also, as outlined in "applicability of ACTN to IETF Network Slices" below, ACTN ([RFC8453]) offers a framework that is used elsewhere in IETF specifications to create virtual network (VN) services similar to IETF network slices. NEW Also, as described in Section 4, below, ACTN offers a framework that is used elsewhere in IETF specifications to create virtual network (VN) services similar to IETF network slices. END --- 4. COMPLETE REPLACEMENT 4. Applicability of ACTN to IETF Network Slices Abstraction and Control of TE Networks (ACTN - [RFC8453]) is a management architecture and toolkit used to create virtual networks (VNs) on top of a traffic engineering (TE) underlay network. The VNs can be presented to customers for them to operate as private networks. In many ways, the function of ACTN is similar to IETF network slicing. Customer requests for connectivity-based overlay services are mapped to dedicated or shared resources in the underlay network in a way that meets customer guarantees for service level objectives and for separation from other customers' traffic. [RFC8453] the function of ACTN as collecting resources to establish a logically dedicated virtual network over one or more TE networks. Thus, in the case of a TE-enabled underlying network, the ACTN VN can be used as a basis to realize an IETF network slicing. While the ACTN framework is a generic VN framework that can be used for VN services beyond the IETF network slice, it also a suitable basis for delivering and realizing IETF network slices. Figure 1 illustrates the mapping between IETF network slice management and interfaces, and the ACTN management components and interfaces. For reference, the ACTN abbreviations are as follows: CNC : Customer Network Controller MDSC : Multi-Domain Service Coordinator PNC : Provisioning Network Controller CMI : CNC-MDSC Interface MPI : MDSC-PNC Interface IETF Network Slice | ACTN analogous Terminology / Concepts Terminology | and Concepts +--------------------------------------+ |Consumer higher level operation system| | +-----+ | (e.g E2E network slice orchestrator) | =====> | CNC | +--------------------------------------+ | +-----+ ^ ^ | NSC NBI | | CMI v v +-------------------------------------+ | +------+ | IETF Network Slice Controller (NSC) | =====> | MDSC | +-------------------------------------+ | +------+ ^ ^ | NSC SBI | | MPI v v +-------------------------------------+ | +-----+ | Network Controller(s) | =====> | PNC | +-------------------------------------+ | +-----+ Figure 1 : Mapping Between IETF Network Slice and ACTN Components Note that the details of all function below the NSC SBI are out of scope of this document. Further discussion of the applicability of ACTN to IETF network slices including a discussion of the relevant YANG models can be found in [I-D.king-teas-applicability-actn-slicing]. --- Hope this helps. Best, Adrian
- [Teas] ACTN and Network Slicing in draft-ietf-tea… Adrian Farrel
- Re: [Teas] ACTN and Network Slicing in draft-ietf… Daniele Ceccarelli
- Re: [Teas] ACTN and Network Slicing in draft-ietf… Adrian Farrel
- Re: [Teas] ACTN and Network Slicing in draft-ietf… John E Drake