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

[<[e-mail]>]

Hi Cristina,

Thank you for sharing the draft. Please find below some comments, fwiw:

(1) Section 4.2.1 mentions the following:


"the [SLA-Exchange<https://tools.ietf.org/html/draft-qiang-netslices-gap-analysis-00#ref-SLA-Exchange>] can be used to
   negotiate the SLAs and report on SLA events.  Further analysis is
   needed to provide a complete package.
"


Actually, this is not possible with [SLA-Exchange] given that document says explicitly: "The SLA negotiation and assurance is outside the scope of this document."

(2) Section 4.2.2. says the following:


   The NSRS requirement for reachability, direction, bandwidth

   requirements, performance metrics, traffic isolation constraints, and

   flow identification can be built utilizing protocol which can perform

   operations (read, write, notification, actions (aka rpcs)) on a yang

   service layer that supports these traffic engineer and resource

   definition at the service layers.  The network slicing service data

   model can extend existing work in the TEAS and I2RS working group for

   protocol-independent topology models.  These models support

   configuration or the dynamic datastores defined in [NMDA<https://tools.ietf.org/html/draft-qiang-netslices-gap-analysis-00#ref-NMDA>] which will

   be abbreviated as NMDA in this section.  This section provides the

   detail on how the NSRS can be built from these models and the

   RESTCONF protocol.

I'm a little bit puzzled here given that the NSRS is not about interacting with underlying network nodes. Especially, I'm not sure to understand the discussion about "protocol which can perform operations (read, write, notification, actions (aka rpcs))" in this context.


(3) Table 2:



·         Putting aside what is meant by "NS state monitoring", is there any particular reason "Mechanism/protocols for NS state monitoring;" is listed under NSRS? This is IMHO more an OAM issue.

·         Item "8) Mechanisms for on-demand, isolated, elastic and efficient network slice instantiation and resource association" is mysterious. I failed to find where that item is discussed in Section 6.

·         I'm not sure to understand what is meant by "10) Mechanisms for customized network slices".

·         Items 12 and 13 are not related to NS identification. Further, those are not discussed in the corresponding section.

Thank you.

Cheers,
Med

De : Netslices [mailto:[e-mail]] De la part de qiangli (D)
Envoyé : vendredi 2 juin 2017 11:36
À : [e-mail]
Objet : [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