Feature Tracking

Introduction

Current mirror date: 2019.05.20

This page is a mirror of the Feature Tracking page on the NFV private wiki. Information on the private wiki page is frequently updated, whilst the present page is regularly mirrored. Links to contributions will require authentication with an ETSI Online Account.

Introduction

Some introduction will be put here including guidelines, process description and tutorials.

• Link to Release 3 implementation process
  • Link to the "consolidated IFA Release 3 Feature plan". Refer to NFVIFA(17)000914 and revisions. Latest version NFVIFA(17)000914r4
• Training for Feature Primes
  • Process
  • Wiki editing
• Naming conventions: e.g. FEAT00_IFA007_[Contribution name]
• To build a link to all contributions belonging to a feature, replace FEAT99 in the link stated below with the Feature short name for your feature e.g. FEAT15:

 https://portal.etsi.org/Contribution.aspx?Tb_Id=789&searchText=FEAT99&IncludeSubTb=True&sort=pk_contribution&sortorder=DESC&NbItemsPerPage=50&Year=2017,2018

• Note: Agreed content can be added to Pseudo meeting --> If the access is restricted, this may only work within a workgroup.
• Related/Dependent Features: Please indicate other features which relate to the ongoing work. Details can be given in the implementation plan or in the issues section.

FEATxx: Feature Title

Overview

Feature Prime	Name, Company, E-Mail
Feature description	Short Description of the Feature
Target Release	Release 3 (2018-X-X)
Impacted WIs	IFAxx, IFAyy, SOLzz
MegaCRs	IFAxxx MegaCR NFVIFA(18)000xxx (CR Status) IFAyyy MegaCR NFVIFA(18)000yyy (CR Status)
Related/Dependent Features	FEATxx FEATyy
Status	Ongoing (0% complete)
Contributions	All feature contributions Agreed content
Feature team	Name (Company)
Last Updated	20xx-xx-xx

Implementation Plan

Items to consider in the implementation plan

• Detailed description what has to be done in which work item.
• Timeplan of when the team plans to conclude a particular action in the implementation plan.

IFA

ID	Action	Impacted WG(s)	Target completion	Status
001	Add interface X in to IFA007. CR draft [LINK]	IFA	March-2018	Open

SOL

ID	Action	Impacted WG(s)	Target completion	Status
001	Add interface X in to SOL001. CR draft [LINK]	SOL	March-2018	Open

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT03: NFVI software modification

Overview

