[Teas] Network Slicing design team definitions- transport slice

"BRUNGARD, DEBORAH A" <db3546@att.com> Tue, 01 September 2020 14:31 UTC

Return-Path: <db3546@att.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF193A0915 for <teas@ietfa.amsl.com>; Tue, 1 Sep 2020 07:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXqHPGZ-leEw for <teas@ietfa.amsl.com>; Tue, 1 Sep 2020 07:31:33 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 691AB3A0903 for <teas@ietf.org>; Tue, 1 Sep 2020 07:31:33 -0700 (PDT)
Received: from pps.filterd (m0049458.ppops.net [127.0.0.1]) by m0049458.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id 081ENTLU001043 for <teas@ietf.org>; Tue, 1 Sep 2020 10:31:31 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049458.ppops.net-00191d01. with ESMTP id 339qvt8e18-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <teas@ietf.org>; Tue, 01 Sep 2020 10:31:31 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 081EVUto025599 for <teas@ietf.org>; Tue, 1 Sep 2020 10:31:30 -0400
Received: from zlp30487.vci.att.com (zlp30487.vci.att.com [135.47.91.176]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 081EVRGh025544 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <teas@ietf.org>; Tue, 1 Sep 2020 10:31:27 -0400
Received: from zlp30487.vci.att.com (zlp30487.vci.att.com [127.0.0.1]) by zlp30487.vci.att.com (Service) with ESMTP id 5C3D24009E6E for <teas@ietf.org>; Tue, 1 Sep 2020 14:31:27 +0000 (GMT)
Received: from GAALPA1MSGEX1DE.ITServices.sbc.com (unknown [135.50.89.118]) by zlp30487.vci.att.com (Service) with ESMTPS id 48FB640002AA for <teas@ietf.org>; Tue, 1 Sep 2020 14:31:27 +0000 (GMT)
Received: from GAALPA1MSGEX1DE.ITServices.sbc.com (135.50.89.118) by GAALPA1MSGEX1DE.ITServices.sbc.com (135.50.89.118) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2044.4; Tue, 1 Sep 2020 10:31:26 -0400
Received: from GAALPA1MSGEX1DE.ITServices.sbc.com ([135.50.89.118]) by GAALPA1MSGEX1DE.ITServices.sbc.com ([135.50.89.118]) with mapi id 15.01.2044.004; Tue, 1 Sep 2020 10:31:26 -0400
From: "BRUNGARD, DEBORAH A" <db3546@att.com>
To: TEAS WG <teas@ietf.org>
Thread-Topic: Network Slicing design team definitions- transport slice
Thread-Index: AdaAahQV6S/yA+OKSoyFMszSSgrA3Q==
Date: Tue, 1 Sep 2020 14:31:26 +0000
Message-ID: <70af45b0bdf54f418ad83fcb65906f4a@att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.181.101]
x-tm-snts-smtp: BBD7D80A405081FCFF835C6031CAF592E8E6F95693087E7D54DF4F2D604A8CFA2
Content-Type: multipart/alternative; boundary="_000_70af45b0bdf54f418ad83fcb65906f4aattcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-09-01_08:2020-09-01, 2020-09-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 suspectscore=0 mlxscore=0 clxscore=1015 lowpriorityscore=0 spamscore=0 impostorscore=0 malwarescore=0 bulkscore=0 adultscore=0 mlxlogscore=577 priorityscore=1501 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2006250000 definitions=main-2009010121
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/63UTQEqbgKCvXwKvIDu_iSyXzmQ>
Subject: [Teas] Network Slicing design team definitions- transport slice
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2020 14:31:35 -0000

Hi,
(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)?

Deborah
(speaking as individual)