Feature Tracking Release 5

Introduction

Current mirror date: 2024.02.14

This page is a mirror of the Release 5 Feature Tracking Page on the NFV private wiki. Feature tracking information is frequently updated on the private wiki page and regularly mirrored onto the present public page. Links to contributions will require authentication with an ETSI Online Account.

Feature Overview Release 5

Feature Overview and Status

Feature	Stage 1	Stage 2	Stage 3
FEAT19a (Rel. 5 extensions): Enhanced container networking	ongoing (Rel 5)	not started	not started
FEAT19b: NFV-Connect - connectivity integration and operationalization	ongoing (Rel 5)	not started	not started
FEAT20: Auto	completed (Rel 4)	completed (Rel 4)	not started
FEAT21: 5GNFV	completed (Rel 4)	ongoing (Rel 4 & 5)	ongoing (Rel 4 and 5)
FEAT22: M-Tenant	ongoing (Rel 5)	not started	not started
FEAT24: VNF generic management functions	completed (Rel 5)	ongoing (Rel 5)	not started
FEAT26: Policy-models	completed (Rel 4)	completed (Rel 4)	ongoing (Rel 5)
FEAT27: NFV for vRAN	completed (Rel 5)	ongoing (Rel 5)	not started
FEAT29: Green NFV	completed (Rel 5)	ongoing (Rel 5)	not started
FEAT30: VNF configuration	completed (Rel 5)	ongoing (Rel 5)	not started
FEAT31: Flexible VNF deployment	completed (Rel 4 and 5)	completed (Rel 4 and 5)	completed (Rel 4 and 5)
FEAT33: Physical Infrastructure Management	ongoing (Rel 5)	ongoing (Rel 5)	not started
FEAT35: VNF management gaps with Open Source	completed (Rel 5)	ongoing (Rel 5)	not started
ENH01.01: Certificate Management	completed (Rel 4) Rel 5 not started	completed (Rel 4)	ongoing (Rel4)
ENH02: Special technical enhancements (Rel 5)	none applied yet (Rel 5)	not started	not started
NOTEs: none so far

FEAT19: NFV-Conn

Overview

Feature Prime	Manchang Ju (ZTE), ju.manchang@zte.com.cn Hammad Zafar (NEC), Hammad.Zafar@neclab.eu
Feature description	The scope of IFA038 (Release 4) covers the following areas: a) investigating aspects of network connectivity for container-based VNF, b) determining the enhancement related to NFV descriptors and NFV-MANO functional aspects for the management of network connectivity of containerized VNFs, c) determining the enhancement related to NFV-MANO interfaces for the management of OS container multiple networks. The scope of IFA035 (Release 4) covers the following areas: A “flatter” networking to remove complex L1 and L2 network layering dependencies for the network functions. Exposure of high-performance overlay network capabilities to network functions. Support of dynamic routing capabilities in the network. Enable more dynamic network provisioning and reconfiguration “end-to-end”, within and across sites. Minimize manual intervention for network provisioning, while increasing automation. The scope of IFA043 (Release 5) covers the following areas: Analyse the telecom specific use cases (e.g., interconnectivity among operators, connectivity for containers realizing vRAN, etc.) The scenarios, requirements and solutions applicable to the container networking for NFV system are proposed for the maximum reuse of open source technologies The enhancement of OS container multiple networks management Define network policy for effective isolation of networks Automated network orchestration for container networking
Target Release	Stage 2 Step 1 : Release 4 drop 3 (2022-02) Stage 2 Step 2 : Release 4 drop 5 (2023-07) Stage 3 Step 2: Release 4 ed431 (2022-07)
Impacted WIs	Stage 2: IFA010, IFA007, IFA011, IFA013, IFA014 Stage 3: SOL001, SOL002, SOL003, SO005, SOL006
MegaCRs	Stage 2 Step 1 (drop3): IFA010 MegaCR NFVIFA(22)000179 (Approved at IFA#276) IFA040 MegaCR NFVIFA(22)000180 (Approved at IFA#276)
Related/Dependent Features	FEAT17
New Specifcations	Informative: ETSI GR NFV-IFA 038 , ETSI GR NFV-IFA 035 (completed), ETSI GR NFV-IFA 043 (ongoing) Normative: not required
Status	Stage 2 Step 1: Completed Stage 2 Step 2: Ongoing Stage 3 Step 1: Completed
Contributions	All feature contributions Agreed content
Feature team	Stage 2: Manchang Ju (ZTE), Hammad Zafar (NEC), Baoguo Xie(ZTE) Stage 3: Name (Company)
Last Updated	2023-09-22

Stage 1 Informative Work Plan

Informative work in ETSI GR NFV-IFA 035 (October 2019 - June 2023)

IFA035

ID	Action	Impacted WG(s)	Target completion	Status
001	Scope and skeleton draft for GR IFA035 Accepted contributions: NFVIFA(19)000918r2, NFVIFA(19)000956	IFA	December-2019	Completed
002	Clause 4 Overview and introduction of networking infrastructure and virtual networks; Annex examples of networking infrastructure and virtual networks Accepted contributions: NFVIFA(20)000207r1, NFVIFA(20)000208, NFVIFA(20)000335r2, NFVIFA(20)000292	IFA	July-2020	Completed
003	Clause 4: Overview of networking technologies(Carrier Ethernet, network isolation), Connectivity services for L2VPN and L3VPN technologies Accepted contributions: NFVIFA(20)000541r1, NFVIFA(20)000613r2, NFVIFA(20)000676r1, NFVIFA(20)000827	IFA	December-2020	Completed
004	Clause 4: Overview of networking technologies(MPLS, Carrier Ethernet); Clause 5: Intra-site networking infrastructure and virtual networks, L2VPN technologies (VXLAN, NVGRE); Clause 6: Inter-site networking infrastructure and virtual networks Accepted contributions: NFVIFA(21)000900r1, NFVIFA(21)0001021r1; NFVIFA(21)000788r1, NFVIFA(21)0001019, NFVIFA(21)0001020r1; NFVIFA(21)000911r2	IFA	December-2021	Completed
005	Clause 4 Overview of networking technologies (MPLS, BGP); Clause 5 L2VPN & L3VPN technologies (VPLS, VLAN, IPSec); Clause 6: L2VPN technologies (EVPN) Accepted contributions: NFVIFA(22)000321r1, NFVIFA(22)000367; NFVIFA(22)000122r2, NFVIFA(22)000397r1; NFVIFA(22)000366r1	IFA	June-2022	Completed
006	Clause 4: Overview of networking technologies (Segment Routing), Clause 5: L3VPN technologies (iBGP), Analysis of L2VPN & L3VPN technologies for intra-site; Clause 6: L3VPN technologies (MPLS) Accepted contributions: NFVIFA(22)000925r1; NFVIFA(22)000521r1, NFVIFA(22)000672, NFVIFA(22)000870, NFVIFA(22)000919r2; NFVIFA(22)000671	IFA	December-2022	Completed
007	Clause 4: Overview of networking technologies (SDN); Clause 6 L3VPN technologies (MPBGP); Clause 7: Recommendations related to interfaces and information elements Accepted contributions: NFVIFA(23)000157; NFVIFA(23)000171; NFVIFA(23)000130	IFA	March-2023	Completed
008	Clause 5: OAM solutions and analysis; Clause 6: L3VPN Analysis for inter-site, OAM solutions and analysis; Clause 7 Recommendations; and Clause 8 Conclusion Accepted contributions: NFVIFA(23)000158r1, NFVIFA(23)000159r1, NFVIFA(23)000249r1, NFVIFA(23)000383, NFVIFA(23)000384; NFVIFA(23)000254, NFVIFA(23)000420r1, NFVIFA(23)000431r1, NFVIFA(23)000432, NFVIFA(23)000433	IFA	June-2023	Completed
009	WG Review of IFA035 Accepted contributions: NFVIFA(23)000541r1; NFVIFA(23)000542r1; NFVIFA(23)000564r3; NFVIFA(23)000563r3; NFVIFA(23)000585r2; NFVIFA(23)000609r2	IFA	August-2023	Completed

IFA043

Informative work in ETSI GR NFV-IFA 043(July 2021 - July 2023)

ID	Action	Impacted WG(s)	Target completion	Status
001	First GR draft introducing the skeleton and the scope. Accepted contributions: NFVIFA(21)000786r1, NFVIFA(21)000787r1	IFA	October-2021	Done
002	Problem statement and introducion Accepted contributions: NFVIFA(21)000961r2, NFVIFA(21)000962r2	IFA	December-2021	Done
003	Use case for CCM preconfigures cluster network Accepted contributions: NFVIFA(22)000159r4	IFA	April-2022	Done
004	Network policy and use case for re-configuration of secondary container cluster network Accepted contributions: NFVIFA(22)000897, NFVIFA(22)898r4	IFA	December-2022	Done
005	Solutions for re-configuration of secondary container cluster networks and pre-configuration of secondary container cluster networks	IFA	June-2023	ongoing
006	support of network policies, Potential architectural enhancements	IFA	June-2023	Not started
007	Recommendations related to NFV descriptors and other artefacts if needed Recommendations on architectural framework if needed Recommendations on functional aspects if needed	IFA	July-2023	Not started

Stage 2 Implementation Plan

Informative work in ETSI GR NFV-IFA 038(October 2019 - November 2021)

IFA038

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

Normative work plan (December 2021- February 2022)

ID	Action	Impacted WI(s)	Target completion	Status
001	Add general functional requirements for management of connectivity for multiple networks. Add functional requirements for the NFVO, VNFM and CISM to support of the management of network connectivity of containerized VNFs.	IFA010	Dec-2021	Completed
002	Add functional requirements for the VNFM, and interface and information model specification for the VNF LCM to support OS container multiple networks.	IFA007	July-2023	Not started
003	Add requirements and modelling for the VNFD and NSD to support describing the properties for one or more secondary container cluster internal/external networks. Add requirements and modelling for the VNFD and NSD to support describing the information for associating the VLD with the declarative descriptors of secondary container cluster internal/external networks. Add resource requirements for the VNFD to support describing load balancers associated to network MCIOs.	IFA011, IFA014	July-2023	Not started
004	Add functional requirements to the NFVO, and interface and information model specification to the VNF LM or NS LCM to support OS container multiple networks.	IFA013	July-2023	Not started
005	Add service interface requirements related to OS container multiple networks management to the CISM, to support the configuration and management of OS container multiple networks.	IFA040	Jan-2022	Completed
NOTE :

FEAT19b - IFA035

Informative work in ETSI GR NFV-IFA 035 (Dec 2019 - Aug 2023). Normative work for FEAT19b is provided below (Sep 2023 - Aug 2024).

ID	Action	Impacted WI(s)	Target completion	Status
001	Add functional requirements for the NFV architectural framework to support the capabilities regarding network connectivity and integration according to recommendations derived in ETSI GR NFV-IFA 035 (see clause 7.3).	IFA010	Mar-2024	Not started
002	Add enhancements in the relevant interfaces and information elements based on the gaps identified in ETSI GR NFV-IFA 035 (see clause 7.5).	IFA005 IFA006 IFA032	Mar-2024	Not started
003	Enhance NFV descriptors to carry information related to networking management based on the gaps identified in ETSI GR NFV-IFA 035 (see clause 7.4).	IFA011	Mar-2024	Not started
004	Determine the form and place of documentation, and document/specify the interactions between NFV-MANO entities and SDN controllers, and between NFV-MANO entities and other NFVI networking components (e.g., NFVI-PoP network gateway and Intra-NFVI-PoP network fabric) based on the OAM solutions provided in ETSI GR NFV-IFA 035.	IFA0xx	August-2024	Not started

Stage 3 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.

SOL

ID	Action	Impacted WG(s)	Target completion	Status
001	enhance CP for container network (FEAT17) - SOL003 NFVSOL(21)000482r4 - SOL002 NFVSOL(22)000177 (482r4 mirror)	SOL001, SOL002, SOL003, SOL005, SOL006	July-2022	Completed
002	introduce secondary container cluster network - NFVSOL(22)000357r1	SOL018	July-2022	Completed

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT20: Auto

Overview

Feature Prime	Haitao XIA (Huawei), xiahaitao@huawei.com
Feature description	The scope of the feature covers the following areas: - NFV-MANO support for managing autonomous networks. -  Enabling higher level of automation for NFV-MANO. -  Intent-based principles for external exposure network services management.
Target Release	Stage 1: Release 4 informative work (2021-08-17) Published as ETSI GR NFV-IFA 041 v4.1.1. Stage 2 Step 1: MDAF related specs (IFA047) target release v4.4.1, Stage 2 Step 2: Intent management related specs (IFA050) target release v4.5.1. Stage 3: Release 5 (2023-6-30)
Impacted WIs	Stage 2: IFA010ed441 (for MDAF functional requirements), IFA010ed451 (for Intent Management functional requirements) Stage 3: SOLzz
MegaCRs	Stage 2: IFA010 MegaCR NFVIFA(18)000xxx (CR Status, to be created) Stage 3: SOLzzz MegaCR NFVSOL(19)000zzz (CR Status)
Related/Dependent Features	FEAT07 FEAT26
New Specifcations	Stage1:- IFA041 Stage2: - IFA047 (MDAF service interfaces specification) - IFA050 (Intent management service interface specification) Stage3: - SOLxxx (Intent management service interface specification)
Status	Stage 1: Informative work completed (delivered in IFA041) Stage 2 Step 1: Completed Stage 2 Step 2: Completed Stage 3: Not started
Contributions	All feature contributions Agreed content
Feature team	Stage 2: Haitao XIA (Huawei), Cristina BADULESCU (Ericsson), Joan TRIAY (Docomo)，Rajavarma BHYRRAJU (Ericsson), Jiachen ZHANG (China Mobile), Shen GAO (China Telecom), Shitao LI (Huawei) Stage 3: Yu Chao (Huawei)
Last Updated	2023-09-22

Stage 2 Implementation Plan

Informative work in ETSI GR NFV-IFA 041(October 2019 - May 2021)

IFA041

ID	Action	Impacted WG(s)	Target completion	Status
001	First GR (IFA041) draft introducing the skeleton and the scope. Accepted contributions: NFVIFA(19)000859r2, NFVIFA(19)000860r1	IFA	October-2019	Done
002	Overview of related work in NFV-MANO and other SDOs. Accepted contributions: NFVIFA(19)000959, NFVIFA(19)000960r1, NFVIFA(19)000961r2, NFVIFA(19)000962r2, NFVIFA(19)000963r2,	IFA	February-2020	Done
003	Use cases related to NFV-MANO autonomous management, mainly include three categories: - Intent based NS management - Management Data Analytics assisted management - Autonomous container infrastructure management Accepted contributions: NFVIFA(20)000017r1, NFVIFA(20)000021, NFVIFA(20)000051r2, NFVIFA(20)000134r1, NFVIFA(20)000230r1, NFVIFA(20)000245r1, NFVIFA(20)000246r1, NFVIFA(20)000247r2, NFVIFA(20)000248r1, NFVIFA(20)000279r1, NFVIFA(20)000280r1, NFVIFA(20)000319, NFVIFA(20)000281r3, NFVIFA(20)000472r2, NFVIFA(20)000591, NFVIFA(20)000592, NFVIFA(20)000622r1, NFVVIFA(20)000720r3, NFVIFA(20)000781r1, NFVIFA(20)000782r1	IFA	November-2020	Done
004	Analysis of key issues related to use cases in Clause 6. Accepted contributions: NFVIFA(20)000353r1, NFVIFA(20)000354r2, NFVIFA(20)000355r1, NFVIFA(20)000416r2, NFVIFA(20)000418r2, NFVIFA(20)000445r1, NFVIFA(20)000446r1, NFVIFA(20)000447r1, NFVIFA(20)000557, NFVIFA(20)000566r3, NFVIFA(20)000593, NFVIFA(20)000594r3, NFVIFA(20)000623r4, NFVIFA(20)000624r1, NFVIFA(20)000729r3, NFVIFA(20)000732r3, NFVIFA(21)000793r1, NFVIFA(20)000878r1, NFVIFA(20)000879r1, NFVIFA(21)000013 NFVIFA(21)000014r2, NFVIFA(21)000022r1, NFVIFA(21)000058r1	IFA	February-2021	Done
005	Analysis of pontential architectural impacts on NFV-MANO in clause 7. Accepted contributions: NFVIFA(20)000794r1, NFVIFA(20)000797r3, NFVIFA(21)000060, NFVIFA(21)000062r7, NFVIFA(21)000133r2, NFVIFA(21)000134r5, NFVIFA(21)000135r2, NFVIFA(21)000149r7	IFA	May-2021	Done
006	Recommendations and conclusion in clause 8. Accepted contributions: NFVIFA(21)000073, NFVIFA(21)000280r1, NFVIFA(21)000281r3, NFVIFA(21)000284r2, NFVIFA(21)000285r2, NFVIFA(21)000321r3, NFVIFA(21)000322r1, NFVIFA(21)000413	IFA	May-2021	Done

Normative work plan (October 2021- June 2022)

• Not urgent for ISG NFV to start the stage 2 normative work, need more close observation/analysis on 3GPP SA5 R17 related normative work (IDMS and MDAS) and FEAT23 output on MANO SBA.
• One or two new group specifications are expected to carry stage 2 normative work on intent management and MDA interfaces.
• MDA input information model improvement related normative work has been kicked off by FEAT28/IFA045 development.

IFA047/IFA050

(IFA047 development in March 2022 to January 2023, IFA050 development in July 2022 to June 2023)

ID	Action	Impacted WG(s)	Target completion	Status
001	IFA047 first draft including the skeleton and scope	IFA	March-2022	Done
002	IFA047 interface requirements specification	IFA	May-2022	Done
003	IFA047 interface operations specification	IFA	November-2022	Done
004	IFA047 annex on use cases (stable draft) and IFA010ed441 megaCR	IFA	December-2022	Done
005	IFA050 first draft including the skeleton and scope	IFA	July-2022	Done
006	IFA050 use cases	IFA	January-2023	Done
007	IFA050 interface requirements specification	IFA	January-2023	Done
008	IFA050 interface operations specifications and IFA010ed451 megaCR	IFA	June-2023	Done

Stage 3 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.

SOL

ID	Action	Impacted WG(s)	Target completion	Status
001	new interface intent management service	SOL	June-2024	Open

Issues

List of issues raised based on the feature implementation.

Security Considerations

N/A.

FEAT21: 5GNFV

Overview

Feature Prime	Joan Triay (DOCOMO)
Feature description	The scope of the feature covers the following areas: a) investigating the NFV support for deploying 5G networks, capabilities and associated requirements. b) determine the 5G network capabilities and features interworking and their relationship with NFV, and c) determine and profile how NFV can support 5G deployments.
Target Release	Stage 2: Release 4 (2023/07) Stage 3: Release 4 (2023/10)
Impacted WIs	Stage 2: IFA010, IFA013, IFA014, IFA011, IFA007, IFA008, IFA049 Stage 3: SOL001, SOL002, SOL003, SOL005
MegaCRs	Stage 2: ed431: includes action 007 of stage 2 work, i.e. "Add enhancements related to NSD processing" - IFA010: NFVIFA(22)000186r1 IFA010ed431 FEAT21 MegaCR --> Approved at IFA#277 - IFA013: NFVIFA(22)000187r2 IFA013ed431 FEAT21 MegaCR --> Approved at IFA#277 - IFA014: NFVIFA(22)000188r1 IFA014ed431 FEAT21 MegaCR --> Approved at IFA#277 - MegaCR Index: NFVIFA(22)000248r2 FEAT21 stage 2 set #1 in ed431 MegaCR Index ed441: no updates ed451: - IFA010: NFVIFA(23)000010r3 IFA010ed451 FEAT21 MegaCR for PaaS Services aspects --> Approved at IFA#337 - IFA007: NFVIFA(23)000347r3 IFA007ed451 FEAT21 MegaCR for PaaS Services aspects --> Approved at IFA#337 - IFA008: NFVIFA(23)000419r1 IFA008ed451 FEAT21 MegaCR for PaaS Services aspects --> Approved at IFA#337 - IFA011: NFVIFA(23)000346r3 IFA011ed451 FEAT21 MegaCR for PaaS Services aspects --> Approved at IFA#337 - IFA013: NFVIFA(23)000418r2 IFA013ed451 FEAT21 MegaCR for PaaS Services aspects --> Approved at IFA#337 - IFA014: NFVIFA(23)000389r1 IFA014ed451 FEAT21 MegaCR for PaaS Services aspects --> Approved at IFA#337 - IFA011: NFVIFA(23)000524r1 IFA011ed451 FEAT21 MegaCR for other enhancements --> Approved at IFA#343 - IFA014: NFVIFA(23)000525 IFA014ed451 FEAT21 MegaCR for other enhancements --> Approved at IFA#343 - IFA007: NFVIFA(23)000526 IFA007ed451 FEAT21 MegaCR for other enhancements --> Approved at IFA#343 - IFA008: NFVIFA(23)000527 IFA008ed451 FEAT21 MegaCR for other enhancements --> Approved at IFA#343 - IFA013: NFVIFA(23)000528 IFA013ed451 FEAT21 MegaCR for other enhancements --> Approved IFA#343 - MegaCR Index: NFVIFA(23)000533r2 FEAT21 IFAed451 MegaCR Index
Related/Dependent Features	FEAT17 on "Cloud-native VNF and container infrastructure management" FEAT19 on "NFV connectivity"
New Specifcations	Informative: DGR/NFV-IFA037 Stage 2: None (currently) Stage 3: TBD
Status	Informative: completed Stage 2: ongoing (85%) Stage 3: ongoing (20%)
Contributions	All feature contributions Agreed content
Feature team	Informative: Joan Triay (DOCOMO) Stage 2: Joan Triay (DOCOMO) Stage 3: Bertrand (DOCOMO)
Last Updated	2024-02-12

