Re: [Teas] New Version Notification for draft-ietf-teas-applicability-actn-slicing-04.txt

daniel@olddog.co.uk Tue, 29 August 2023 21:16 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 B23F0C14CE5F for <teas@ietfa.amsl.com>; Tue, 29 Aug 2023 14:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.655
X-Spam-Level:
X-Spam-Status: No, score=-1.655 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=danielking-net.20221208.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zf-EZU7YdInj for <teas@ietfa.amsl.com>; Tue, 29 Aug 2023 14:16:03 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8941FC14CE5E for <teas@ietf.org>; Tue, 29 Aug 2023 14:16:03 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id ffacd0b85a97d-313e742a787so127048f8f.1 for <teas@ietf.org>; Tue, 29 Aug 2023 14:16:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielking-net.20221208.gappssmtp.com; s=20221208; t=1693343761; x=1693948561; darn=ietf.org; h=thread-index:content-language:content-transfer-encoding :mime-version:message-id:date:subject:in-reply-to:references:to:from :sender:from:to:cc:subject:date:message-id:reply-to; bh=P37G1BL1ep407goalnKaNwEdENZzoTXyWtQ5810ryRY=; b=D58WB8sHx4B3RqWNaFv3ZmSreywATkGM6IfobaO2/rvBxRDMKxjY5avvGU68NJapoC XjJw4EivQ7/h/YLAJU29PGtF0QaoaylVuz5C01v8w+xciHe1ZV4xcpIE9MrU9gdlB3Qo a4XC0rjBQFypHOOt+/QZDPzIMdLROLsYCw0kNWuZSC1zAwGZbGgAXNVQaESEmZEdPENn ii+PgXH0bvwdTyr83d++PQVJGQRmWp1/x3AMgveYJWHtqR/2QX+oTpOJBoSEHwXq2qto kdnuhlHFAUqY3GAWPoV12wr9VigsjCdLMJ+Roam+akZXXIRP0mUf/0uUNo+phAAtAUE/ Rr8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693343761; x=1693948561; h=thread-index:content-language:content-transfer-encoding :mime-version:message-id:date:subject:in-reply-to:references:to:from :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=P37G1BL1ep407goalnKaNwEdENZzoTXyWtQ5810ryRY=; b=PhyoUuf31Jr2f3DbRy62DWWW8G+uQ5T9TaSfiNep0rH/JswAyE8iEf/i/0xIkkIpm2 OzdRWgQ3bsR/EUr/8YS4QQ8qmOfq7EMT4isS3chcP0yfsjUpA14edUFZnopbBZVltU8f 9r3nsHEHauWRAus0DZ/p09PbLAJfQSxXFSbdY8TKxaEP5p5u8cJVxWCTZaXyk0MUa+UI h0knWTjoqGJo9Y5/4O1uGcNByEzWsolJpZbkxOXzcDP0hJGpnpXbNrfsMUuiToFisNsW t+UsCUV27KqEfJPpwBxEqxBiekm6Y+RHm5vdoeulzTe0l6KBtBFaCPlgCZIe3TCDyL7t U7Nw==
X-Gm-Message-State: AOJu0YxDZNziGXd1yuPGu5UV4QI+QYYXIfaNlsjoy4gq6cOa/47fS2x2 iTreFN+9W3uPQBpm0v6trz7H3fVcLxmXZaL4XkZhsg==
X-Google-Smtp-Source: AGHT+IHZhUPQG3CTHbEr/uDJMktI46Tfxnx5HrvRZlaKvOgPCHHMgW+hvF9JEeCcnufQolmX/HOD1Q==
X-Received: by 2002:a5d:4f0c:0:b0:317:a499:72c8 with SMTP id c12-20020a5d4f0c000000b00317a49972c8mr2725655wru.1.1693343760528; Tue, 29 Aug 2023 14:16:00 -0700 (PDT)
Received: from CIPHER ([2a00:23c7:105:2801:85f7:638e:cb2d:a18]) by smtp.gmail.com with ESMTPSA id n12-20020a5d67cc000000b00317afc7949csm14756364wrw.50.2023.08.29.14.15.59 for <teas@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Aug 2023 14:15:59 -0700 (PDT)
Sender: Daniel King <dk@danielking.net>
X-Google-Original-Sender: <dk@danielking.net>
From: daniel@olddog.co.uk
To: teas@ietf.org
References: <169334281323.15659.9359881409537261643@ietfa.amsl.com>
In-Reply-To: <169334281323.15659.9359881409537261643@ietfa.amsl.com>
Date: Tue, 29 Aug 2023 22:15:58 +0100
Message-ID: <02bf01d9dabe$018c17a0$04a446e0$@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
Content-Language: en-gb
Thread-Index: AQGxrxGQj/cVoG5k00DDyks6ycIrFLBSGe3g
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/pey17Mni-CG7xQHnmPgwcsBNKO4>
Subject: Re: [Teas] New Version Notification for draft-ietf-teas-applicability-actn-slicing-04.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
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, 29 Aug 2023 21:16:07 -0000

Hi teas,

Please find a new version of our I-D, with some minor updates:

- Added xMI interface to figure 1 as per discussion (earlier teas list email)
- Various readability updates and NITS
- Updated references 

This version represents the version the authors would like the Chairs/WG to consider for Last Call. 

Re: draft-ietf-teas-applicability-actn-slicing and possible overlap with draft-barguil-teas-network-slices-instantation

Following up on my comments during the IETF 117 TEAS session. 

draft-ietf-teas-applicability-actn-slicing - Our applicability document is very specific to the ACTN architecture and, of course, the models. The instantiation draft is more of an overview of all the YANG models available and how they could be used in different instantiations. 

draft-barguil-teas-network-slices-instantation mentions ACTN, but only at a very high level. Therefore, it could certainly reference the ACTN applicability document, and it should, maybe, include a short subsection listing ACTN models. 

However, including the full ACTN applicability text in draft-barguil-teas-network-slices-instantation would swamp all of the other material, while putting non-ACTN in the ACTN applicability draft would be wrong.

I hope that makes the situation clearer. 

BR, Dan (on behalf of the authors)

-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: Tuesday, August 29, 2023 10:00 PM
To: Adrian Farrel <adrian@olddog.co.uk>; Daniel King <daniel@olddog.co.uk>; Haomian Zheng <zhenghaomian@huawei.com>; John Drake <jdrake@juniper.net>
Subject: New Version Notification for draft-ietf-teas-applicability-actn-slicing-04.txt

A new version of Internet-Draft
draft-ietf-teas-applicability-actn-slicing-04.txt has been successfully submitted by Daniel King and posted to the IETF repository.

Name:     draft-ietf-teas-applicability-actn-slicing
Revision: 04
Title:    Applicability of Abstraction and Control of Traffic Engineered Networks (ACTN) to Network Slicing
Date:     2023-08-29
Group:    teas
Pages:    24
URL:      https://www.ietf.org/archive/id/draft-ietf-teas-applicability-actn-slicing-04.txt
Status:   https://datatracker.ietf.org/doc/draft-ietf-teas-applicability-actn-slicing/
HTML:     https://www.ietf.org/archive/id/draft-ietf-teas-applicability-actn-slicing-04.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-teas-applicability-actn-slicing
Diff:     https://author-tools.ietf.org/iddiff?url2=draft-ietf-teas-applicability-actn-slicing-04

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 Engineered (TE) network that utilizes IETF technologies.
   It also identifies the features of network slicing not currently
   within the scope of ACTN, and indicates where ACTN might be extended.



The IETF Secretariat