IETF Logo Mail Archive

Re: [Netslices] draft-qiang-netslices-gap-analysis-00 Uploaded

"qiangli (D)" <qiangli3@huawei.com> Mon, 05 June 2017 02:00 UTC

Return-Path: <qiangli3@huawei.com>
X-Original-To: netslices@ietfa.amsl.com
Delivered-To: netslices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE9F7124D6C for <netslices@ietfa.amsl.com>; Sun, 4 Jun 2017 19:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 kA4PvonFsklO for <netslices@ietfa.amsl.com>; Sun, 4 Jun 2017 19:00:27 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 962EE124B0A for <NetSlices@ietf.org>; Sun, 4 Jun 2017 19:00:26 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DHX03453; Mon, 05 Jun 2017 02:00:25 +0000 (GMT)
Received: from SZXEMI413-HUB.china.huawei.com (10.86.210.41) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 5 Jun 2017 03:00:24 +0100
Received: from SZXEMI507-MBS.china.huawei.com ([169.254.7.88]) by SZXEMI413-HUB.china.huawei.com ([10.86.210.41]) with mapi id 14.03.0235.001; Mon, 5 Jun 2017 10:00:20 +0800
From: "qiangli (D)" <qiangli3@huawei.com>
To: "sebastian.thalanany@ieee.org" <sebastian.thalanany@ieee.org>, "NetSlices@ietf.org" <NetSlices@ietf.org>
Thread-Topic: [Netslices] draft-qiang-netslices-gap-analysis-00 Uploaded
Thread-Index: AdLbg6wkZDvFET2IQnSWu3FhZDRtRv//u1GA//uGX7A=
Date: Mon, 05 Jun 2017 02:00:20 +0000
Message-ID: <06C389826B926F48A557D5DB5A54C4ED29BB642E@SZXEMI507-MBS.china.huawei.com>
References: <06C389826B926F48A557D5DB5A54C4ED29BB624F@SZXEMI507-MBS.china.huawei.com> <007d01d2dba4$63c21930$2b464b90$@gmail.com>
In-Reply-To: <007d01d2dba4$63c21930$2b464b90$@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.163.138]
Content-Type: multipart/alternative; boundary="_000_06C389826B926F48A557D5DB5A54C4ED29BB642ESZXEMI507MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090205.5934BB39.0073, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.7.88, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 2a81c57f96bcd33d7421b85a14dc4407
Archived-At: <https://mailarchive.ietf.org/arch/msg/netslices/AtD3K4ORs7ZQQql47pq__nVkWOM>
Subject: Re: [Netslices] draft-qiang-netslices-gap-analysis-00 Uploaded
X-BeenThere: netslices@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This list is intended for discussion and review of network slicing at IETF." <netslices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netslices>, <mailto:netslices-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netslices/>
List-Post: <mailto:netslices@ietf.org>
List-Help: <mailto:netslices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netslices>, <mailto:netslices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jun 2017 02:00:30 -0000

Hi Sebastian,

Good point. As we stated in Sec. 2, all of the network slicing related terminology used in the gap-analysis doc. have been defined in draft-geng-netslices-architecture-01.

Best regards,

Cristina QIANG

From: sebastian [mailto:comscape@gmail.com]
Sent: Friday, June 02, 2017 9:30 PM
To: qiangli (D); NetSlices@ietf.org
Subject: RE: [Netslices] draft-qiang-netslices-gap-analysis-00 Uploaded

Dear Colleagues,

Thanks for delineating the prominent aspects of network slicing.

Here are some thoughts on terminology.

With the diverse nature of services in the 5G realm, where XaaS (Anything as a Service) is an emerging paradigm, perhaps some of the legacy terminology may need to be generalized.
For example, the term 'operator' was typically used with reference to various types of 'access' modalities.

In NGMN, such terminology is being generalized.
NSP : Network Service Provider (instead of 'operator'): This entity only provides 'access' type of services
SP: Service Provider: This entity provides any service above the network layer, but may also behave as an NSP

Best wishes.
-Sebastian


From: Netslices [mailto:netslices-bounces@ietf.org] On Behalf Of qiangli (D)
Sent: Friday, June 2, 2017 4:36 AM
To: NetSlices@ietf.org<mailto:NetSlices@ietf.org>
Subject: [Netslices] draft-qiang-netslices-gap-analysis-00 Uploaded


Dear All,



We have upload "Gap Analysis for Network Slicing" draft 00 on https://datatracker.ietf.org/doc/draft-qiang-netslices-gap-analysis/?include_text=1

Your comments and reviews are greatly appreciated.



Abstract:

   This document presents network slicing differentiation from the non-

   partition network or from simply partition of connectivity resources.

   It lists 15 standardization gaps related to 6 key requirements for

   network slicing.  It also presents an analysis of existing related

   work and other potential solutions on network slicing.



   This gap analysis document aims to provide a basis for future works

   in network slicing.

Best regards,

Co-authors

v2.23.0 | Report a Bug | By Email