Informative work

IFA

ID	Action	Impacted WG(s)	Target completion	Status
001	Skeleton and scope - NFVIFA(19)000900 IFA037 skeleton --> Approved - NFVIFA(19)000901 IFA037 Scope --> Approved	IFA	Nov-2019	Completed
002	Introduction and overview - NFVIFA(20)0001021 IFA037 Clause 4.1 Introduction to 5G network --> Approved - NFVIFA(20)0001022 IFA037 Clause 4.2 Characteristics of 5G network --> Approved - NFVIFA(20)000830 IFA037 Clause 5.1 Introduction to characteristics --> Approved	IFA	Jan-2020	Completed
003	Profiling and analysis of characteristic: Network function modularization - NFVIFA(20)000760r1 IFA037 Clause 5 Adding characteristic NF modularization --> Approved - NFVIFA(21)000573 FEAT21 IFA037 Clause 5.2 Gap analysis modularization --> Approved	IFA	Dec-2020	Completed
004	Characteristic: Service-based interfaces, communication and service mesh - NFVIFA(21)000100r1 FEAT21 IFA037 Clause 5 Adding characteristic SBI, communication and service mesh --> Approved - NFVIFA(21)000544 FEAT21 IFA037 Clause 5.3 Adding missing solutions on SBI, communication and mesh --> Approved - NFVIFA(21)000574 FEAT21 IFA037 Clause 5.3 Gap analysis SBI --> Approved	IFA	Feb-2021	Completed
005	Characteristic: Network slicing - NFVIFA(21)000099r3 FEAT21 IFA037 Clause 5 Adding characteristic network slicing --> Approved - NFVIFA(21)000545 FEAT21 IFA037 Clause 5.4 Completing solutions of network slicing --> Approved - NFVIFA(21)000575 FEAT21 IFA037 Clause 5.4 Gap analysis network slicing --> Approved	IFA	Feb-2021	Completed
006	Characteristic: Convergent (3GPP and non-3GPP) access - NFVIFA(21)000522r1 FEAT21 IFA037 Clause 5 Adding characteristic Convergent access --> Approved - NFVIFA(21)000594 FEAT21 IFA037 Clause 5.10 Gap analysis convergent access --> Approved	IFA	Jun-2021	Completed
007	Characteristic: Stateless NF, with separation of data processing from state - NFVIFA(21)000257 IFA037 Clause 5 Adding characteristic Stateless NF --> Approved - NFVIFA(21)000592r1 FEAT21 IFA037 Clause 5.7 Gap analysis stateless NF --> Approved	IFA	Mar-2021	Completed
008	Characteristic: Network capabilities exposure - NFVIFA(21)000502 FEAT21 IFA037 Clause 5 Adding characteristic Network capabilities exposure --> Approved - NFVIFA(21)000595r2 FEAT21 IFA037 Clause 5.8 Gap analysis Network capabilities exposure --> Approved - NFVIFA(21)000722r3 FEAT21 IFA037 Start cleaning up EN_nef_non3gpp --> Approved	IFA	May-2021	Completed
009	Characteristic: Distribution of services across the network (local and centralized) - NFVIFA(21)000293r1 FEAT21 IFA037 Clause 5 Adding characteristic distribution of services across the network --> Approved - NFVIFA(21)000576r1 FEAT21 IFA037 Clause 5.4 Gap analysis services distribution --> Approved	IFA	Mar-2021	Completed
010	Characteristic: Unified authentication framework - NFVIFA(21)000329r1 IFA037 Clause 5 Adding characteristic Unified authentication framework --> Approved - NFVIFA(21)000496r1 FEAT21 IFA037 5.6 Adding potential solutions for characteristic Unified authentication framework --> Approved	IFA	May-2021	Completed
011	Characteristic: Roaming capabilities - NFVIFA(21)000526 FEAT21 IFA037 Clause 5 Adding characteristic roaming --> Approved - NFVIFA(21)000593 FEAT21 IFA037 Clause 5.9 cleaning up editor notes --> Approved	IFA	Jul-2021	Completed
012	Derivation of recommendations and conclusion - NFVIFA(21)000639r1 FEAT21 IFA037 Clause 6.1 Adding recommendations overview --> Approved - NFVIFA(21)000659r2 FEAT21 IFA037 Clause 6 Adding recommendations related to all characteristics --> Approved - NFVIFA(21)000660 FEAT21 IFA037 Clause 7 Adding Conclusion --> Approved - NFVIFA(21)000660 FEAT21 IFA037 Clause 7 Adding Conclusion --> Approved - NFVIFA(21)000678r4 FEAT21 IFA037 Clause 6 Adding recommendations related to unified authentication --> Approved	IFA	Jul-2021	Completed
013	Address remaining major technical editor's notes - NFVIFA(21)000543 FEAT21 IFA037 Start cleaning up EN --> Approved - NFVIFA(21)000544 FEAT21 IFA037 Clause 5.3 Adding missing solutions on SBI, communication and mesh --> Approved - NFVIFA(21)000545 FEAT21 IFA037 Clause 5.4 Completing solutions of network slicing --> Approved - NFVIFA(21)000677r2 FEAT21 IFA037 Clause 5.6 addresses Editor’s Note about SEC005 and gap analysis of unified authentication framework --> Approved - NFVIFA(21)000698 FEAT21 IFA037 Clauses 5.4.2.2 and 6.5 addressing EN about L2 connectivity --> Approved - NFVIFA(21)000722r3 FEAT21 IFA037 Start cleaning up EN_nef_non3gpp --> Approved	IFA	Jun/Jul-2021	Completed
014	Final review - NFVIFA(21)000748r1 IFA037 Review clause 1,3,4 editorial clean-up --> Approved - NFVIFA(21)000749r1 IFA037 Review clause 5 editorial clean-up --> Approved - NFVIFA(21)000768r1 IFA037 Review clause 6 editorial clean-up --> Approved - NFVIFA(21)000777 IFA037 Review 6.3 refining recommendations 002 and 003 --> Noted - NFVIFA(21)000796r1 IFA037 review - editorial fixes and small technical wording improvements --> Approved - NFVIFA(21)000797 IFA037 review - comments and questions --> Noted - NFVIFA(21)000798r2 IFA037 review - miscellaneous technical improvements --> Approved - NFVIFA(21)000807 FEAT21 IFA037 Clause 5.1 Statement of 3GPP Release baseline and update of references --> Approved - NFVIFA(21)000809r1 FEAT21 IFA037 Clause 4 to 5.6.2.2 Minor miscellaneous changes --> Approved - NFVIFA(21)000820r1 FEAT21 IFA037 Clauses 5.7 to 5.10 Miscellaneous changes --> Approved - NFVIFA(21)000821r1 FEAT21 IFA037 Clauses 6 Miscellaneous changes to recommendations --> Approved - NFVIFA(21)000822 FEAT21 IFA037 Deleting unused clauses --> Approved - NFVIFA(21)000838 IFA037 review - removing misleading recommendations --> Noted - NFVIFA(21)000842r2 FEAT21 IFA037 Deleting unused clauses --> Approved - NFVIFA(21)000848r2 FEAT21_IFA037_Comments_missing_gap_associated_recommendations --> Approved - NFVIFA(21)000849 FEAT21 IFA037 Clause 5.6 Clarifying security aspects --> Approved - NFVIFA(21)000852 FEAT21 IFA037 Security comments in clause 5.6 --> Approved - NFVIFA(21)000872r1 FEAT21_IFA037_security_recommendations_gap 5.5 --> Agreed at IFA#256	IFA	Aug/Sep-2021	Completed

Stage 2 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 WI(s)	Target completion	Status
001	Add functional requirements for the NFV architectural framework to include the support of inventory of VNF Common and Dedicated Services and platform/infrastructure capabilities (5gnfv.arch.001) Contributions: - NFVIFA(21)0001022r2 IFA010ed431 FEAT21 Adding PaaS Services management --> FEAT Agreed at IFA#266 - NFVIFA(22)000123 IFA010ed431 FEAT21 Adding PaaS Services management --> see action 005 Pending CRs: - None	IFA010	Jun-2023	Completed in IFAed451
002	Add functional requirements for the NFV architectural framework to include the support of operator certificate management functions (5gnfv.arch.002), requirements on the operator certificate management functions to synchronize the LCM of the certificates with the LCM operations of the VNF/VNFC (5gnfv.func.008), and retrieval of VNF/VNFC runtime information from VNFM/NFVO (5gnfv.if.011). See note 2.	IFA010	See ENH01.01	See ENH01.01
003	Add functional requirements to the VNFM, and interface and information model specification to the VNF LCM to support adding/removing VNF external CP that are not sub-ports of a trunk (5gnfv.func.001, 5gnfv.if.004).	IFA010, IFA007, IFA008	Jun-2023	Not started
004	Add requirements and modelling for the VNFD and NSD to support describing requirement to use VNF Common/Dedicated Services (5gnfv.desc.001). See note 3. Contributions: - NFVIFA(21)0001025 IFA011ed431 FEAT21 Adding requirements for PaaS Services --> FEAT Agreed at IFA#265 - NFVIFA(21)0001028r1 IFA014ed431 FEAT21 Adding requirements for PaaS Services --> FEAT Agreed at IFA#266 - NFVIFA(23)000276r1 FEAT21 IFA011 VNFD modeling to use PaaS Services: FEAT Agreed at IFA#332 - NFVIFA(23)000277r2 FEAT21 IFA014 NSD modeling to use PaaS Service: FEAT Agreed at IFA#335 - NFVIFA(23)000351 IFA011ed451 FEAT21 VNFD PaaS Servivce modeling refinements on top of 276r1: FEAT Agreed at IFA#335 Pending CRs: - None	IFA011, IFA014	Jun-2023	Completed in IFAed451
005	Determining the mapping and requirements for the NFV architectural framework about the "PaaS service management function" (5gnfv.func.002). See note 3. Contributions: - NFVIFA(22)000123r5 IFA010ed431 FEAT21 Adding PaaS Services management --> FEAT Agreed at IFA#313 - Addressing editor's notes as shown in the interim MegaCR for IFA010 in contribution NFVIFA(23)000010 NFVIFA(23)000278r1 FEAT21 IFA010 Address EN about PSM framework: FEAT Agreed at IFA#332 Pending CRs: - None	IFA010	Jun-2023	Completed in IFAed451
006	Add functional requirements to the VNFM and NFVO to support determining and triggering LCM for VNF Common/Dedicated Services (5gnfv.func.002, 5gnfv.func.003). See note 3. Contributions: - NFVIFA(22)000123r1 IFA010ed431 FEAT21 Adding PaaS Services management --> see action 005 - NFVIFA(23)000279 FEAT21 IFA007 Enhance granting to support PaaS Services requirements for a VNF: FEAT Agreed at IFA#332 - NFVIFA(23)000300 FEAT21 IFA007 Enhance VnfInfo to support PaaS Services information for a VNF: FEAT Agreed at IFA#332 - NFVIFA(23)000301 FEAT21 IFA013 Enhance NsInfo to support PaaS Services information for a VNF and NS: FEAT Agreed at IFA#332 - NFVIFA(23)000409 (Mirror of 300) FEAT21 IFA008 Enhance VnfInfo to support PaaS Services information for a VNF: Almost FEAT agreed at IFA#336 Pending CRs: - None	IFA010, IFA007, IFA008, IFA013	Jun-2023	Completed in IFAed451
007	Add enhancements related to NSD processing: - requirements and modelling on the NSD management interface to allow onboarding of an NSD even if not all VNF packages, nested NSDs and PNFDs have been previously on-boarded (5gnfv.func.004a), - requirements and modelling on the NS LCM to handle the case of not all constituent elements being on-boarded (5gnfv.if.006), - functional requirement to the NFVO to support processing information related to version dependencies between constituent VNF (5gnfv.func.004b), - requirements for the NSD regarding whether NSD on-boarding can be performed even if not all referred VNF Packages, NSD and PNFDs are on-boarded (5gnfv.desc.007a), and - requirements for the NSD to support information related to constituent VNF version dependencies (5gnfv.desc.007b). Contributions: - NFVIFA(22)000086r1 FEAT21-IFA010ed431-Clause 6.3.1 NFVO support for version dependency information --> FEAT Agreed at IFA#273 - NFVIFA(22)000100r1 FEAT21 IFA014ed431 Adding version dependencies --> FEAT agreed at IFA#275 - NFVIFA(22)000101r1 FEAT21-IFA013ed431-Adding version dependencies to NS LCM operations --> FEAT agreed at IFA#275 - NFVIFA(22)000178 FEAT21 IFA013ed431 Exposure of version dependencies --> FEAT Agreed at IFA#276 - NFVIFA(22)000191r1 FEAT21-IFA014ed431-Clause 6.2.2 Add flag for strict NSD onboarding --> Agreed at IFA#276 - NFVIFA(22)000192r1 FEAT21-IFA010ed431-Clause 6.6.1 NFVO allow lenient NSD onboarding --> FEAT Agreed at IFA#276 - NFVIFA(22)000189r1 FEAT21 IFA013ed431 precondition about onboarded constituents --> FEAT Agreed at IFA#276	IFA013, IFA010, IFA011, IFA014	Nov-2021	Completed in IFAed431
008	Add requirements to extend the capability support of NFVO and VNFM to handle the modification of security groups of a particular VNF instance based on LCM actions performed on the corresponding VNF instance (5gnfv.func.005, 5gnfv.if.007) and updates on the relevant descriptors to indicate the mapping of security groups to target CP (5gnfv.desc.008).	IFA010, IFA007, IFA014	Jun-2023	Not started
009	Add enhancements to the VL construct to support additional services such as name resolution, communication security, etc. (5gnfv.desc.002). Contributions: - CR for IFA014 to address 5gnfv.desc.002 NFIFA(23)000406r1 FEAT21 IFA014ed451 Enhancing VL with additional capabilities (action 009): FEAT Agreed at IFA#337	IFA014	Jun-2023	Completed in IFAed451
010	Add enhancements, requirements to address the capability to indicate, reuse and shared virtualised resources among VNF instances, including extensions to the granting LCM interface (5gnfv.desc.004, 5gnfv.desc.005, 5gnfv.if.005) and to the scaling of virtualised storage resources independently (5gnfv.desc.003). Contributions: - NFVIFA(23)000008r1 IFA007ed441 FEAT21 Granting for shared virtual resource --> Almost FEAT Agreed at IFA#316 - NFVIFA(23)000079r2 FEAT21 IFA011ed451 Add scaling model --> Available - NFVIFA(23)000081r1 FEAT21 IFA011ed451 VNFD for storage scaling --> Available	IFA011, IFA014, IFA007	Jun-2023	Ongoing
011	Add requirements and modelling to the NS LCM interface to address various capabilities: - providing information about external L2 networks (5gnfv.if.001), - providing location constraints of constituents of a VNF to be deployed (5gnfv.if.002), - providing naming related information related to SAP or VNF external CP (5gnfv.if.003), and - relevant descriptor enhancements in the VNFD/NSD for additional network properties (5gnfv.desc.006). Contributions: - NFVIFA(23)000440 FEAT21 IFA013ed451 Providing naming related information for SAP or VnfExtCp (action 011): FEAT Agreed at IFA#337 - NFVIFA(23)000441 (mirror of 440) FEAT21 IFA007ed451 Providing naming relating information for VnfExtCp (action 011): FEAT Agreed at IFA#337 - NFVIFA(23)000442 (mirror of 440) FEAT21 IFA008ed451 Providing naming relating information for VnfExtCp (action 011): FEAT Agreed at IFA#337 - NFVIFA(23)000439 FEAT21 IFA013ed451 Providing location constraints of VNF constituents (action 011): FEAT Agreed at IFA#337 - NFVIFA(23)000438 FEAT21 IFA013ed451 Providing information about external L2 networks (action 011): FEAT Agreed at IFA#337 - NFVIFA(23)000437r1 FEAT21 IFA011ed451 Additional network properties for CPs (action 011): FEAT Agreed at IFA#339 - NFVIFA(23)000482 FEAT21 IFA014ed451 Additional network properties for SAPs (action 011): FEAT Agreed at IFA#339	IFA013, IFA011, IFA014, IFA007, IFA008	Jun-2023	Completed in IFAed451
012	Update the definition of VNF to clarify that a VNF can be used to deploy the implementation of a subset of an NF (5gnfv.func.007). Contributions:- NFVIFA(23)000107 FEAT21 NFV003ed191 Update definition of VNF: available Pending CRs: none	NFV003	Jun-2023	Ongoing
013	Enhancements to the VNFD to support describing requirements to use VNF Common/Dedicated Services related to authorization server (5gnfv.desc.009), CA (5gnfv.desc.010) and identify if VNF provides authorization server capabilities (5gnfv.desc.011). See notes 2 and 3.	IFA011	Jun-2023	Not started. Postponed to complete first ENH01.01
014	Add functional requirements, interface requirements, interface modelling to cover the aspects of registering/unregistering client information in respective authorization server: - NFVO requirements (5gnfv.func.006) - VNF LCM interface (5gnfv.if.008) - VNF Configuration interface (5gnfv.if.009 and 5gnfv.if.010) See note 2.	IFA010, IFA007, IFA008	Jun-2023	Not started Postponed to complete first ENH01.01
015	Document about the potential use of non-MANO artefacts describing the relationship of scaling aspects with the purposed services offered by the VNF (5gnfv.other.001). Contributions:- NFVIFA(23)000108 FEAT21 IFA011ed511 Update ScalingAspect to relate to NF services: available Pending CRs: none	IFA011	Jun-2023	Ongoing
016	Modeling of the PaaS Services descriptors for VNF Common/Dedicated services. Contributions: - NFVIFA(23)000280 FEAT21 IFA049 Scope and skeleton extension for future IFA049 version to include PaaS Services management: endorsed/noted - NFVIFA(23)000667r1 FEAT21 IFA049 Scope and skeleton extension for release 5 version to include PaaS Services management: approved at IFA#350 - NFVIFA(24)000092 FEAT21 IFA049ed511 Clause 9.4 PSD general requirements: available - NFVIFA(24)000094 FEAT21 IFA049ed511 Clause 9.5 Adding PSD modelling specification: available -NFVIFA(24)000095 FEAT21 IFA049ed511 Clause 9.1 and 9.2 PaaS generalization of descriptors: available Pending CRs: address open editor's notes	IFA049	Mar-2024	Ongoing
017	Specification of interfaces and information modeling of management of PaaS Services. Contributions: - NFVIFA(23)000280 FEAT21 IFA049 Scope and skeleton extension for future IFA049 version to include PaaS Services management: endorsed/noted - NFVIFA(23)000667r1 FEAT21 IFA049 Scope and skeleton extension for release 5 version to include PaaS Services management: approved at IFA#350 - NFVIFA(23)000751 FEAT21 IFA049ed511 Clause 4 Updates for PaaS: approved at IFA#362 - NFVIFA(23)000756 FEAT21 IFA049ed511 Clause 8.1 Updated service interactions for PaaS: approved at IFA#362 - NFVIFA(23)000759r1 FEAT21 IFA049ed511 Clause 10 PSM and PSR interface requirements: approved at IFA#362 - NFVIFA(24)000042r1 FEAT21 IFA049ed511 Clause 10.3 PaaS Services LCM interface operations: available - NFVIFA(24)000043 FEAT21 IFA049ed511 Clause 10.3 PSD management interface operations: available - NFVIFA(24)000044 FEAT21 IFA049ed511 Clause 10.3 PaaS Services Registration management interface operations: available Pending CRs: address open editor's notes	IFA049	Mar-2024	Ongoing
NOTE 1: In the actions, references to relevant recommendations in ETSI GR NFV-IFA 037 v0.12.0 are provided for more information and details regarding the expected recommendation. NOTE 2: This action might be performed via a specific "security enhancement" feature. If so, proper cross-referencing will be highlighted on the feature plan. NOTE 3: Relationship with other features such as FEAT24 "Generic VNF OAM" and FEAT17 on aspects of "PaaS" will be evaluated to determine what feature work takes final responsibility to perform the specification in order to avoid overlapping specification.

