[Teas] Status of draft-king-teas-applicability-actn-slicing?

Adrian Farrel <adrian@olddog.co.uk> Wed, 30 June 2021 11:41 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E730B3A1979; Wed, 30 Jun 2021 04:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id L7NAbgTqjsc1; Wed, 30 Jun 2021 04:41:47 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com []) (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 9D5473A197B; Wed, 30 Jun 2021 04:41:45 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com []) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id 15UBfgAp009335; Wed, 30 Jun 2021 12:41:42 +0100
Received: from vs3.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id 644484604A; Wed, 30 Jun 2021 12:41:42 +0100 (BST)
Received: from vs3.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id 4E8424604C; Wed, 30 Jun 2021 12:41:42 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown []) by vs3.iomartmail.com (Postfix) with ESMTPS; Wed, 30 Jun 2021 12:41:42 +0100 (BST)
Received: from LAPTOPK7AS653V ([]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 15UBff35026454 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 30 Jun 2021 12:41:41 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'TEAS WG Chairs'" <teas-chairs@ietf.org>
Cc: <teas@ietf.org>
Date: Wed, 30 Jun 2021 12:41:42 +0100
Organization: Old Dog Consulting
Message-ID: <145001d76da4$e5eae680$b1c0b380$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_1451_01D76DAD.47AFC3B0"
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AddtoN50C+Ljl72dSOuPz9s4YtBpig==
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--22.200-10.0-31-10
X-imss-scan-details: No--22.200-10.0-31-10
X-TMASE-Result: 10--22.200100-10.000000
X-TMASE-MatchedRID: 6Vc8nWqZiRAOwAmmWH5kBBlJRfzNw8afT5ysQDj6eFkG2HMvWEJenlGi Oqj6wJDgmecayrqVrlNoVevZOrgubBNmUW1dq3NxUNaPigviKR+lGCIMbr7g/hLf1vz7ecPHxDm 9zIKPPUjxvqitRxaOHg10AGA5mE3o5lKdq+fFOu03xCYZDydSGqPYwffgQaRTg8vHe9ji82LJWF oycyc6mUT3MhbZetjr+UBmJ92Zcj9n3JIP9wW2TiyEakGwrofurkGhd90/DD5Q3OD8q9D1sDn3z GQhjJHeeg/DuIC/0hm5vFu25c4E4RwuGy4l9jCQdZnGxcSCdeWp/958oU3WcGt7gCgLtiLmGckl hMfaVvgEBblmchCoRaYhVcaUoYwyIQfL/X4hFEjaize54oCwVJRRlLuwwc4YmvnwKSwd+bfoIVP vrLIEFjba6gSbbjl+iONMOkcrBiaHO/kG/PtN6Qi0LLplf+UvghZKmuN2x5sDLr9vPVWwiHZ5Wv uLBD7q977H1s/08PtPlNWvPMXFkPCDFvXZFmYywpU1WSBl38gIJ2rqTcuYdgoDY6gYCVOTP0pcr FO+EMNVngNu1PoOXVyD5GjbhO+Cf8qbljhTExAc9jA4mLo8uRLBqTl41fL7jADHP5S17Cv352h5 EyPfULlNCIMdKEuYPQ9TM3qQq55vh+emQexLu54CIKY/Hg3AFotZ8Dipw4GYj59oOLB2GmF5X5y uwTohVgaABuyCCQGJXfsUQIi2qyligZ83mqLHu1fEmsG6A7+9rx8yBohLNw==
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/YxT0uZAQc4wAdFdu98bW5L2HpQA>
Subject: [Teas] Status of draft-king-teas-applicability-actn-slicing?
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: Wed, 30 Jun 2021 11:41:52 -0000



I think there were three questions about
draft-king-teas-applicability-actn-slicing that needed to be answered:


1. How to resolve overlap with draft-ietf-teas-enhanced-vpn?

My understanding is that there has been some rebalancing of material between
the drafts based on two factors:

a.	VPN+ is not just about slicing
b.	There is more material needed to describe the ACTN applicability
than conveniently fits in a subsection of the VPN+ document

I think this issue is resolved. The question was opened on the list last
year, and there were no objections to how the text is now balanced.


2. How to resolve terminology issues with the network slicing work?

We have come a long way with network slicing.
draft-ietf-teas-ietf-network-slices now represents the work-in-progress.

Although there is still work to be done with network slices (and that is
queued with me - sorry), I think we have all the core terminology and
concepts resolved.

draft-king-teas-applicability-actn-slicing has "recently" been updated to
use align the terminology, so I think this issues is resolved.


3. Do we even need an applicability statement?

I think this resolves to "Is it useful? Does the WG want it?"

Of course, the material could be published as a white paper or a blog, but
it does seem to link together a number IETF (particularly TEAS) technologies
and that seems to be valuable.

Perhaps this question is a question for the WG during an adoption poll?


So that leads me to ask whether the chairs are now ready to reconsider an
adoption poll for this document?