IETF Logo Mail Archive

Re: [spring] A new draft on Segment Routing for End-to-End IETF network slicing

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

Return-Path: <jie.dong@huawei.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBEA33A3528 for <spring@ietfa.amsl.com>; Fri, 14 May 2021 07:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 DS92S9eOCEhP for <spring@ietfa.amsl.com>; Fri, 14 May 2021 07:44:57 -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 1224C3A3526 for <spring@ietf.org>; Fri, 14 May 2021 07:44:57 -0700 (PDT)
Received: from fraeml705-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FhWGt6B3Mz6qnj2 for <spring@ietf.org>; Fri, 14 May 2021 22:33:26 +0800 (CST)
Received: from dggeme753-chm.china.huawei.com (10.3.19.99) by fraeml705-chm.china.huawei.com (10.206.15.54) 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 16:44:52 +0200
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme753-chm.china.huawei.com (10.3.19.99) 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 22:44:50 +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 22:44:49 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "xiechf@chinatelecom.cn" <xiechf@chinatelecom.cn>
CC: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] A new draft on Segment Routing for End-to-End IETF network slicing
Thread-Index: AddImA0It4733A5eRvyl5e+xCalORP//jdqA//9vaxA=
Date: Fri, 14 May 2021 14:44:49 +0000
Message-ID: <821fe091a4da47ff8c94bc34829283fc@huawei.com>
References: <61a99ced69074e269918557dd05d89ee@huawei.com> <0D0FAEF3-44BB-46B7-83ED-982C3ED65BB9@chinatelecom.cn>
In-Reply-To: <0D0FAEF3-44BB-46B7-83ED-982C3ED65BB9@chinatelecom.cn>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.189.141]
Content-Type: multipart/alternative; boundary="_000_821fe091a4da47ff8c94bc34829283fchuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/ZvcefyqdAmfckRf2-Y_vOq86MU4>
Subject: Re: [spring] A new draft on Segment Routing for End-to-End IETF network slicing
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2021 14:45:02 -0000

Hi Chongfeng,

Thanks for your valuable comments. The term “IETF network slice” was chosen by the network slicing design team in TEAS WG, after many discussion in both the design team and the WG.  This document tries to align with the terminology there.

I also agree that the terms in different SDOs needs to be aligned, or the relationship and mapping between different terms could be defined.

Best regards,
Jie

From: xiechf@chinatelecom.cn<mailto:xiechf@chinatelecom.cn> [mailto:xiechf@chinatelecom.cn]
Sent: Friday, May 14, 2021 5:18 PM
To: Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>
Cc: spring@ietf.org<mailto:spring@ietf.org>
Subject: Re: [spring] A new draft on Segment Routing for End-to-End IETF network slicing

Hi，Jie，
I think this work is useful and support its progress in spring or other WGs. However, I have some concerns about the term of "IETF slicing”, from the perspective of operator, the terms of “IETF slicing” and “3GPP slicing” may be confusing, there should be a universal set of terms of slicing across different SDOs, even they may cover different sections or layers of the network system.  What’s your opinion?

Best regards
Chongfeng


2021年5月14日 下午4:10，Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>> 写道：

Hi WG,

Recently we published a new draft on Segment Routing for End-to-End IETF Network Slicing:

https://datatracker.ietf.org/doc/html/draft-li-spring-sr-e2e-ietf-network-slicing

It introduces the new SRv6 behaviors and SR-MPLS BSIDs to enable the mapping and concatenation of multi-domain IETF network slices. This document is aligned with the framework for end-to-end IETF network slicing as described in draft-li-teas-e2e-ietf-network-slicing.

Your review and comments are welcome.

Best regards,
Jie
_______________________________________________
spring mailing list
spring@ietf.org<mailto:spring@ietf.org>
https://www.ietf.org/mailman/listinfo/spring

v2.23.0 | Report a Bug | By Email