Re: [Teas] The definition of a Network Slice in draft-nsdt-teas-ietf-network-slice-definition Mon, 16 November 2020 08:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9B9913A0D4C; Mon, 16 Nov 2020 00:08:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Status: No, score=-2.096 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 E4bnX90h9LjO; Mon, 16 Nov 2020 00:08:30 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 819513A0D4B; Mon, 16 Nov 2020 00:08:30 -0800 (PST)
Received: from (unknown [xx.xx.xx.68]) by (ESMTP service) with ESMTP id 4CZMCK0Zz5zygk; Mon, 16 Nov 2020 09:08:29 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ORANGE001; t=1605514109; bh=YVq4KyAnOVRBwJwcZmUMuFWoEX5FGi1ulePdXJDwzSs=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=Spe0yJB8i9f7eYABqNQO16wnxTja/jWn3BUFQvxP40sR4w9tBXBsYOWPgQBGvEcFJ lguyXtOTC+c8GdzXnjArwxtG5mIijTEC75AON9dN5101J7qsQCxER88cNXQDSiJpXY PWqL0HuckgWYiZSRK2glcEl09OSOjYpkgKO6d8lFwqx2YGqan3R00AJ87YdkefkSeW sz28+vrjOn2WAiukFGdf5kG7/64MZYbXDpQ6SDkbeyoY+17sZ5kQYfXiPTPbj23GB3 pc8FyLhpvfOzecsXaIawigx4hXwjspSH7YZjNuH3Anm1xDRcXw9STk6qkVyXnvs+tS T4s5VHy2pQnvw==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.60]) by (ESMTP service) with ESMTP id 4CZMCJ6zNcz1xpW; Mon, 16 Nov 2020 09:08:28 +0100 (CET)
To: "" <>, 'Jari Arkko' <>
CC: "" <>, "" <>
Thread-Topic: [Teas] The definition of a Network Slice in draft-nsdt-teas-ietf-network-slice-definition
Thread-Index: Ada5piXHleRdfzx0RhmsYb9i2G5H9QB61R+AAAA6HYAAFYQwQA==
Date: Mon, 16 Nov 2020 08:08:28 +0000
Message-ID: <18004_1605514109_5FB2337D_18004_262_1_787AE7BB302AE849A7480A190F8B93303157A50E@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <008201d6bacb$26b80590$742810b0$> <> <016201d6bb9a$c64cd4d0$52e67e70$>
In-Reply-To: <016201d6bb9a$c64cd4d0$52e67e70$>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.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: Mon, 16 Nov 2020 08:08:33 -0000

Hi Adrian, Jari, all,

I agree with the observations made by Adrian and Jari's comment.

It would be helpful to have a name to refer to the connectivity component of an IETF network slice. Also, if there are concrete examples of non-connectivity IETF components that can be cited in the draft, this would be even great.   


> -----Message d'origine-----
> De : Teas [] De la part de Adrian Farrel
> Envoyé : dimanche 15 novembre 2020 23:01
> À : 'Jari Arkko' <>
> Cc :;
> Objet : Re: [Teas] The definition of a Network Slice in draft-nsdt-
> teas-ietf-network-slice-definition
> 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:; draft-nsdt-teas-ietf-network-slice-
> 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


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.