[Teas-ns-dt] 答复: Definition of transport network slicing

"Aijun Wang" <wangaijun@tsinghua.org.cn> Thu, 17 October 2019 01:10 UTC

Return-Path: <wangaijun@tsinghua.org.cn>
X-Original-To: teas-ns-dt@ietfa.amsl.com
Delivered-To: teas-ns-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25A301200EB for <teas-ns-dt@ietfa.amsl.com>; Wed, 16 Oct 2019 18:10:30 -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, DC_PNG_UNO_LARGO=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 V1KlOGUJRMAA for <teas-ns-dt@ietfa.amsl.com>; Wed, 16 Oct 2019 18:10:27 -0700 (PDT)
Received: from m176115.mail.qiye.163.com (m176115.mail.qiye.163.com [59.111.176.115]) by ietfa.amsl.com (Postfix) with ESMTP id 0A66D120019 for <teas-ns-dt@ietf.org>; Wed, 16 Oct 2019 18:10:24 -0700 (PDT)
Received: from WangajPC (unknown [219.142.69.77]) by m176115.mail.qiye.163.com (Hmail) with ESMTPA id 7A58466427C; Thu, 17 Oct 2019 09:10:19 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: "'Rokui, Reza (Nokia - CA/Ottawa)'" <reza.rokui@nokia.com>, "'Dongjie (Jimmy)'" <jie.dong@huawei.com>, teas-ns-dt@ietf.org
References: <23F39B19-B3FE-4F67-BCB2-4C4891A591AB@nokia.com>
In-Reply-To: <23F39B19-B3FE-4F67-BCB2-4C4891A591AB@nokia.com>
Date: Thu, 17 Oct 2019 09:10:19 +0800
Message-ID: <019d01d58487$a50d95c0$ef28c140$@org.cn>
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----=_NextPart_000_019E_01D584CA.B330D5C0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHVhCmLNkwDr32fR0W4Hi17u6EzmKdeAz5Q
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgYFAkeWUFZVktVSkxOQkJCTEtKS0lISktJWVdZKF lBSkxLS0o3V1ktWUFJV1kJDhceCFlBWTU0KTY6NyQpLjc#WQY+
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6Oi46Mjo6ITg*TT49NBcpECEx GR8wCQNVSlVKTkxKSUxPTUlITk1LVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxMWVdZCAFZQUlLSUxLTjcG
X-HM-Tid: 0a6dd743faec9373kuws7a58466427c
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-ns-dt/RCVvi_kpr9JOaF8y8jCB9nHUxJs>
Subject: [Teas-ns-dt] 答复: Definition of transport network slicing
X-BeenThere: teas-ns-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TEAS Network Slicing Design Team <teas-ns-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas-ns-dt>, <mailto:teas-ns-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas-ns-dt/>
List-Post: <mailto:teas-ns-dt@ietf.org>
List-Help: <mailto:teas-ns-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas-ns-dt>, <mailto:teas-ns-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2019 01:10:31 -0000

Hi, Reza,Jie and all:

For the transport, do we need to emphasize the isolation? Is any solution that can meet the application’ SLA  acceptable?

>From the 5G document, the isolation concept refer mainly to its functional entities.

 

Best Regards.

 

Aijun Wang

China Telecom

 

发件人: teas-ns-dt-bounces@ietf.org [mailto:teas-ns-dt-bounces@ietf.org] 代表 Rokui, Reza (Nokia - CA/Ottawa)
发送时间: 2019年10月16日 21:57
收件人: Dongjie (Jimmy); teas-ns-dt@ietf.org
抄送: Rokui, Reza (Nokia - CA/Ottawa)
主题: Re: [Teas-ns-dt] Definition of transport network slicing

 

Hi Jie and all,

 

Your definition is correct. However, the following is my view. Please add comments.

 

In general a transport slice has a definition and a realization (aka implementation). The transport slice definition is whatever Jie mentioned below and I rephrase it here. i.e. 

*	Transport slice definition: A set of connections each with appropriate isolation and specific Service Level Agreement (SLA). 

 

However an transport slice has an implementation (or realization) as well. To clarify, let’s have an example.

The following picture shows the most complex 5G network (i.e. Cloud RAN where it contains fronthaul, midhaul and backhaul networks. In this picture there are 4 different transport slices for a single E2E network slice. 

 

Each of transport slices 1 to 4 has an implementation which potentially has different technologies and different techniques. For example, the transport slice 3 can be realized on IP network using L3VPN or VPN+ or any other techniques to satisfy certain SLAs. The fact is that we can realize the transport slice 3 using different techniques but the regardless of that, the definition of the transport slice 3 does not change (which is connectivity of CUs to Core network).

 

Another example is the transport slice 2 in midhaul which its definition is connectivity between DUs to CUs. In majority of  deployments, this transport slice will be realized using PON technique or IP VPNs. Again regardless of implementation, the transport slice 2’s definition is DUs to CUs connectivity with certain SLAs.

 

If needed, I can present a few slides during our call on Oct 17th. 

 

Cheers,

Reza

 

 



 

 

 

From: Teas-ns-dt <teas-ns-dt-bounces@ietf.org> on behalf of "Dongjie (Jimmy)" <jie.dong@huawei.com>
Date: Monday, October 14, 2019 at 5:57 PM
To: "teas-ns-dt@ietf.org" <teas-ns-dt@ietf.org>
Subject: [Teas-ns-dt] Definition of transport network slicing

 

Hi, 

 

As one of the action points of the design team conference call in last week, we will discuss and give the definition of transport network slicing. Here I’d like to reference the definition in https://tools.ietf.org/html/draft-ietf-teas-enhanced-vpn-03 as the starting point:

 

“A transport network slice is a virtual (logical) network with a particular network topology and a set of shared or dedicated network resources, which are used to provide the network slice consumer with the required connectivity, appropriate isolation and specific Service Level Agreement (SLA). “

 

Please feel free to provide your comments and suggestions. 

 

Best regards,

Jie