Stage 3 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.

SOL

ID	Action	Impacted WI(s)	Target completion	Status
001	Add version dependancy to VNFD and NSD - NFVSOL(22)000189: Approved - NFVSOL(22)000225: Approved	SOL001	2022-April	Completed in ed431
002	Add version dependancy to VNFD and NSD - NFVSOL(22)000305: Approved	SOL006	2022-April	Completed in ed431
003	Add version dependency to VNF LCM and NS LCM - NFVSOL(22)000173 Approved	SO005	2022-April	Completed in ed431
004	Add modelling for the VNFD and NSD to support describing requirement to use VNF Common/Dedicated Services - NFVSOL(23)000308r3 Approved - NFVSOL(23)000309r5 Approved	SOL001	2024-January	Completed in ed451
005	Add modelling for the runtime information of the VNF and NS instance that can make use of VNF Common/Dedicated Services - NFVSOL(23)000200 Approved - NFVSOL(23)000172 Approved - NFVSOL(23)000189 Approved Enhance granting interface - NFVSOL(23)000173 Approved	SOL002, SOL003, SOL005	2024-January	Completed in ed451

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT22: M-Tenant

Overview

Feature Prime	Ulrich Kleber, Huawei, Ulrich.kleber@huawei.com
Feature description	Start with use cases where multiple users consume services from the same NFV-MANO environment and implement necessary enhancements in the NFV-MANO stack.
Target Release	Stage 1: Release 5 Stage 2: Release 5 (2021-X-X) Stage 3: Release 5 (2021-X-X)
Impacted WIs	Stage 1: EVE018 Stage 2: tbd Stage 3: tbd
MegaCRs	Stage 2: IFAxxx MegaCR NFVIFA(18)000xxx (CR Status) IFAyyy MegaCR NFVIFA(18)000yyy (CR Status)
Related/Dependent Features
New Specifcations	Stage 1: EVE018 Stage 2: none Stage 3: none
Status	Stage 1: Ongoing (60% completed) Stage 2: Not started Stage 3: Not started
Contributions	All feature contributions Agreed content
Feature team	Stage 1: U.Kleber (Huawei) Stage 2: Name (Company) Stage 3: Name (Company)
Last Updated	2023-09-22

Stage 2 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 IFA0xx. CR draft [LINK]	IFA	xx	Open

SOL

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

Stage 3 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.

SOL

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

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT23: M-SBA

Overview

Feature Prime	Janusz Pieczerak, Orange, janusz.pieczerak@orange.com
Feature description	This feature studies the application of a Service-Based Architecture (SBA) design style to the NFV architectural framework and provides recommendations on the evolution of the ISG specifications structure to apply SBA design patterns to the NFV architectural framework.
Target Release||Stage 2: Release 5 (2022-12) Stage 3: Release 5 (2024-X-X)
Impacted WIs	Stage 2: TBD Stage 3: TBD
MegaCRs	Stage 2: IFAxxx Stage 3: SOLzzz MegaCR NFVSOL(19)000zzz (CR Status)
Related/Dependent Features	None
New Specifcations	Informative: DGR/NFV-IFA039 (published) Stage 2: TBD Stage 3: TBD
Status	Informative: Completed (100%) Stage 2: TBD Stage 3: TBD
Contributions	All feature contributions Agreed content
Feature team	Stage 2: Janusz Pieczerak (Orange) Stage 3: Name (Company)
Last Updated	2022-12-06

Stage 2 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	2023	Open

SOL

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

Stage 3 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.

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.

FEAT24: VNF-OAM

Overview

Feature Prime	Kostas Katsalis, DOCOMO, Katsalis@docomolab-euro.com & Yuhan Zhang, China Mobile, zhangyuhan@chinamobile.com
Feature description	This feature will analyse further the types of OAM functions for VNFs defined in Release 4 and Release 5 (stage 0/1) supporting the provisioning, connectivity, configuration and monitoring of VNFs on a virtualized platform. Interactions with other NFV-MANO entities like MDAF will be also delineated. The feature will also formalize the way generic OAM functions can be realized by leveraging PaaS capabilities. The necessary functional requirements, interface requirements, like also the necessary interface and information models will be specified for functions defined in Release 5 stage 0/1, while interfaces and IE defined functions will be extended, if necessary. The result will also report possible NFV-MANO architectural enhancements.
Target Release	Stage 2: Release 5 (2025 March) Stage 3: Release 4 (2020-X-X)
Impacted WIs	Stage 2: IFA047, IFA010 Stage 3: Pending Release 4 further development in stage 3
MegaCRs	Stage 2: IFA0xx Stage 3: SOLzzz MegaCR NFVSOL(19)000zzz (CR Status)
Related/Dependent Features	FEAT17: cloud-native VNF and NFV architecture PaaS FEAT21: 5GNFV
New Specifcations	Stage 2: IFA049 Stage 3: None
Status	Stage 2: Ongoing (10% started) Stage 3: Not started
Contributions	All feature contributions Agreed content
Feature team	Stage 2: Kostas Katsalis (DOCOMO), Yuhan Zhang (China Mobile) Stage 3: Name (Company)
Last Updated	2023-10-31

Stage 2 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	Specify the relationship and interactions between the Notification manager specified in Release 4 and the rest of VNF generic OAM functions. Related recommendations from ETSI GR NFV-EVE 019 v5.1.1: GenericOamType.009	IFA049	March 2024	Open
002	Add functional requirements for the VNF generic OAM functions of policy agent, VNF testing manager, Notifications manager. Related recommendations from ETSI GR NFV-EVE 019 v5.1.1: GenericOamType.011, GenericOamType.012	IFA049	March 2024	Open
003	Update functional requirements of MDAF to consider interactions with VNF generic OAM framework. Related recommendations from ETSI GR NFV-EVE 019 v5.1.1: vnf.generic.func.001	IFA049, IFA010	August 2024	Open
004	Interface requirement and interface operation for the VNF generic OAM functions of Policy agent, VNF testing manager and Notifications manager. Related recommendations from ETSI GR NFV-EVE 019 v5.1.1: GenericOamType.011, GenericOamType.012, GenericOamType.009	IFA049	March 2024	Open
005	Information elements for the VNF generic OAM functions of Policy agent, VNF testing manager and Notifications manager. Related recommendations from ETSI GR NFV-EVE 019 v5.1.1: GenericOamType.011, GenericOamType.012,	IFA049	March 2024	Open
006	Specify mechanisms and possible NFV-MANO extensions on existing FBs/functions to enable management of network connectivity with service mesh and configure service mesh. Specify, where applicable, extensions to VNF generic OAM functions like the Network configuration manager to make it compatible with aspects of service mesh related configuration. Related use cases from ETSI GR NFV-EVE 019 v5.1.1, as described in clause 4.4.1.2 and clause 4.4.1.3.	IFA049	March 2024	Open
007	Specify mechanisms to enable the VNF generic OAM function of Policy agent supporting automation for the actual decision making, to ease administration tasks and offload responsibility from the operator. Policy agent can be used to enable closed-loop control through interaction with NFV-MANO, other VNF generic OAM functions and other functions like MDAF.	IFA049	March 2024	Open
008	Specify the relationship between MDAF and VNF generic OAM functions of VNF Metrics analyser (for metrics) and the Log analyser. Related recommendations from ETSI GR NFV-EVE 019 v5.1.1: vnf.generic.func.001	IFA049, IFA047	August 2024	Open
009	Further detail the scope of configuration of VNF configuration manager function regarding "application related configuration". Related use cases from ETSI GR NFV-EVE 019 v5.1.1, as clause 4.3.10, and recommendation GenericOamType.007.	IFA049	March 2024	Open

SOL

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

Stage 3 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.

SOL

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

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT25: VNF-CI

Overview

Feature Prime	Huzhong Ling, China Mobile, linghuzhong@chinamobile.com
Feature description	This feature will analyse and define how to implement a "Joint Pipeline" to provide DevOps process beween VNF providers and VNF operators. The feature will also determine possible extentions of NFV MANO to realize such DevOps process.
Target Release	Stage 2: Release 4 (2020-H2) Stage 3: Release 3 (2021-H1)
Impacted WIs	Stage 2: IFAxx, IFAyy, SOLzz Stage 3: SOLzz
MegaCRs	Stage 2: IFAxxx MegaCR NFVIFA(18)000xxx (CR Status) IFAyyy MegaCR NFVIFA(18)000yyy (CR Status) Stage 3: SOLzzz MegaCR NFVSOL(19)000zzz (CR Status)
Related/Dependent Features	FEATxx FEATyy
New Specifcations	Stage 2: none Stage 3: SOLaaa
Status	Stage 2: Completed Stage 3: Ongoing (20% completed)
Contributions	All feature contributions Agreed content
Feature team	Stage 2: Name (Company) Stage 3: Name (Company)
Last Updated	20xx-xx-xx

Stage 2 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	Requirements for test information including in VNF Pacakge VNF package should contain references to dependent functions or services, which are machine readable and can be bound automatically to the particular VNF at deployment time into the test, staging, production environment.   VNF package should contain a testing section with various information concerning testing and DevOps   VNF Package should contain acceptance test descriptions.   VNF Package should contain acceptance test code that can be executed automatically after deployment into the various environments. VNF Package should contain information about a test execution framework what is capable to execute the test code included in the VNF Package.   VNF Package should contain a reference to the acceptance test results of the VNF Provider.   VNF Package should contain information about the operator environment, in which it makes sense to test.	IFA011	2nd Half-2020	Open
002	VNF should support to specify the test mode via configuration interface between VNFM and VNF	IFA	2nd Half-2020	Open
003	When a common test framework is used , it's recommended that VNF should support standardized test API	IFA	1st Half-2021	Open

SOL

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

Stage 3 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.

SOL

ID	Action	Impacted WG(s)	Target completion	Status
001	Under the '/tests' directory in VNF package, there should contain information about VNF test mode.	SOL	Need further focus	Open

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT26: Policy Management Models

Overview

Feature Prime	Lingli Deng, China Mobile, denglingli@chinamobile.com
Feature description	This feature will analyse existing policy information and data models and identify solutions that potentially could be applied to NFV-MANO; clarify the main alternatives for policy management (between NFV-MANO and OSS/BSS); determine the objectives and management alternatives for policy management applicable to NFV-MANO; identify policy expression information model applicable to NFV-MANO; identify policy expression data model applicable to NFV-MANO.
Target Release	Study: Release 4 (2021-04-15) Study to be completed Stage 2: Release 4 (2022-12-15) Stage 3: Release 5 (2024-6-30)
Impacted WIs	Stage 2: IFA005/006/007/008/013/030 Stage 3: SOL012
MegaCRs	Stage 2: Stage 3:
Related/Dependent Features	FEAT07
New Specifcations	Study: IFA042 Stage 2: IFA048 Stage 3:
Status	Stage 2: Completed Stage 3: Not started
Contributions	All feature contributions Agreed content
Feature team	Stage 2: Chen Wang (China Mobile) Stage 3: Keguang He (China Mobile)
Last Updated	2023-09-22

Stage 2 Implementation Plan

0Items 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	First GR (IFA042) draft introducing the skeleton and the scope. Accepted contributions: NFVIFA(20)000553r2	IFA042	August-2020	Done
002	Analysis of existing SDOs and Open Source Community policy models Accepted contributions: NFVIFA(20)000615r2 NFVIFA(20)000616r6 NFVIFA(20)000617r1 NFVIFA(20)000618r2 NFVIFA(20)000619r2 NFVIFA(20)000620r1	IFA042	November-2020	Done
003	NFV-MANO policy model potential requirements analysis Analysis of existing SDOs and Open Source Community policy models NFVIFA(21)000304 NFVIFA(21)000305r2 NFVIFA(21)000306r3 NFVIFA(21)000307r2 NFVIFA(21)000308r3 NFVIFA(21)000309r4 NFVIFA(21)000310r3 NFVIFA(21)000313r2_IFA042_5_4_1_Examples__Potential_Attributes_of_the_VNF_Auto- NFVIFA(21)000314r2_IFA042_5_4_2_Examples__Potential_Attributes_of_the_NS_Self-h NFVIFA(21)000315r3_IFA042_5_4_3_Examples__Potential_Attributes_of_the_Virtualiz NFVIFA(21)000316r2_IFA042_6_3_2_3_A_YANG_Data_Model_for_ECA_Policy_Management	IFA042	January-2021	Done
004	Analysis and Recommendations NFVIFA(21)000310r3_IFA042_5_3_1_General_Recommendations NFVIFA(21)000311r2_IFA042_5_3_2_Recommendations_for_Policy_Model_Information_El NFVIFA(21)000312r2_IFA042_5_3_3_Recommendations_for_Policy_Model_Attributes NFVIFA(21)000407r1 NFVIFA(21)000408 NFVIFA(21)000409r1 NFVIFA(21)000410r2 NFVIFA(21)000411r2 NFVIFA(21)000424r2 NFVIFA(21)000439r1 NFVIFA(21)000440r1 NFVIFA(21)000441r1 NFVIFA(21)000443r1 NFVIFA(21)000444r1 NFVIFA(21)000454r1 NFVIFA(21)000442r1 NFVIFA(21)000445r1 NFVIFA(21)000446r1 NFVIFA(21)000487r1 NFVIFA(21)000488r1 NFVIFA(21)000489r1 NFVIFA(21)000503r1 NFVIFA(21)000520r1 NFVIFA(21)000530r1 NFVIFA(21)000558r1 NFVIFA(21)000559r1 NFVIFA(21)000560r1 NFVIFA(21)000561r1 NFVIFA(21)000562 NFVIFA(21)000563r1 NFVIFA(21)000617r2 NFVIFA(21)000618r2	IFA042	Feburary-2021	Done
005	Review NFVIFA(21)000674r1 NFVIFA(21)000675r1 NFVIFA(21)000699 NFVIFA(21)000701r2 NFVIFA(21)000700r1 NFVIFA(21)000727 NFVIFA(21)000728 NFVIFA(21)000729r1 NFVIFA(21)000730r1	IFA042	September-2021	Done
006	Policy information model - NFVIFA(22)000254 - NFVIFA(22)000335r1 - NFVIFA(22)000333r3 - NFVIFA(22)000334r2 - NFVIFA(22)000382r1 - NFVIFA(22)000336r3 - NFVIFA(22)000337r4 - NFVIFA(22)000411 - NFVIFA(22)000410r1 - NFVIFA(22)000409r1 - NFVIFA(22)000408r1	IFA048		Done
007	General - NFVIFA(22)000385r1 - NFVIFA(22)000383r1 - NFVIFA(22)000384r2 - NFVIFA(22)000406r1 - NFVIFA(22)000407r2 Example of policy model - NFVIFA(22)000347r2 Review - NFVIFA(22)000743 - NFVIFA(22)000744 - NFVIFA(22)000745 - NFVIFA(22)000746 - NFVIFA(22)000740r1 - NFVIFA(22)000776	IFA048		Done
008	Policy management alignment with IFA048 - NFVIFA(23)000024r1 - NFVIFA(23)000025r1 - NFVIFA(23)000026r1 - NFVIFA(23)000027r1 - NFVIFA(23)000028r1	IFA005 IFA006 IFA007 IFA008 IFA013		Done

