Re: [Teas] WG adoption - draft-nsdt-teas-transport-slice-definition

Adrian Farrel <> Fri, 28 August 2020 22:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 764EA3A0D75; Fri, 28 Aug 2020 15:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Status: No, score=-1.894 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id MsvSLieP2158; Fri, 28 Aug 2020 15:57:02 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4B27D3A0D7A; Fri, 28 Aug 2020 15:56:52 -0700 (PDT)
Received: from ( []) by (8.14.4/8.14.4) with ESMTP id 07SMunUZ031269; Fri, 28 Aug 2020 23:56:49 +0100
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id 54E6522044; Fri, 28 Aug 2020 23:56:49 +0100 (BST)
Received: from (unknown []) by (Postfix) with ESMTPS id 3F8D322042; Fri, 28 Aug 2020 23:56:49 +0100 (BST)
Received: from LAPTOPK7AS653V ([]) (authenticated bits=0) by (8.14.4/8.14.4) with ESMTP id 07SMummo011600 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 28 Aug 2020 23:56:48 +0100
From: Adrian Farrel <>
To: 'Vishnu Pavan Beeram' <>, 'TEAS WG' <>
Cc: 'TEAS WG Chairs' <>
References: <>
In-Reply-To: <>
Date: Fri, 28 Aug 2020 23:56:41 +0100
Organization: Old Dog Consulting
Message-ID: <05ba01d67d8e$83617a80$8a246f80$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_05BB_01D67D96.E5271B00"
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQJFgDPaxYcvrtKyiSzqHlBkkBJ8kqhwGyMA
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--16.312-10.0-31-10
X-imss-scan-details: No--16.312-10.0-31-10
X-TMASE-Result: 10--16.312000-10.000000
X-TMASE-MatchedRID: IeZYkn8zfFrxIbpQ8BhdbHZfNnBVXJYniFB88PweKrXnUD8POrkddooq qJHJHX2WIE+yrJoXHyV98uTk7zcFe1H+T48/HBwjucWz1xJfHWaPSNdj1JMyAZNyfiOLWydOxUD TxL3vuSBqiJeghlwGGUfXke00bBz6/u0euujb/zERgc884o1LVapW8MqA90G14ZmC0TPZtohpaZ rmIAHLOHW/djWorYrJ7u/TlrbPllFs/7vJ3zbsJGzBijri5+RVF9s8UTYYetVV5D/AXr/H3NAYW Uo4HSIkqjtz90j0VPnIif6xwSA0igAYypzZlhFp9FQh3flUIh5L9x4FCuBLUQ/vnJWZIdGASD2g gSXn5eAdjaiO/zggUi2QD7fdlz93KXFwpy84b0o8TeSGZW8c7mW7wAkGQ80wmbdPE3zcujge4Q9 rmjgCD04qaSs6OmJalww8GuFrcTsn4llhB/GgfImR/mpCAiHdE3Ba/Z0GuaSbkEl1SMP4VZakb9 Cst1glmkAOgxjWpisdsDDkKdu5NErYfGvC1HVreJ2BzwQDOOgKF0jiwuWuOIVquVYFwXAmChcbH TwAl8LhQ8WVHvZupah0K7+2RkRF0u6qOSEgKL78Jrg+3ve3W6dlL9piCOvONPic0YcVgOsjJxwp T9SCmwuDvWf2RSAGmQTlFR/45lQhB8v9fiEUSMLRNemq17EirVkZQpHRiCwItQd56gn7IViqAyk 7LkbkI22wyx0Nae1ATzeCdAKeQK/V8/cgjzjSqa6SJk58+LYpWss5kPUFdMlgi/vLS2726ZhZJf DWK58RsHN+CG+OBhHlKZ0KtAaIR1vveBQPCReeAiCmPx4NwGmRqNBHmBve1B0Hk1Q1KyLr8uVzX avvgwaIkv313qJpOwBXM346/+xz21XwgPGHHrEScRQIMcwU9m3sV1ZD/owkMf0b/qVX3J3cqzAt 75rF
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <>
Subject: Re: [Teas] WG adoption - draft-nsdt-teas-transport-slice-definition
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 28 Aug 2020 22:57:04 -0000

Hi all,


I spent a good chunk of time yesterday and today catching up on the threads about this document. I believe there are several important things to say:


1. Many thanks are due to the Design Team which I know has invested a lot of time and thought into working on their small set of documents. Such effort should not go unrecognised.


2. Several comments have referred to the consensus that the Design Team reached on the content of the document. It's good that the DT was able to reach consensus - I haven't gone back to determine whether it was rough and how it was measured, and that doesn't matter if they agree it was reached. However, the consensus, of itself is only informational as we consider the document and doesn't carry weight against arguments put forward in this discussion (especially by people who were not active participants in the DT). Let's hear all voices and opinions and not squash them with the DT's collective view.


3. I am puzzled by the debate about what to do with text that might be removed from this document. We are debating adopting this draft and don't (at this stage) have control over what goes in other DT documents (or any other non-WG document). If the WG decides that text does not belong in this document, then that is all we decided and people are free to place that text elsewhere: in some other non-WG draft if their co-authors agree, or in a new draft of their own. So let's debate what text we want in *this* document on its own merits.


4. The discussion of "isolation" seems to get significantly hung up on the difference between "isolation as part of a service objective" and "isolation as a delivery mechanism". Service objectives are not necessarily directly or easily observable by a client. For example, you might ask your service provider to guarantee that your traffic is not routed via <insert name of country you don't trust>, but when packets are tunnelled and the provider doesn't give you good access to their internal diagnostic traces, it can be less than simple to verify that they are meeting this objective. Thus, absolute requests for isolation are probably meaningless at the service interface and in some network technologies they cannot really be delivered, anyway. What is more important is that we deconstruct "isolation" into the concepts that the client does actually care about: no misdelivery, no observation of traffic by another client, no interference on traffic quality/delivery owing to the activity of other clients. In draft-king-teas-applicability-actn-slicing we tried to tease out these distinctions and believed that the way in which these service features might be delivered are an entirely different matter - if someone wants to write a document called "Delivering Service Isolation Using SRv6" then I think that would be a fine place to discuss such issues.


5. Document review and opinion on adoption. That's next on my list 😊





From: Teas <> On Behalf Of Vishnu Pavan Beeram
Sent: 19 August 2020 16:50
To: TEAS WG <>
Cc: TEAS WG Chairs <>
Subject: [Teas] WG adoption - draft-nsdt-teas-transport-slice-definition



This is start of a *three* week poll on making
draft-nsdt-teas-transport-slice-definition-03 a TEAS working group document.
Please send email to the list indicating "yes/support" or "no/do not
support". If indicating no, please state your reservations with the
document. If yes, please also feel free to provide comments you'd
like to see addressed once the document is a WG document.

The poll ends September 9th (extra week to account for vacation season).

Pavan and Lou