Re: [Teas] A draft on the framework for end-to-end IETF network slicing

"Dongjie (Jimmy)" <jie.dong@huawei.com> Fri, 14 May 2021 03:55 UTC

Return-Path: <jie.dong@huawei.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 9B4743A20B5 for <teas@ietfa.amsl.com>; Thu, 13 May 2021 20:55:09 -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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 0ZxWp6ChHKR3 for <teas@ietfa.amsl.com>; Thu, 13 May 2021 20:55:05 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B915F3A20B3 for <teas@ietf.org>; Thu, 13 May 2021 20:55:04 -0700 (PDT)
Received: from fraeml714-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FhDwV0XF1z6ygtL for <teas@ietf.org>; Fri, 14 May 2021 11:46:34 +0800 (CST)
Received: from dggeme704-chm.china.huawei.com (10.1.199.100) by fraeml714-chm.china.huawei.com (10.206.15.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Fri, 14 May 2021 05:54:55 +0200
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme704-chm.china.huawei.com (10.1.199.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Fri, 14 May 2021 11:54:53 +0800
Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.2176.012; Fri, 14 May 2021 11:54:53 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] A draft on the framework for end-to-end IETF network slicing
Thread-Index: AddHoyBLABnySO+KTBWZMMOaXQaqcf//mhSA//37oYA=
Date: Fri, 14 May 2021 03:54:52 +0000
Message-ID: <16d8b18dc5574d728842f086227efa97@huawei.com>
References: <c7bb7462db8f4149912d644adbd4760b@huawei.com> <e8e5e968-f6af-a910-d2ec-510fc98ff1d6@joelhalpern.com>
In-Reply-To: <e8e5e968-f6af-a910-d2ec-510fc98ff1d6@joelhalpern.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.143]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/Fp11q0CiWOgiIsRYrtDO9AErKCg>
Subject: Re: [Teas] A draft on the framework for end-to-end IETF network slicing
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: Fri, 14 May 2021 03:55:10 -0000

Hi Joel, 

Thanks for your comments.

The requirement of carrying network slice related identifier in the data packet was described in draft-dong-teas-enhanced-vpn-vtn-scalability and other relevant documents. Currently there are several proposals about the encapsulation of network slice related identifiers. Based on that, this document further describes the considerations about the multi-domain IETF network slice scenario, and the interaction with other technical domains for 5G end-to-end network slicing. 

You are right that the path selection, resource allocation and traffic handling would be based on the identifiers internal to a network domain. As described in this draft, the end-to-end network slice identifier may be used for traffic monitoring at the end-to-end network slice granularity.

Best regards,
Jie

> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> Sent: Thursday, May 13, 2021 12:49 PM
> To: Dongjie (Jimmy) <jie.dong@huawei.com>om>; teas@ietf.org
> Subject: Re: [Teas] A draft on the framework for end-to-end IETF network
> slicing
> 
> It is not at all clear that any identifiers are needed inside the various networks,
> and specifically it is not clear that an internal identifier for the end-to-end
> network slice is needed at the level of the IETF network slice as is being defined
> by teas.  Since path selection, QoS parameter handling, and resource
> allocation needs to be handled in aggregate, it seems likely that no such
> identifier is needed.
> 
> Yours,
> Joel
> 
> On 5/12/2021 10:53 PM, Dongjie (Jimmy) wrote:
> > Hi WG,
> >
> > Recently we published a draft on the framework for end-to-end IETF
> > network slicing:
> > https://datatracker.ietf.org/doc/html/draft-li-teas-e2e-ietf-network-s
> > licing
> > <https://datatracker.ietf.org/doc/html/draft-li-teas-e2e-ietf-network-
> > slicing>
> >
> > This document describes the scenarios of end-to-end network slicing,
> > and the framework of network slice mapping between different network
> > segments and network domains. Multiple network slice related
> > identifiers are defined to covers different network scopes.
> >
> > The network slice related identifiers of different network scopes can
> > be instantiated with MPLS or IPv6 data plane, which are further
> > described in the following drafts:
> >
> > https://datatracker.ietf.org/doc/draft-li-mpls-e2e-ietf-network-slicin
> > g/
> > <https://datatracker.ietf.org/doc/draft-li-mpls-e2e-ietf-network-slici
> > ng/>
> >
> > https://datatracker.ietf.org/doc/html/draft-li-6man-e2e-ietf-network-s
> > licing
> > <https://datatracker.ietf.org/doc/html/draft-li-6man-e2e-ietf-network-
> > slicing>
> >
> > https://datatracker.ietf.org/doc/html/draft-li-spring-sr-e2e-ietf-netw
> > ork-slicing
> > <https://datatracker.ietf.org/doc/html/draft-li-spring-sr-e2e-ietf-net
> > work-slicing>
> >
> > Your review and comments are welcome. (Comments on the specific data
> > plane draft can go to the corresponding WG mail list).
> >
> > Best regards,
> >
> > Jie
> >
> >
> > _______________________________________________
> > Teas mailing list
> > Teas@ietf.org
> > https://www.ietf.org/mailman/listinfo/teas
> >