Re: [Teas] The definition of a Network Slice in draft-nsdt-teas-ietf-network-slice-definition

Adrian Farrel <> Sun, 15 November 2020 22:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2E7273A0E70; Sun, 15 Nov 2020 14:00:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
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, 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 6ezRjKQv2nxV; Sun, 15 Nov 2020 14:00:52 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DCF783A0E68; Sun, 15 Nov 2020 14:00:50 -0800 (PST)
Received: from ( []) by (8.14.4/8.14.4) with ESMTP id 0AFM0nru012242; Sun, 15 Nov 2020 22:00:49 GMT
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id 02FDF22044; Sun, 15 Nov 2020 22:00:49 +0000 (GMT)
Received: from (unknown []) by (Postfix) with ESMTPS id E1B7122042; Sun, 15 Nov 2020 22:00:48 +0000 (GMT)
Received: from LAPTOPK7AS653V ([]) (authenticated bits=0) by (8.14.4/8.14.4) with ESMTP id 0AFM0lrE010776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 15 Nov 2020 22:00:48 GMT
Reply-To: <>
From: "Adrian Farrel" <>
To: "'Jari Arkko'" <>
Cc: <>, <>
References: <008201d6bacb$26b80590$742810b0$> <>
In-Reply-To: <>
Date: Sun, 15 Nov 2020 22:00:45 -0000
Organization: Old Dog Consulting
Message-ID: <016201d6bb9a$c64cd4d0$52e67e70$>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJbg7JORjtUMOnlzFQvq1yLCsmWvQFQNDCcqLWrxaA=
Content-Language: en-gb
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--0.966-10.0-31-10
X-imss-scan-details: No--0.966-10.0-31-10
X-TMASE-Result: 10--0.965600-10.000000
X-TMASE-MatchedRID: VfovoVrt/oayoI+bK8UPQnFPUrVDm6jtaKq1Yhw50js5+qEYOELvPef0 QjjOEQY76vdhmRIaSgG4qW21Esgi/erc3PMw0ds5zNY33yIEF4bpVMb1xnESMnATs0J+9trcZzo WIGKfgt21IKRGwk5D15GarAjCAlO43zfWGx5cY+GI8hHRrWLqF5Ry1HDTPOXaWUNXQqAdJYe202 5S1WXaLBoBoSlc7UQ7qht9LWxMafLISRx+nwhCvVD5LQ3Tl9H7pNh/2/1+WiWbKItl61J/ycnjL TA/UDoAY/XFS+uWHLUXyGzxbm0xz2rz/G/ZSbVq+gtHj7OwNO2FR9Hau8GO7iZavwi50dplIOg/ eEpWxh5yT/UZLM7eLW9VKFkVkO5Cb0h1/r/nWYgdQtrBcNNLIwInjTf7216HdKsyna9Jd2MY4Fa 9hRoUhWIbgT35V5pQp8i26iGCN+fD/c2Y8mxrik1Z+dSdugwvIEkRmWEtatBDDKa3G4nrLQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <>
Subject: Re: [Teas] The definition of a Network Slice in draft-nsdt-teas-ietf-network-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: Sun, 15 Nov 2020 22:00:54 -0000

Maybe a way through this would be to acknowledge slicing of all types of
network as possible, and then say that this document is focusing on slicing
of connectivity resources.


-----Original Message-----
From: Jari Arkko <> 
Sent: 15 November 2020 21:54
Subject: Re: [Teas] The definition of a Network Slice in


Thanks for this as well. Again, I largely agree with what you suggest. 

(The one exception may be that I do believe firmly that we should be careful
to keep the scope of our concept close to what we are experts in, i.e.,
communication. It also reduces the risk potential confusion and overlap with
others who work in the broader area.)