Stage 3 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.

SOL

ID	Action	Impacted WG(s)	Target completion	Status
001	Study of solution - NFVSOL(23)000084r1	NWI
002	Policy management alignment with IFA048 - NFVSOL(23)000014	SOL012		Done
003	Policy information model			Not started
004	Policy data model			Not started

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT27: NFV for vRAN

Overview

Feature Prime	Kostas Katsalis (DOCOMO EUL)
Feature description	The scope of this feature covers the following areas: a) study the advances concerning the virtualization of the RAN and profile the NFV framework to determine how it can support virtualized RAN (vRAN) use cases, b) identify key technical challenges relevant to architectural, operational and management aspects, in case the NFV architectural framework is leveraged to support virtualization of the RAN,  c) provide recommendations for enhancements to the NFV architectural framework and its functionality, aiming to provide further support for vRAN use cases, d) based on the recommendations, enhance when needed the overall NFV-MANO framework, existing NFV-MANO interfaces and descriptors.
Target Release	Stage 2: Release 5 (2025 March) Stage 3: TBD
Impacted WIs	Stage 2: IFA002, IFA005, IFA006 IFA010, IFA011, IFA014, IFA036, IFA040, IFA046, IFA049, IFA053 Stage 3: TBD
MegaCRs	Stage 2: TBD Stage 3: TBD
Related/Dependent Features	FEAT17 on "Cloud-native VNF and container infrastructure management" FEAT19 on "NFV connectivity" FEAT21 on "5GNFV" FEAT33 on "Physical Infrastructure Management"
New Specifcations	Stage 2: TBD Stage 3: TBD
Status	Stage 2: Informative work completed (GR NFV-IFA 046 Ver. 5.1.1) Stage 3: TBD
Contributions||All feature contributions Agreed content
Feature team	Informative: Kostas Katsalis (DOCOMO EUL) Stage 2: Kostas Katsalis (DOCOMO EUL) Stage 3: Name (Company)
Last Updated	2023-10-31

Informative work

IFA

ID	Action	Impacted WG(s)	Target completion	Status
001	Informative profiling of the VNF generic OAM functions framework including the PaaS management aspects to O-RAN. See note.	IFA046	Mar-2025	Open
002	Informative profiling of the energy efficiency aspects developed in NFV to O-RAN. See note.	IFA046	Mar-2025	Open
003	Informative profiling of the NFV testing framework to O-RAN. See note.	IFA046	Mar-2025	Open
004	Informative profiling of the NFV automation framework (Policy management, Intent management and MDAF) to O-RAN. See note.	IFA046	Mar-2025	Open
005	Informative profiling of the NFV certificate management framework to O-RAN WG6 and WG11 activities. See note.	IFA046	Mar-2025	Open
006	Informative profiling of physical resource management aspects developed in IFA053 to O-RAN WG6 activities in IMS. See note.	IFA046	Mar-2025	Open
NOTE : This task is considered to continuously profile the NFV framework for vRAN with the advancements that other features work performs. It is not a mandatory task to be performed, but it can be considered in the work plan if resources permit it.

Stage 2 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	Specify interactions between NFV-MANO entities with the Physical Infrastructure Management (PIM) function. See note 1. Relevant to recommendation vran.arch.001 in ETSI GR NFV-IFA 046.	IFA053	Mar-2025	Open
002	Specify functional requirements for VIM, CCM and NFVO to be able to support physical resources management and physical infrastructure inventory information from PIM. See notes 1 and 2. Relevant to recommendation vran.func.001, vran.func.002 and vran.func.003 in ETSI GR NFV-IFA 046.	IFA010, IFA053	Mar-2025	Open
003	Specify and/or profile acceleration resources abstraction which can be used for both VM-based and container-based deployments. Relevant to endorsed solution SOL-B1-1 in ETSI GR NFV-IFA 046.	IFA002	Aug-2025	Open
004	Support VIM to be able to manage and configure virtualised resources for VM-based deployments considering requirements related to acceleration resources and virtual accelerator abstraction. Relevant to recommendation vran.func.004 and vran.func.007 in ETSI GR NFV-IFA 046.	IFA010	Mar-2025	Open
005	Support CISM to be able to manage containerized workloads for OS container-based deployments considering requirements related to acceleration resources and virtual accelerator abstraction. Relevant to recommendation vran.func.005 in ETSI GR NFV-IFA 046.	IFA010, IFA040	Mar-2025	Open
006	Support CCM to be able to manage CIS clusters considering requirements related to acceleration resource and virtual acceleration abstraction. Relevant to recommendation vran.func.006 in ETSI GR NFV-IFA 046.	IFA010, IFA036	Mar-2025	Open
007	Support CCM to be able to configure accelerator resources and virtual accelerator abstraction on CIS clusters. Relevant to recommendation vran.func.008 in ETSI GR NFV-IFA 046.	IFA036	Mar-2025	Open
008	Specify functional requirements for the NFVO and VNFM to be able to manage partial VNF packaging. Relevant to recommendation vran.func.009 in ETSI GR NFV-IFA 046.	IFA010	Aug-2025	Open
009	The description of virtual accelerator abstraction for both VM-based and containerized deployments needs to be supported. Relevant to recommendation vran.descr.001 in ETSI GR NFV-IFA 046	IFA011	Mar-2025	Open
010	Support VNF Package containing only parts (VNFC) of the software of a VNF or artifacts necessary for the management of the VNF (partial packaging). Relevant to recommendation vran.descr.002 in ETSI GR NFV-IFA 046	IFA011	Aug-2025	Open
011	Specify interactions between VIM/CCM/NFVO and PIM. See notes 1 and 2. Relevant to recommendations vran.inter.001, vran.inter.002, vran.inter.003 in ETSI GR NFV-IFA 046.	IFA053	Mar-2025	Open
012	Specify interactions to be able to support and manage virtualised resources for VM-based deployments considering requirements related to acceleration resources and virtual accelerator abstraction. Relevant to recommendations vran.inter.004 in ETSI GR NFV-IFA 046.	IFA005, IFA006	Mar-2025	Open
013	Specify interface exposed by CISM to consider requirements related to acceleration resources and virtual accelerator abstraction when managing containerized workloads for OS container-based deployments. Relevant to recommendations vran.inter.005 in ETSI GR NFV-IFA 046.	IFA040	Mar-2025	Open
014	Extend the endpoint (virtual ports, connection points) information models to support time synchronization. Relevant to recommendations vran.inter.006 in ETSI GR NFV-IFA 046.	IFA005, IFA006	Mar-2025	Open
015	Clarify in the specifications the use of "PaaS Services" feature as equivalent support for custom resources based on the CRDs. Relevant to SOL-C2-1 in ETSI GR NFV-IFA 046.	IFA010, IFA049, IFA011, IFA014	Mar-2025	Open
016	Support interactions between VNF generic OAM functions and NFV-MANO entities for the configuration of VNFs. See note 3. Relevant to SOL-D5-3 in ETSI GR NFV-IFA046.	IFA049, IFA010	Mar-2025	Open
NOTE 1:   A dedicated on PIM has been proposed, and the task might be developed as part of such a feature. The task will then focus on checking that the specific vRAN related requirements are considered. NOTE 2:   Whether CISM also consumes PIM functionality needs to be investigated further. NOTE 3:   A dedicated feature on "VNF configuration" (see FEAT30) is related to this task. The work might be developed by that feature instead.

Stage 3 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.

SOL

ID	Action	Impacted WG(s)	Target completion	Status
001	TBD	TBD	TBD	TBD

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT28: Fault management models

Overview

Feature Prime	WANG Chen (China Mobile) & TRIAY Joan (DOCOMO)
Feature description	The proposed feature aims to extend the defined data model of alarms and values of attributes (e.g., fault type) to enhance the processing of failure information. In addition, the proposal will analyse, determine and enrich the fault management interfaces to provide and acquire information to/from fault management closed loops in between different NFV-MANO, platform and OSS layers. Thus, the objectives of the feature comprise: -Define the necessary vendor agnostic information and data models for alarms and event notifications. - Expose and relate the type, cause, and additional information of the faults with appropriate levels of severity of the violation, like critical, major, minor, warning as defined in the current Alarm information elements. - Enable automated fault detection and performance degradation analysis over complex and correlated metrics. NOTE: Alarms related to security violations are out of scope of this activity.
Target Release	Stage 2: Release 4 drop ed451 (Aug 2023) Stage 3: TBD (Release 5 (2023-X-X))
Impacted WIs	Stage 2: IFA005, IFA006, IFA007, IFA008, IFA013 Stage 3: SOL002, SOL003, SOL005, SOL018, SOL014
MegaCRs	Stage 2: None at this moment. Stage 3: TBD
Related/Dependent Features	FEAT24 on "Generic VNF OAM"
New Specifcations	Stage 2: ETSI GS NFV-IFA 045 Stage 3: TBD
Status	Stage 2: IFA045 completed, IFA CRs ongoing (total 90%) Stage 3: TBD
Contributions	All feature contributions Agreed content
Feature team	Normative: WANG Chen, Lingli Deng (China Mobile) & Joan TRIAY (DOCOMO) Stage 2: WANG Chen, Lingli Deng (China Mobile) & Joan TRIAY (DOCOMO) Stage 3: Name (Company)
Last Updated	2023-08-31

Stage 2 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	Skeleton and scope for the IFA045. Contributions: - NFVIFA(21)000810 Proposed ETSI GS skeleton IFA045 FM Models: approved - NFVIFA(23)000463 FEAT28 IFA045 Adding scope: approved	IFA045	Sept-2021	Completed
002	Overview and introduction of IFA045 content (clause 4). Contributions: - NFVIFA(21)000914 FEAT28 IFA045 Clause 4 Adding introduction: approved	IFA045	Oct-2021	Completed
003	Define the “alarm definition template” (clause 6). See note 1. Contributions: - NFVIFA(21)0001067r2 FEAT28 IFA045 clause 6 Alarm definition template: approved - NFVIFA(22)000506 FEAT28 IFA045 Add Alarm Definition Template: available	IFA045	Nov-2021	Completed
004	Development of use cases related to FM alarms (annex A.1). Contributions: - NFVIFA(21)000915 FEAT28 IFA045 Annex A.1.2 Use cases VR and NFVI alarms: approved - NFVIFA(21)0001068r2 FEAT28 IFA045 A1.2.m Use case about packet loss alarm: approved - NFVIFA(22)000045r1 FEAT28 IFA045 A1.2.m Use case about unavailable storage service alarm: approved - NFVIFA(22)000151 IFA045 A1.2.m Use case about network link anomaly alarm: approved - NFVIFA(23)000152 FEAT28 IFA045 Annex A.1 Use cases about VNF and NS alarms: approved - NFVIFA(23)000443r1 FEAT28 IFA045 Clause A.1.2.3 adding annex about container and cluster alarms: approved	IFA045	May-2023	Completed
005	Development of use cases related to use of Alarms information (annex A.2). Contributions: - NFVIFA(21)0001043r1 IFA045 A.2.1.1 Use case about generic procedure of using alarm information produced by the VIM: approved - NFVIFA(21)0001044r1 IFA045 A.2.1.2 Use case about generic procedure of using alarm information produced by the VNFM: approved - NFVIFA(21)0001045r1 IFA045 A.2.1.3 Use case about generic procedure of using alarm information produced by the NFVO: approved	IFA045	Mar-2021	Completed
006	Definition of object types that can be fault monitored (clause 5). See note 1 and note 2. Contributions: - NFVIFA(22)000911 FEAT28 IFA045 virtualised resource object types: approved - NFVIFA(23)000140r1 FEAT28 IFA045 VNF/NS object types: approved - NFVIFA(23)000153 FEAT28 FM and alarms for containerized workloads: noted - NFVIFA(23)000271 FEAT28 IFA045 MSCS object types: approved - NFVIFA(23)000275 FEAT28 IFA045 Discussion about CIS cluster management object types: noted - NFVIFA(23)000391 FEAT28 IFA045 CIS cluster object types: approved - NFVIFA(23)000444 FEAT28 IFA045 additional CIS cluster object types: approved - NFVIFA(23)000445 FEAT28 IFA045 containerized workload object types: approved - NFVIFA(23)000398r1 FEAT28 IFA045 Clause 5.1 Introduction: approved	IFA045	Jun-2023	Completed
007	Alarm definitions (clause 7). See note 1 and note 2. Contributions: - NFVIFA(22)000912r2 FEAT28 IFA045 VIM alarms baseline: common definitions: approved - NFVIFA(22)000913r1 FEAT28 IFA045 VIM alarms baseline: compute and CPU: approved - NFVIFA(22)000914 FEAT28 IFA045 VIM alarms baseline: memory: approved - NFVIFA(22)000915 FEAT28 IFA045 VIM alarms baseline: storage: approved - NFVIFA(22)000916r1 FEAT28 IFA045 VIM alarms baseline: network interface: approved - NFVIFA(23)000917 FEAT28 IFA045 VIM alarms baseline: network: approved - NFVIFA(23)000141r1 FEAT28 IFA045 VNFM alarms baseline: common definitions: approved - NFVIFA(23)000143 FEAT28 IFA045 NFVO alarms baseline: common definitions: approved - NFVIFA(23)000144 FEAT28 IFA045 VNFM alarms baseline: VNF: approved - NFVIFA(23)000145 FEAT28 IFA045 VNFM alarms baseline: VNFC: approved - NFVIFA(23)000146 FEAT28 IFA045 VNFM alarms baseline: VNF virtual link: approved - NFVIFA(23)000147r1 FEAT28 IFA045 VNFM alarms baseline: VNF internal CP: approved - NFVIFA(23)000148r1 FEAT28 IFA045 VNFM alarms baseline: VNF external CP: approved - NFVIFA(23)000149 FEAT28 IFA045 NFVO alarms baseline: NS: approved - NFVIFA(23)000150r1 FEAT28 IFA045 NFVO alarms baseline: NS virtual link: approved - NFVIFA(23)000151 FEAT28 IFA045 NFVO alarms baseline: NS service access point: approved - NFVIFA(23)000272 FEAT28 IFA045 WIM alarms baseline: common definitions: approved - NFVIFA(23)000273 FEAT28 IFA045 WIM alarms baseline: MSCS: approved - NFVIFA(23)000274 FEAT28 IFA045 WIM alarms baseline: MSNC: approved - NFVIFA(23)000318r2 FEAT28 IFA045 VNFM alarms: clarification of virtual compute and MCIO based VNFC caused alarms: approved - NFVIFA(23)000413r1 FEAT28 IFA045 Clause 7.1 Introduction: approved - NFVIFA(23)000392r2 FEAT28 IFA045 CIS cluster alarms baseline: common definitions: approved - NFVIFA(23)000393r1 FEAT28 IFA045 CCM alarms baseline: CIS cluster: approved - NFVIFA(23)000394r2 FEAT28 IFA045 CCM alarms baseline: CIS cluster node: approved - NFVIFA(23)000395r1 FEAT28 IFA045 CCM alarms baseline: CIS cluster storage: approved - NFVIFA(23)000396r1 FEAT28 IFA045 CCM alarms baseline: CIS cluster network: approved - NFVIFA(23)000397r1 FEAT28 IFA045 CCM alarms baseline: MCCO: approved - NFVIFA(23)000446 FEAT28 IFA045 CISM alarms baseline: common definitions: approved - NFVIFA(23)000447 FEAT28 IFA045 CISM alarms baseline: CISI: approved - NFVIFA(23)000448 FEAT28 IFA045 CISM alarms baseline: MCIO: approved - NFVIFA(23)000400r1 FEAT28 IFA045 Updating event types of alarms produced by VIM: approved - NFVIFA(23)000415 FEAT28 IFA045 Updating event types of alarms produced by VNFM: approved - NFVIFA(23)000416 FEAT28 IFA045 Updating event types of alarms produced by NFVO: approved - NFVIFA(23)000417 FEAT28 IFA045 Updating event types of alarms produced by WIM: approved	IFA045	Jun-2023	Completed
008	Final review of IFA045 and addressing open editor's notes. Contributions: - NFVIFA(23)000401 FEAT28 IFA045 addressing editorial and guideline editor's note: approved - NFVIFA(23)000399r2 FEAT28 IFA045 Clause A.1.1 and A.2.1 overview: approved - NFVIFA(23)000581r1 FEAT28 IFA045 Multiple clauses Addressing EN: approved - NFVIFA(23)000572r1 FEAT28 IFA045 Additional problem causes: approved - NFVIFA(23)000598 FEAT28 IFA045 Clause 7.3 Clarification containerized VNFC: approved - NFVIFA(23)000584 FEAT28 IFA045 Review delete empty clauses: approved - NFVIFA(23)000583 FEAT28 IFA045 Multiple clauses Adding and providing consistency of probable causes: approved - NFVIFA(23)000582 FEAT28 IFA045 Clause 7.2 Adding new alarms: approved - NFVIFA(23)000580 FEAT28 IFA045 Clause 4.2 adding missing spec references: approved - NFVIFA(23)000579 FEAT28 IFA045 Multiple clauses small technical clarifications: approved - NFVIFA(23)000578 FEAT28 IFA045 Editorial review: approved	IFA045	Jun-Jul 2023	Completed
009	Alignment CRs to other NFV-IFA specifications. Contributions:	IFA	Dec-2023	Not started
NOTE 1:  It can run in parallel with the development of use cases, in particular if there are diverse object types and some of them are clarified with use cases at early stages. NOTE 2:  Additional sub-task details could be defined to sequence or parallelize the work on different object types and associated alarm definitions, e.g., split by “NFV managed objects such as VR, MSCS, VNF, NS” or by “resource related domain, such as compute, storage, network”.

Stage 3 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.

SOL

ID	Action	Impacted WG(s)	Target completion	Status
001	TBD	TBD	TBD	TBD

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT29: Green NFV

Overview

