[Teas] FW: New Version Notification for draft-king-teas-applicability-actn-slicing-05.txt

daniel@olddog.co.uk Tue, 16 June 2020 14:52 UTC

Return-Path: <dk@danielking.net>
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 4E15E3A1645 for <teas@ietfa.amsl.com>; Tue, 16 Jun 2020 07:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=danielking-net.20150623.gappssmtp.com
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 yedhAv9DNjnN for <teas@ietfa.amsl.com>; Tue, 16 Jun 2020 07:52:07 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B49333A16A7 for <teas@ietf.org>; Tue, 16 Jun 2020 07:51:57 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id l17so3177431wmj.0 for <teas@ietf.org>; Tue, 16 Jun 2020 07:51:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielking-net.20150623.gappssmtp.com; s=20150623; h=sender:from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=b9BIuUP4YAEpA/tuXZeHdEcTIdRQ6mQcLIgI7hqPCic=; b=tBd687KMtX0Bu2+YxlULCfeAs5im2S3V9KiUGVDVijHFvjSaxZxfXQTTunBAs7AHUr 9R7YD3vHjEu4m+5uu2IfkmlE3XWgxo0jkNSe/9d3NlUTMIsPSGu59+yxkIhdPnM6jM6C BG0ruTMkyBeaDxnCQ+Ln+1D9FxDl8l15uN4pLdmW7EFECbQi4F45alswU4Izprxl9e79 yxLZA7ZR2JKgkWNrzPtBAO0Wunf90DQTIEhWD6PAXiuegoPyhZxR5FwiIKPmCFJHKER0 SiDqx+Tetvued4SgCxkQr5uAFOugqkCVwDXBD2iSIZqlfR1oLKyu1eJiJnEmRz/36UgI n1zQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:references:in-reply-to:subject :date:message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=b9BIuUP4YAEpA/tuXZeHdEcTIdRQ6mQcLIgI7hqPCic=; b=Fli0WufYlz1gy8dCu+vFP8cNcYFQtdSVT+fg39co/bUMxbTP0ZXCG2Hom43EugXi6A K5SggM5JJ07Cz7Ss2H/93DyfJ8lnw06Wf9iyDxQIY5dnI76Jkn17DOf5HjWWKTqKZkMU MrdXKOWw5jvdYM26B2wphJgZd/C13zQ6qmcRo57ksB1/sSgtQVvCpU35CZKVa8QtmjWb 1nTINdsSUpruEAhgQxcIpmu56/fJ3TSFySGI+wNM7mHhIDjSLmyOkavkWNCl4ciSlQXk nNRvj+eoykM8lBeF6Svc60oAXfdd3AGULvedgMWYsHXZgVzVitcIxpEGPpXUhBQzUv2P bs3w==
X-Gm-Message-State: AOAM5331+HTKstCK1CN47aUL5FLfG035Rruxx897+Q4DLfs2Tsqcjxi7 hOBaue4cv055C5+fXZ4uDPq/gQ==
X-Google-Smtp-Source: ABdhPJyHfCughGca5zUALyYb6ry89SdeBSqxnXewro9hEsNOb7DQENEjEuSZD+ZEgRkGQ2rq45UHQg==
X-Received: by 2002:a05:600c:2256:: with SMTP id a22mr3577430wmm.18.1592319115783; Tue, 16 Jun 2020 07:51:55 -0700 (PDT)
Received: from CIPHER ([2a00:23c7:100:ca00:488a:31e8:af46:b8ea]) by smtp.gmail.com with ESMTPSA id v24sm2444331wrd.92.2020.06.16.07.51.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Jun 2020 07:51:55 -0700 (PDT)
Sender: Daniel King <dk@danielking.net>
X-Google-Original-Sender: <dk@danielking.net>
From: daniel@olddog.co.uk
To: teas@ietf.org
Cc: 'John E Drake' <jdrake@juniper.net>, 'Zhenghaomian' <zhenghaomian@huawei.com>
References: <159231804989.1886.9996953325296702167@ietfa.amsl.com>
In-Reply-To: <159231804989.1886.9996953325296702167@ietfa.amsl.com>
Date: Tue, 16 Jun 2020 15:51:54 +0100
Message-ID: <00f901d643ed$ad7626c0$08627440$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQI3FrHE0IN0soBaRslJ25D9b+E4IqgZqfsw
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/lGzZYCJwJ8YoKpZ_s8MUobrIcaU>
Subject: [Teas] FW: New Version Notification for draft-king-teas-applicability-actn-slicing-05.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: Tue, 16 Jun 2020 14:52:09 -0000

Dear teas drinkers, 

Since ACTN is a key output of the TEAS working group, and because Network Slicing continues to be a subject of interest, we thought we should resume the following I-D:

Applicability of Abstraction and Control of Traffic Engineered Networks (ACTN) to TE Network Slicing
https://datatracker.ietf.org/doc/draft-king-teas-applicability-actn-slicing/

You might remember the main purpose of this document was to show how ACTN is an applicable technology for requesting, provisioning, and managing network slices in TE and transport networks. In particular, it draws on a lot of published RFCs and a number of YANG models that are being worked on (including in TEAS) to show how a management system can be put together using existing building blocks.

Yes! We are aware that there is work going on in the Network Slicing Design Team to refine definitions that apply to network slicing. It is not our intention to subvert that work, and we have kept the number of terms that we have defined to a basic minimum and we scope those definitions to just this document. We also know that the Design Team plans to include some text on the applicability of ACTN, but we feel that that is most likely to be just a few paragraphs in a bigger document. As you can see from this document, we think that the subject requires a few more words. 

What next? Obviously, we believe we have some more work to do on this document. Several areas for discussion present themselves, including:

o to specify the slice-related model applicability, on both CMI and MPI; 
o to have an architectural match between ACTN and TS arch (we notice similar work in the DT draft);
o to evaluate the multi-technology, such as packet-optical and/or PON+OTN as slice delivery;

We would welcome any review or comments.

Dan, John and Haomian. 

-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: 16 June 2020 15:34
To: Haomian Zheng <zhenghaomian@huawei.com>; Daniel King <daniel@olddog.co.uk>; John Drake <jdrake@juniper.net>
Subject: New Version Notification for draft-king-teas-applicability-actn-slicing-05.txt


A new version of I-D, draft-king-teas-applicability-actn-slicing-05.txt
has been successfully submitted by Daniel King and posted to the IETF repository.

Name:		draft-king-teas-applicability-actn-slicing
Revision:	05
Title:		Applicability of Abstraction and Control of Traffic Engineered Networks (ACTN) to TE Network Slicing
Document date:	2020-06-16
Group:		Individual Submission
Pages:		17
URL:            https://www.ietf.org/internet-drafts/draft-king-teas-applicability-actn-slicing-05.txt
Status:         https://datatracker.ietf.org/doc/draft-king-teas-applicability-actn-slicing/
Htmlized:       https://tools.ietf.org/html/draft-king-teas-applicability-actn-slicing-05
Htmlized:       https://datatracker.ietf.org/doc/html/draft-king-teas-applicability-actn-slicing
Diff:           https://www.ietf.org/rfcdiff?url2=draft-king-teas-applicability-actn-slicing-05

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

   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 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 transport 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.

                                                                                  


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.

The IETF Secretariat