Subject: [Netslices] 答复: some considerations for the next steps towards IETF101.

From: "Liguangpeng (Roc, Network Technology Laboratory)" <[email-masked]>
Date: Tue, 2 Jan 2018 01:26:19 +0000

Hi Alex

  I am glad to join the weekly Wednesday WebCall. Could you include me in the discussing?

Best Regards
Guangpeng Li

> -----邮件原件-----
> 发件人: Netslices [mailto:[email-masked]] 代表 Alex Galis
> 发送时间: 2017年12月23日 21:36
> 收件人: Network Slices <[email-masked]>
> 主题: Re: [Netslices] some considerations for the next steps towards IETF101.
> 
> Hi All
> 
> Please find enclosed some additional considerations for the next steps towards
> IETF101.
> 
> The two presentations at the last IETF100 have highlighted the following new
> needed work:
> 
> 1. Jari Arkko, Jeff Tantsura et all - Presentation: "Considerations on Network
> Virtualization and Slicing"
> (https://datatracker.ietf.org/meeting/100/materials/slides-100-rtgwg-sessa-dr
> aft-arkko-arch-virtualization/). Proposed new work:
> 
> • 1.1 Data models
> 
> • 1.2 Managing heterogeneous technologies, e.g., across SDN and
> traditionally built networks, or manage both general-purpose and very
> technology-specific virtualization parameters (e.g., VPNs + 5G radio)
> 
> • 1.3 New underlying VPN or API capabilities — e.g., ability to specify
> "statistical" rather than hard performance parameters
> 
> • 1.4 Cross-domain management and VPNs
> 
> • 1.5 Some terminology and conceptual alignment across industry would also
> be useful, e.g., to know what words to use in SLAs.
> 
> 
> 2. Liang Geng et all network slicing proponents - Presentation: "4 drafts from
> the netslicing proponents"
> (https://datatracker.ietf.org/meeting/100/materials/slides-100-opsawg-ietf10
> 0-netslicing-slides/). Proposed new work:
> 
> • 2.1 Review and feedback from the group and Update and consolidate drafts
> 
> • 2.2 Align terminologies among related drafts
> 
> • 2.3 (Common Operation and Management on network Slicing ) COMS-centric
> working items
> 
> •          2.3.1 Service delivery and network configuration model design
> (NBI/SBI of NS manager)
> 
> •          2.3.2 Interfaces and data model for Network slicing OAM
> interfaces and data models
> 
> o          Life-cycle management, fault detections, monitoring and etc.
> 
> o          Information exchange between multiple NS domain agents
> 
> •          2.3.3 Management capability exposure to NST
> 
> 
> 
> 3. Additional feedback from Benoit: he recommended for the next steps to
> better clarify the positioning of COMS work in relation to the following 4
> dimensions:
> 
> • 3.1 Better account of the 4 key elements used in COMS: connectivity,
> compute, storage resources + network & service functions
> 
> • 3.2 Better description of the functional blocks and heir positions used in
> COMS
> 
> • 3.3 FCAPS coverage
> 
> • 3.4 Coverage of the management of the dataplane
> 
> 
> 
> Taking into account all the above and in line with what was already discussed by
> Cristina/ Hannu/ Xavier/ Diego / Pedro / Kiran I trust that there is sufficient
> interest to progress on existing/new drafts for IETF101 and also as support for
> COMS BoF as follows:
> 
> Progress on existing COMS-centric drafts:
> 
> I.          consolidated management slicing architecture (i.e. issues 1.5, 2.2
> and 3.2) objective based on existing drafts:
> https://tools.ietf.org/html/draft-geng-netslices-architecture-02 and
> draft-geng-coms-problem-statement-01 )
> 
> II.         consolidation of COMS Information model (issues 1.1 and 3.1)
> based on existing draft
> https://www.ietf.org/internet-drafts/draft-qiang-coms-netslicing-information-
> model-01.txt)
> 
> III.       consolidation of subnet interconnections and slice compositions
> based on
> https://tools.ietf.org/id/draft-defoy-coms-subnet-interconnection-01.tx
> 
> IV.        Refinements of slice management requirements based on
> draft-netslices-usecases-02
> 
> V.         Refinements & consolidation of FCAP coverage – issue 3.3 - based
> on draft-flinck-slicing-management-00
> 
> 
> 
> Starting some new COMS-centric drafts:
> 
> 
> VI.        Service model mapping to an instance of a slice and its
> management – issue 2.3.1
> 
> VII.      Management capability exposure - issue 2.3.3 (i.e. this can be
> combined with (V)
> 
> VIII.     Cross domain management of slices -issue 1.4
> 
> IX.        Mapping COMS Information model to ACTN – issues 1.2, 3.4
> 
> 
> 
> Please note that “New underlying VPN or API capabilities” (issue 1.3 ) and how
> various existing IETF pieces fit together (service models... traffic engineering...
> detnetworking... ACTN…, VPN.++…) would be better addressed by RTG.
> 
> 
> 
> The NetSlicing proponents will start discussing and progressing the above work
> plan in weekly Wednesday at 13:00 London time WebCall starting with 10th
> January 2015. Please send an email if you are interested in joining our
> Netslicing proponents efforts.
> 
> Thank you in advance
> 
> 
> 
> May I take this opportunity to thank you for your support and work at IETF and
> to wish you all Best Seasonal Greetings, a Happy 2018 Year and relaxing and
> enjoyable vacation time.
> 
> 
> 
> Best Regards
> 
> Alex
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Netslices mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/netslices