Feature Prime	Joan Triay (DOCOMO)
Feature description	The scope of the feature covers the following areas: - Analyse aspects of NFV (VNF design, NFV-MANO and VNF operation, deployment configuration of NFV-MANO, NFVI, etc.) that have impact on energy consumption and those that can enable smart energy NFV and power saving features. - Identify design guidelines needed for optimizing energy consumption. - Specify enhancements to specifications on interfaces and information model, augment exposed KPIs and metrics to enable resources orchestration and VNF/NS LCM to operate following power saving policies.
Target Release	Informative: Summer 2023 Stage 1/2: Release 5 drop 1 (ed511) and drop 2 (ed521) Stage 3: TBD (Release 5 (2021-X-X))
Impacted WIs	Stage 1/2: IFA005, IFA006, IFA007, IFA008, IFA010, IFA011, IFA013, IFA027, IFA031, IFA036, IFA040, IFA049, IFA053 Stage 3: TBD (SOLzz)
MegaCRs	Stage 2: TBD: IFAxxx MegaCR NFVIFA(18)000xxx (CR Status) IFAyyy MegaCR NFVIFA(18)000yyy (CR Status) Stage 3: TBD: SOLzzz MegaCR NFVSOL(19)000zzz (CR Status)
Related/Dependent Features	FEAT20 on "Autonomous management" (Release 4) FEAT07 on "Policy management framework" (Release 4) FEAT26 on "Policy models" (Release 4)
New Specifications	Informative: ETSI GR NFV-EVE 021 Stage 2: No new spec required Stage 3: TBD
Status	Informative: completed (100%) Stage 2: ongoing (40%) Stage 3: TBD
Contributions	All feature contributions Agreed content
Feature team	Informative: Joan Triay (DOCOMO) Stage 2: Joan Triay (DOCOMO) Stage 3: Name (Company)
Last Updated	2024-02-06

Informative work

EVE

ID	Action	Impacted WG(s)	Target completion	Status
001	Skeleton and scope. Contributions: - NFVEVE(21)000080 FEAT29 EVE021 Skeleton: Approved - NFVEVE(21)000081 FEAT29 EVE021 Scope: Approved	EVE (EVE021)	Oct-2021	Completed
002	Introduction and overview - Introduction to energy efficiency and global initiatives - NFV and energy efficiency - Other organizations work Contributions: - NFVEVE(21)000107r1 FEAT29 EVE021 Clause 4.1 Introduction to energy efficiency: Approved - NFVEVE(21)000133r1 FEAT29 EVE021 Clause 4.2 NFV and energy efficiency: Approved - NFVEVE(21)000134r1 FEAT29 EVE021 Clause 4.3.1 Energy efficiency in 3GPP: Approved - NFVEVE(22)000017r1 EVE021 Energy Efficiency - clause 4.3: Approved - NFVEVE(22)000027r1 FEAT29 - EVE021 - Proposed update to clause 4.3: Approved - NFVEVE(22)000043 FEAT29 EVE021 Clause 2.2 correct reference of DMTF Redfish: Approved - NFVEVE(22)000051 FEAT29 EVE021 Clause 2.2 additional references for DMTF Redfish: Approved	EVE (EVE021)	Mar-2022	Completed
003	Development of use cases. See note 1 and note 2. - Network-wide and NFV-MANO aspects. - Energy related measurements and runtime aspects. - Energy-driven design - Enabling smart energy usage and decision making. Contributions: - NFVEVE(22)000037r1 FEAT29 EVE021 Clause 5 UC resources sleep resume: Approved - NFVEVE(22)000052r2 FEAT29 EVE021 Clause 5 UC Power saving management function under limited power supply: Approved - NFVEVE(22)000075r2 FEAT29 EVE021 Clause 5 UC acquiring infrastructure power consumption data: Approved - NFVEVE(22)000076r2 FEAT29 EVE021 Clause 5 UC acquiring NFV power consumption data: Approved - NFVEVE(22)000077r1 FEAT29 EVE021 Clause 5 UC processing power state driven deployment: Approved - NFVEVE(22)000116r1 FEAT29 EVE021 Clause 5 UC power consumption and resources placement optimization: Approved - NFVEVE(22)000115r2 FEAT29 EVE021 Clause 5 UC Restoration management from resource reservation in power saving situations: Approved - NFVEVE(22)000162 FEAT29 EVE021 Clause 5 UC on dynamic power state management: Approved - NFVEVE(22)000175 FEAT29 EVE021 Clause 5 UC on dynamic power state management - actors, conditions and flow description: Approved - NFVEVE(23)000101 FEAT29 EVE021 Clause 5.1 Overview of use cases: Agreed	EVE (EVE021)	Oct-2022	Completed
004	Documentation of key issues. See note 1 and note 2. - Energy consumption - Energy efficiency management - Energy efficient design - Energy related metrics and KPI Contributions: - NFVEVE(22)000096r1 FEAT29 EVE021 Clause 6 Key issues: Approved - NFVEVE(22)000161r1 FEAT29 EVE021 Clause 6 Update key issues: Approved - NFVEVE(22)000204 FEAT29 EVE021 Clause 6 Re-organize questions between key issues: Approved - NFVEVE(22)000209 FEAT29 EVE021 Clause 6 Key issues related to CPU power state management: Approved	EVE (EVE021)	Sep-2022	Completed
005	Framework and potential solutions. Contributions: - NFVEVE(22)000205 FEAT29 EVE021 Clause 7.1 Solutions introduction: Approved - NFVEVE(22)000199r2 FEAT29 EVE021 Clause 7 Solutions key issues #1.1 and #1.2: Approved - NFVEVE(22)000206 FEAT29 EVE021 Clause 7 Solutions key issues #1.2: Approved - NFVEVE(22)000219 FEAT29 EVE021 Clause 7 Solutions key issues #2.2 resources: Approved - NFVEVE(22)000220r1 FEAT29 EVE021 Clause 7 Solutions key issues #2.2 state and config: Approved - NFVEVE(22)000221r1 FEAT29 EVE021 Clause 7 Solutions key issues #3.1 VNF power profiles: Approved - NFVEVE(22)000222 FEAT29 EVE021 Clause 7 Solutions key issues #3.1 VNF power management: Approved - NFVEVE(23)000041 FEAT29 EVE021 Clause 7 Solutions key issues #3.3 Power state based zones in NFVI: Approved - NFVEVE(23)000042 FEAT29 EVE021 Clause 7 Solutions key issue #2.1 Power state aware allocation of compute resources: Approved - NFVEVE(23)000043r1 FEAT29 EVE021 Clause 7 Solutions key issues #2.1 energy policies: Approved - NFVEVE(23)000044r1 FEAT29 EVE021 Clause 7 Solutions key issue #3.2 NFV-MANO power consumption: Approved - NFVEVE(23)000045 FEAT29 EVE021 Clause 7 Updating key issues by existing solutions: Approved - NFVEVE(23)000046r1 FEAT29 EVE021 Clause 7 Solutions key issue #2.1 NFV-MANO capabilities: Approved - NFVEVE(23)000047 FEAT29 EVE021 Clause 7.1 Update summary of solutions and related key issues: Approved - NFVEVE(23)000051 FEAT29 EVE021 Clause 7.1 Update summary of solutions and related key issues (2nd round): Approved - NFVEVE(23)000065 FEAT29 EVE021 Clause 7.1 Further update summary of solutions and related key issues (3nd round): Approved - NFVEVE(23)000066 FEAT29 EVE021 Clause 7 Solutions key issue #4.2 VIM for acquiring VR power consumption: Approved - NFVEVE(23)000067 FEAT29 EVE021 Clause 7 Solutions key issue #4.2 CISM for acquiring containerized power consumption: Approved - NFVEVE(23)000068 FEAT29 EVE021 Clause 7.2.6 Update solution to address key issue #4.3 of acquiring VNF power consumption: Approved - NFVEVE(23)000069 FEAT29 EVE021 Clause 7 Solutions key issue #4.4 NFVO for acquiring NS power consumption: Approved - NFVEVE(23)000070 FEAT29 EVE021 Clause 7 Solutions key issue #4.2, #4.3 and #4.4 NFV power manager for acquiring power consumption: Approved - NFVEVE(23)000074 FEAT29 EVE021 Clause 7.1 Further update summary of solutions (4th round): Approved - NFVEVE(23)000078 FEAT29 EVE021 Clause 7 Solutions key issue #4.1 energy efficiency of NFVI physical resources: Approved - NFVEVE(21)000081 FEAT29 EVE021 Clause 7 Solutions key issue #4.2 energy efficiency and metrics of virtualised resources and containerized workloads: Approved - NFVEVE(23)000082 FEAT29 EVE021 Clause 7 Solutions key issue #4.3 energy efficiency and metrics of VNF: Approved - NFVEVE(23)000083 FEAT29 EVE021 Clause 7 Solutions key issue #4.4 energy efficiency and metrics of NS: Approved - NFVEVE(23)000090 FEAT29 EVE021 Clause 7.1 Further update summary of solutions (5th round): Approved - NFVEVE(23)000098r1 FEAT29 EVE021 Clause 7 Solutions key issue #4.1 PIM for acquiring PR power consumption: Approved - NFVEVE(23)000103r2 FEAT29 EVE021 Clause 7.3 Evaluation of solutions: Approved	EVE (EVE021)	May-2023	Completed
006	Documentation of recommendations. Contributions: - NFVEVE(23)000104r1 FEAT29 EVE021 Clause 8 Recommendations: Approved	EVE (EVE021)	Jun-2023	Completed
007	Documentation of the conclusion. Contributions: - NFVEVE(23)000105 FEAT29 EVE021 Clause 9 Conclusions: Approved	EVE (EVE021)	Jun-2023	Completed
008	Final review of EVE021. See note 3. Contributions: - NFVEVE(23)000052 FEAT29 EVE021 Clause 2.2 and 7.2.9.2 Fix missing reference: Approved - NFVEVE(23)000102r1 FEAT29 EVE021 Clean-up of various editor's notes and empty template clauses: Approved - NFVEVE(23)000116 FEAT29 EVE021 EN resolution vCPU power characteristics and VNF power profiles mapping: Approved - NFVEVE(23)000122 FEAT29 EVE021 Clause 7.1 Final update summary of solutions (6th round): Approved - NFVEVE(23)000127 FEAT29 EVE021 Review removing empty clauses: Approved - NFVEVE(23)000128 FEAT29 EVE021 Review addressing editorial editor's notes: Approved - NFVEVE(23)000135r1 EVE021 Review comments: Approved - NFVEVE(23)000134 FEAT29 EVE021 Editorial revision based on NFVEVE(23)000115_Draft_contribution_GR_NFV-EVE021v001400: Noted - NFVEVE(23)000133r1 FEAT29 EVE021 EN resolution of power consumption correlation with Sol#23: Approved - NFVEVE(23)000147 FEAT29 EVE021 Clause 8.3 Addressing EN recommendation of VNF power management: Approved - NFVEVE(23)000148 FEAT29 EVE021 Clause 8.7 Final clean-up of EN on recommendations: Approved - NFVEVE(23)000126r1 FEAT29 EVE021 Clause 8 Recommendations regarding solution #23: Approved - NFVEVE(23)000146r2 FEAT29 EVE021 Editorial review: Approved - NFVEVE(23)000143r1 FEAT29 EVE021 Multiple clauses Addressing remaining EN: Approved - NFVEVE(23)000149r4 FEAT29 EVE021 Multiple clauses Small technical fixes: Approved - NFVEVE(23)000125r3 FEAT29 EVE021 Review status of EN in v0.14.0: Noted	EVE (EVE021)	Jul-2023	Completed
NOTE 1:  Minimum set of items to consider are listed. NOTE 2:  These tasks can run in parallel, since as we develop use cases, we can start documenting findings about related key issues. NOTE 3:  It may include addressing “minor” editor’s notes that do not require substantial new content.

Stage 2 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) and WI(s)	Target completion	Status
001	Add inventory of physical resources in the NFVI to the NFV architectural framework. Related recommendations from EVE021: greennfv.arch.001 Contributions: - NFVIFA(23)000745r1 FEAT33 FEAT29 IFA053 Clause 6 Inventory: approved at IFA#362 Missing contributions: - IFA010: functional requirements for PIM (pending on conclusion of IFA053)	IFA010 and IFA053	Mar-2024	Ongoing
002	Add support for discovery, collection and use of information about power consumption characteristics, information about power state aware zoning and pooling of physical resource in the NFVI. Related recommendations from EVE021: greennfv.arch.002, greennfv.arch.003. Contributions: - NFVIFA(23)000746r1 FEAT33 FEAT29 IFA053 Clause 6 Topology: approved at IFA#362 - NFVIFA(23)000747 FEAT33 FEAT29 IFA053 Clause 6 Monitoring: approved at IFA#362 Missing contributions: - IFA010: functional requirements for PIM (pending on conclusion of IFA053)	IFA010, IFA053, and potentially IFA005/006	Mar-2024	Ongoing
003	Add support to collect measurements related to energy metrics associated to all NFV-MANO managed objects. Related recommendations from EVE021: greennfv.arch.002, greennfv.arch.004. Contributions: - NFVIFA(23)000747 FEAT33 FEAT29 IFA053 Clause 6 Monitoring: approved at IFA#362 - NFVIFA(24)000102 FEAT29 IFA010ed511 Additional functional reqs Green NFV for CCM: available Missing contributions: - IFA010: functional requirements for VNFM, NFVO	IFA010	Aug-2024 (see note 2)	Ongoing
004	Add support for power management of VNF instances. See note 1. Related recommendations from EVE021: greennfv.arch.002, greennfv.arch.005.	IFA010, potentially IFA049 and/or IFA007/008	Aug-2024	Not started
005	Add functional requirements to VIM to support managing the power states of managed virtualised compute resources and enhance relevant virtualised resource management interfaces produced by the VIM. Determine if also possible for other kinds of resources, and specify accordingly. Related recommendations from EVE021: greennfv.func.001 Contributions: - NFVIFA(23)000790 FEAT29 IFA010ed511 Functional reqs Green NFV for VIM, CCM, CISM: FEAT agreed at IFA#362 - NFVIFA(23)000793 FEAT29 IFA005ed511 Green NFV interface enhancements: FEAT agreed at IFA#362 - NFVIFA(24)000039 FEAT29 IFA005ed511 Clarify power management of virtualised resources: available Missing contributions: - IFA006: mirror of 793 and 039 Postponed items: - Management of power states for virtuliased resources other than compute	IFA010, IFA005/006	Mar-2024	Ongoing
006	Add functional requirements to CCM to support managing the power states of CIS cluster nodes and enhance relevant CIS cluster management interfaces produced by the CCM. Determine if also possible for other kinds of cluster resources, and specify accordingly. Related recommendations from EVE021: greennfv.func.002 Contributions: - NFVIFA(23)000790 FEAT29 IFA010ed511 Functional reqs Green NFV for VIM, CCM, CISM: FEAT agreed at IFA#362 - NFVIFA(23)000794r1 FEAT29 IFA036ed511 Green NFV interface enhancements: FEAT agreed at IFA#362 Postponed items: - Management of power states for objects other than CIS cluster nodes	IFA010 and IFA036	Mar-2024	Ongoing
007	Add functional requirements to PIM to support managing the power states of physical resources in the NFVI, and enhance relevant management interfaces produced by the PIM. Related recommendations from EVE021: greennfv.func.003 Contributions: - NFVIFA(23)000770r3 FEAT33 FEAT29 IFA053 Resource Provisioning and LCM: approved at IFA#362 Missing contributions: - IFA010: functional requirements for PIM - IFA053: interface specification aspects	IFA010 and IFA053	Mar-2024	Ongoing
008	Add functional requirements for VNF power management function to support managing the power states of a VNF and enhance associated management interfaces. See note 1. Related recommendations from EVE021: greennfv.func.004	IFA010 or IFA049, and IFA007/008 or IFA049	Aug-2024	Not started
009	Add functional requirements to the VIM to support scheduling and instantiation of virtualised resources considering power state requirements, and enhance relevant virtualised resource management interfaces produced by the VIM to support providing power state requirements for the virtualised resources to be allocated. Related recommendations from EVE021: greennfv.func.005, greennfv.if.003 Contributions: - NFVIFA(23)000790 FEAT29 IFA010ed511 Functional reqs Green NFV for VIM, CCM, CISM: FEAT agreed at IFA#362 - NFVIFA(23)000793 FEAT29 IFA005ed511 Green NFV interface enhancements: FEAT agreed at IFA#362 Missing contributions: none	IFA010, IFA005/006	Mar-2024	Ongoing
010	Add functional requirements to the CISM to support scheduling and instantiation of containerized workloads considering power state requirements, and enhance relevant interfaces produced by the CISM. Related recommendations from EVE021: greennfv.func.006 Contributions: - NFVIFA(23)000790 FEAT29 IFA010ed511 Functional reqs Green NFV for VIM, CCM, CISM: FEAT agreed at IFA#362 - NFVIFA(23)000795 FEAT29 IFA040ed511 Green NFV interface enhancements: FEAT agreed at IFA#362 Missing contributions: none	IFA010, IFA040	Mar-2024	Ongoing
011	Add requirements to the CCM to support additional tagging scopes for CIS cluster nodes related to CPU power profiles, and enhance relevant models and interfaces produced by the CCM and CISM. Related recommendations from EVE021: greennfv.func.007 Contributions: - NFVIFA(23)000794r1 FEAT29 IFA036ed511 Green NFV interface enhancements: FEAT agreed at IFA#362 Missing contributions: none	IFA036	Mar-2024	Ongoing
012	Add requirements for the PIM to support providing power consumption and energy metrics associated to its managed objects. Related recommendations from EVE021: greennfv.func.008 Contributions: - NFVIFA(23)000747 FEAT33 FEAT29 IFA053 Clause 6 Monitoring: approved at IFA#362 Missing contributions: - IFA010: functional requirements - IFA053: interface enhancements	IFA010 and/or IFA053	Mar-2024	Ongoing
013	Add requirements for the VIM to support providing power consumption and energy metrics associated to its managed objects. Related recommendations from EVE021: greennfv.func.009 Contributions: - NFVIFA(23)000790 FEAT29 IFA010ed511 Functional reqs Green NFV for VIM, CCM, CISM: FEAT agreed at IFA#362 Missing contributions: none	IFA010 and/or IFA005/006	Mar-2024	Ongoing
014	Add requirements for the CISM to support providing power consumption and energy metrics associated to its managed objects. Related recommendations from EVE021: greennfv.func.010 Contributions: - NFVIFA(23)000790 FEAT29 IFA010ed511 Functional reqs Green NFV for VIM, CCM, CISM: FEAT agreed at IFA#362 - NFVIFA(23)000795 FEAT29 IFA040ed511 Green NFV interface enhancements: FEAT agreed at IFA#362 Missing contributions: none	IFA010 and/or IFA040	Mar-2024	Ongoing
015	Add requirements for the VNF power management function to support providing power consumption and energy metrics associated to VNFs. See note 1. Related recommendations from EVE021: greennfv.func.011	IFA010 and/or IFA007/008 and/or IFA049	Aug-2024	Not started
016	Add requirements for the NFVO to support providing power consumption and energy metrics associated to its managed objects. Related recommendations from EVE021: greennfv.func.012	IFA010 and/or IFA013	Aug-2024	Not started
017	Add requirements and enhancements to the VNFD to support the description of power profiles of a VNF, and support the description of CPU power state related information and constraints on a per VDU basis. Related recommendations from EVE021: greennfv.desc.001, greennfv.desc.002.	IFA011	Aug-2024	Not started
018	Add requirements and enhancements for the virtualised resource reservation interface(s) produced by the VIM to support - providing information about which virtualised resources are expected to be terminated, and - providing references to existing allocated virtualised resources during which virtualised resource reservation creation. Related recommendations from EVE021: greennfv.if.001, greennfv.if.002	IFA005	Aug-2024	Not started
019	Add requirements and enhancements for the VNF and NS LCM interfaces produced by the VNFM and NFVO, respectively, to enable the parameterization of power state related requirements associated to VDUs to be deployed. Determine relationship with feature of "Flexible VNF deployment". Related recommendations from EVE021: greennfv.if.004	IFA013 and IFA007/008	Aug-2024	Not started
020	Add requirements and enhancements to the NFV-MANO configuration and information management interface produced by an NFV-MANO functional entity to support: - suspending a managed entity, such as the NFV-MANO functional entity application and NFV-MANO service interfaces, and - suspending the consumption of NFV-MANO service interfaces produced by a peer NFV-MANO functional entity. Related recommendations from EVE021: greennfv.if.005, greennfv.if.006	IFA031	Aug-2024	Not started
021	Define metrics about energy efficiency of: - NFVI physical resources, including compute, storage and network, - Virtualised compute resource, and determine if feasible for other kinds of virtualised resources, - A group of one or more OS containers. - VNF Define metrics about performance of: - A virtual compute resource, and determine if feasible for other kinds of virtualised resources, - A group of one or more OS containers. Related recommendations from EVE021: greennfv.if.007, greennfv.if.008, greennfv.if.009, greennfv.if.010, greennfv.if.011, greennfv.if.015, greennfv.if.017.	IFA027	Aug-2024 (see note 2)	Not started
022	Define a set of metrics related to energy/power consumption of: - NFVI physical resources, - Virtualised compute resource (and possibly for other kinds of virtualised resources), - A group of one or more OS containers, - VNF, - NS. Related recommendations from EVE021: greennfv.if.012, greennfv.if.013, greennfv.if.014, greennfv.if.016, greennfv.if.018 Contributions: - NFVIFA(24)000040 FEAT29 IFA027ed511 Power/energy consumption metrics of VR: available - NFVIFA(24)000041 FEAT29 IFA027ed511 Power/energy consumption metrics of containerized workloads: available Missing contributions: - Metrics for NFVI physical resources (pending on IFA053 interface definition) - Metrics for VNF/VNFC - Metrics for NS	IFA027	Aug-2024 (see note 2)	Ongoing
NOTE 1: A solution needs to be agreed as documented in the EVE021; this can impact different specifications. NOTE 2: Specification could be delivered in different drops for subsets of managed objects. It is expected to prioritize from lower to higher layers in the NFV stack, i.e., first infrastructure level and last NS level, with intermediate results that can be delivered at earlier drops (e.g., Mar-2024).

