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

Stewart Bryant <> Mon, 16 November 2020 10:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6525F3A0489; Mon, 16 Nov 2020 02:37:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kFfvEa3zn4Hk; Mon, 16 Nov 2020 02:37:27 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A6D033A07DF; Mon, 16 Nov 2020 02:37:21 -0800 (PST)
Received: by with SMTP id k2so18156354wrx.2; Mon, 16 Nov 2020 02:37:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VNJGK90Ef3mqcjf4+gDcYJw1ekPasRDU4JPRZtayXo8=; b=TW7yYqw3wiZKVz/M3S7bnAuK+eilkU0tACBGVXGkVok5G7rUBWJKfAT43BUqLOl6XM GBr/oeq5RANU8+SwHQcC5lDfJydudv34jkB389YYV94Y0v++mDy+f6TJTXMqEiI9hpQ5 yWxqwbcNWR6A3ppbE15dVJSXD8zMkIi+ajed4QeGy1F9YHEBVcZK+bAq/fIwiMaZqcpB FSInCn49zlkUEoOLzjG3I5fy/uv/dPzVbrUgKbe2XyBgkUfM6zcuqUKYmoAXHFLQMRgQ +lxirm4b72M95K6v7cBJPEyaxQj7YGs+8lai6CF6Im21tviHcuKk1HL/KXJBPaLWrn7l IPfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VNJGK90Ef3mqcjf4+gDcYJw1ekPasRDU4JPRZtayXo8=; b=ZhXe7cVYKZa3KECrkrzhAuqvvLu+YHkNLGg6sxEgLEQbGUepRIbOyzhJuAama0haX4 AQ8+b+xDb1k/jYrSuQJeaEel2xL46sCBMUGnKr/Gggu4sVvWoJhGekEDbn2zxzKRO/GN DBUOEP4oIw6jqL8JotrAAy9X5izuPIp0owEHCQ8WtRu5hm76enSrWtzVT4/mnE0jDiRn OPOBugh6rE5KhMeMFEjZP6PwNCPDaxLVrXhGktQuF13dveSPrEp/jQqT4Onfz/yFDk4y XCVjHbY9JQaWNWi1uJjaZn9SvcfJq4iIHlUPevrTTXHV6RJwrJ3TEDerlcxjWVTwj+dH lyRg==
X-Gm-Message-State: AOAM5338QEI8BEFJhDQCFTnUK0hA2CbsydqL5A3T3IlCG6wGLZhk5Kc0 R7ANBtFuBi/5fD3ZaNUpdC4=
X-Google-Smtp-Source: ABdhPJzkS5kXWJX+I5/2GgdlvK4C2WMvpBB5+cGdRdb4tcXAq7jC492CtDcZZlE7yeyfsY7hiqV3yg==
X-Received: by 2002:a5d:514a:: with SMTP id u10mr18369648wrt.312.1605523039254; Mon, 16 Nov 2020 02:37:19 -0800 (PST)
Received: from ([2a00:23c5:3395:c901:3413:91da:d8fd:ad13]) by with ESMTPSA id e5sm14655292wra.80.2020. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Nov 2020 02:37:18 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
From: Stewart Bryant <>
In-Reply-To: <016201d6bb9a$c64cd4d0$52e67e70$>
Date: Mon, 16 Nov 2020 10:37:15 +0000
Cc: Stewart Bryant <>, Jari Arkko <>,,
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <008201d6bacb$26b80590$742810b0$> <> <016201d6bb9a$c64cd4d0$52e67e70$>
To: Adrian Farrel <>
X-Mailer: Apple Mail (2.3608.
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: Mon, 16 Nov 2020 10:37:28 -0000

I think that would be a useful approach.

There are some that have been studying slicing for many years and have a strong view that it applies to many resources in addition to connectivity with compute and storage often cited.

I think acknowledging the wider scope of slicing whilst expressly stating that we are dealing with a narrow subset of the problem that is within our expertise would be a good practical approach.


> On 15 Nov 2020, at 22:00, Adrian Farrel <> wrote:
> Hmm.
> 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.
> Adrian
> -----Original Message-----
> From: Jari Arkko <> 
> Sent: 15 November 2020 21:54
> To:
> Cc:;
> Subject: Re: [Teas] The definition of a Network Slice in
> draft-nsdt-teas-ietf-network-slice-definition
> Adrian:
> 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.)
> Jari
> _______________________________________________
> Teas mailing list