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

Igor Bryskin <Igor.Bryskin@huawei.com> Sat, 03 June 2017 18:06 UTC

Return-Path: <Igor.Bryskin@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 A067E12EB5E for <netslices@ietfa.amsl.com>; Sat, 3 Jun 2017 11:06:28 -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 Cq6dKP4R4oyC for <netslices@ietfa.amsl.com>; Sat, 3 Jun 2017 11:06:26 -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 5BDB212EB42 for <NetSlices@ietf.org>; Sat, 3 Jun 2017 11:06:25 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DOI86761; Sat, 03 Jun 2017 18:06:22 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Sat, 3 Jun 2017 19:06:21 +0100
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.117]) by SJCEML701-CHM.china.huawei.com ([169.254.3.56]) with mapi id 14.03.0235.001; Sat, 3 Jun 2017 11:05:16 -0700
From: Igor Bryskin <Igor.Bryskin@huawei.com>
To: "comscape@gmail.com" <comscape@gmail.com>, "liang.geng@hotmail.com" <liang.geng@hotmail.com>, "sebastian.thalanany@ieee.org" <sebastian.thalanany@ieee.org>, "qiangli (D)" <qiangli3@huawei.com>, "NetSlices@ietf.org" <NetSlices@ietf.org>
Thread-Topic: [Netslices] draft-qiang-netslices-gap-analysis-00 Uploaded
Thread-Index: AQHS3BQas7agLHm0IUWSL8LHsakC16ITb8BS
Date: Sat, 03 Jun 2017 18:05:16 +0000
Message-ID: <etPan.5932fa68.df270ba.44e4@localhost>
References: <06C389826B926F48A557D5DB5A54C4ED29BB624F@SZXEMI507-MBS.china.huawei.com>, <007d01d2dba4$63c21930$2b464b90$@gmail.com> <HK2PR06MB0913CB13A7089DE72A48D2AE87F70@HK2PR06MB0913.apcprd06.prod.outlook.com>, <00e601d2dc14$084b60a0$18e221e0$@gmail.com>
In-Reply-To: <00e601d2dc14$084b60a0$18e221e0$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_etPan5932fa68df270ba44e4localhost_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.5932FA9F.005C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.4.117, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 0dd1dd2fe2cbbf7b7cad50de8ba3d9dd
Archived-At: <https://mailarchive.ietf.org/arch/msg/netslices/KQufJJoInrZqfejksn6PpbNX7f4>
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: Sat, 03 Jun 2017 18:06:28 -0000

Hi,

I think "3.3.1 Reclusiveness" should me replaced with "3.3.1 Recursiveness" .

Cheers,
Igor
From:sebastian
To:'GENG Liang','sebastian.thalanany',qiangli (D),NetSlices@ietf.org,
Date:2017-06-02 22:50:04
Subject:Re: [Netslices] draft-qiang-netslices-gap-analysis-00 Uploaded

Hello, Liang,

Thanks for the reference draft.
The terminology with respect to the various aspects of a network slice and related abstractions, look good.

In several sections of the draft there are references to the term ‘operator’, in different contexts.

A generalized distinction, in terms of NSP and SP would be relevant in the draft, from a forward-looking perspective, where domain owners may either just be an NSP or an SP, or an SP that also behaves as an NSP.
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

Happy to scrub the text, with tracked changes with generalized terminology that uses SP and NSP, instead of ‘operator’

Many thanks.
-Sebastian


From: GENG Liang [mailto:liang.geng@hotmail.com]
Sent: Friday, June 2, 2017 3:59 PM
To: sebastian.thalanany <sebastian.thalanany@ieee.org>; 'qiangli (D)' <qiangli3@huawei.com>; NetSlices@ietf.org
Subject: Re: Re: [Netslices] draft-qiang-netslices-gap-analysis-00 Uploaded

Hi Sebastian,

We have defined term with similar generalization concernsin Architecture draft. All other rnetslices draft is referring to these terminologies. This document can be find here
https://tools.ietf.org/html/draft-geng-netslices-architecture-01


Best wishes
Liang

________________________________
Liang GENG
China Mobile Research Institute

From: sebastian<mailto:comscape@gmail.com>
Date: 2017-06-02 21:30
To: 'qiangli \(D\)'<mailto:qiangli3@huawei.com>; NetSlices@ietf.org<mailto: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