Stage 3 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.

SOL

ID	Action	Impacted WG(s)	Target completion	Status
001	TBD	TBD	TBD	TBD

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT30: VNF configuration

Overview

Feature Prime	Bruno Chatras (Orange)
Feature description	The scope of this feature covers the following areas: 1) Provide guidelines on the use of the configuration options available in the NFV framework and the types of configuration data applicable to each of these options. 2) Specify related enhancements to the set of ETSI NFV specifications needed to improve interoperability between VNFs and independently-developed VNF configuration management functions and further facilitate automation of VNF configuration.
Target Release	Stage 2: Release 5 drop 1 (ed511) and drop 2 (ed521) Stage 3: TBD (Release 5 (2023-X-X))
Impacted WIs	Stage 2: TBD (IFAxx, IFAyy, SOLzz) Stage 3: TBD (SOLzz)
MegaCRs	Stage 2: TBD: IFAxxx MegaCR NFVIFA(21)000xxx (CR Status) IFAyyy MegaCR NFVIFA(21)000yyy (CR Status) Stage 3: TBD: SOLzzz MegaCR NFVSOL(21)000zzz (CR Status)
Related/Dependent Features	FEAT24 on "VNF generic OAM"
New Specifcations	Informative: ETSI GR NFV-EVE 022 Stage 2: Not required Stage 3: TBD
Status	Informative: Completed Stage 2: ongoing (40%) Stage 3: TBD
Contributions	All feature contributions Agreed content
Feature team	Informative: Bruno Chatras (Orange) Stage 2: Joan Triay (DOCOMO) Stage 3: Name (Company)
Last Updated	2024-02-13

EVE

ID	Action	Impacted WG(s)	Target completion	Status
001	Skeleton and scope - NFVIFA(21)000751 EVE022 skeleton and scope	EVE	Sept-2021	Completed
002	Overview and and use cases	EVE	Oct-2021	Completed
003	Analysis of Use Cases and Identification of Key Issues	EVE	Nov-2021	Completed
004	Solutions identification	EVE	March-2022	Completed
005	Solutions comparison	EVE	June-2022	Completed
006	Recommendations	EVE	Sep-2022	Completed

Stage 2 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) and WI(s)	Target completion	Status
001	Add support to enable VNFs and EMs to register in a service registry, information enabling other entities to discover the protocols and data models to use for providing configuration information. This could be done leveraging a specification about such "service registry", e.g., either based on NFV-MANO SBA or PaaS Services. Related recommendations from EVE022: REQ-GEN-1	Potentially IFA049 or NFV-MANO SBA related specs	Aug-2024	Not started
002	Add a recommendation for VNF designers to enable the VNFs to be able to register their configuration interfaces details in a service registry, directly or indirectly (e.g., via a PaaS service). Related recommendations from EVE022: REQ-OTHER-1	IFA011 and potentially IFA049 or NFV-MANO SBA related specs	Aug-2024	Not started
003	Add support in the NFV architectural framework to enable the distribution and storage of configuration data for one or multiple VNF instances in a common and centralized manner (also known as Configuration Server in EVE022), including specific enhancements like: - Add requirements of the Configuration Server of its capabilities, such as (not limited): storing configuration data, transforming configuration data, enabling the provisioning and reading of configuration data, notifying about changes about stored configuration data. - Specify interfaces produced by the Configuration Server. Related recommendations from EVE022: REQ-GEN-4, REQ-FUNC-3, REQ-IF-1 Contributions: - NFVIFA(23)000777 FEAT30 IFA049ed511 Multiple clauses Adding Configuration Server PaaS Service: approved at IFA#362 - NFVIFA(23)000778 FEAT30 IFA049ed511 Clause 6.3 Configuration Server interfaces: approved at IFA#362 - NFVIFA(24)000035 FEAT30 IFA049ed511 Clause 7 Information elements Configuration Server: approved at IFA#367 Missing contributions: none	IFA049	Mar-2024	Completed
004	Add requirements to VNFM to support the capability of interacting with a Configuration Server for the purpose of providing/reading configuration data for/of managed VNF instances. Related recommendations from EVE022: REQ-FUNC-4 Contributions: - NFVIFA(23)000796 FEAT30 IFA010ed511 Clause 7.3 VNFM requirement for Config Server: approved at IFA#362 Missing contributions: none	IFA010	Mar-2024	Completed
005	Add requirements to relevant VNF generic OAM function (e.g., VNF configuration, Network configuration functions) to support the capability of interacting with a Configuration Server for the purpose of reading and applying configuration data for/of managed VNF instances. Related recommendations from EVE022: REQ-FUNC-4 Contributions: - NFVIFA(23)000780 FEAT30 IFA049ed511 Clause 5 Requirements to use the Configuration Server by other functions: approved at IFA362 Missing contributions: none	IFA049	Mar-2024	Completed
006	Add requirements and enhance models and interfaces to support the capability of the NFVO of: - sending notifications to the OSS if a VNF instance has been modified as a result of an auto-scale decision made by the VNFM, and - including VNFM interface details for subscribing to VNF LCM notification in the VNF information made available to the OSS. Related recommendations from EVE022: REQ-FUNC-1, REQ-FUNC-2 Contributions: - NFVIFA(24)000036 FEAT30 IFA010ed511 Clause 6 NFVO requirements VNF LCM notifications and information: available - NFVIFA(24)000037 FEAT30 IFA013ed511 Clause 8.3 VNF LCM events and information for configuration: available Missing contributions: none	IFA010 and IFA013	Mar-2024	Ongoing
007	Enhance the VNFD with new attributes in the CPD to identify in a machine-processable format the connection points to be connected to the OSS/EM. Related recommendation from EVE022: REQ-DESC-1 Contributions: - NFVIFA(24)000038 FEAT30 IFA011ed511 Enhancements for configuration: available Missing contributions: none	IFA011	Mar-2024	Ongoing
008	Enhance the VNFD with new standard VNF configurable properties to enable identifying and performing the configuration into the VNF of CPs and relevant protocol layer information (e.g., IP addresses) of the management system to which the VNF is to be connected/peered with. Related recommendation from EVE022: REQ-DESC-2 Contributions: - NFVIFA(24)000038 FEAT30 IFA011ed511 Enhancements for configuration: available Missing contributions: none	IFA011	Mar-2024	Ongoing
009	Add requirements to support the specification on the DSL for LCM scripts, which would support invoking an agent-less configuration solution. Related recommendations from EVE022: REQ-GEN-2 Contributions:- NFVIFA(24)000109 FEAT30 IFA011ed511 DSL requirement for agent-less configuration: available Missing contributions: none	IFA011	Mar-2024	Ongoing
010	Select a solution from key issue#1 of EVE022 to map API parameters, in addition to configurable properties, into MCIOP input parameters. Related recommendations from EVE022: REQ-GEN-5	IFA010 and IFA011	Mar-2024	Completed by ENH02.06?
011	Enhance the VNFD to mandate that the output of an LCM script triggered upon detection of a VNF lifecycle event corresponding to the start of a VNF LCM procedure as described in ETSI GS NFV-IFA 011 be made available as input to the implementation of the corresponding LCM procedure. Related recommendations from EVE022: REQ-DESC-3	IFA011	Mar-2024	Completed by ENH02.06?
012	Document the pros and cons of analysis made in clause 7 as a guideline. Related recommendations from EVE022: REQ-GEN-3	EVE022 or new GR	Aug-2024	Not started
NOTE 1: Inputs of actions and major parts of text come from contribution NFVEVE(22)000190.

Stage 3 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.

SOL

ID	Action	Impacted WG(s)	Target completion	Status
001	TBD	TBD	TBD	TBD

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT31: Flexible VNF deployment

Overview

Feature Prime	Arturo Martin de Nicolas (Ericsson)
Feature description	This feature enhances the flexibility of the VNF deployment by introducing parametrization of VNF deployment flavours. It covers the following areas 1) Ability to specify in the VNFD which VDUs or groups of VDUs are optional for a particular deployment flavour 2) Ability to specify in the VNFD which VDU attributes related to resource capacity are configurable 3) Ability to specify in the NSD the selected optional VDUs or group of VDUs of a constituent VNF that are to be deployed 4) Ability to specify in the NS LCM and VNF LCM interfaces the selected optional VDUs or group of VDUs to be deployed 5) Ability to specify in the NS LCM and VNF LCM interfaces the selected values for VDU attributes related to resource capacity
Target Release	Stage 2: TBD (Release 5 (2023-X-X)) Stage 3: TBD (Release 5 (2023-X-X))
Impacted WIs	Stage 2: IFA010 IFA011 IFA007 IFA008 IFA013 IFA014 Stage 3: SOL001 SOL002 SOL003 SOL005 SOL016? SOL018?
MegaCRs	Stage 2: TBD: IFAxxx MegaCR NFVIFA(21)000xxx (CR Status) IFAyyy MegaCR NFVIFA(21)000yyy (CR Status) Stage 3: TBD: SOLzzz MegaCR NFVSOL(21)000zzz (CR Status)
Related/Dependent Features	None
New Specifcations	Informative: IFA044
Status	Informative: Completed Stage 2: Not started Stage 3: Not started
Contributions	All feature contributions Agreed content
Feature team	Stage 2: Arturo Martin de Nicolas (Ericsson) Stage 3: Arturo Martin de Nicolas (Ericsson)
Last Updated	2023-01-10

Stage 2 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

Deployable Modules Part

ID	Action	Impacted WG(s)	Target completion	Status
001	Add requirements on functional behaviour as per recommendations Vnfm.DepMod.001 and Nfvo.DepMod.001 IFA044 clause 8.1. CRs: NFVIFA(23)000126r2 Status: Feat agreed in NFVIFA#325	IFA010	Completed	All CRs Feat agreed
002	Introduce deployableModules in the VNFD as per recommendations VNFD.DepMod.001, VNFD.DepMod.002 and VNFD.DepMod.003 in IFA044 clause 8.2. CRs: NFVIFA(23)000127r1 Status: Feat agreed in NFVIFA#325 NFVIFA(23)000206 Status: Feat agreed in NFVIFA#329 NFVIFA(23)000128 Status: Feat agreed in NFVIFA#325	IFA011	Completed	All CRs Feat agreed
003	Add a provision in ScalingAspect IE to exclude combining VDUs that don't belong to the same deployable modules CRs: NFVIFA(23)000264r2 Status: Feat agreed in NFVIFA#334 NFVIFA(23)000477r1 Status: Feat agreed in NFVIFA#339	IFA011	Completed	All CRs Feat agreed
004	Add a provision in MciopProfile IE to exclude combining VDUs that don't belong to the same deployable modules CRs: NFVIFA(23)000270r2 Status: Feat agreed in NFVIFA#334 NFVIFA(23)000477r1 Status: Feat agreed in NFVIFA#339	IFA011	Completed	All CRs Feat agreed
005	Introduce new attributes in VnfProfile and NsProfile for the support of the selection of deployableModules of the constituent VNFs as per recommendations NSD.DepMod.001, NSD.DepMod.002, NSD.DepMod.003, NSD.DepMod.004 in IFA044 clause 8.2. CRs: NFVIFA(23)000131r2 Status: Feat agreed in NFVIFA#327	IFA014	Completed	All CRs Feat agreed
006	Introduce new parameters in VNF LCM operations Instantiate VNF, Change VNF flavour, Change current VNF package operation to convey the selection of deployableModules. as per recommendations Vnflcm.DepMod.001, Vnflcm.DepMod.003 and Vnflcm.DepMod.004 in IFA044 clause 8.3. CRs: NFVIFA(23)000181r1 Status: Feat agreed in NFVIFA#327 NFVIFA(23)000243 Status: Feat agreed in NFVIFA#332	IFA007 IFA008	Completed	All CRs Feat agreed
007	Introduce provisions for how to handle instantiation or scale level information related to VNFCs that are not part of the selected deployable modules. CRs: NFVIFA(23)000223r1 Status: Feat agreed in NFVIFA#332 NFVIFA(23)000359 Status: Feat agreed in NFVIFA#337 NFVIFA(23)000360r1 Status: Feat agreed in NFVIFA#337	IFA007 IFA008 IFA013	Completed	All CRs Feat agreed
008	Introduce new VNF LCM operation to support the modification of the selection (addition or removal) of deployableModules as per recommendation Vnflcm.DepMod.002 in IFA044 clause 8.3. CRs: NFVIFA(23)000185r3 Status: Feat agreed in NFVIFA#329 NFVIFA(23)000244 Status: Feat agreed in NFVIFA#332	IFA007 IFA008	Completed	All CRs Feat agreed
009	Introduce a new attribute in the VnfInfo or InstantiatedVnfInfo to indicate the deployable modules currently selected CRs: NFVIFA(23)000199r1 Status: Feat agreed in NFVIFA#330 NFVIFA(23)000246 Status: Feat agreed in NFVIFA#332 NFVIFA(23)000269 Status: Feat agreed in NFVIFA#332	IFA007 IFA008 IFA013	Completed	All CRs Feat agreed
0010	Add SelectVnfDeployableModules configuration parameters to VnfLcmOperationsConfiguration IE CRs: NFVIFA(23)000226 Status: Feat agreed in NFVIFA#331	IFA011	Completed	All CRs Feat agreed
011	Add attributes to IEs used in the update NS operation to support conveying the selection of deployableModules as per recommendations Nslcm.DepMod.001, Nslcm.DepMod.002, Nslcm.DepMod.003, Nslcm.DepMod.004, Nslcm.DepMod.005, Nslcm.DepMod.006, Nslcm.DepMod.007 in IFA044 clause 8.3. CRs: NFVIFA(23)000222 Status: Feat agreed in NFVIFA#331	IFA013	Completed	All CRs Feat agreed
012	Add new NS update type to the update NS operation and corresponding new IE to support the modification of the selection of deployableModules as per recommendations Nslcm.DepMod.008 in IFA044 clause 8.3. CRs: NFVIFA(23)000245r1 Status: Feat agreed in NFVIFA#332	IFA013	Completed	All CRs Feat agreed
013	Add new parameters in the grant VNF lifecycle operation to convey the selected deployableModules as per recommendation VnfGrant.DepMod.001 in IFA044 clause 8.3. CRs: NFVIFA(23)000200r2 Status: Feat agreed in NFVIFA#330	IFA007	Completed	All CRs Feat agreed
014	Add SAP to deployable modules mapping information in the NSD CRs: NFVIFA(23)000388r1 Status: Feat agreed in NFVIFA#337 NFVIFA(23)000478r1 Status: Feat agreed in NFVIFA#339	IFA014	Completed	All CRs Feat agreed
015	MegaCRs: FEAT31 IFA010ed451 Mega-CR for deployable modules support: NFVIFA(23)000474 Status: Approved in IFA #339 FEAT31 IFA011ed451 Mega CR for deployable modules support: NFVIFA(23)000480r1 Status: Approved in IFA #339 FEAT31 IFA014ed451 Mega CR for deployable modules support: NFVIFA(23)000500 Status: Approved in IFA #341 FEAT31 IFA007ed451 Mega CR for deployable modules support: NFVIFA(23)000520 Status: Approved in IFA #342 NFVIFA(23)000602 Status: Approved FEAT31 IFA008ed451 Mega CR for deployable modules support: NFVIFA(23)000521 Status: Approved in IFA #342 FEAT31 IFA013ed451 Mega CR for deployable modules support: NFVIFA(23)000523 Status: Approved in IFA #342 FEAT31 Flexible VNF deployment - Deployable Modules Part - MegaCR Index NFVIFA(23)000545 Status: Noted in IFA #342		Completed	All Mega CRs approved

Configurable capacity attributes part

