Re: [Teas] Network Slicing design team definitions- transport slice

"BRUNGARD, DEBORAH A" <> Wed, 02 September 2020 13:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8CB683A0D60; Wed, 2 Sep 2020 06:30:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.796
X-Spam-Status: No, score=-1.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id CxVhDLlo2RZr; Wed, 2 Sep 2020 06:29:56 -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 360683A0D4B; Wed, 2 Sep 2020 06:29:56 -0700 (PDT)
Received: from pps.filterd ( []) by ( with SMTP id 082DNmFO033868; Wed, 2 Sep 2020 09:29:56 -0400
Received: from ( []) by with ESMTP id 33ac8105x4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 02 Sep 2020 09:29:54 -0400
Received: from (localhost []) by (8.14.5/8.14.5) with ESMTP id 082DTqJl030083; Wed, 2 Sep 2020 09:29:53 -0400
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id 082DTlKV029915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 2 Sep 2020 09:29:47 -0400
Received: from ( []) by (Service) with ESMTP id A46F54009E78; Wed, 2 Sep 2020 13:29:47 +0000 (GMT)
Received: from (unknown []) by (Service) with ESMTPS id 7EBD44009E77; Wed, 2 Sep 2020 13:29:47 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2044.4; Wed, 2 Sep 2020 09:29:46 -0400
Received: from ([]) by ([]) with mapi id 15.01.2044.004; Wed, 2 Sep 2020 09:29:46 -0400
CC: Daniele Ceccarelli <>, "Rokui, Reza (Nokia - CA/Ottawa)" <>, TEAS WG <>
Thread-Topic: [Teas] Network Slicing design team definitions- transport slice
Thread-Index: AdaAahQV6S/yA+OKSoyFMszSSgrA3QAJ5F2AAAb+YAD//86xR4ABIjsAgAALZgCAAAKwhg==
Date: Wed, 02 Sep 2020 13:29:46 +0000
Message-ID: <>
References: <> <>, <> <> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-tm-snts-smtp: 781AB46468CFD036942485B2663E4E71431BD515CBCE980C67289B25C8988EFF2
Content-Type: multipart/alternative; boundary="_000_2B5FCF59D1504606938200C572A2ED34attcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-09-02_09:2020-09-02, 2020-09-02 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 phishscore=0 mlxlogscore=999 spamscore=0 impostorscore=0 malwarescore=0 bulkscore=0 suspectscore=0 adultscore=0 clxscore=1011 mlxscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2006250000 definitions=main-2009020125
Archived-At: <>
Subject: Re: [Teas] Network Slicing design team definitions- transport slice
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: Wed, 02 Sep 2020 13:30:01 -0000

Hi all,
(as individual)

I don’t see differentiating this work from the rest of the industry use of network slice as a valid justification and only will prevent IETF’s work from being visible. We will be so hung up in explaining our term vs. solution.

This work in TEAS needs to be generic for providing an integrated solution E2E for a network. You may not be aware, TEAS needs to provide the platform for detnet (TSN integration with network) and raw (satellite and radio). No one in IETF uses “transport”.

I understand the DT wanted to scope the work for defining but the choice of a name is not just for a DT or wg but to allow for industry visibility. As this is now time for adopting, just as for ACTN, we need to align with other work.

Sent from my iPhone

On Sep 2, 2020, at 5:20 AM, LUIS MIGUEL CONTRERAS MURILLO <> wrote:

Hi all,

I fully share Daniele’s view on this. “Transport slice” (or even “Transport network slice”, as was also considered during DT discussions) provides a valid understanding of what is the subject, not only for 3GPP services but for any other service that could need of slices in the transport network (i.e., using IP, MPLS, MW, optics, etc).

Best regards


De: Teas <> En nombre de Daniele Ceccarelli
Enviado el: miércoles, 2 de septiembre de 2020 10:39
Para: BRUNGARD, DEBORAH A <>; Rokui, Reza (Nokia - CA/Ottawa) <>
Asunto: Re: [Teas] Network Slicing design team definitions- transport slice

Hi Deborah,

I’m not 100% happy with the term either but I think a new one is needed.
Network Slice or TE network slice are IMO not good enough to state the RAN and Core are NOT included. Using 3GPP terms both Network Slice or TE network slice makes me think of the NSI, while what we need to define here is the NSSI for the transport part only.

If we call it Network slice we risk to be forced to speak of an IETF Network Slice which will be different from a 3GPP Network Slice…not nice.

Transport slice could potentially have issues with Layer 4 slice. I know very little of Layer 4 to understand if a L4 slice exists or will ever exist, but it’s something we can check.


From: Teas <<>> On Behalf Of BRUNGARD, DEBORAH A
Sent: den 1 september 2020 21:21
To: Rokui, Reza (Nokia - CA/Ottawa) <<>>
Cc: TEAS WG <<>>
Subject: Re: [Teas] Network Slicing design team definitions- transport slice


I’m still very confused by introducing the new term “transport” for IETF work on TE. As Young noted, it will be confused with the archaic term transport for many and it’s a misuse of 3GPP terms if it is not limited to 3GPP’s transport. Please look at the discussion thread on ACTN.

Ccamp and RAW cover wireless technologies so TEAS work is not limited to 3GPP “transport”. This work should be generic - a base - for other IETF work.

Before defining yet another term, why is the term Network Slice or TE network slice not acceptable? TE network slice will distinguish this work is for TE domains (TEAS charter work), network slice will align with IETF’s terms used in other groups. I don’t think TE transport slice is acceptable either - when we already have existing terminology that is concise.

I think you are confusing with the technology - especially if you are introducing new terms for all parts of the network - RAN slices, Core slices, Transport slice - TEAS work has never been constrained by the technology domain. “Network” is the network, no matter the division. There’s no need for all these terms.

Sent from my iPhone

On Sep 1, 2020, at 2:17 PM, Rokui, Reza (Nokia - CA/Ottawa) <<>> wrote:


Please note that 3GPP does not use the term “RAN Slice” or “Core slice”. Instead they use term “Slice Subnet”.
Please refer to the following 3GPP documents for example for more info:

  *   TS 28.531
  *   TR 28.801

Also see the following (taken from<>).
The term NSI is for Network Slice instance and term NSSI is for Network Slice Subnet instance. As the picture shows, 3GPP does not differentiate between RAN and Core, all are called NSSI
The draft’s co-authors did not use the term “subnet” because at IETF this term (i.e. IP Subnet) has very clear meaning and using it in context of network slicing is confusing.

Also since the work at IETF is not just for 5G, we use the term “Transport slice”. If the use case is 5G, we also used RAN and Core Slices instead of NSSI to remove any confusion.


From: Teas <<>> on behalf of Young Lee <<>>
Date: Tuesday, September 1, 2020 at 10:56 AM
Cc: TEAS WG <<>>
Subject: Re: [Teas] Network Slicing design team definitions- transport slice

Hi Deborah,

I also am wondering where ' transport slicing' came from. 3GPP uses network slicing in the following three subnets: RAN, CN, and TN; and accordingly it uses RAN slicng, CN slicing  and TN slicing.

There is always prefix "Network" is associated with slicing whether it is RAN, CN, or TN.

As you pointed out, when RFC 8453 was developed in TEAS WG, we originally used the term Transport Network Slicing, but later this term was replaced with Traffic Engineered (TE) Network slicing.

Transport slicing is a bit orphanish. It should be either TE network slicing or Transport network slicing. In TEAS WG, TE network slicing might be more consistent with RFC 8453. Just for your reference, the following terminology has been defined in RFC 8453:

TE Network Slicing:  In the context of ACTN, a TE network slice is a

      collection of resources that is used to establish a logically

      dedicated virtual network over one or more TE networks.  TE

      network slicing allows a network operator to provide dedicated

      virtual networks for applications/customers over a common network

      infrastructure.  The logically dedicated resources are a part of

      the larger common network infrastructures that are shared among

      various TE network slice instances, which are the end-to-end

      realization of TE network slicing, consisting of the combination

      of physically or logically dedicated resources.


2020년 9월 1일 (화) 오후 11:31, BRUNGARD, DEBORAH A <<>>님이 작성:
(speaking as an individual)

Picking up on Jari’s comment “sometimes people want to use labels that are a bit more imprecise, but I think we should strive to avoid such labels as much as we can”, can you give more background on the choice of the term “transport slice”?

I noted while you have text on the use of “transport” by 3GPP as specifying a very specific sub-network in the radio network (which excludes the handoff to the rest of the network), you referenced RFC5921 (MPLS-TP) for the term “transport”.

There was a long thread of mail on ACTN, RFC8453, to move away from the term “transport” to “TE networks” which was agreed to be more specific/appropriate for TEAS. Considering IETF is already using the term “network slicing” (including TEAS RFC8453) and 3GPP use of the term, I don’t understand the use of “transport” in this document.

Considering IETF already uses the term “network slice” and 3GPP uses the term (and all the industry SDOs), I am concerned we will be confusing the industry, especially as “transport” is an imprecise term for TEAS work. Is this work a subset and scoped only to the 3GPP “transport” cloud (and implied use of MPLS-TP)? Or is it planned to be generic (for all TE networks)?

(speaking as individual)
Teas mailing list<><>


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição