IETF Logo Mail Archive

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

"Dongjie (Jimmy)" <jie.dong@huawei.com> Mon, 17 May 2021 09:28 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 37CF63A3045 for <teas@ietfa.amsl.com>; Mon, 17 May 2021 02:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level:
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 Co2gop37wzQJ for <teas@ietfa.amsl.com>; Mon, 17 May 2021 02:28:20 -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 6D0C43A3041 for <teas@ietf.org>; Mon, 17 May 2021 02:28:20 -0700 (PDT)
Received: from fraeml738-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FkD9c59t4z6rmGh; Mon, 17 May 2021 17:19:48 +0800 (CST)
Received: from dggeme751-chm.china.huawei.com (10.3.19.97) by fraeml738-chm.china.huawei.com (10.206.15.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Mon, 17 May 2021 11:28:16 +0200
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme751-chm.china.huawei.com (10.3.19.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Mon, 17 May 2021 17:28:15 +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; Mon, 17 May 2021 17:28:14 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Jeff Tantsura <jefftant.ietf@gmail.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+KTBWZMMOaXQaqcQBH+LkAAI5YtbA=
Date: Mon, 17 May 2021 09:28:14 +0000
Message-ID: <fe82678b59664a9b9113402250d74b98@huawei.com>
References: <c7bb7462db8f4149912d644adbd4760b@huawei.com> <49ca2ff9-6530-44d7-888e-fa88b7e0a060@Spark>
In-Reply-To: <49ca2ff9-6530-44d7-888e-fa88b7e0a060@Spark>
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: multipart/alternative; boundary="_000_fe82678b59664a9b9113402250d74b98huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/xSMjXM0Rr9-gctajwx5vVMYpdy4>
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: Mon, 17 May 2021 09:28:25 -0000

Hi Jeff,

Thanks for your comments and suggestion.

This document mainly describes the mapping of end-to-end IETF network slices and 5G end-to-end network slices to the multi-domain and intra-domain VTNs in the underlay, this is reflected by “e2e-ietf-network-slicing” in the draft name.

I understand your point is to add “VTN” in the draft name, we will think about it.

Best regards,
Jie

From: Jeff Tantsura [mailto:jefftant.ietf@gmail.com]
Sent: Saturday, May 15, 2021 5:14 AM
To: teas@ietf.org; Dongjie (Jimmy) <jie.dong@huawei.com>
Subject: Re: [Teas] A draft on the framework for end-to-end IETF network slicing

Jie,

I think, it would have been more appropriate to have “vtn/vtn-id” in the draft name, rather than "e2e-ietf-network-slicing"

Cheers,
Jeff
On May 12, 2021, 7:54 PM -0700, Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>, 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-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-slicing/

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-network-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<mailto:Teas@ietf.org>
https://www.ietf.org/mailman/listinfo/teas

v2.23.0 | Report a Bug | By Email