Re: [Teas] ACTN and Network Slicing in draft-ietf-teas-ietf-network-slice-framework
Adrian Farrel <adrian@olddog.co.uk> Tue, 30 March 2021 13:46 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 EBE123A12D9; Tue, 30 Mar 2021 06:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level:
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 a7Wg8FiBzoup; Tue, 30 Mar 2021 06:46:20 -0700 (PDT)
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 451903A12E3; Tue, 30 Mar 2021 06:46:19 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id 12UDkFU8001980; Tue, 30 Mar 2021 14:46:15 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 74D582203B; Tue, 30 Mar 2021 14:46:15 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs1.iomartmail.com (Postfix) with ESMTPS id 5F17D2203A; Tue, 30 Mar 2021 14:46:15 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.2.51]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id 12UDkErn024388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 Mar 2021 14:46:14 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Daniele Ceccarelli' <daniele.ceccarelli@ericsson.com>, 'TEAS WG' <teas@ietf.org>
Cc: draft-ietf-teas-ietf-network-slice-framework@ietf.org
References: <04fa01d7253f$1af28df0$50d7a9d0$@olddog.co.uk> <HE1PR0701MB22820D9C5D98B26902D74202F07D9@HE1PR0701MB2282.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR0701MB22820D9C5D98B26902D74202F07D9@HE1PR0701MB2282.eurprd07.prod.outlook.com>
Date: Tue, 30 Mar 2021 14:46:14 +0100
Organization: Old Dog Consulting
Message-ID: <056b01d7256b$0ddb8e60$2992ab20$@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: AQHxk+JpZMXxcpsxQ/Dglf185r/fywGwnuy2qlopKKA=
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.006
X-TM-AS-Result: No--10.075-10.0-31-10
X-imss-scan-details: No--10.075-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-26060.006
X-TMASE-Result: 10--10.075300-10.000000
X-TMASE-MatchedRID: IeZYkn8zfFqyoI+bK8UPQnFPUrVDm6jtkYC3rjkUXRI10hFCwEzEueXr Sue84i14+h4WVqRDM2Qwvdy2gdphoGMFwILfD7YgyZHnIMmQ+DgZskwWqoib3N7p0Ru8jKvFN/d qX4FDkxhfYW/FmKot4sGUBmnakUtgtm5R78dgvqo9IJCDcFqqFSH2Y0Xxk8nY61WlA7aRGtf0Bw RY9hFTLcdGwzlLDeSMqnNvd1wIfX3fr6cLayBKMhlJRfzNw8af52mltlE2n8gjlnxOIeMfMCOGa xJXnUqcaQZxQWzvnZZy7+t8Pc7WmEMF745Go/MHXK5keCa+bmggT/sXtGXrfy4mS5ZcbgykoD/N ZHDQhfSPwh92nT/B1Tt7KpPs5IMxutbsRFhsjTL8Jrg+3ve3W+vGseyykgyEL31P64kiV5G6o5p OE3X0ppE8Rz8q1MV0pP+IK7o0NLLSEvzdMidJ+kzQymcuf4b04+riWbWg6PtYC5LPd7BvbeLDpS m0dAoCs4Tt0Fkf8imAUjMwpAlk0qWp8HD37J/MdPuue3cRiRiiGsyrScSFB+NP0iynJ94s4r+Tn vxb7Q21PIEmDIX+G0I9gXSBGMBFGsa4wcazOZCK5Jq39CIIv+NQ6HUR7OtPjFFYmmGGytzIQMUy 4ToeqKhPDwZeB+AQ6dnwXyB+JR2cLk40H/k2fCBF12zrx7MgNroBpCbt+GbYrWoRBlQinUlmz+P /3+i2lFWKgQ18rOBlQF/V92m4h697RGeEdHm+5dgjTPgwOPQ7GNv1BBu35HNAt+hcPnO5c3wuqc +4WoxGkwm3No56haW6Ctebkgpw0iILwdNxhJKeAiCmPx4NwLTrdaH1ZWqCii7lXaIcF/Ww7M6dy uYKg/cUt5lc1lLgOMB0shqXhHrku2kjwbgZiO3nToBMdO2+X8ygcmajvrgAyxD8v8RW/PU2VOpj dSiV
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/VzUL-s2JTnygLF_JOM5QcLzxQZE>
Subject: Re: [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 13:46:25 -0000
Thanks Daniele, Yes should be [RFC8453] describes the function of... Adrian -----Original Message----- From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com> Sent: 30 March 2021 12:42 To: adrian@olddog.co.uk; 'TEAS WG' <teas@ietf.org> Cc: draft-ietf-teas-ietf-network-slice-framework@ietf.org Subject: RE: [Teas] ACTN and Network Slicing in draft-ietf-teas-ietf-network-slice-framework Hi Adrian, Your proposal makes sense to me. I still have some reserves about the traffic separation part, but the rest is fine. Just a minor issue, there is probably something missing in this sentence. " [RFC8453] the function of ACTN as collecting resources to establish a logically dedicated virtual network over one or more TE networks. " BR Daniele -----Original Message----- From: Teas <teas-bounces@ietf.org> On Behalf Of Adrian Farrel Sent: den 30 mars 2021 10:32 To: 'TEAS WG' <teas@ietf.org> Cc: draft-ietf-teas-ietf-network-slice-framework@ietf.org Subject: [Teas] ACTN and Network Slicing in draft-ietf-teas-ietf-network-slice-framework 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 mailing list Teas@ietf.org https://www.ietf.org/mailman/listinfo/teas
- [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