Re: [Netslices] New Version Notification for draft-flinck-slicing-management-00.txt

["Flinck, Hannu (Nokia - FI/Espoo)" <[e-mail]>]

Hello Med and Liang

It was not our intention to tie the approach with the one use case you suggest below, namely single tenant per slice. However, even with a shared slice between multiple tenants a single tenant is likely to require customized view on the FCAPS of the slice per tenant’s SLA. Of course if a slice is a tool for  operator internal service optimization there is no need to expose slice KPIs to the end users.


Best regards
Hannu

From: GENG Liang [mailto:[e-mail]]
Sent: Thursday, July 06, 2017 1:43 PM
To: [e-mail]; Flinck, Hannu (Nokia - FI/Espoo) <[e-mail]>; [e-mail]
Subject: Re: Re: [Netslices] New Version Notification for draft-flinck-slicing-management-00.txt

Dear Med

I think "one single tenant per slice" and "multiple tenants per slice" are both valid slice arrangements. It is rather a implementation/business model choice of Network Slice Provider (Operator/infrastructure owner)  leasing infrastructures/resource/capabilities in different granularities.

The operator may use "multiple tenants per slice" approach to advertise the "eMBB","URLLC" slices. However for more customized requirements (i.e. a specific acceleration/CDN/sercurity ) from a AR gaming application vendor, operator may use  "one single tenant per slice" approach. The level of provisioning abilities exposed to the tenants would be different in these two cases and would be a interesting topic to be addressed in the future.

Best wishes
Liang


________________________________
Liang GENG
China Mobile Research Institute

From: [e-mail]<mailto:[e-mail]>
Date: 2017-07-05 21:52
To: Flinck, Hannu (Nokia - FI/Espoo)<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: Re: [Netslices] New Version Notification for draft-flinck-slicing-management-00.txt
Dear Flinck,

Thank you for sharing this draft.

I had the impression that you assume a "slices for sale" approach (or a "lease" network approach if you will) and that there is one single tenant for each instantiated network slice.

It is fine to cover this case (even if I have some concerns with it), but I do personally see slicing as an internal tool for a network provider to honor the needs of services/customer having common requirements. That is a network slice can be shared among multiple tenants/services. Doing so allows to rationalize the usage of resources within a network without requiring instantiated slices to linearly increase as a function of the tenants.

I don't see this second perspective reflected in your document.

Cheers,
Med

> -----Message d'origine-----
> De : Netslices [mailto:[e-mail]] De la part de Flinck,
> Hannu (Nokia - FI/Espoo)
> Envoyé : mardi 4 juillet 2017 17:56
> À : [e-mail]<mailto:[e-mail]>
> Objet : [Netslices] FW: New Version Notification for draft-flinck-slicing-
> management-00.txt
>
>
>
> A new version of I-D, draft-flinck-slicing-management-00.txt
> has been successfully submitted by Hannu Flinck and posted to the
> IETF repository.
>
> Name: draft-flinck-slicing-management
> Revision: 00
> Title: Network Slicing Management and Orchestration
> Document date: 2017-07-03
> Group: Individual Submission
> Pages: 10
> URL:            https://www.ietf.org/internet-drafts/draft-flinck-slicing-
> management-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-flinck-slicing-
> management/
> Htmlized:       https://tools.ietf.org/html/draft-flinck-slicing-
> management-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-flinck-
> slicing-management-00
>
>
> Abstract:
>    Network Slicing is worked in multiple SDOs from different view
>    points.  As network slicing is an end-to-end topic, this draft
>    proposes that network slices architecture [NS-Framework] aligns with
>    the work done in NGMN, 3GPP and ETSI with relation to management and
>    orchestration.  The key aspect that this draft makes is the rational
>    for role and need for Network Slice Management Function (NSMF) entity
>    that operates above Network Virtualization Function Orchestrator and
>    PNFs Management Functions.  NSMF needs to support different
>    abstractions of resources and to offer access to different management
>    entities.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
> _______________________________________________
> Netslices mailing list
> [e-mail]<mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/netslices

_______________________________________________
Netslices mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/netslices