Feature Prime	Maria Toeroe, Ericsson.
Feature description	This feature addresses the support for the coordination of the NFVI software modification process with the VNFs hosted on the NFVI in order to minimize impact on service availability.
Target Release	Release 3 drop 2 (2019-X-X)
Impacted WIs	IFA005, IFA006, IFA007, IFA008, IFA010, IFA011
MegaCRs	IFA010: NFVIFA(19)000038r3 Baseline (Agreed in IFA#150) IFA011: NFVIFA(19)000039r5 Baseline (Agreed in IFA#144) IFA006: NFVIFA(19)000040r2 Baseline IFA005: IFA007: IFA008:
Related/Dependent Features	N/A
Status	Ongoing (85% complete)
Contributions	All feature contributions Agreed content
Feature team	Maria Toeroe (Ericsson) Stefan Arntzen (Huawei) Shaoji Ni (Huawei) Mehmet Toy (Verizon) Gerald Kunzmann (DOCOMO)
Last Updated	2019-01-25

Implementation Plan

Items to consider in the implementation plan

• Detailed description what has to be done in which work item.
• Timeplan of when the team plans to conclude a particular action in the implementation plan.

ID	Action	Impacted WG(s)	Target completion	Status
001	Based on REL006 add functionality description of NFVI software modification support to IFA010 for the VIM, VNFM and NFVO. CR Drafts: NFVIFA(18)000283r2 Status: Obsolete NFVIFA(18)000285r5 Status: Agreed NFVIFA(18)000631r4 Status: Agreed NFVIFA(18)000875r2 Status: Obsolete NFVIFA(19)000092r1 Status: Agreed FEAT (IFA#141) NFVIFA(19)000287r3 Status: Agreed FEAT (IFA#148) NFVIFA(19)000345r2 Status: Agreed FEAT (IFA#149) NFVIFA(19)000384r3 Status: candidate for Agreed FEAT in IFA#152 NFVIFA(19)000400r1 Status: candidate for Agreed FEAT in IFA#152 NFVIFA(19)000426r2 Status: candidate for Agreed FEAT in IFA#152	IFA010	November-2018	Started
002	Based on REL006 specify the requirements for an interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vi reference point	IFA005	December-2018	Open
003	Based on REL006 specify the requirements for an interface for the coordination of the NFVI software modifications with the hosted VNFs on the Vi-Vnfm reference point	IFA006	December-2018	Open
004	Based on REL006 specify the requirements for an interface for the coordination of the NFVI software modifications with the hosted VNFs on the Ve-Vnfm reference point	IFA008	December-2018	Open
005	Based on REL006 specify the requirements for an interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vnfm reference point	IFA007	December-2018	Open
006	Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vi reference point. CR Drafts: NFVIFA(18)000763 Status: Obsolete NFVIFA(19)000003r1 NFVIFA(19)000052r1	IFA005	November-2018	Started
007	Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Vi-Vnfm reference point. CR Drafts: NFVIFA(18)000296r9 Status: Agreed NFVIFA(18)000762r1 Status: Obsolete NFVIFA(18)000987r18 Status: Withdrawn NFVIFA(18)0001053r4 Status: Agreed NFVIFA(18)0001054r4 Status: Agreed NFVIFA(19)000033 Status: Agreed NFVIFA(19)000066r14 Status: NOTED (IFA#144) NFVIFA(19)000067r7 Status: NOTED (IFA#144) NFVIFA(19)000068r6 Status: NOTED (IFA#144) NFVIFA(19)000318r4 Status: Agreed FEAT (IFA#148)	IFA006	November-2018	Started
008	Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Ve-Vnfm reference point. CR Drafts: NFVIFA(18)000761 Status: Obsolete NFVIFA(18)000990r10 NFVIFA(18)000991r10 NFVIFA(18)000989r7 NFVIFA(19)000002r6 Status: replaced by NFVIFA(19)000241 NFVIFA(19)000075 Status: Withdrawn NFVIFA(19)000102r8 Status: Agreed FEAT (IFA#144) NFVIFA(19)000240 Status: Noted (IFA#144) NFVIFA(19)000241 Status: Noted (IFA#144)	IFA008	November-2018	Started
009	Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vnfm reference point. CR Drafts: NFVIFA(18)000764 Status: Obsolete NFVIFA(19)000004 NFVIFA(19)000069 Status: Agreed FEAT (IFA#141) NFVIFA(19)000260 Status: Noted (IFA#144)	IFA007	November-2018	Started
010	Specify the VNF constraints parameters for NFVI software modifications in the VNFD. CR Drafts: NFVIFA(18)000456r5 Status: Agreed FEAT (IFA#129) NFVIFA(18)000873r3 Status: Agreed FEAT (IFA#129) NFVIFA(19)000091 Status: Agreed FEAT (IFA#141) NFVIFA(19)000090r2 Status: Agreed FEAT (IFA#144) NFVIFA(19)000087 Status: Agreed FEAT (IFA#141) NFVIFA(19)000265r1 Status: Agreed FEAT (IFA#144) NFVIFA(19)000319r3 Status: Agreed FEAT (IFA#148)	IFA011	November-2018	Started

Issues

List of issues raised based on the feature implementation.

Security Considerations

Security considerations for the feature are in NFVIFA(19)000036r2

FEAT06: Enhancement Network Service (NS) Package

Overview

More information and current status can be found on the wiki for FEAT06NSPackage

Feature Prime	Bhumip Khasnabish (ZTE), Haibin Chu (Ericsson) and Yaoye Zhang (Huawei)
Feature description	An NS Package is an archive including the meta-model descriptors NSD and other files (scripts, security materials, possible rules, policies, NS over multi-tenants, etc.), that are required to manage an NS from design to test/verification to validation/certification to runtime management; the holistic end-to-end NS lifecycle, as discussed in NFV(17)000247.
Target Release	same as DGS/NFV-SOL007 (1H-2019)
Impacted WIs	IFA010, IFA012 (TBC), IFA013, and IFA014. Note-1: We identify the impacted specifications in IFA WG only. The impacted specifications in other WGs (e.g. SOL, TST, SEC, REL, etc) needs to be addressed separately and the chairs of SOL and TST WGs have been informed. We will follow up the impacts on SEC and REL WGs. Note-2: The impact on IFA012 is dependent on the ISG's decision whether IFA012 is released as GS or GR by the end of Y2017.
Mega-CRs	IFA010 [not available] IFA012 [not available] IFA013 [not available] IFA014 [not available]
Related/Dependent Features	FEATxx FEATyy
New Specification	No new WI is expected in IFA WG. Name of New Specification in SOL WG is DGS/NFV-SOL007 (NSD file structure spec., based on NFVIFA(18)000174/NFVIFA(17)000879, NFVSOL(17)000711 and NFV(18)000066/NFV(17)000364; created on 2018-03-01 and approved on 2018-03-12).] The scope of this work item [DGS/NFV-SOL007] is to specify the Network Service Descriptor file structure and naming conventions for the different files, fulfilling the requirements specified in ETSI GS NFV-IFA 014. The work item deliverable will contain normative provisions. WI Status [In Progress; to be completed by 1H-2019].
Status	Ongoing (as DGS/NFV-SOL007)
Contributions	All feature contributions Agreed content
Feature team	Bhumip Khasnabish (ZTE) Haibin Chu (Ericsson) Yaoye Zhang (Huawei) Maopeng Zhang (ZTE) Lingli Deng (CMCC)
Last Updated	2018-10-01

Implementation Plan

Items to consider in the implementation plan

• Detailed description what has to be done in which work item.
• Timeplan of when the team plans to conclude a particular action in the implementation plan.

ID	Action	Impacted WG(s)	Target completion	Status
001	Add use case description of NS packaging to IFA014 Annex. CR draft NFVIFA(17)000956r10	IFA014	Same as in DGS/NFV-SOL007	Started
002	Update the NS packaging requirement in IFA014.Add a new clause 5.X to describe the NS packaging requirement, including the NS packaging structure, content, identification, integrity, etc. CR draft NFVIFA(17)000959r8	IFA014	Same as in DGS/NFV-SOL007	Started
003	Update the functional requirements on NFVO in IFA010. Add new functional requirements on NFVO about NS package management by either adding a new clause (e.g. 6.6.X) or updating the existing clause (i.e. 6.6.1). CR draft NFVIFA(17)000958r5	IFA010	Same as in DGS/NFV-SOL007	Started
004	Update the interface requirement on NSD or NS package management interface in IFA013. Add new requirements of NS package management interface by either adding a new clause (i.e. 5.3.X) or updating the existing clause (i.e. 5.3.1). CR draft NFVIFA(17)000947r2	IFA013	Same as in DGS/NFV-SOL007	Started
005	Update the existing NSD management interface or add a new NS Package management interface in IFA013. Add new operations and notifications related to NS package management interface by either adding a new clause (i.e. 7.X) or updating the existing clause (i.e. 7.2). Current PNFD management may be updated as well based on the requirement discussion in action #002. CR draft NFVIFA(17)000947r2	IFA013	Same as in DGS/NFV-SOL007	Started
006	Update the NSD management related chapters in IFA012, if the IFA012 is released as GS in Rel.2. CR draft [LINK]	IFA012	Same as in DGS/NFV-SOL007	Open

Issues

List of issues raised based on the feature implementation.

•Below technical issues are identified:
->Current PNFD has its own management operations, e.g. On-board PNFD, etc.
­->After the concept of NS package enhancement is introduced, the issue of merging them into NS package management operations needs to be addressed.
->The issue of backward compatibility with current NSD management interface needs to be addressed.

•The impacts on SOL WG have been discussed.
A new SOL work item [DGS/NFV-SOL007 (NSD file structure spec.)] has been created based on NFVIFA(18)000174/NFVIFA(17)000879, NFVSOL(17)000711 and NFV(18)000066/NFV(17)000364
While the impacts on TST, SEC and REL WGs need to be discussed.

Security Considerations

List of security considerations implied by the feature (to be determined).

FEAT12: Enhancement support for MEC in NFV deployments

Overview

Feature Prime	Uwe Rauschenbach, Nokia
Feature description	Update to selected NFV interfaces. The intent is to define extensions which can be used to specify how ETSI MEC can be deployed in an NFV environment, allowing to run MEC applications on the NFVI besides VNFs, and re-using ETSI NFV MANO components to perform common MANO tasks on the MEC applications. 3 parts: Small Os-Ma enhancements (to be started, waiting for MEC requirements) Small Ve-Vnfm enhancements (finalized, can re-use LCM coordination interface that has been defined as part of updating FEAT15 in IFA008ed321) Support for Non-MANO artifact sets in VNF package (finalized IFA011/SOL004 ed251)
Target Release	Release 3 (2019)
Impacted WIs	IFA013, IFA008, IFA011, SOL005, SOL002, SOL004
MegaCRs	For part 3: Related content already included in Rel 2 maintenance (V 2.4.1) For part 2 NFVIFA(18)001024r2 for IFA008ed321 For part 1 IFAxxx MegaCR NFVIFA(18)000xxx (not available)
Related/Dependent Features	FEAT15 (LCM coordination interface that is part of VNF Snapshot)
Status	Ongoing (70% complete)
Contributions	All feature contributions NFVIFA(17)000900r3_IFA011ed241_3rd_party_VNF_Package_extensions NFVSOL(17)000585r3_SOL004_non_MANO_artifact_sets NFVIFA(18)0001024r2_IFA008ed321_-_Remove_ConfirmVnfSnapshot__Add_LCM_Coordinatio Agreed content NFVIFA(17)000900r3_IFA011ed241_3rd_party_VNF_Package_extensions NFVSOL(17)000585r3_SOL004_non_MANO_artifact_sets NFVIFA(18)0001024r2_IFA008ed321_-_Remove_ConfirmVnfSnapshot__Add_LCM_Coordinatio
Feature team	Uwe Rauschenbach, Nokia Yang Xu, Huawei Pekka Kuure, Nokia Anatoly Andrianov, Nokia
Last Updated	2019-02-18

Implementation Plan

Items to consider in the implementation plan

• Detailed description what has to be done in which work item.
• Timeplan of when the team plans to conclude a particular action in the implementation plan.

ID	Action	Impacted WI(s)	Target completion	Status
001	Add needed MEC extensions to IFA013 (placement control).	IFA013	tbd	Open
002	Add needed MEC extensions to SOL005 (placement control).	SOL005	tbd	Open
003	Add requirement for 3rd party VNF package extension mechanism to IFA011.	IFA011	Feb 2018	Complete
004	Add specification for 3rd party VNF package extension mechanism to SOL004.	SOL004	Feb 2018	Complete
005	Add needed MEC extensions to IFA008 (graceful termination).	IFA008	Feb 2019	Complete, pending MEC confirmation
006	Add needed MEC extensions to SOL002 (to allow standardizing graceful termination).	SOL002	tbd	Open

Issues

Delay on MEC side in providing requirements.

Security Considerations

List of security considerations implied by the feature.

FEAT16: Service Availability Level

Overview

Feature Prime	Stefan Arntzen, Huawei.
Feature description	This feature adds the functions needed to assign resources with defined reliability characteristics to NSs with special reliability requirements. It also allows to achieve an optimized assignment of resources with defined availability characteristics to multiple VNFs and NSs (belonging to the same slice)
Target Release	Release 3 drop 3
Impacted WIs	IFA010, IFA005, IFA006, IFA007, IFA014
MegaCRs	TODO
Related/Dependent Features	N/A
Status	Ongoing (40% complete)
Contributions	All feature contributions Agreed content
Feature team	Shaoji Ni (Huawei) Stefan Arntzen (Huawei)
Last Updated	2019-05-13

Implementation Plan

Items to consider in the implementation plan

• Detailed description what has to be done in which work item.
• Timeplan of when the team plans to conclude a particular action in the implementation plan.

ID	Action	Impacted WG(s)	Target completion	Status
001	Add terminology of the “service availability level (SAL)” and explain difference between FEAT05 Slicing NFVIFA(18)000970 Status: Agreed FEAT (IFA#127) NFVIFA(19)000402r1 Status: Drafting call agreed (FEAT16#5)	IFA010	November-2018	Ongoing
002	Specify requirements for the VIM to support the capability for supporting SAL for the assignment/reservation of resources. Specify requirements for the NFVO/VNFM to support SAL for requesting the assignment/reservation of resources. NFVIFA(18)0001027r1 Status: Agreed FEAT (IFA#133) NFVIFA(19)000274r1] Status: Noted, replaced by NFVIFA(19)000306 (IFA#144) NFVIFA(19)000296r1] Status: Noted (IFA#145) NFVIFA(19)000306r5 Status: Agreed FEAT (IFA#150) NFVIFA(19)000307r7 Status: Agreed FEAT (IFA#149) NFVIFA(19)000309r2 Status: Agreed FEAT (IFA#148) NFVIFA(19)000310r5 Status: Agreed FEAT (IFA#148) NFVIFA(19)000311r2 Status: Agreed FEAT (IFA#148)	IFA010	November-2018	Ongoing
003	Specify requirements for an NFVI resource management on the Or-Vi/Vi-Vnfm to support SAL for the assignment/reservation of resources.	IFA005/006	December-2018	Open
004	Add the parameter of SAL into “VnfDF”, “vdu profile”, “VirtualLinkDescFlavour” of VNFD NFVIFA(19)000357r2	IFA011	December-2018	Open
005	Add a requirement and the parameter of SAL into “Network service deployment flavour” of NSD NFVIFA(19)000355r2 Status: Drafting call agreed (FEAT16#5) NFVIFA(19)000397r1 Status: Drafting call agreed (FEAT16#5)	IFA014	December-2018	Ongoing
006	Specify operations of the assignment/reservation of resources in Or-Vi/Vi-Vnfm/Or-Vnfm interfaces to support SAL by adding the parameter of “SAL” into the Virtual resource assignment/reservation requests NFVIFA(19)000399r1 Status: Drafting call agreed (FEAT16#5)	IFA005/006/007	February-2019	Ongoing

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT17: Cloud-Native VNF and NFV Architecture PaaS

Overview

Feature Prime	Jörg Aelken (Ericsson LM) Ulrich Kleber (Huawei Technologies Co.,Ltd)
Feature description	The VNFCLOUD feature is currently being specified in ETSI GS NFV-EVE 011, the NFVPAAS feature is currently being studied in ETSI GR NFV-IFA 029. The VNFCLOUD will implement mechanisms for the life-cycle management of NFV Micro-Services while NFVPAAS will enhance the NFV architecture to support identified PaaS-like capabilities and cloud-native design principles for VNFs.
Target Release	To be defined, either Release 3 drop 3 or later release
Impacted WIs	IFA007, IFA008, IFA010, IFA011, IFA029 further impacts expected, but to be defined
MegaCRs	TODO
Related/Dependent Features	FEATxx FEATyy
New Specification	Name of New Specification to be defined WI Status [WID to be prepared]
Status	Pending 0% completed
Feature team	Ulrich Kleber (Huawei Technologies Co.,Ltd) Jörg Aelken (Ericsson LM)
Last Updated	2018-11-30

Implementation Plan

ID	Action	Impacted WI(s)	Target completion	Status
001	Analyse EVE011 for potential architectural enhancements and include them in IFA029.	IFA029	November-2018	Open
002	Update feature implementation request for VNFCLOUD if necessary and create feature implementation request for NFVPAAS. Implementation request NFV(17)000276	N/A	February-2019	Open
003	Prepare detailed feature implementation plan. Feature implementation plan [LINK to be added later]	N/A	March-2019	Open
004	New potential work item approved (if applicable)	N/A	April-2019	Open

Issues

Background Information

According to its latest definition, the ETSI NFV Release 3 includes objectives:

• To specify requirements and enhancements to NFV Architectural Framework to support PaaS features.
• To specify non-functional parameters to classify and characterize VNF cloud-native implementations.

They are reflected in the following two features and corresponding work items:

Feature ID	Title	Work Item
R03.F19	NFV Architecture PaaS (NFVPAAS)	IFA029
R03.F20	Cloud-Native VNF (VNFCLOUD)	EVE011

During the work on the two work items it was discovered that both features are very much related and the envisioned solutions and implementations might overlap and will target the same impacted work items.
During discussions in IFA#73 it was further identified that EVE011, even though it is normative, should be considered as stage 1 requirements on cloud-native on a high abstraction level without taking the actual implementation into consideration. It was further identified in this meeting that IFA029 as a GR looks at architectural aspects of both Cloud Native and PaaS.

Feature implementation approach

This feature implementation plan proposes to implement both features, VNFCLOUD and NFVPAAS, together. It is proposed to delay the feature implementation and aim for ETSI NFV Release 3 drop 2 with the following approach:

• Finalize EVE011 and get it approved
• Analyze EVE011 for potential architectural impacts and evolve them in IFA029
• Get IFA029 in a stable stage
• Implement both features based on recommendations from IFA029 and recommendations from EVE011 which could be directly implemented

Security Considerations

List of security considerations implied by the feature.

FEAT18: Security

Overview

Feature Prime	Mark Shepherd (Tencastle)
Feature description	To address security challenges arising in NFV, particularly in terms of isolation of sensitive functions and security management and monitoring
Target Release	Release 3 drop X (2019-06-30)
Impacted WIs	Active work items: IFA026, IFA033, SEC019. Future work items: consider whether SOL or TST items would be appropriate. Existing work items: SEC009, SEC011, SEC012, SEC013.
MegaCRs	tbd
Related/Dependent Features	None
Status	Ongoing (25% complete)
Contributions	All feature contributions Agreed content (direct links to search-URLs to be added later)
Feature team	Alex Leadbeater (Rapporteur), BT Leslie Willis (Rapporteur), BT Mark Shepherd, Tencastle
Last Updated	2018-10-19

Implementation Plan

ID	Action	Impacted WG(s)	Target completion	Status
001	Complete requirements in IFA026	IFA026	November 2018	Open
002	Map requirements from IFA026 into IFA033 and assign to each interface	IFA026 IFA033	November 2018	Open
003	Complete all of IFA026 and identify all interfaces in IFA033	IFA026 IFA033	December 2018	Open
004	Complete IFA033	IFA0233	May 2019	Open

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

ARCHIVE - COMPLETED FEATURES

FEAT02: VNF software modification

Overview

Feature Prime	Stefan Arntzen, Huawei
Feature description	This feature addresses the initiation and the coordination of the software modification process related to VNFs. Goal is to minimise the impact of software modification on service availability.
Target Release	Release 3
Impacted WIs	IFA007, IFA008, IFA011, IFA013, IFA010 (not approved)
MegaCRs	MegaCR Index in NFVIFA(19)000117r1 IFA007: NFVIFA(19)000059r4 Status: Approved MegaCR (IFA#137) IFA008: NFVIFA(19)000058 Status: Approved MegaCR (IFA#137) IFA010: NFVIFA(19)000060 Status: Approved MegaCR (IFA#137) IFA011: NFVIFA(19)000061r3 Status: Approved MegaCR (IFA#137) IFA013: NFVIFA(19)000077r3 (single contribution for IFA013)
Related/Dependent Features	N/A
Status	Completed
Contributions	All feature contributions Agreed content
Feature team	Stefan Arntzen (Huawei) Maria Toeroe (Ericsson) Shaoji Ni (Huawei) Dmytro Gassanov (NEC) Lijuan Chen (ZTE) Gerald Kunzmann (DOCOMO) Joan Triay (DOCOMO)
Last Updated	2019-02-06

Implementation Plan

Items to consider in the implementation plan

• Detailed description what has to be done in which work item.
• Timeplan of when the team plans to conclude a particular action in the implementation plan.

ID	Action	Impacted WG(s)	Target completion	Status
001	Add functionality description of VNF software modification synchronisation in to IFA010. CR drafts: NFVIFA(18)000869r3 Status: Agreed FEAT (IFA#124) NFVIFA(19)000051r2 Status: Agreed FEAT (IFA#136)	IFA010	January-2019	Completed
002	Define metadata to allow to synchronize the software modification process CR drafts: - NFVIFA(18)000936r2 Status: Agreed FEAT (IFA#125) - NFVIFA(18)0001037r1 Status: Agreed FEAT (IFA#129) - NFVIFA(18)0001122r3 Status: Agreed FEAT (IFA#136) - NFVIFA(18)0001125r2 Status: Agreed FEAT (IFA#132) - NFVIFA(18)0001126r1 Status: Agreed FEAT (IFA#132) - NFVIFA(18)0001149r1 Status: Agreed FEAT (IFA#134) - NFVIFA(18)0001150r2 Status: Agreed FEAT (IFA#134) - NFVIFA(18)0001151r6 Status: Agreed FEAT (IFA#137) - NFVIFA(18)0001155r4 Status: Agreed FEAT (IFA#135) - NFVIFA(18)0001156 Status: NOTED in drafting call #05 - NFVIFA(19)000049r1 Status: not handled in v3.2.1 - NFVIFA(19)000056 Status: not handled in v3.2.1 - NFVIFA(19)000082 Status: Agreed FEAT (IFA#137) - NFVIFA(19)000083r2 Status: Agreed FEAT (IFA#137) - NFVIFA(19)000101r2 Status: Agreed FEAT (IFA#137) - NFVIFA(19)000105r1 Status: Agreed FEAT (IFA#137)	IFA011	January-2019	Completed
003	Derive the requirements from REL006 for an interface for the coordination of VNF software modifications actions on the Or-Vnfm reference point	IFA007	December-2018	Completed
004	Derive the requirements from REL006 for an interface for the coordination of VNF software modifications actions on the Ve-Vnfm reference point	IFA008	December-2018	Completed
005	Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vnfm reference point CR drafts: - NFVIFA(18)000937r3 Status: Agreed FEAT (IFA#125) - NFVIFA(18)000935r2 Status: Agreed FEAT (IFA#125) - NFVIFA(18)0001154r2 Status: Agreed FEAT (IFA#135) - NFVIFA(19)000115r1 Status: Agreed FEAT (IFA#137)	IFA007	January-2019	Completed
006	Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Ve-Vnfm reference point CR drafts: - NFVIFA(18)000938 Status: Obsolete (superseeded by 107r2) - NFVIFA(19)000106 Status: Agreed FEAT (IFA#137) - NFVIFA(19)000107r2 Status: Agreed FEAT (IFA#137) - NFVIFA(19)000116 Status: Agreed FEAT (IFA#137)	IFA008	January-2019	Completed
007	Add annex with information flows to document the procedures for the VNF software modifications CR drafts (IFA007): - NFVIFA(18)000933r6: Status: Agreed FEAT (IFA#128) - NFVIFA(19)000094r1 Status: Agreed FEAT (IFA#137) - NFVIFA(19)000096r1 Status: Agreed FEAT (IFA#137) - NFVIFA(19)000097r3 Status: Agreed FEAT (IFA#137) CR drafts (IFA013): - NFVIFA(18)000934 Status: not handled in v3.2.1	IFA007, IFA013	January-2019	Completed
008	Finalize CRs for the changes from 001, 002, 005, 006, 007 and create MegaCRs	IFA	February-2019	Completed
009	Security analysis: - NFVIFA(18)0001147r1 Status: Agreed by SEC WG	IFA	January-2019	Completed
010	Requirements and operations for NS LCM interface: - NFVIFA(19)000077r3 Status: Agreed FEAT (IFA#137)	IFA013	January-2019	Completed

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT04: Host Reservation

Overview

Feature Prime	Gerald KUNZMANN (DOCOMO Communications Lab.)
Feature description	The present enhancement proposes adding the capability to the NFV-MANO architectural framework to support the reservation of compute hosts (see clause 3.1 in GS NFV-PER 001) in the NFVI. Detailed feature proposal is available in IFA_Enhancement_Host_Reservation
Target Release	Release 3 drop 1 (2018-05)
Impacted WIs	IFA005, IFA007, IFA010, IFA013
MegaCRs	IFA005 MegaCR in NFVIFA(18)000420r1 (Approved MegaCR) (new text in clauses 2.2, 5.2, 5.3.X, 5.3.Y, 5.3.Z, 7.X, 7.Y, 8.X; updates clause 8.7.4) IFA007 MegaCR in NFVIFA(18)000421r1 (Approved MegaCR) (updates clauses 6.3.2 "Grant VNF Lifecycle Operation operation" and 8.3.3 "GrantInfo information element") IFA010 MegaCR in NFVIFA(18)000419r3 (Approved MegaCR) (new text in clauses 2.2, 3.1, 6.1.6, 6.X, 8.2.3, 8.X, A.2) IFA013 MegaCR in NFVIFA(18)000422r2 (Approved MegaCR) (new text in clauses 5.2, 5.X, 7.X, 8.X)
Related/Dependent Features	N/A
Status	Approved. MegaCR Index available in NFVIFA(18)000475r1
Contributions	All feature contributions Agreed content
Feature team	Arturo Martin De Nicolas (Ericsson LM) Bertrand Souville (DOCOMO Communications Lab.) Joan Triay (DOCOMO Communications Lab.)
Last Updated	2018-07-30

Implementation Plan

NOTE: below contributions are marked as "OBSOLETE" as all content has been migrated to the MegaCRs (see above) and FEAT04 has been approved at IFA#101.

ID	Action	Impacted WG(s)	Target completion	Status
001	Specify a requirement for the VIM to support the capability of handling reservation of resources at the host level. Specify a requirement for the NFVO to support requesting the reservation of resources at the host level. CR drafts: NFVIFA(17)0001086 (VIM) Status: Obsolete NFVIFA(18)000146 (NFVO) Status: Obsolete	IFA010	January-2018	Completed
002	Specify requirements for an interface specialized on NFVI management on the Or-Vi to support the reservation of resources at the host level. CR draft NFVIFA(18)000053 Status: Obsolete	IFA005	January-2018	Completed
003	Specify an interface and its operations to support the reservation of resources at the host level. CR draft NFVIFA(18)000145r2 Status: Obsolete	IFA005	February-2018	Completed
004	Extend Annex A.2 to introduce physical compute host reservation. CR draft NFVIFA(18)000205 Status: Obsolete	IFA010	March-2018	Completed
005	Extend clause 6.3.2 Grant VNF Lifecycle Operation operation. CR draft NFVIFA(18)000206r2 Status: Obsolete	IFA007	March-2018	Completed
006	Enhancements of capacity management due to new functionality of host reservation: - Specify a requirement for the VIM to support NFVI capacity management. - Specify a requirement for the NFVO to support NFVI capacity management. CR drafts: NFVIFA(18)000207r2 (NFVO) Status: Obsolete NFVIFA(18)000208r1 (VIM) Status: Obsolete	IFA010	March-2018	Completed
007	Specify an interface (IFA005, clause 7.X) and its operations to support Compute Hosts Capacity Management. CR draft NFVIFA(18)000364 Status: Obsolete	IFA005	March-2018	Completed
008	A new interface and its operations may be needed in IFA013 for notifications from the NFVO related to resource capacity shortage. CR drafts: NFVIFA(18)000365r1 Status: Obsolete NFVIFA(18)000418 Status: Obsolete	IFA013	March-2018	Completed

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT05 Network Slicing

Overview

The latest version of NFV EVE Network Slicing Report (EVE012 V3.1.1) can be downloaded at EVE012.

Feature Prime	Anatoly Andrianov (Nokia), Cristina Badulescu (Ericsson), Ulrich Kleber (Huawei), Bhumip Khasnabish (ZTE)
Feature description	EVE to IFA REL SEC Feature NFVSLICE EVE012 network slicing Support Network Slicing by defining the necessary requirements and enhancements of interfaces, as discussed in NFV(17)000252.
Target Release	Release 3 Drop 2
Impacted WIs	IFA010, IFA013, IFA014, IFA024
MegaCRs	MegaCR for IFA010: NFVIFA(18)000844r7_IFA010_MegaCR_FEAT05_Slicing.docx MegaCR for IFA013: NFVIFA(19)000014r1_IFA013_MegaCR_FEAT05_Slicing.docx Only one CR for IFA014: NFVIFA(18)000653r4_FEAT05__IFA014_add_priority_to_NSD Only one CR for IFA024: NFVIFA(18)0001091_FEAT05_IFA024_Add_Slicing_Touchpoint MegaCR Index: NFVIFA(19)000016r1_FEAT05_MegaCR_Index.docx
Related/Dependent Features	After analysis and LS exchange with 3GPP no dependencies for the time frame of this feature are seen anymore.
Status	Completed
Reliability Review	Done in REL#270 on January 15, 2019
Security Review	Reviewed in SEC#139 on January 24, 2019 See NFVIFA(19)000054r2_FEAT05_security_considerations.docx or NFVSEC(19)000008r1_FEAT05_security_considerations.zip
Contributions	Latest status on Feature Dashboard
Feature team	Anatoly Andrianov, Nokia Cristina Badulescu, Ericsson Bhumip Khasnabish, ZTE Ulrich Kleber, Huawei Sibylle Schaller, NEC Zarrar Yousaf, NEC Gerald Kunzmann, DOCOMO Communications Lab
Last Updated	2019-01-28

Summary of decisions / agreed concepts

1. Based on 3GPP's answer below, FEAT05 assumes that current NS LCM can be used by slicing to build slices and slice subnets.
2. Based on 3GPP's answer below, FEAT05 can concentrate on analysing the use of NS priority only.
3. Based on 3GPP's answer below, FEAT05 expects that a NS instance doesn't need to keep track of different consumers of a NS instance, but the existing multi-tenancy concept can be used by 3GPP.
4. Based on 3GPP's answer below, FEAT05 closes the work on slice specific policies and multi-domain issues.

It is expected that Slice management functions can build the slices by using (instantiating) NS instances. NFV MANO is not aware of the network slices. Thus slice consumers / tenants are not known by MANO. Only the NS tenant is seen.

Depending on the use cases (contributed to an Annex for IFA010), it will be decided whether NS priorities need to be propagated to VNFM or VIM.

Overview Liaison Exchange

Specific Liaisons with 3GPP SA5 on Network Slicing

• LS to 3GPP SA5 on NFV support for Network Slicing: NFV(18)000065r2
• LS reply from 3GPP SA5 on NFV support for Network Slicing: NFV(18)000088

Summary of the answers:

1. The definition of slice specific policies is not within the scope of ongoing Rel-15 work items
2. Assurance data and Performance Management work item may have potential impacts on ETSI GS IFA027, but no detailed information
3. 3GPP relies on the use of ETSI NFV NS concept. Current expectations are for the support of priorities at the NS level (e.g. expressed as attribute value in the NSD).
4. Fixed mapping of slice tenant and NS tenant was not explicitly confirmed. Keeping track of multiple consumers doesn't seem to be necessary. 3GPP is aware of the NS tenants and will use the concept by some mapping between the slice consumer and the tenant of supporting NS(s).
5. According to the answer, 3GPP is not planning to share NS instance between two slices if isolation is needed.
6. 3GPP expects that slicing management will use Os-Ma-nfvo and Ve-Vnfm-em reference points only.

A second set of questions has been sent to 3GPP SA5:

• LS to 3GPP SA5 on usage of NS priority in NFV MANO in support for Network Slicing: NFV(18)000264
• LS from 3GPP SA5 as first answer: NFV(18)000276
• LS Reply to SA5 with clarifications on questions: NFV(18)000288r1
• Preparation material for requested joint call: NFVIFA(18)000964_Prep_material_for_joint_session_3GPP_SA5.pptx
• LS Reply from 3GPP SA5 containing a set of answers: NFV(18)000299_Reply_LS_from_3GPP_SA5_on_clarifications_topics_for_NFV_NS_i.zip
• Main statements, see some questions in report from FEAT05 drafting call NFVIFA(18)000995_Report_of_FEAT05_Drafting_19_November_20.docx

Reply by SA5: NFV(18)000299_Reply_LS_from_3GPP_SA5_on_clarifications_topics_for_NFV_NS_i Main issues that could be clarified:

• Priorities are meant for LCM operations and resolution of resource conflicts in case of shortage
• MANO can act autonomously using the priority values
• If priority values are the same, MANO should act “first come first served”
• There should be a top priority, i.e. one that cannot be pre-empted.
• SA5 prefers the priority as attribute in NSD-DF.

Open questions collected:

1. 2.1.1: “3GPP will expect to receive a notification” might be understood that the consumer will receive the notification.
2. 2.1.3: “For LCM actions on NFV NSs that potentially impacts 3GPP communication services, MANO should ask permission for such LCM actions the 3GPP management system and not use the provided NS priority” is unclear in the wording.
3. What should MANO use instead if it shouldn’t use the priority?
4. 2.1.3: It is unclear how NFV should know which NS would impact 3GPP communication services and not be allowed to use the priority.
5. 2.1.4.1: 3GPP doesn’t acknowledge here that there might be other consumers for NS/resources that may use resources and need to be considered in the setting of priorities.
6. 2.1.4.2: The wording allows also pre-emption in case a low priority NS instance is fully instantiated. Does 3GPP intend this or do they refer only to NS LCM operations being in execution at the same time concurrently?
7. Should MANO use priority during autohealing and “kill” a low priority NS instance to be able to heal a high priority NS instance in a resource shortage situation?

Other Liaisons with SA5

LS received in cc, but containing valuable inputs:

• Reply LS from 3GPP SA5 on draft Recommendation Y.3103: NFV(18)000277
• LS from SA5 to GSMA informing about documents: NFV(18)000282, referenced documents are 3GPP Rel-15 TS 28.530, 3GPP Rel-15 TS 28.531, 3GPP Rel-15 TS 28.541

Liaisons with other SDOs

Reply LS from ITU-T SG13 on consent of Recommendation Y.3103 (addressing network slicing) see NFV(18)000302_Reply_LS_from_ITU-T_SG13_on_consent_of_Recommendation_Y3103

Implementation Plan

ID	Action	Impacted WG(s)	Target completion	Status
001	Add Functional requirements to support NFVSLICE in IFA010 CR Drafts agreed: - NFVIFA(18)000049r3_FEAT05_IFA010_Add_Requirements_from_Slicing_to_NFVO_and_VNFM status: FEAT AGREED (IFA#89) - NFVIFA(18)000120r5_FEAT05_IFA010_General_Functional_Requirements status: FEAT AGREED (IFA#125) - NFVIFA(18)000172_FEAT05_IFA010_Requirements__Network_Connections_NFVI_PoPs Routed to FEAT10 and FEAT AGREED (IFA#104) - NFVIFA(18)000478r2_FEAT05_IFA010_CR_UseCases_for_Network_Slicing FEAT AGREED (IFA#105) - NFVIFA(18)000692r2_FEAT05_IFA010__Scaling_Use_Cases_for_Network_Slicing_in_Anne FEAT AGREED (IFA#116) - NFVIFA(18)000699r4_FEAT05_IFA010__Use_case__Re-instantation_of_multiple_NS_inst FEAT AGREED (IFA#122) - NFVIFA(18)000732r2_FEAT05_IFA010_priority-based_NS_resource_Mngmnt_by_NFVO FEAT AGREED (IFA#118) - NFVIFA(18)000847r2_FEAT05_IFA010__Consider_priorities_during_resource_reservati FEAT AGREED (IFA#122) - NFVIFA(18)000848r1_FEAT05_IFA010__Consider_priorities_during_VNF_Lifecycle_Oper FEAT AGREED (IFA#122) - NFVIFA(18)000849r1_FEAT05_IFA010__Consider_priorities_during_NS_scaling FEAT AGREED (IFA#122) - NFVIFA(18)000850r1_FEAT05_IFA010__Consider_priorities_in_a_multiple_administrat FEAT AGREED (IFA#122) - NFVIFA(18)000867r5_FEAT05_IFA010_priority_support_in_allowance_management FEAT AGREED (IFA#125) - NFVIFA(18)000868r1_FEAT05_IFA010_priority_support_in_scheduled_NS_lifecycle_ope FEAT AGREED (IFA#122) - NFVIFA(18)000879r1_Restructuring_Annex_of_IFA010__FEAT05_proposal_.docx APPROVED (IFA#125) - NFVIFA(18)000963r3_FEAT05_IFA010__Use_case__Instantiation_of_NS_in_parallel_to FEAT AGREED in IFA#128 - NFVIFA(18)0001000r3_FEAT05_IFA010_Clarification_on_Resource_Conflict_Resolution to be FEAT AGREED in IFA#129 - NFVIFA(18)0001065r2_FEAT05_IFA010__Use_case__Resolving_a_conflict_by_pre-empting.docx FEAT AGREED in IFA#129 - NFVIFA(18)0001089r1_FEAT05_IFA010_Annex_NS_sharing_conclusions.docx FEAT AGREED in IFA#129 - NFVIFA(18)000252r7_FEAT05_IFA010_Annex_Use_of_NFV_Constructs_in_Network_Slicing FEAT AGREED in IFA#131 - NFVIFA(18)0001119r2_FEAT05_IFA010_Editorial_alignment_of_use_cases.docx FEAT AGREED in IFA#131 - NFVIFA(18)0001123r1_FEAT05_IFA010_Add_LCM_coordination_interface_to_use_cases.docx FEAT AGREED in IFA#131 - NFVIFA(18)0001139r2_FEAT05_IFA010_Annex_D_1_Introduction_to_general_use_cases.zip FEAT AGREED in IFA#131 - NFVIFA(18)0001140r1_FEAT05_IFA010_Add_requirements_on_isolation.docx FEAT AGREED in IFA#131 - NFVIFA(18)0001148_FEAT05_IFA010_Add_use_of_NsLcmCapacityShortageNotification.docx FEAT AGREED in IFA#133	IFA010	Jan-2019	Completed
002	Identify and add new parameters for NSD to allow support of the network slice and network slice subnet. CR Drafts agreed: - NFVIFA(18)000653r4_FEAT05__IFA014_add_priority_to_NSD FEAT AGREED in IFA#129	IFA014	Jan-2019	Completed
003	Investigate whether any new parameters in VNFD may be needed.	IFA011	Jan-2019	No update needed Completed
004	Investigate whether any new parameters in Os-Ma-Nfvo reference point may be needed to realize NFVSLICE lifecycle capabilities which include: - Determining the requirements on the lifecycle of the Network Service used as part of a Network Slice - Determining the requirements for the lifecycle of the Network Service used as part of a Network Slice Subnet	IFA013	Jan-2019	No update needed Completed
005	Investigate whether any new parameters in Os-Ma-Nfvo reference point may be needed to realize NFVSLICE feature capabilities which include: - Determining the requirements for policy handling for Network Service instance - Determining the requirements for performance and fault data handling - Determining the requirements for LCM handling CR Drafts: - NFVIFA(18)0001008r1_FEAT05_IFA013__NsLcmOperationOccurenceNotification_in_case_o.docx FEAT AGREED in IFA#129 - NFVIFA(18)0001141_FEAT05_IFA013_Add_shortage_notification_.docx FEAT AGREED in IFA#133 Note: According to EVE012 further analysis is necessary on whether there is any impact on the IFA013	IFA013	Jan-2019	Completed
006	Investigate whether any new parameters in Or-Vi reference point may be needed to realize NFVSLICE feature capabilities which include: - Determining the resource requirements for Network Service instance - Communicating resource prioritization related data	IFA005	Jan-2019	No update needed Completed
007	Investigate whether any new parameters in Vnfm-Vi reference point may be needed to realize NFVSLICE feature capabilities which include: - Determining the resource requirements for VNF/C instances - Communicating resource prioritization related data	IFA006	Jan-2019	No update needed Completed
008	Investigate whether any enhancements are needed for Application and Service Management Interface and Information Model Specification.	IFA012	Jan-2019	Completed: No change needed: Use cases will be covered in IFA010, Touchpoints in IFA024. Not necessary to re-open Document in drop 2.
009	Investigate whether any Security requirements may be needed to realize the following features: Resource isolation for security reasons and per allocation policy: At Network Service level At VNF level At NFVI level Isolation of network service management for multiple tenants Security review available in NFVIFA(19)000054_FEAT05_security_considerations.docx Note: Affected documents to be discussed with SEC WG	SEC012	Jan-2019	No update need to be initiated from FEAT05 Completed
010	Reliability requirements to realize the following features: - The NS instantiation which is used in the creation of a network slice instance, or in the network slice subnet instance - Maintaining the reliability of NS supporting the network slice instance during and after resource changes - Applying the reliability requirements and policies associated with network slice instance or the network slice subnet instance, throughout the lifecycle management of the Network Service instance As discussed with REL WG on Sept.30 2018, all reliability aspects will be analysed and covered by the REL010 work item. Impacts on IFA documents cannot be analysed in drop 2 time frame. Thus these can only be done (if necessary) in a second phase of FEAT05. Reliability review was conducted with REL WG on January 15, 2019 in meeting REL#270	REL010	June-2019	Completed Delegate to REL10 No CR in drop 2 from FEAT05
011	The touchpoint between NFV and network slice management functions needs to be specified. The diagram illustrating it can be found in LS from SA5 NFV(18)000282_Reply_LS_from_3GPP_SA5_on_GSMA_Network_Slicing_Use_Case_Requ CR Drafts: - NFVIFA(18)0001091_FEAT05_IFA024_Add_Slicing_Touchpoint.zip	IFA024	Feb-2019	Completed

CRs abandoned

- NFVIFA(18)000876r1_FEAT05_IFA010_priority_support_in_software_image_distributio noted in IFA
- NFVIFA(18)000104r6_FEAT05_IFA010_priority-based_NS_resource_Mngmnt_by_NFVO replaced by 732
- NFVIFA(18)000102r2_FEAT05_IFA010_priority-based_NS_resource_Mngmnt_by_VIM not needed according to SA5 LS
- NFVIFA(18)000103r2_FEAT05_IFA010_priority-based_NS_resource_Mngmnt_by_VNFM not needed according to SA5 LS
- NFVIFA(18)000101r2_FEAT05-IFA010-Arch_Level_Req_to_Support_Additional_NS_Featur Noted in IFA#129
- NFVIFA(18)000108r2_FEAT05_IFA010_policy__priority__and_isolation_based_Multiple Noted in IFA#129
- NFVIFA(18)000109_FEAT05_IFA010_policy__priority__and_isolation_based_Multiple Noted in IFA#129
- NFVIFA(18)000110_FEAT05_IFA010_policy__priority__and_isolation_based_Multiple Noted in IFA#129
- NFVIFA(18)000866r3_FEAT05_IFA010__priority_support_in_NFP_management Noted in IFA#129
- NFVIFA(18)000877r1_FEAT05_IFA010_priority_support_in_NS_performance_management Noted in IFA#129

Other Contributions

• Presentation for Webinar "Network Slicing and ETSI NFV": NFV(17)000328
• Analyse NGMN Requirements on Slicing: NFVIFA(18)000017r1
• LS from 3GPP SA5 on transport network support of network slicing management: NFV(18)000026
• LS reply to 3GPP SA5 on transport network support of network slicing management: NFV(18)000057
• LS to 3GPP SA5 on NFV support for Network Slicing: NFV(18)000065r2
• LS reply from 3GPP SA5 on NFV support for Network Slicing: NFV(18)000088
• Presentation: "Towards NFV definition for Network Slicing" NFVIFA(18)000115r1
• Presentation at the Network Slicing World Summit held in Berlin, Germany on 23rd October 2018 NFV(18)000283
• Proposals to resolve editors notes NFVIFA(18)0001138_FEAT05_IFA010_Resolving_Editors_Notes.pptx

Issues

List of issues raised based on the feature implementation.

Security Considerations

see action 009,
see also NFVIFA(18)0001084r1_FEAT05_Security_Topics_joint_IFA_SEC_at_NFV24.pptx
Security review using the SEC006 template is available in NFVIFA(19)000054r2_FEAT05_security_considerations.docx
This evaluation was approved in SEC WG call on January 24, 2019 as NFVSEC(19)000008r1_FEAT05_security_considerations.zip and finally approved by IFA WG in IFA#136 on January 30, 2019.

FEAT07: MANO Policy Management (MANO_PLC)

Overview

Feature Prime	Haitao Xia (Huawei)
Feature description	This feature addresses the interface operation definition when policy management is introduced to NFV-MANO
Target Release	Release 3 drop 1 (2018-06)
Impacted WIs	IFA010 IFA013 IFA007 IFA008 IFA005 IFA006
Mega-CRs	IFA013 MegaCR in NFVIFA(18)000429r1 (Approved) IFA007 MegaCR in NFVIFA(18)000430r1 (Approved) IFA008 MegaCR in NFVIFA(18)000431r1 (Approved) IFA005 MegaCR in NFVIFA(18)000432r1 (Approved) IFA006 MegaCR in NFVIFA(18)000433r1 (Approved) IFA010 MegaCR in NFVIFA(18)000455r3 (Approved)
Related/Dependent Features	no dependency
Status	Completed. MegaCR Index available in NFVIFA(18)000492r1
Contributions	All feature contributions Agreed content
Feature team	Haitao Xia (Huawei)
Last Updated	2018-06-07

Implementation Plan

NOTE:Contributions are marked as "OBSOLETE" as all content has been migrated to the corresponding MegaCRs.

ID	Action	Impacted WG(s)	Target completion	Status
001	Add functional requirements of policy management for the NFVO, VNFM and VIM IFA010 CRs (Status: Feature Agreed) NFVIFA(18)000018r3 NFVIFA(18)000029r2	IFA010	Jan-2018	Completed
002	Specify a new interface of policy management over Os-Ma-nfvo reference point, including the interface requirements, policy management operations and corresponding information model IFA013 CRs (Status: Obsolete) NFVIFA(18)000032r3 NFVIFA(18)000088r1 NFVIFA(18)000089r1 NFVIFA(18)000094r6 NFVIFA(18)000165r4 NFVIFA(18)000186r2 NFVIFA(18)000187 NFVIFA(18)000213r1 NFVIFA(18)000481r1	IFA013	Mar-2018	Completed
003	Derive policy management interface over Nfvo-vnfm, Ve-Vnfm, Nfvo-Vi, Vi-vnfm reference point (mirror CRs to IFA013GS) based on the output of IFA013 interface operation definition IFA007 mirror CRs (Status: Obsolete) NFVIFA(18)0000272 NFVIFA(18)0000273 NFVIFA(18)0000274 NFVIFA(18)0000275r1 NFVIFA(18)0000276r1 NFVIFA(18)0000277 NFVIFA(18)0000278 IFA008 mirror CRs (Status: Obsolete) NFVIFA(18)0000313 NFVIFA(18)0000314 NFVIFA(18)0000315r1 NFVIFA(18)0000316 NFVIFA(18)0000317 NFVIFA(18)0000318 NFVIFA(18)0000319 IFA005 mirror CRs (Status: Obsolete) NFVIFA(18)0000340 NFVIFA(18)0000383 NFVIFA(18)0000385 NFVIFA(18)0000387 NFVIFA(18)0000389 NFVIFA(18)0000391 NFVIFA(18)0000393 IFA006 mirror CRs (Status: Obsolete) NFVIFA(18)0000341 NFVIFA(18)0000384 NFVIFA(18)0000386 NFVIFA(18)0000388 NFVIFA(18)0000390 NFVIFA(18)0000392 NFVIFA(18)0000394	IFA007/IFA008/IFA005/IFA006	May-2018	Completed
004	Define information model enhancement to the NFV descriptor (e.g., NSD) when necessary Conclusion: Based on the discussion output of NFVIFA(18)000135r1,there is no necessity to introduce policy descriptor to the NSD information model	IFA014	Feb-2018	Completed

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT08: Support of composite NS across multi-domain (MANOMD_NS)

Overview

Feature Prime	Haitao Xia (Huawei), Arturo Martin de Nicolas (Ericsson)
Feature description	This feature addresses the architectural changes needed for the support of composite network services across multiple administrative domains
Target Release	Release 3 drop 1 (2018-06)
Impacted WIs	IFA010 IFA030 (new deliverable)
Mega-CRs	IFA010 MegaCR in NFVIFA(18)000425r1 (Approved)
Related/Dependent Features	no dependency
Status	Completed MegaCR Index available in NFVIFA(18)000515r2 New deliverable IFA030GS Approved
Contributions	All feature contributions Agreed content
Feature team	Haitao Xia (Huawei) Arturo Martin de Nicolas (Ericsson) Bhumip Khasnabish (ZTE)
Last Updated	2018-09-01

Implementation Plan

NOTE:Contributions are marked as "OBSOLETE" as all content has been migrated to the corresponding MegaCRs.

ID	Action	Impacted WG(s)	Target completion	Status
001	Determine the content skeleton and input for introduction Approved contributions: NFVIFA(17)0001172r3 NFVIFA(17)0001176r2	IFA030	Jan-2018	Completed
002	Add NFVO functional requirement description derived from Table 6.3-2 of IFA028 to IFA010 IFA010 CRs (Status: Obsolete) NFVIFA(18)000042r3 NFVIFA(18)000050r5	IFA010	May-2018	Completed
003	Add interface requirement description of Or-Or reference point derived from Table 6.3-1 of IFA028 Approved contributions: NFVIFA(18)000056r1 NFVIFA(18)000041r2 NFVIFA(18)000167 NFVIFA(18)000337	IFA030	Apr-2018	Completed
004	Define Or-Or interface functions of NSD management, NS LCM, NS PM and NS FM which are derived from IFA013 GS and necessary adaptation is made Approved contributions: NFVIFA(18)000077r1 NFVIFA(18)000338	IFA030	Apr-2018	Completed
005	Define Or-Or interface functions of NS lifecycle granting and NS instance usage notification Approved contributions: NFVIFA(18)000097r3 NFVIFA(18)000112r2	IFA030	Apr-2018	Completed
006	Develop Or-Or operational flows as informative Annex (when necessary) Conclusion: No operational flows are expected to be included in IFA030 GS: 1. Align with the same definition style of other interface specifications; 2. IFA028 report has already provided the flows for reference.	IFA030	Mar-2018	Completed
007	New GS (IFA030) clean-up, EN resolution Approved Contributions: NFVIFA(18)000441r1 NFVIFA(18)000442r1 NFVIFA(18)000443 NFVIFA(18)000444r1 NFVIFA(18)000447	IFA030	May-2018	Completed

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT10: Mgmt & Connectivity Multi-Site Services (MCMSS)

Overview

Feature Prime	Hiroshi Dempo Zarrar Yousaf
Feature description	Following the recommendations written in IFA022, this feature is to specify management requirements, interfaces and information models to support connectivity for Multi-Site Services
Target Release	Release 3 drop 2 (2018-12)
Impacted WIs	IFA005, IFA007, IFA010, IFA011, IFA013, IFA014, IFA022, IFA032
Mega-CRs	IFA005 MegaCR in NFVIFA(18)0001111r2 IFA007 MegaCR in NFVIFA(18)0001112r4 IFA010 MegaCR in NFVIFA(18)0001107r2 IFA013 MegaCR in NFVIFA(18)0001110r4 IFA014 MegaCR in NFVIFA(18)0001113r2
Related/Dependent Features	N/A
Status	Ongoing (100% complete) MegaCR Index available in NFVIFA(18)0001117r3
Contributions	All feature contributions Agreed content
Feature team	Hiroshi Dempo (NEC Europe Ltd.) Zarrar Yousaf (NEC Europe Ltd.) Lei Zhu (Huawei Tech (UK) Co., Ltd. Ulrich Kleber (Huawei Tech (UK) Co., Ltd. Marc Flauw (HPE)
Last Updated	2018-12-11

Implementation Plan

Items to consider in the implementation plan

• Detailed description what has to be done in which work item.
• Timeplan of when the team plans to conclude a particular action in the implementation plan.

ID	Action	Impacted WG(s)	Target completion	Status
001	- Approve FEAT10 and new WI draft titled “Reference point between NFVO and WIM- Interface and Information Model Specification"	None	Oct-2017	Done
002	- Approve IFA022 as a stable draft Status: Published Document: Report on Management and Connectivity for Multi-Site Services	IFA022	Dec-2017	Done
003	- Specify general and functional recommendations for Multi-Site Service - Describe architectural and functional outline of Multi-Site Service (e.g. as a new annex) Approved None Agreed IFA#89: CR NFVIFA(18)000079r2 IFA#89: CR NFVIFA(18)000080r1 IFA#89: CR NFVIFA(18)000081r1 IFA#100: CR NFVIFA(18)000262r2 IFA#100: CR NFVIFA(18)000263r1 IFA#100: CR NFVIFA(18)000264r2 IFA#100: CR NFVIFA(18)000265r1 IFA#100: CR NFVIFA(18)000266r1 IFA#105: CR NFVIFA(18)000172r6 In discussion	IFA010	Jan/ 2018	Completed
004	- Specify Os-Ma-Nfvo reference point interface and information model specification for Multi-Site Service - Make relevant changes to the scope and overview sections to include the support for Multi-site Service on Os-a-Nfvo reference point. Approved None Agreed IFA#99: CR NFVIFA(18)000129r3 IFA#100: CR NFVIFA(18)000155r1 In discussion None	IFA013	Mar-2018	Completed
005	- Specify Or-Vi reference point interfaces and information model specification between NFVO and VIM for Multi-Site Service - Make relevant changes to the scope and overview sections to include the support for Multi-site Service Approved IFA#118: CR NFVIFA(18)000780r3 Agreed None In discussion None	IFA005	Mar-2018	Completed
006	- Specify enhancements to Or-Vnfm ref. point interfaces and information model to address the case of VNF multi-site deployment. - Make relevant changes to the scope and overview sections to include the support for Multi-site Service on Or-Vnfm reference point Approved None Agreed IFA#99 CR NFVIFA(18)000128r5 In discussion None	IFA007	Mar-2018	Completed
007	- Specify parameters for the VNFD file relevant for the support of Multi-Site Service " No CRs received"	IFA011	May-2018	Closed
008	- Specify parameters for the NSD file relevant for the support of Multi-Site Service Approved None Agreed IFA#89: CR NFVIFA(18)000117 IFA#89: CR NFVIFA(18)000118r1 In discussion None	IFA014	May-2018	Completed
009	- Specify Or-Vi reference point interfaces and information model specification between NFVO and WIM for Multi-Site Service Approved IFA#89: NFVIFA(18)000159r1 IFA#100: NFVIFA(18)000413 IFA#100: NFVIFA(18)000414r1 IFA#100: NFVIFA(18)000415 IFA#100: NFVIFA(18)000416r1 IFA#100: NFVIFA(18)000417 IFA#105: NFVIFA(18)000496r2 IFA#105: NFVIFA(18)000497r3 IFA#105: NFVIFA(18)000524r4 IFA#105: NFVIFA(18)000558r1 IFA#105: NFVIFA(18)000582r1 IFA#108: NFVIFA(18)000702r1 IFA#118: NFVIFA(18)000781r2 IFA#118: NFVIFA(18)000782r1 IFA#118: NFVIFA(18)000783r2 IFA#118: NFVIFA(18)000784r2 IFA#118: NFVIFA(18)000785r2 IFA#118: NFVIFA(18)000786 IFA#118: NFVIFA(18)000787r1 IFA#118: NFVIFA(18)000788 IFA#118: NFVIFA(18)000826r1 IFA#125: NFVIFA(18)000912r1 IFA#125: NFVIFA(18)000913r1 IFA#125: NFVIFA(18)000916r3 IFA#125: NFVIFA(18)000951r1 Agreed None In discussion None NOTE: As written in ID#2, naming of the ref. point is FFS. Purpose of the specification is to focus on virtualised network resource management subset of existing IFA005, and necessary extensions/enhancements particular to managing resources in the WAN	IFA032	May-2018	Completed

Issues

List of issues raised based on the feature implementation.

- All topics can start from the beginning but the progress needs to be managed on the action IDs (e.g. individual mega CRs and new deliverable basis)
- The target dates are set according to the requirement categories in IFA022 (CRs for general, functional, reference point and information element, descriptor, or new deliverable)
- Discussion for IFA032 may take more time than CRs but finalise before the 1st drop of Release 3.

Security Considerations

List of security considerations implied by the feature.

FEAT11: NFV_M&M (NFV-MANO management)

Overview

Feature Prime	Yaoye Zhang (Huawei) Joan Triay (DOCOMO)
Feature description	Following the recommendations written in ETSI GR NFV-IFA 021, this feature will enable the management of the NFV Management and Orchestration functional blocks identified by the NFV Architectural Framework.
Target Release	Release 3 drop 1 (2018-06)
Impacted WIs	ETSI GS NFV-IFA 010
MegaCRs	IFA010ed311: NFVIFA(18)000576 Status: APPROVED at IFA#104
Related/Dependent Features	None
New Specification	ETSI GS NFV-IFA 031 ("NFV; Management and Orchestration; Requirements and interfaces for NFV-MANO management Specification") Work Item: DGS/NFV-IFA031
Status	Completed
Contributions	All feature contributions Agreed content
Feature team	Yaoye Zhang (HUAWEI) Joan Triay (DOCOMO) Gerald Kunzmann (DOCOMO)
Last Updated	2018-07-30

Implementation Plan

ID	Action	Impacted WI(s)	Target completion	Status
001	Specify high-level requirement for the NFV Architectural Framework to support the management of NFV-MANO functional entities. Contributions: - CR draft: NFVIFA(17)0001065 status: FEAT AGREED at IFA#79 - IFA010 megaCR FEAT11 on NFV-MANO management: NFVIFA(18)000576 Status: APPROVED at IFA#104	IFA010	Nov-2017	Completed
002	Specify a requirement set for the NFVO, the VNFM, as well as the VIM as a managed entity to support NFV-MANO fault, performance, configuration and information, state and log management by a managing entity. Contributions: CR draft: NFVIFA(17)0001066 status: FEAT AGREED at IFA#79 - IFA010 megaCR FEAT11 on NFV-MANO management: NFVIFA(18)000576 Status: APPROVED at IFA#104	IFA010	Nov-2017	Completed
003	Skeleton, scope and introduction description for the new deliverable. Contributions: - Skeleton overview/draft: NFVIFA(17)0001067r1 Status: for discussion and NOTED - Skeleton: NFVIFA(18)000009r1 Status: APPROVED at IFA#83 - Scope: NFVIFA(18)000046 status: APPROVED at IFA#84	IFA031	Nov-2017	Completed
004	Add description of the general framework and interfaces for NFV-MANO management using as a reference “Solution D” and “Solution E” descriptions available in clauses 7.1.4 and 7.1.5 of ETSI GR NFV-IFA 021. Contributions: - NFVIFA(17)0001068 status: APPROVED at IFA#79 - Relationship NFV-MANO services and interfaces: NFVIFA(18)000351 status: APPROVED at IFA#100	IFA031	Nov-2017	Completed
005	Specify a requirement set for the different interfaces to be supported, which include: - NFV-MANO fault management interface - NFV-MANO performance management interface - NFV-MANO configuration and information management interface - NFV-MANO state management interface, and - NFV-MANO log management interface. Contributions: - Requirement set: NFVIFA(17)0001069 Status: APPROVED at IFA#79 - Overview and conventions: NFVIFA(18)000085 Status: APPROVED at IFA#87	IFA031	Dec-2017	Completed
006	Specify the NFV-MANO functional entity information elements that will be reused in multiple interface definitions using as a reference the “Solution A” description available in clause 7.1.1 of ETSI GR NFV-IFA 021. Contributions: - For configuration and information mgmt: NFVIFA(18)000015r4 Status: APPROVED at IFA#84 - For performance mgmt: NFVIFA(18)000047r1 Status: APPROVED at IFA#84 - For state mgmt: NFVIFA(18)000086r3 Status: APPROVED at IFA#89 - For fault mgmt: NFVIFA(18)000215r2 Status: APPROVED at IFA#93 - For log mgmt: NFVIFA(18)000219r3 Status: APPROVED at IFA#98	IFA031	Dec-2017	Completed
007	Specify the interface for NFV-MANO configuration management using as a reference the “Solution F” description in clause 7.1.6.5 of ETSI GR NFV-IFA 021. Contributions: - Configuration I/F and related IE: NFVIFA(18)000015r4 Status: APPROVED at IFA#84 - Clause 6.2.3 adding filter for QueryConfigInfo operation: NFVIFA(18)000498 Status: APPROVED at IFA#103	IFA031	Jan-2018	Completed
008	Specify the interface for NFV-MANO performance management using as a reference the “Solution F” description available in clause 7.1.6.4 of ETSI GR NFV-IFA 021. Contributions: - Performance I/F and related IE: NFVIFA(18)000047r1 Status: APPROVED at IFA#84	IFA031	Jan-2018	Completed
009	Specify the interface for NFV-MANO fault management using as a reference the “Solution F” description available in clause 7.1.6.3 and the fault reporting information modelling in “Solution B” in clause 7.1.2 of ETSI GR NFV-IFA 021. Contributions: -Fault I/F and related IE: NFVIFA(18)000215r2 Status: APPROVED at IFA#93	IFA031	Feb-2018	Completed
010	Specify the interface for NFV-MANO state management using as a reference the “Solution F” description available in clause 7.1.6.6. Contributions: - State I/F and related IE: NFVIFA(18)000086r3 Status: APPROVED at IFA#89	IFA031	Feb-2018	Completed
011	Specify the interface for NFV-MANO log management using as a reference the “Solution F” description available in clause 7.1.6.7. Contributions - Log I/F and related IE: NFVIFA(18)000219r3 Status: APPROVED at IFA#98	IFA031	Mar-2018	Completed
012	Specify the definitions of performance metrics using as a reference the “Solution C” description available in clause 7.1.3 of ETSI GR NFV-IFA 021. Contributions: - Performance measurement definitions template: NFVIFA(18)000225r2 Status: APPROVED at IFA#94 - Measured objects: NFVIFA(18)000226r1 Status: APPROVED at IFA#94 - NFV-MANO entity resource measurements: NFVIFA(18)000227r1 Status: APPROVED at IFA#94 - Managed objects for performance measurements: NFVIFA(18)000292 Status: APPROVED at IFA#96 - NFV-MANO service measurements: NFVIFA(18)000293 Status: APPROVED at IFA#96 - NFV-MANO interface producer measurements: NFVIFA(18)000294r3 Status: APPROVED at IFA#98 - NFV-MANO interface consumer measurements: NFVIFA(18)000295r3 Status: APPROVED at IFA#98 - Additional managed objects: NFVIFA(18)000350r1 Status: APPROVED at IFA#100	IFA031	Mar-2018	Completed
013	Resolution of editor's notes and final review of the document draft. Contributions: - Clause 7 EN resolution dependency state information: NFVIFA(18)000405 Status: APPROVED at IFA#100 - Clause 7 EN resolution MANO configuration information element: NFVIFA(18)000406r1 Status: APPROVED at IFA#100 - Clause 7 EN resolution list of interfaces: NFVIFA(18)000434 Status: APPROVED at IFA#100 - Clause 6, 7, and 8 EN resolution on PmJob and Threshold Objects: NFVIFA(18)000436 Status: APPROVED at IFA#100 - Clause 8.2 adding ManoInterfaceConsumer measured object NFVIFA(18)000437r1 Status: APPROVED at IFA#100 - Clause 8 EN resolution PM description improvements: NFVIFA(18)000438r1 Status: APPROVED at IFA#100 - Adding Annex for information flows with flow related to configuration: NFVIFA(18)000449 Status: APPROVED at IFA#100 - Clause 6.2.3 adding filter for QueryConfigInfo operation: NFVIFA(18)000498 Status: APPROVED at IFA#103 - Clause 5 and 6 adding query subscriptions operations: NFVIFA(18)000499 Status: APPROVED at IFA#103 - Clause 6 EN resolution aligning terminate subscription operation: NFVIFA(18)000500 Status: APPROVED at IFA#103 - Clause 7 EN resolution information specific info objects: NFVIFA(18)000501 Status: APPROVED at IFA#103 - Clause 6 and 7 EN resolution log report condition and location: NFVIFA(18)000502 Status: APPROVED at IFA#103 - Clause 7.2.10 EN resolution ManoService and ManoInterface: NFVIFA(18)000544 Status: APPROVED at IFA#104 - Clause 7.2.4 EN resolution apiEndpoint: NFVIFA(18)000545r2 Status: APPROVED at IFA#104 - Clause 3 adding definitions and abbreviations: NFVIFA(18)000528r3 Status: APPROVED at IFA#104 - Clause 4.3 and 7.2, update description and clarifications of NFV-MANO service and interface: NFVIFA(18)000543r2 Status: APPROVED at IFA#104 - Clause 8 EN resolution and improvements to workflow measurements: NFVIFA(18)000572 Status: APPROVED at IFA#104 - Clause 8 correcting measurement unit: NFVIFA(18)000573 Status: APPROVED at IFA#104 - General consistency review: NFVIFA(18)000574 Status: APPROVED at IFA#104 - Multiple clauses deletion guideline EN: NFVIFA(18)000575 Status: APPROVED at IFA#104 - Clause 7.3.2 Change later specification statement: NFVIFA(18)000623 Status: APPROVED at IFA#104 - General consistency review for IFA031 v0.5.0: NFVIFA(18)000677 Status: APPROVED at IFA#107 - Clause 5 Consistency review alignment interface reqs: NFVIFA(18)000678 Status: APPROVED at IFA#107 - Clause 7 generalize IE clauses: NFVIFA(18)000679 Status: APPROVED at IFA#107 - Clause 7 Consistency review missing mandatory statements for notifications: NFVIFA(18)000680 Status: APPROVED at IFA#107 - Clause 7 Consistency review writable attributes: NFVIFA(18)000681r1 Status: APPROVED at IFA#107 - Clauses 5 and 7 Clean-up related heartbeat functionality and addressing and EN: NFVIFA(18)000682 Status: APPROVED at IFA#107	IFA031	May-2018	Completed
014	Review of security aspects. Security-related editor's notes are available throughout the IFA031 GS draft. The contributions needed to resolve those editor's notes which are specific to security topics will be listed here. Contributions: - Clause 9 security considerations: NFVIFA(18)000538r2 Status: APPROVED at IFA#108 - Multiple clauses EN resolution consumer and securityInfo: NFVIFA(18)000578r1 Status: APPROVED at IFA#104	IFA031	Jun-2018	Completed

Word version of the implementation plan in contribution NFVIFA(17)000897r1 (check for latest revision). It is very likely that the information contained in this wiki is more recent and updated more frequently.

Issues

List of issues raised based on the feature implementation.
With regards to specific planning action:

• CLOSED: Action 004: description is deemed complete, but needs to be checked with some additional clarification or references to possible informative flows are needed.
  • Status: completed. Additional content was added as part of action 013.
• CLOSED: Action 007: main content is available and approved, but some editor's notes need to be resolved (see action 013).
  • Status: completed. Additional content was added as part of action 013.
• CLOSED: Action 008: main content is available and approved, but some editor's notes need to be resolved (see action 013).
  • Status: completed. Contributions addressing the editor's notes have been approved.
• CLOSED: Action 010: main content is available and approved, but some editor's notes need to be resolved (see action 013).
  • Status: completed. Contributions addressing the editor's notes have been approved.
• CLOSED: Action 004/006/008/010/011: need to analyze and define the relationship of NFV-MANO Service and interfaces.
  • Status: completed. Additional content was added as part of action 013.
• CLOSED: Action 009: main content is available and approved, but some editor's notes need to be resolved (see action 013).
  • Status: completed. Contributions addressing the editor's notes have been approved.
• CLOSED: Action 009: the "heartbeat" functionality was deleted in the approved FM interface and IE contribution (see NFVIFA(18)000215r2). It needs to be resolved how the heartbeat functionality relates to fault management, or whether it needs a specific interface for it.
  • Status: contributions providing a new interface to handle the heartbeat functionality were available, but they were not discussed. The technical assessment and discussion would be postponed to later IFA031 releases, in order to make sure the completion of a stable version of IFA031 for the Rel. 3 drop #1 (1H2018).
• CLOSED: Action 011: main content is available and approved, but some editor's notes need to be resolved (see action 013).
  • Status: completed. Contributions addressing the editor's notes have been approved.
• CLOSED: Action 012: main content is available and approved, but some editor's notes need to be resolved (see action 013).
  • Status: completed. Additional content was added as part of action 013.

Other issues:

• CLOSED: (Jan. 2018) At IFA#84 F2F meeting: discussed the possibility of having some informative information flows to show examples on how the interfaces can be used. An Annex could be added.
  • Status: completed. An annex has been added to add informative information flows. Refer to contribution NFVIFA(18)000449.

Security Considerations

List of security considerations implied by the feature.

• CLOSED: As captured in some editor's notes in clause 6: Editor’s Note: actors in the operations are “consumer” and “NFV-MANO functional entity”. The consumer is intended to be an authorized consumer, thus, not all possible consumers may be authorized to access all operations. Further description and analysis about this is expected to be part of the “Security Considerations” clause.
  • Status: completed. Additional content was added as part of action 014, and in particular with contribution NFVIFA(18)000578r1.
• Action 014 (added in May 2018) to list specific security related contributions.

FEAT15: VNF Snapshotting

Overview

Feature Prime	Jörg Aelken (Ericsson LM) (stage 2) Joan Triay (DOCOMO) (stage 3)
Feature description	The VNF_PHOTO is a feature that has been investigated and described in the published ETSI GR NFV-TST 005. A VNF Snapshot is a replication of a VNF instance at a specific point in time with a corresponding VNF Snapshot Package which is collection of files representing a VNF Snapshot. The feature implementation enables operations on and management of VNF Snapshots and their corresponding packages.
Target Release	Stage 2: Release 3 drop 1 (2018-06) Stage 3: TBD
Impacted WIs	Stage 2: IFA005, IFA006, IFA007, IFA008, IFA010, IFA011, IFA013 Stage 3: SOL002, SOL003, SOL005, SOL001
MegaCRs	Stage 2 - IFA005: NFVIFA(18)000559 Status: Approved MegaCR; Implemented in: IFA005ed311 draft version 3.0.1 - IFA006: NFVIFA(18)000560 Status: Approved MegaCR; Implemented in: IFA006ed311 draft version 3.0.1 - IFA007: NFVIFA(18)000561r3 Status: Approved MegaCR; Implemented in: IFA007ed311 draft version 3.0.2 - IFA008: NFVIFA(18)000535r2 Status: Approved MegaCR; Implemented in: IFA008ed311 draft version 3.0.1 - IFA010: NFVIFA(18)000539 Status: Approved MegaCR; Implemented in: IFA010ed311 draft version 3.0.3 - IFA011: NFVIFA(18)000540r1 Status: Approved MegaCR; Implemented in: IFA011ed311 draft version 3.0.2 - IFA013: NFVIFA(18)000541r1 Status: Approved MegaCR; Implemented in: IFA013ed311 draft version 3.0.3
Related/Dependent Features	N/A
New Specification	Stage 2: Not required Stage 3: SOL010 (VNF Snapshot Package specification)
Status	Stage 2: Completed Stage 3: Ongoing (40%)
Contributions	All feature contributions Agreed content
Feature team	Stage 2: - Bertrand Souville (DOCOMO) - Gerald Kunzmann (DOCOMO) - Jörg Aelken (Ericsson LM) Stage 3: - Joan Triay (DOCOMO) Manchang Ju (ZTE) Yuya Kuno (DOCOMO)
Last Updated	2018-06-28

Stage 2 Implementation Plan

ID	Action	Impacted WI(s)	Target completion	Status
001	Add functional requirements on the NFVO (IFA010 6.2.x) to support granting for VNF/VNFC Snapshot operations, based on Clause 7.2.1 in TST005 (recommendation Nfvo.001). CR draft NFVIFA(17)0001010r1 Status: obsolete	IFA010	November-2017	Completed
002	Add functional requirements on the VNFM (IFA010 7.x) to support VNF/VNFC Snapshot operations and VNF/VNFC Snapshot Packaging, based on Clause 7.2.2 in TST005 (recommendations Vnfm.001 to Vnfm.009). CR draft NFVIFA(17)0001021r2 Status: obsolete	IFA010	November-2017	Completed
003	Add functional requirements on the VIM (IFA010 8.x) to support virtualized resource Snapshot capabilities based on Clause 7.2.3 in TST005 (recommendations Vim.001 and Vim.002). CR draft NFVIFA(17)0001032r4 Status: obsolete	IFA010	November-2017	Completed
004	Add requirement on Virtualised Resources Management interface on the Or-Vi reference point (IFA005 clause 5.3.5) to support attaching/detaching Volumes to virtualized compute resources, based on Clause 7.5.2 in TST005 (recommendations OrVi-Vcrm.001 and OrVi-Vcrm.002). CR draft NFVIFA(18)000030 Status: obsolete	IFA005	December-2017	Completed
005	Add new operation for attaching/detaching Volumes, including new information elements, to Virtualized Compute Resources Management interface (IFA005 clause 7.3.1.x), based on Clause 7.5.2 in TST005 (recommendations OrVi-Vcrm.001 and OrVi-Vcrm.002). CR draft NFVIFA(18)000031r1 Status: obsolete	IFA005	December-2017	Completed
006	Add values to the computeOperation parameter descriptions of the OperateComputeRequest and OperateComputeResponse of the Virtualized Compute Management interface (IFA005 clause 7.3.1.6) to support quiescing/unquiescing and reverting to Snapshot virtualised compute resources, based on Clause 7.5.2 in TST005 (recommendations OrVi-Vcrm.003 to OrVi-Vcrm.005). CR draft NFVIFA(17)0001082 Status: obsolete	IFA005	December-2017	Completed
007	Add value to the storageOperation parameter description of the OperateStorageRequest of the Virtualized Storage Management interface IFA005 clause 7.5.1.6.2) to support reverting to Snapshot virtualised storage resources, based on Clause 7.5.2 in TST005 (recommendation OrVi-Vsrm.001). CR draft NFVIFA(17)0001083 Status: obsolete	IFA005	December-2017	Completed
008	Mirror requirements from IFA005 towards IFA006, i.e. - Add requirement on Virtualised Resources Management interfaces on the Vi-Vnfm reference point (IFA006 clause 5.3.3) to support attaching/detaching Volumes to virtualized compute resources, based on Clause 7.5.1 in TST005 (recommendations ViVnfm-Vcrm.001 and ViVnfm-Vcrm.002). CR draft NFVIFA(18)000033 Status: obsolete - Add new operation for attaching/detaching Volumes, including information elements, to Virtualized Compute Resources Management interface (IFA006 clause 7.3.1.x), based on Clause 7.5.1 in TST005 (recommendations ViVnfm-Vcrm.001 and ViVnfm-Vcrm.002). CR draft NFVIFA(18)000035r1 Status: obsolete - Add values to the computeOperation parameter descriptions of the OperateComputeRequest and OperateComputeResponse of the Virtualized Compute Management interface (IFA006 clause 7.3.1.6) to support quiescing/unquiescing and reverting to Snapshot virtualised compute resources, based on Clause 7.5.1 in TST005 (recommendations ViVnfm-Vcrm.003 to ViVnfm-Vcrm.005). CR draft NFVIFA(17)0001084 Status: obsolete - Add value to the storageOperation parameter description of the OperateStorageRequest of the Virtualized Storage Management interface (IFA006 clause 7.5.1.6.2) to support reverting to Snapshot virtualised storage resources, based on Clause 7.5.1 in TST005 (recommendation ViVnfm-Vsrm.001). CR draft NFVIFA(17)0001085 Status: obsolete	IFA006	December-2017	Completed
009	Add a requirement on the Or-Vnfm reference point (IFA007 clause 5.2) to support a Snapshot Package Management interface produced by the VNFM, based on Clause 7.5.3 in TST005 (recommendation Or-Vnfm.001) and Clause 7.5.4 in TST005 (recommendation OrVnfm-Vspm.001). CR draft NFVIFA(18)000006r2 Status: obsolete	IFA007	January-2018	Completed
010	Add requirements on a new Snapshot Package Management interface on the Or-Vnfm reference point (IFA007 clause 5.3.x) to support VNF Snapshot Package operations, based on Clause 7.5.4 in TST005 (recommendations OrVnfm-Vspm.002 to OrVnfm-Vspm.005). CR draft NFVIFA(18)000007r4 Status: obsolete	IFA007	January-2018	Completed
011	Add new Snapshot Package Management interface specification (IFA007 clause 7.x) to support VNF Snapshot Package operations, based on Clause 7.5.4 in TST005 (recommendations OrVnfm-Vspm.002 to OrVnfm-Vspm.005). CR draft NFVIFA(18)000008r16 Status: obsolete	IFA007	January-2018	Completed
012	Add a requirement on the Ve-Vnfm-vnf reference point (IFA008 clause 5.3.0) to support a VNF Snapshot Notification interface produced by the VNFM, based on Clause 7.5.5 in TST005 (recommendation Ve-Vnfm-vnf.001) and Clause 7.5.6 in TST005 (recommendation VeVnfmvnf-Vsn.001). Status: Not needed according to alternative solution (see note)	IFA008	January-2018	Not needed
013	Add requirements on the Ve-Vnfm-em and Ve-Vnfm-vnf reference points (IFA008 clause 5.2.1.1 and 5.3.1.1) to support receiving confirmations upon sent VNF lifecycle management operation occurrence notifications related to VNF Snapshots to enable the continuation or abortion of a VNF Snapshot operation after required modifications in the VNF triggered by the notification. This solution was preferred over and replaces the original intended solution of adding requirements on a new VNF Snapshot Notification interface on the Ve-Vnfm-vnf reference point (IFA008 clause 5.3.1.x) to support VNF Snapshot notifications, based on Clause 7.5.6 in TST005 (recommendations VeVnfmvnf-Vsn.002 and VeVnfmvnf-Vsn.003). (see note) CR draft NFVIFA(18)000012 Status: obsolete	IFA008	January-2018	Completed
014	Add specifications on the VNF Lifecycle Management interface (IFA008 clause 7.2.x) to receive confirmations upon sent VNF lifecycle management operation occurrence notifications related to VNF Snapshot to enable the continuation or abortion of a VNF Snapshot operation after required modifications in the VNF triggered by the notification. This solution was preferred over and replaces the original intended solution of adding a new VNF Snapshot Notification interface specification (IFA008 clause 7.x) to support VNF Snapshot notifications, based on Clause 7.5.6 in TST005 (recommendations VeVnfmvnf-Vsn.002 and VeVnfmvnf-Vsn.003). (see note) CR draft NFVIFA(18)000013 Status: obsolete	IFA008	January-2018	Completed
015	Add requirements on VNF Lifecycle Management interface on the Ve-Vnfm-em reference point (IFA008 clause 5.2.1.1) to support querying/deleting available VNF/VNFC Snapshot information and to support create/revert to VNF/VNFC Snapshot operations, based on Clause 7.5.7 in TST005 (recommendations VeVnfmem-Vlm.001 and VeVnfmem-Vlm.002). CR draft NFVIFA(18)000070r1 Status: obsolete	IFA008	January-2018	Completed
016	Add new operations for querying/deleting information on available VNF/VNFC Snapshots and creating/reverting to VNF/VNFC Snapshots, including information elements, to VNF Lifecycle Management interface (IFA008 clause 7.2.x), based on Clause 7.5.7 in TST005 (recommendations VeVnfmem-Vlm.001 and VeVnfmem-Vlm.002). CR draft NFVIFA(18)000071r2 Status: obsolete	IFA008	January-2018	Completed
017	Add requirements on NS Lifecycle Management interface on the Os-Ma-Nfvo reference point (IFA013 clause 5.3.2) to support querying/deleting available VNF/VNFC Snapshot information and to support create/revert to VNF/VNFC Snapshot operations, based on Clause 7.5.8 in TST005 (recommendations OsMaNfvo-Nslm.001 and OsMaNfvo-Nslm.002). CR draft NFVIFA(18)000230r3 Status: obsolete	IFA013	February-2018	Completed
018	Add new values to the updateType for deleting VNF Snapshot information and for creating/reverting to VNF Snapshots and new parameters, including information elements, to the Update NS operation of the NS Lifecycle Management interface (IFA013 clause 7.3.5), based on Clause 7.5.8 in TST005 (recommendations OsMaNfvo-Nslm.001 and OsMaNfvo-Nslm.002). CR draft NFVIFA(18)000231r5 Status: obsolete	IFA013	February-2018	Completed
019	Add Opconfig Information Elements to enable the configuration of LCM snapshot operations (IFA011 clause 7.1.5). CR draft NFVIFA(18)000457 Status: obsolete	IFA011	March-2018	Completed
020	Add new events to the LifeCycleManagementScript related to VFN Snapshotting (IFA011 clause 7.1.13). CR draft NFVIFA(18)000458r1 Status: obsolete	IFA011	March-2018	Completed
021	Add a new attribute to the Vdu information element (IFA011 clause 7.1.6.2.2) with a content of a new information element for VNFC Snapshot descriptor. CR draft not required for Release 3 drop 1. The additional VNFC Snapshot properties are not required for a complete VNF Snapshot feature implementation. For further study which properties are needed and which of them are required to be modifiable, might be added as maintenance CR later.	IFA011	March-2018	Not needed
022	Add the specification of a new information element for a VNFC Snapshot descriptor (IFA011 clause 7.1.6.x), based on Clause 7.3 in TST005 (recommendations Vnfsd.005 to Vnfsd.016). CR draft not required for Release 3 drop 1. The additional VNFC Snapshot properties are not required for a complete VNF Snapshot feature implementation. For further study which properties are needed and which of them are required to be modifiable, might be added as maintenance CR later.	IFA011	March-2018	Not needed
023	Mirror VNF lifecycle management interface extensions for Snapshots from IFA008 to IFA007: - Add requirements on VNF Lifecycle Management interface on the Or-Vnfm reference point (IFA007 clause 5.3.4) to support querying/deleting available VNF Snapshot information and to support create/revert to VNF Snapshot operations. CR draft NFVIFA(18)000126r1 Status: obsolete - Add new operations for querying/deleting information on available VNF Snapshots and creating/reverting to VNF Snapshot, including information elements, to VNF Lifecycle Management interface (IFA007 clause 7.2.x). CR draft NFVIFA(18)000127r3 Status: obsolete	IFA007	February-2018	Completed
024	Extend the Grant VNF Lifecycle Operation operation of the VNF Lifecycle Operation Granting interface (IFA007 clause 6.3.2) to support granting of VNF Snapshot operations. CR draft NFVIFA(18)000144 Status: obsolete	IFA007	February-2018	Completed
025	Mirror VNF Snapshot Package Management interface specifications from IFA007 to IFA013: - Add a requirement on the Os-Ma-nfvo reference point (IFA013 clause 5.2) to support a VNF Snapshot Package Management interface produced by the NFVO. CR draft NFVIFA(18)000130r2 Status: obsolete - Add requirements on a new Snapshot Package Management interface on the Os-Ma-nfvo reference point (IFA013 clause 5.3.x) to support VNF Snapshot Package operations. CR draft NFVIFA(18)000131r4 Status: obsolete - Add new Snapshot Package Management interface specification (IFA013 clause 7.x) to support VNF Snapshot Package operations. CR draft NFVIFA(18)000132r8 Status: obsolete	IFA013	February-2018	Completed
026	Mirror trigger conditions for VnfLcmOperationOccurrenceNotification from IFA008 to IFA007: - Add trigger conditions for VnfLcmOperationOccurrenceNotification for create and revert-to VNF Snapshots to information elements and notifications related to VNF Lifecycle Changes (IFA007 clause 8.6.2.2). CR draft NFVIFA(18)000281 Status: obsolete	IFA007	April-2018	Completed
027	Add description on filters and attributes for VNF Snapshot information, including information elements, to the Query NS operation of the NS Lifecycle Management interface (IFA013 clauses 7.3.6 and 8.3.3). CR draft NFVIFA(18)000284r1 Status: obsolete	IFA013	April-2018	Completed
028	Add support of a VNFC Snapshot Package Management interface to Ve-Vnfm-em reference point: - Add requirements on a new VNFC Snapshot Package Management interface on the Ve-Vnfm-em reference point (IFA008 clause 5.2.x). CR draft NFVIFA(18)000424 Status: obsolete - Add specification of the VNFC Snapshot Package Management interface on the Ve-Vnfm-em reference point (IFA008 clauses 7.X, 9.Y). CR draft NFVIFA(18)000460r1 Status: obsolete	IFA008	May-2018	Completed
029	Add support for requesting transfer of VNF Snapshot Package image artefacts from the NFVO towards the VIM. CR draft not required for Release 3 drop 1. The information on the image artifacts is already included in the information element VnfcSnapshotImageInfo, available after package upload. The NFVO can access this IE after the extraction of the package is requested and can then transfer the images from the VIM using the provided access information.	IFA007	May-2018	Not needed
030	Add support for granting of VNF Snapshot Package operations. CR draft not required for Release 3 drop 1. Current assumption is that it is not needed, but instead the NFVO is expected to validate incoming requests based on policies/VNFD and only forwards allowed requests to the VNFM. Might be needed for Snapshot Package management exposed towards EM (IFA008). For further study, might be added as maintenance CR later.	IFA013	May-2018	Not needed
NOTE: An alternative solution for a VNF Snapshot Notification Interface in IFA008 could be to add a new VNF Snapshot notification type to the VNF LCM interface. The final solution will be developed when working on the items for IFA008. After investigation of the alternative, it was decided to implement this alternative by re-using the VNF lifecycle notification interface and adding an operation to enable the VNF/EM to confirm the received notification concerning VNF snapshotting.

Stage 3 Implementation Plan

ID	Action	Impacted WI(s)	Target completion	Status
001	TBD CR draft. Status: TBD	SOL003	TBD	TBD

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.