ID	Action	Impacted WG(s)	Target completion	Status
001	Add requirements on functional behaviour as per recommendations Vnfm.ConfAttr.001 in IFA044 clause 8.1. CRs: NFVIFA(23)000126r2 Status: Feat agreed in NFVIFA#325	IFA010	Completed	All CRs Feat agreed
002	Introduce support for indication that a VDU resource capacity related attribute is configurable and in which operations the value is modifiable as per recommendations VNFD.ConfAttr.001 and VNFD.ConfAttr.002 in IFA044 clause 8.2. CRs: NFVIFA(23)000281r1 Status: Feat agreed in NFVIFA#333 NFVIFA(23)000697 Status: Feat agreed in NFVIFA#358 NFVIFA(23)000744r2 Status: Feat agreed in NFVIFA#362 NFVIFA(23)000785r2 Status: Feat agreed in NFVIFA#362	IFA011	Completed	All CRs Feat agreed
003	Introduce a new attribute in the VnfProfile to indicate whether it is allowed or not to modify values of VDU attributes related to resource capacity by means of NS LCM interface as per recommendation NSD.ConfAttr.001 in IFA044 clause 8.2. CRs: NFVIFA(23)000742 Status: Feat agreed in NFVIFA#362 NFVIFA(24)000011r1 Status: Feat agreed in INFIVA#365	IFA014	Completed	All CRs Feat agreed
004	Introduce new parameters in VNF LCM operations Instantiate VNF, Change VNF flavour, Change current VNF package to convey selected values for VDU attributes related to resource capacity as per recommendations Vnflcm.ConfAttr.001, Vnflcm.ConfAttr.003 and Vnflcm.ConfAttr.004 in IFA044 clause 8.3. CRs: NFVIFA(23)000692r2 Status: Feat agreed in NFVIFA#357 NFVIFA(23)000768 Status: Feat agreed in NFVIFA#362 NFVIFA(23)000740 Status: Feat agreed in NFVIFA#362 NFVIFA(23)000769r2 Status: Feat agreed in NFVIFA#362 NFVIFA(23)000724 Status: Feat agreed in NFVIFA#359 NFVIFA(23)000741 Status: Feat agreed in NFVIFA#362 NFVIFA(23)000799 Status: Feat agreed in NFVIFA#362 NFVIFA(23)000803 Status: Feat agreed in NFVIFA#362	IFA007 IFA008	Completed	All CRs Feat agreed
005	Decide whether to use scale VNF operation or add a new VNF LCM operation to support the modification of selected values for VDU attributes related to resource capacity and add new parameters to the scale VNF operation or add new operation based on the decision, as per recommendation Vnflcm.ConfAttr.002 in IFA044 clause 8.3. Decision: Use Scale VNF operation CRs: NFVIFA(23)000696r2 Status: Feat agreed in NFVIFA#358 NFVIFA(23)000739 Status: Feat agreed in NFVIFA#361	IFA007 IFA008	Completed	Completed
006	Add an attribute in the InstantiatedVnfInfo IE to indicate the current values of capacity related VDU attributes, if different to the default values indicated in the VNFD. CRs: NFVIFA(23)000716r2 Status: Feat agreed in NFVIFA#360 NFVIFA(23)000749 Status: Feat agreed in NFVIFA#362 NFVIFA(23)000752 Status: Feat agreed in NFVIFA#362 Note: It was decided not to implement the NS LCM related impacts in v5.1.1. Thus NFVIFA(23)000752 will not be implemented in v5.1.1.	IFA007 IFA008 IFA013	Completed	All CRs Feat agreed
007	Introduce new parameters in VNF LCM operation Select VNF deployable modules to convey selected values for VDU attributes related to resource capacity CRs: NFVIFA(23)000825 Status: Feat agreed in NFVIFA#362 NFVIFA(23)000826 Status: Feat agreed in NFVIFA#362	IFA007 IFA008	Completed	All CRs Feat agreed
008	Add attributes to IEs used in the update NS operation to support conveying selected values for VDU attributes related to resource capacity as per recommendations Nslcm.ConfAttr.001, Nslcm.ConfAttr.002, Nslcm.ConfAttr.003, Nslcm.ConfAttr.004, Nslcm.ConfAttr.005, Nslcm.ConfAttr.006, Nslcm.ConfAttr.007 in IFA044 clause 8.3. CRs: NFVIFA(23)000738r3 Status: Feat agreed in NFVIFA#362 NFVIFA(23)000800 Status: Feat agreed in NFVIFA#362 NFVIFA(23)000804 Status: Feat agreed in NFVIFA#362 Note: It was decided not to implement the NS LCM related impacts in v5.1.1. Thus NFVIFA(23)000738r3, NFVIFA(23)000800 and NFVIFA(23)000804 will not be implemented in v5.1.1.	IFA013	Completed	All CRs Feat agreed
009	Decide whether to use scale NS operation or introduce new NS update type or use the new NS update type introduced in activity 011 to support the modification of selected values for VDU attributes related to resource capacity and add attributes to the new or existing IEs, depending on the decision, as per recommendation Nslcm.ConfAttr.008 in IFA044 clause 8.3. CRs:NFVIFA(23)000738r3 Status: Feat agreed in NFVIFA#362 Note: It was decided not to implement the NS LCM related impacts in v5.1.1. Thus NFVIFA(23)000738r3 will not be implemented in v5.1.1.	IFA013	Completed	All CRs Feat agreed
010	Add attributes to IEs used in the Update NS operation to support conveying selected values for VDU attributes related to resource capacity when selecting VNF deployable modules CRs:NFVIFA(23)000827 Status: Feat agreed in NFVIFA#362 Note: It was decided not to implement the NS LCM related impacts in v5.1.1. Thus NFVIFA(23)000827 will not be implemented in v5.1.1.	IFA013	Completed	All CRs Feat agreed
011	Add new parameters in the grant VNF lifecycle operation to convey values for VDU attributes related to resource capacity as per recommendation VnfGrant.ConfAttr.001 in IFA044 clause 8.3. CRs: NFVIFA(23)000717r1 Status: Feat agreed in NFVIFA#360	IFA007	Completed	All CRs Feat agreed
	MegaCRs:FEAT31 IFA010ed451 Mega-CR for dynamic VDU capacity support: NFVIFA(23)000814 Status: Approved in IFA #362 FEAT31 IFA011ed451 Mega CR for dynamic VDU capacity support: NFVIFA(23)000815r1 Status: Approved in IFA #362 FEAT31 IFA014ed451 Mega CR for dynamic VDU capacity support: NFVIFA(24)000012r1 Status: Approved in IFA #365 FEAT31 IFA007ed451 Mega CR for ddynamic VDU capacity support: NFVIFA(23)000841 Status: Approved in IFA #364 FEAT31 IFA008ed451 Mega CR for dynamic VDU capacity support: NFVIFA(23)000844r1 Status: Approved in IFA #364 FEAT31 Flexible VNF deployment - dynamic VDU capacity Part - MegaCR Index NFVIFA(24)000020 Status: Noted in IFA #365		Completed	All MegaCRs approved

Stage 3 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.

SOL

Deployable modules part

ID	Action	Impacted WG(s)	Target completion	Status
001	Introduce deployableModules in the VNFD as per recommendations VNFD.DepMod.001, VNFD.DepMod.002 and VNFD.DepMod.003 in IFA044 clause 8.2. CRs: NFVSOL(23)000176 Status: Feature agreed in SOL #248, Approved in SOL #256 NFVSOL(23)000256 Status: Approved in SOL #256 NFVSOL(23)000179 Status: Feature agreed in SOL #248, Approved in SOL #256	SOL001	Completed	All CRs approved
002	Add a provision in ScalingAspect to exclude combining VDUs that don't belong to the same deployable modules CRs: NFVSOL(23)000177 Status: Feature agreed in SOL #248, Approved in SOL #256	SOL001	Completed	All CRs approved
003	Add a provision in Mciop node to exclude combining VDUs that don't belong to the same deployable modules CRs: NFVSOL(23)000180 Status: Feature agreed in SOL #248, Approved in SOL #256	SOL001	Completed	All CRs approved
004	Introduce new attributes in VnfProfile and NsProfile for the support of the selection of deployableModules of the constituent VNFs as per recommendations NSD.DepMod.001, NSD.DepMod.002, NSD.DepMod.003, NSD.DepMod.004 in IFA044 clause 8.2. CRs: NFVSOL(23)000181 Status: Feature agreed in SOL #248, Approved in SOL #256	SOL001	Completed	All CRs approved
005	Introduce new parameters in VNF LCM operations Instantiate VNF, Change VNF flavour, Change current VNF package operation to convey the selection of deployableModules. as per recommendations Vnflcm.DepMod.001, Vnflcm.DepMod.003 and Vnflcm.DepMod.004 in IFA044 clause 8.3. CRs: NFVSOL(23)000182 Status: Feature agreed in SOL #248, Approved in SOL #253 NFVSOL(23)000199 Status: Feature agreed in SOL #250, Approved in SOL #253	SOL003 SOL002	Completed	All CRs approved
006	Introduce provisions for how to handle instantiation or scale level information related to VNFCs that are not part of the selected deployable modules. CRs: NFVSOL(23)000210r1 Status: Feature agreed in SOL #250, Approved in SOL #253 NFVSOL(23)000223 Status: Feature agreed in SOL #253, Approved in SOL #253 NFVSOL(23)000233 Status: Approved in SOL #253 NFVSOL(23)000234 Status: Approved in SOL #253	SOL003 SOL002 SOL005	Completed	All CRs approved
007	Introduce new VNF LCM operation to support the modification of the selection (addition or removal) of deployableModules as per recommendation Vnflcm.DepMod.002 in IFA044 clause 8.3. CRs: NFVSOL(23)000220r1 Status: Feature agreed in SOL #252, Approved in SOL #253 NFVSOL(23)000236r1 Status: Approved in SOL #253	SOL002 SOL003	Completed	All CRs approved
008	Introduce a new attribute in the VnfInfo or InstantiatedVnfInfo to indicate the deployable modules currently selected CRs: NFVSOL(23)000209 Status: Feature agreed in SOL #250, Approved in SOL #253 NFVSOL(23)000215 Status: Feature agreed in SOL #251, Approved in SOL #253 NFVSOL(23)000216: Status: Feature agreed in SOL #251, Approved in SOL #253	SOL002 SOL003 SOL005	Completed	All CRs approved
009	Add SelectVnfDeployableModules configuration parameters to VnfLcmOperationsConfiguration data type CRs: NFVSOL(23)000257 Status: Feature agreed in SOL #256	SOL001	Completed	All CRs approved
010	Add attributes to datatypes used in the update NS operation to support conveying the selection of deployableModules as per recommendations Nslcm.DepMod.001, Nslcm.DepMod.002, Nslcm.DepMod.003, Nslcm.DepMod.004, Nslcm.DepMod.005, Nslcm.DepMod.006, Nslcm.DepMod.007 in IFA044 clause 8.3. CRs: NFVSOL(23)000267 Status: Approved in SOL #257	SOL005	Completed	All CRs approved
011	Add new NS update type to the update NS operation and corresponding datatype to support the modification of the selection of deployableModules as per recommendations Nslcm.DepMod.008 in IFA044 clause 8.3. CRs: NFVSOL(23)000298r1 Status: Approved in SOL #260	SOL005	Completed	All CRs approved
012	Add new parameters in the grant VNF lifecycle operation to convey the selected deployableModules as per recommendation VnfGrant.DepMod.001 in IFA044 clause 8.3. CRs: NFVSOL(23)000276 Status: Approved in SOL #258	SOL003	Completed	All CRs approved
013	Add SAP to deployable modules mapping information in the NSD CRs: NFVSOL(23)000291r1 Status: Approved in SOL #260	SOL001	Completed	All CRs approved
014	Add example of VNFD with deployable modules CRs: NFVSOL(23)000288 Status: Approved in SOL #259	SOL001	Completed	All CRs approved
015	Add examples of NSD and nested NSD with SAP to deployable module mapping information CRs: NFVSOL(23)000299r1: Status: Approved in SOL #260	SOL001	Completed	All CRs approved
016	Add entries in Annex D mapping table with the deployable modules parameters in the APIs CRs: NFVSOL(23)000310 Status: Approved in SOL #260	SOL001	Completed	All CRs approved
017	Miscelaneous error corrections. CRs: NFVSOL(23)000287r1 Status: Approved in SOL #259 NFVSOL(23)000311 Status: Approved in SOL #260	SOL001	Completed	All CRs approved

Configurable capacity attributes part

ID	Action	Impacted WG(s)	Target completion	Status
001	Introduce sibling properties for VDU capacity related attributes CRs: NFVSOL(23)000376r2 Status: Feature agreed in SOL#269, approved in SOL#274. NFVSOL(24)000001r1 Status: Feature agreed in SOL#271, approved in SOL#274.	SOL001	Completed	All CRs approved
002	Add a property to VduProfile data type to indicate in which VNF LCM operations the indication of values for capacity related VDU properties is supported. CRs: NFVSOL(23)000378 Status: Feature agreed in SOL#269, approved in SOL#274. NFVSOL(23)000403 Status: Feature agreed in SOL#270, approved in SOL#274.	SOL001	Completed	All CRs approved
003	Add a property in VnfProfile to indicate whether the overriding of values of capacity related VDU properties is allowed. CRs: NFVSOL(23)000400r1 Status: Feature agreed in SOL#270, approved in SOL#274. NFVSOL(23)000002r1 Status: Feature agreed in SOL#272, approved in SOL#274.	SOL001	Completed	All CRs approved
004	Add attributes to VNF LCM operations to support the indication of values for capacity related VDU propeties. CRs: NFVSOL(23)000381r4 Status: Feature agreed in SOL#270, approved in SOL#274 NFVSOL(24)000003 Status: Feature agreed in in SOL#271, approved in SOL#274 NFVSOL(23)000390r4 Status: Feature agreed in SOL#271, approved in SOL#274	SOL003 SOL002	Completed	All CRs approved
005	Add atributes in InstantiatedVnfInfo for the values of the capacity related VDU properties if different to the default values from the VNFD. CRs: NFVSOL(23)000385r3 Status: Feature agreed in SOL#270, approved in SOL#274 NFVSOL(23)000391r2 Status: Feature agreed in SOL#271, approved in SOL#274	SOL003 SOL002	Completed	All CRs approved
006	Add attributes in the Grant request to indicate the values of capacity related VDU attributes if these were provided in the corresponding VNF LCM operation request. CRs: NFVSOL(23)000384 Status: Feature agreed in SOL#270, approved in SOL#274	SOL003	Completed	All CRs approved

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT33: Physical Infrastructure Management

Overview

Feature Prime	Hammad Zafar (NEC)
Feature description	The scope of FEAT33 covers the following areas: - define requirements for physical infrastructure management in the NFV-MANO framework - provide a common information model for describing hardware attributes and statuses, and specify operations for managing infrastructure hardware with respect to life cycle and FCAPS of physical resources - profile existing solutions related to hardware management
Target Release	Stage 2: Release 5 drop 3 (2025-3) Stage 3: Release 5 (TBD)
Impacted WIs	Stage 2: IFA010, NFV006 Stage 3: TBD
MegaCRs	Stage 2: IFAxxx MegaCR NFVIFA(18)000xxx (CR Status) IFAyyy MegaCR NFVIFA(18)000yyy (CR Status) Stage 3: SOLzzz MegaCR NFVSOL(19)000zzz (CR Status)
Related/Dependent Features	FEAT17: Cloud-Native VNFs and Container Infrastructure management FEAT27: NFV for vRAN FEAT29: Green NFV FEAT19b: NFV Connectivity
New Specifcations	Stage 2: IFA053 Stage 3: TBD
Status	Stage 2: Ongoing (progerss is TBD) Stage 3: Not started
Contributions	All feature contributions Agreed content
Feature team	Stage 2: Name (Company) Hammad Zafar (NEC) Haitao Xia (Huawei) Kostas Katsalis (DOCOMO) Joan Triay (DOCOMO) Stage 3: Name (Company)
Last Updated	2023-10-20

Stage 2 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 WI(s)	Target completion	Status
001	Scope and skeleton of GS IFA053 Contributions: NFVIFA(23)000313r1, NFVIFA(23)000352r1	IFA053	May-2023	Completed
002	Summarize relevant use cases and scenarios related to physical infrastructure management from relevant NFV documents. Contributions: NFVIFA(23)000421r1, NFVIFA(23)000449r2, NFVIFA(23)000539r1, NFVIFA(23)000655r1, NFVIFA(23)000644r1	IFA053	Sep-2023	Completed
003	Analyse PIM frameworks from other organizations and document gaps. Contributions: NFVIFA(23)000654r1	IFA053	Dec-2023	Started
004	Architectural analysis and framework for PIM. Contributions: NFVIFA(23)000628r3, NFVIFA(23)000659r2, NFVIFA(23)000661r2, NFVIFA(23)000660r2, NFVIFA(23)000681r3	IFA053	Dec-2023	Started
005	Requirements for PIM and its services.	IFA053	Dec-2023	Not started
006	Information modelling for PIM based on capability analysis of existing solutions. See note.	IFA053	Jan-2024	Not started
007	Addition of PIM in the NFV-MANO framework and addition of high-level functional requirements associated with PIM.	NFV006, NFV003, IFA010	Jan-2024	Not started
008	Final approval for IFA053	IFA053	Feb-2024	Not started
NOTE: Profiling work could be postponed to Stage 3 or later versions of IFA053 if it requires extensive effort. The full work of the feature is expected to be completed by Release 5 drop 3 at the latest.

Stage 3 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.

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.

FEAT35: VNF management gaps with Open Source

Overview

Feature Prime	Shitao Li (Huawei)
Feature description	The scope of FEAT35 covers the following areas: It is studied in IFA051.
Target Release	Stage 2: Release 5 drop 1 Stage 3: Release 5 (TBD)
Impacted WIs	Stage 2: Stage 3: TBD
MegaCRs	Stage 2: IFAxxx MegaCR NFVIFA(18)000xxx (CR Status) IFAyyy MegaCR NFVIFA(18)000yyy (CR Status) Stage 3: SOLzzz MegaCR NFVSOL(19)000zzz (CR Status)
Related/Dependent Features
New Specifcations	Stage 2: none Stage 3: TBD
Status	Stage 2: Ongoing (progerss is TBD) Stage 3: Not started
Contributions	All feature contributions Agreed content
Feature team	Stage 2: Name (Company) Stage 3: Name (Company)
Last Updated	2024-01-23

ENH01: Security enhancements

This section contains an overview of small and generic security enhancements to the ETSI NFV framework and their current status.

ENH01.01: Certificate Management

Ways of Working for this security enhancement feature. Latest update made by NFVSEC(22)000032r2 at NFV#38/SEC#210 and NFVIFA(23)000459r2 at NFV#42.

• IFA026/IFA033 (SEC responsibility)
  • IFA026 on Basic use case / Basic concept and architectural aspects including IFA010 existing featagreedCRs
  • IFA033
  • update SEC021/022/023/025, if necessary

1. SEC agrees individual CRs.
2. IFA agrees bulk CRs with new draft baseline for 1 week.
3. (Option) If IFA comments technical change, SEC/IFA agrees by email for 3days.
4. Upload new draft

• Existing IFA spec (IFA responsibility)
  • IFA006/007/008/011/013/040
  • (Potential) IFA014

1. IFA agree individual CRs
2. SEC agree same CRs
3. (Option) if SEC comments technical change, IFA/SEC agrees by email for 3days.

ID	Name	Release	Status	Contact	Descirption	Contributions
ENH01.xx	New security enhancement		{Proposal,Under development, Completed, Closed}	Foo Bar (ACME) <foo.bar@acme.org>	A short description of the feaure	List of related CRs
ENH01.01	Certificate management	Release 4	Under development	Yuya Kuno (DOCOMO)	The security enhancement aims to specify the capability to support certificate management by introducing CMF (Certificate Management Function) within the NFV MANO architecture and is enhancing the NFV-MANO reference points and functional blocks. CMF enhances "Certificate Enrolment Server" as defined in ETSI GR NFV-SEC 005.	MegaCR: N/A New interface: N/A See Individual CRs and discussion paper

Enh01.01: Certificate Management

• Discussion paper NFVIFA(23)000459r3 "Enh01.01 remaining issues and future plan".
  • Agreed target of ed511 and ed521 in NFV#43
• Discussion paper NFVSEC(23)000134 "Discussion Paper on way forward for IFA026 & IFA033 Interfaces"
  • SEC#231 - noted

Stage1/2

ID	Action	impacted WI(s)	Target	Status
001-1	Add revoke usecase for direct mode of VNFCI certficate and VNF OAM certificate.	IFA026	ed511	Not started
002-1	Add renew usecase for delegation mode of VNFCI certficate and VNF OAM certificate.	IFA026	ed511	Not started
002-2	Add revoke usecase for delegation mode of VNFCI certficate and VNF OAM certificate.	IFA026	ed511	Not started
003	develop usecase for VNF Package certificate.	IFA026	ed521	Not started
004-1	Add renew usecase for NFV-MANO certificate.	IFA026	ed511	Not started
004-2	Add revoke usecase for NFV-MANO certificate.	IFA026	ed511	Not started
005	develop usecase for VCE C-Plane (Virtualised computation environment control plane) certificate.	IFA026	ed521	Not started
006-1	Update functional requirements for the certificate mgmt.	IFA026 IFA010	ed511	Not started
009-1	Add Deregister Operation	IFA033	ed511	Not started
010-1	Add Revoke Operation	IFA033	ed511	Not started
012	Add Vnf-Cm reference point	IFA033	ed521	Not started
013	Add Or-Cm reference point	IFA033	ed511	Not started
014	Add Vim-Cm reference point	IFA033	ed511	Not started
015	Add Cism-Cm reference point	IFA033	ed511	Not started
016	Add Os-Cm reference point	IFA033	ed511	Not started
017	Add Cm-Ca reference point	IFA033	ed521	Not started
018-1	Update VNFD to support revoke and renew	IFA011	ed511	Not started
019-1	Update VNF LCM to support revoke and renew	IFA006 IFA007 IFA008 IFA040	ed511	Not started
020-1	Update NS LCM to support revoke and renew	IFA013	ed511	Not started

Stage3

ID	Action	Impacted WI(s)	Status
001-1	Enhance VNFD to support certificate mgmt.	SOL001	Not started
001-2	Enhance VNFD to support certificate mgmt.	SOL006	Not started
002-1	Enhance VNF LCM to support certificate mgmt.	SOL002 SOL003	Not started
003-1	Enhance NS LCM to support certificate mgmt.	SOL005	Not started
004-1	Enhance VR mgmt	SOL014	Not started
005	Enhance MCIO mgmt NFVSOL(23)000247r1: SOL018ed451 Add mapping for certificate data	SOL018	ongoing
006-1	Enhance MANO mgmt	SOL009	Not started
007-1	Update MANO procedure	SOL016	Not started

ENH02: Special technical enhancements

This section contains an overview of small and generic technical enhancements to the ETSI NFV framework and their current status.

ID	Name	Release	Status	Contact	Description	Contributions
ENH02.01	NFV-MANO enhancement with SDN-based networking	Release 4	Stage 2 complete Stage 3 complete	Wang Ruixue, <wangruixue@chinamobile.com> Li Shitao,<lishitao@huawei.com>	This new enhancement proposes to enhance the NFV-MANO functionality related to virtualised network management, lifecycle management and template information model to support the integration of SDN-based network in the framework of NFV-MANO during the timeframe of Release 4. This work suggests to specify the SDN-based network resources in the NSD and VNFD model in order to use the different type of network to provision the network connection requirements at the design time. This work also suggests to enhance Os-Ma-nfvo, Or-Vi and Or-Vnfm reference points in order to manage the lifecycle of the different type of network.	Stage 2: NFVIFA(19)000858r4 : feature proposal (accepted) NFVIFA(19)000966r2: adding RD IE in IFA014, available NFVIFA(19)0001018: new requirements to IFA010, FEAT Agreed (IFA#202) NFVIFA(20)000240r2: adding new routing resource as a new type of network resources: FEAT Agreed (IFA#208) NFVIFA(20)000239r1: discussion paper for adding routing resource, available NFVIFA(20)000313r3: adding a new RoutingResorceData for describing a routing resource, FEAT Agreed (IFA#197) NFVIFA(20)000314r3: adding the Routing resource in the Update Virtualised Network Resource operation, FEAT Agreed (IFA#197) NFVIFA(20)000517r3: discussion paper for NSD model for supporting Routing resource: available ============= Mega CRs Approved ======== IFA005: NFVIFA(20)000728r1 (Approved in NFVIFA#216) IFA010: NFVIFA(21)000030r3 (Approval in IFA#230) IFA014: NFVIFA(21)000150r4 (Approval in IFA#230) Stage 3: SOL001 NFVSOL(22)000074r4 (Approved in SOL#197) SOL014 NFVSOL(23)000286 (Approvad in SOL#259)
ENH02.02	NFV-MANO enhancement for NS feasibility check	Release 4	Stage 2 complete Stage 3 completed without SOL016	Junichi Kawasaki <ju-kawasaki@kddi.com>, Kenichi Ogaki <ke-oogaki@kddi.com>, Rajavarma Bhyrraju <rajavarma.bhyrraju@ericsson.com>, Cristina Badulescu <cristina.badulescu@ericsson.com>, Anatoly Andrianov <anatoly.andrianov@nokia.com>, Kleber Ulrich <Ulrich.Kleber@huawei.com>	This new enhancement proposes to add the capability of feasibility check of Network Service to the lifecycle management during the timeframe of Release 4. This is required to support the requirements specified in step-3 of clause 5.1.21 in 3GPP TS28.531 (Management and provisioning of 5G network slicing), to check the feasibility of Network slice subnet by sending enquiry requests to MANO to determine availability of network constituents. This work suggests to enhance the Os-Ma-nfvo reference point to supporting the feasibility check of Network Service.	Stage2: NFVIFA(20)000187r2: New enhancement proposal (accepted, IFA#190) NFVIFA(20)000084a1r6: Discussion paper for option with extending existing operations (Noted, IFA#196) NFVIFA(20)000084r7: Changes to InstantiateNsRequest and UpdateNsRequest (FEAT agreed, IFA#196) NFVIFA(20)000332r3: Extending NsLcmOperationOccurrenceNotification (FEAT agreed, IFA#196) NFVIFA(20)000372r2: Support for modifying schedule time of scheduled operation (FEAT agreed, IFA#198) NFVIFA(20)000397r2: New requirements to IFA010 (FEAT agreed, IFA#200) ============= Mega CRs Approved ======== NFVIFA(20)000662r2: IFA013ed421 MegaCR ENH02.02 NS feasibility check (Accepted - IFA#217) NFVIFA(20)000397r2: New requirements to IFA010 (Accepted - IFA#213) Stage3: SOL005 NFVSOL(21)000549r1 (Approved in SOL#197) SOL005 NFVSOL(21)000551r1 (Approved in SOL#197) SOL005 NFVSOL(21)000550r2 (Approved in SOL#197) SOL005 NFVSOL(21)000548r4 (Approved in SOL#201) SOL005 NFVSOL(22)000106r5 (Approved in SOL#200) SOL005 NFVSOL(21)000553r7 (Approved in SOL#208) SOL016 ongoing
ENH02.03	NFV-MANO enhancement with Data flow mirroring	Release 4	Stage 2 complete Stage 3 complete without SOL14	Chen Shaofan <chenshaofan@chinamobile.com>, Li Shitao <lishitao@huawei.com>	This new enhancement proposes to enhance the NFV-MANO functionality to enable data flow mirroring management during the timeframe of Release 4. This work suggests to specify the intra NFVI-PoP data flow mirroring requirements in the NSD model in order to provide the flow information need to be mirrored at the design time. This work also suggests to enhance Or-Vi reference point in order to manage the intra NFVI-PoP data flow mirroring during the lifecycle of a NS.	Stage2: NFVIFA(20)000401：Supporting_Material_for_NFV_MANO_New_Enhancement_Proposal_Data_Flow_Mirroring（Noted in IFA-197） NFVIFA(20)000402r3: New enhancement proposal (accepted in IFA-202) NFVIFA(20)000491r7_ENH02.03_IFA010_release_4_enhancement_adding_new_requirement_to_NFVO （FEAT agreed in IFA#210） NFVIFA(20)000492r7_ENH02_03_IFA005_release_4_enhancement_adding_new_requirement（FEAT agreed in IFA#211） NFVIFA(20)000561r5_ENH02.03_IFA005_new parameters for Deletion of Data Flow Mirroring Job（FEAT agreed in IFA#211） NFVIFA(20)000563r6_ENH02.03_IFA005_new parameters for Query of Data Flow Mirroring Job（FEAT agreed in IFA#211） NFVIFA(20)000610r4_ENH02.03_IFA005_new parameters for updating of Data Flow Mirroring Job（FEAT agreed in IFA#211） NFVIFA(20)000611r4_ENH02.03_Use_Case_for_Data_Flow_Mirroring（FEAT agreed in IFA#215） NFVIFA(20)000707r2_ENH02.03_Information_Element_for_Data_Flow_Mirroring（FEAT agreed in IFA#215） NFVIFA(21)000050r1_ENH02_03_IFA013_adding_new_parameters_to_Update_NS_Operation（FEAT agreed in IFA#228） NFVIFA(21)000051r1_ENH02_03_IFA013_release_4_enhancement_adding_new_requirement_to_clause_5（FEAT agreed in IFA#226） NFVIFA(21)000052_ENH02_03_IFA013_adding_new_requirement_to_clause_7.3.5.1_introduction（FEAT agreed in IFA#226） NFVIFA(21)000183r1_ENH02_03_IFA013_Information_Element_CreateDataFlowMirroringJob（FEAT agreed in IFA#235） NFVIFA(21)000286r1_ENH02.03_IFA013_Information_Element_UpdateDataFlowMirroringJob（FEAT agreed in IFA#235） NFVIFA(21)000287r1_ENH02.03_IFA013_Add_Parameters_into_IE_NsInfo（FEAT agreed in IFA#235） NFVIFA(21)000288r1_ENH02.03_IFA013_Information_Element_MirroringJobInfo（FEAT agreed in IFA#235） NFVIFA(21)000456r3_ENH02_03_IFA010_adding_new_functional_requirement_to_NS_Instantiation_and_Termination（FEAT agreed in IFA#248） NFVIFA(21)000458r4_ENH02_03_IFA013_adding_new_parameters_to_Instantiate_NS_Operation（FEAT agreed in IFA#250） NFVIFA(21)000392r1_ENH02.03_IFA014_add_Parameters_into_VirtualLinkDf（FEAT agreed in IFA#254） NFVIFA(21)000393r5_ENH02.03_IFA014_Information_Element_NsDataFlowMirroring（FEAT agreed in IFA#254） ============= Mega CRs Approved ======== NFVIFA(21)000891r1_ENH02.03_Index_Summary (For Information) NFVIFA(20)000810r1_ENH02_03_IFA005_release_4_MegaCR NFVIFA(21)000017r6_ENH02_03_IFA010_release_4_MegaCR NFVIFA(21)000853r6_ENH02.03_IFA013_release_4_MegaCR NFVIFA(21)000854r1_ENH02.03_IFA014_release_4_MegaCR Stage3: SOL001 NFVSOL(22)000008r1 (approved at SOL#193) SOL001 NFVSOL(22)000011r3 (approved at SOL#194) SOL006 NFVSOL(22)000307r1 (approved at SOL#211) SOL005 NFVSOL(22)000012r3 (approved at SOL#196) SOL005 NFVSOL(22)000013r2 (approved at SOL#196) SOL005 NFVSOL(22)000014r2 (approved at SOL#196) SOL014 NFVSOL(23)000292 (approved at SOL#259)
ENH02.04	Invariant identification of NSD constituents	Release 4	Stage 2 completed Stage 3 completed	Arturo Martin de Nicolas <arturo.martin-de-nicolas@ericsson.com >	This enhancement proposes to add the capability to identify the VNFDs, nested NSDs and PNFDs of an NSD by invariant identities, as an alternative option to the descriptor Ids. The enhancement will avoid having to change and create a new NSD when its components (VNFDs, PNFDs or nested NSDs) are replaced by another version and this replacement does not require changes in the rest of the NSD.	Stage2: NFVIFA(20)000709r2: New enhancement proposal (accepted) NFVIFA(20)000710: New enhancement proposal - supporting material NFVIFA(20)000835r2: Enh02.04-IFA010ed421 Use of invariant identifications for NSD constituents (FEAT agreed at NFVIFA#223) NFVIFA(20)000836r4: Enh02.04-IFA011ed421 Introduction of a vnfdInvariantId (FEAT agreed at NFVIFA#226) NFVIFA(20)000837r6: Enh02.04-IFA014ed421 Adding invariantIds to the NSD (FEAT agreed at NFVIFA#224) NFVIFA(20)000838r3: Enh02.04-IFA013ed421 Adding descriptor Ids to NS LCM operations (FEAT agreed at NFVIFA#224) NFVIFA(21)000142: Enh02.04-IFA011ed421 Resolution of editor’s notes (FEAT agreed at NFVIFA#228) NFVIFA(21)000143: Enh02.04-IFA014ed421 Resolution of editor’s notes (FEAT agreed at NFVIFA#228) ============= Mega CRs for approval======== NFVIFA(21)000190r1: ENH02.04 MegaCR Index (Noted at IFA#229) NFVIFA(20)000835r2: Enh02.04-IFA010ed421 (approved at NFVIFA#229) NFVIFA(21)000179: Enh02.04-IFA011ed421 MegaCR (approved at NFVIFA#229) NFVIFA(21)000180: Enh02.04-IFA014ed421 MegaCR (approved at NFVIFA#229) NFVIFA(20)000838r3: Enh02.04-IFA013ed421 (approved at NFVIFA#229) Stage3: SOL001 NFVSOL(22)000017r1 (approved at SOL#194) SOL003 NFVSOL(21)000699r2 (approved at SOL#192) SOL005 NFVSOL(21)000590r1 (approved at SOL#187) SOL005 NFVSOL(21)000698r2 (approved at SOL#192) SOL006 NFVSOL(22)000304 (approved at SOL#209)
ENH02.05	Flexibility with scalable VNF/NS instantiation	Release 4	Stage 2 completed Stage 3 completed	Rajavarma Bhyrraju <rajavarma.bhyrraju@ericsson.com>	The enhancement feature proposes to add scaleLevels as input during instantiation to support flexibility with scalable VNF/NS instantiation. The VNFs/NSs supporting flexible instantiations are identified with VNFD/NSD level attribute(s). This enhancement provides flexibility for the service providers to adjust instantiation level when instantiating a VNF and supports instantiate a VNF with required size in one single operation.	Stage2: NFVIFA(20)000820r2: New enhancement proposal (accepted - IFA#219-e) NFVIFA(20)000630r2: Discussion paper for flexible VNF/NS instantiations (Noted - IFA#216) NFVIFA(20)000841r1: ENH02.05 IFA011ed421 Adding support of arbitrary levels VNF instantiation in the VNFD (FEAT agreed - IFA#220) NFVIFA(20)000842r3: ENH02.05 IFA014ed421 Adding support of flexible NS instantiation in the NSD (FEAT agreed - IFA#222) NFVIFA(20)000843r3: ENH02.05 IFA007ed421 Introduction of scaleInfo complementing instantionLevelId (FEAT agreed - IFA#222) NFVIFA(20)000844r3: ENH02.05 IFA008ed421 Introduction of scaleInfo complementing instantionLevelId (FEAT agreed - IFA#222) NFVIFA(20)000845r3: ENH02.05 IFA013ed421 Introduction of nsScaleInfo complementing nsInstantionLevelId (FEAT agreed - IFA#222) ============= Mega CRs for approval======== NFVIFA(21)000138: ENH02.05 MegaCR Index (Approved- IFA#227) NFVIFA(20)000841r1: ENH02.05 IFA011ed421 (Approved- IFA#227) NFVIFA(20)000842r3: ENH02.05 IFA014ed421 (Approved- IFA#227) NFVIFA(20)000843r3: ENH02.05 IFA007ed421 (Approved- IFA#227) NFVIFA(20)000844r3: ENH02.05 IFA008ed421 (Approved- IFA#227) NFVIFA(20)000845r3: ENH02.05 IFA013ed421 (Approved- IFA#227) Stage3: SOL001 NFVSOL(22)000289r2 (approved at SOL#208) SOL001 NFVSOL(22)000456 (approved at SOL#222) SOL003 NFVSOL(21)000366 (approved at SOL#174) SOL003 NFVSOL(22)000249 (approved at SOL#207) SOL005 NFVSOL(21)000588 (approved at SOL#187) SOL005 NFVSOL(22)000453 (approved at SOL#223) SOL006 NFVSOL(22)000306 (approved at SOL#210) SOL006 NFVSOL(22)000323 (approved at SOL#210) SOL016 NFVSOL(22)000379r1 (approved at SOL#218)
ENH02.06	Support for parameter mapping artifacts for MCIOP input	Release 5	Stage 2 completed Stage 3 ongoing	Arturo Martin de Nicolas <arturo.martin-de-nicolas@ericsson.com>	The enhancement adds support for artifacts in the VNF package tha perform the mapping between NFV parameters obtained from the API and input parameters to the cloud native templates (e.g. Helm charts).	Stage2: MegaCR index: NFVIFA(23)000547r1 IFA010: NFVIFA(23)000076r1 IFA011: NFVIFA(23)000515 Stage3: NFVSOL(23)000190r1