Feature Tracking Release 4
Introduction
| Current mirror date: 2024.02.14 | This page is a mirror of the Release 4 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 work of Release 4 is completed and the release has entered maintenance mode.
The Release 4 feature wiki is not further maintained.
Please refer to the latest draft of the release description NFV007:
ETSI GR NFV 007: "Network Functions Virtualisation (NFV); Release Description; Release 4".
It can be downloaded here.
Feature Overview Release 4
| Feature | Stage 1 | Stage 2 | Stage 3 (note 1) |
|---|---|---|---|
| FEAT01: NFV-MANO Upgrades | completed (Rel 4) | not started | not started |
| FEAT04: Host Reservation | n/a | completed (Rel 3) | partially completed (Rel 3)
completed (Rel 4) |
| FEAT10: Mgmt & Connectivity Multi-Site Services (MCMSS) | completed (Rel 3) | completed (Rel 3) | partially completed (Rel 3).
completed (Rel 4) |
| FEAT13: Licensing | completed (Rel 4) | completed (Rel 4) | completed (Rel 4) |
| FEAT17: Cloud-Native VNFs and Container Infrastructure management | completed (Rel 3) | ongoing (Rel 4) | ongoing (Rel 4) |
| FEAT18: Security | completed (Rel 3) | completed: architecture (Rel 3), interfaces (Rel 4). |
not started |
| FEAT19a: NFV-Connect - container networking | completed (Rel 4) | completed (Rel 4) | completed (Rel 4) |
| FEAT20: Auto | completed (Rel 4) | ongoing (Rel 4) | not started |
| FEAT21: 5GNFV | completed (Rel 4) | ongoing (Rel 4) | ongoing (Rel 4) |
| FEAT24: VNF-OAM | completed (Rel 4) | completed (Rel 4) | not started |
| FEAT25: VNF-CI | ongoing (Rel 4) | not started | not started |
| FEAT26: Policy-models | completed (Rel 4) | completed (Rel 4) | ongoing (Rel 4) |
| FEAT28: Fault management models | completed (Rel 4) | ongoing (Rel 4) | ongoing (Rel4) |
| ENH01.01: Certificate Management | completed (Rel 4) Rel 5 not started |
completed (Rel 4) | ongoing (Rel4) |
| ENH02: Special technical enhancements (Rel 4) See note 2. |
completed (Rel 4) | completed (Rel 4) | completed (Rel 4) |
| NOTE 1: Detailed changes for SOL API are described in ETSI GS NFV-SOL 002 Annex E, ETSI GS NFV-SOL 003 Annex F and ETSI GS NFV-SOL 005.
NOTE 2: Concrete enhancement features and their status is available here. | |||
- Overview of each feature: Release Document
- Snapshot of Release 4 ed441/ed451 plan: NFVSOL(22)000520r1 and NFVIFA(22)000944r1
FEAT04: Host Reservation
Overview
| Feature Prime | Gerald KUNZMANN (DOCOMO Communications Lab.) |
| Feature description | The present enhancement proposes adding the capability to the NFV-MANO architectural framework to support the reservation of compute hosts (see clause 3.1 in GS NFV-PER 001) in the NFVI. Detailed feature proposal is available in IFA_Enhancement_Host_Reservation |
| Target Release | Release 3 drop 1 (2018-05) |
| Impacted WIs | IFA005, IFA007, IFA010, IFA013 |
| MegaCRs | IFA005 MegaCR in NFVIFA(18)000420r1 (Approved MegaCR) (new text in clauses 2.2, 5.2, 5.3.X, 5.3.Y, 5.3.Z, 7.X, 7.Y, 8.X; updates clause 8.7.4) IFA007 MegaCR in NFVIFA(18)000421r1 (Approved MegaCR) (updates clauses 6.3.2 "Grant VNF Lifecycle Operation operation" and 8.3.3 "GrantInfo information element") IFA010 MegaCR in NFVIFA(18)000419r3 (Approved MegaCR) (new text in clauses 2.2, 3.1, 6.1.6, 6.X, 8.2.3, 8.X, A.2) IFA013 MegaCR in NFVIFA(18)000422r2 (Approved MegaCR) (new text in clauses 5.2, 5.X, 7.X, 8.X) |
| Related/Dependent Features | N/A |
| Status | Stage2: Completed. MegaCR Index available in NFVIFA(18)000475r1
Stage3: Completed. |
| Contributions | Stage2:
All feature contributions Stage 3: SOL003 Grant operation: NFVSOL(19)000223 SOL005 NFVI capacity: NFVSOL(19)000359r2, NFVSOL(19)000358r3, NFVSOL(19)000373r1, NFVSOL(19)000372r1 and NFVSOL(20)000276r1 SOL014 Compute Resource Reservation: NFVSOL(22)000165, NFVSOL(23)000196 and NFVSOL(23)000266 |
| Feature team | Arturo Martin De Nicolas (Ericsson LM) Bertrand Souville (DOCOMO Communications Lab.) Joan Triay (DOCOMO Communications Lab.) |
| Last Updated | 2023-01-01 |
Implementation Plan
NOTE: below contributions are marked as "OBSOLETE" as all content has been migrated to the MegaCRs (see above) and FEAT04 has been approved at IFA#101.
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Specify a requirement for the VIM to support the capability of handling reservation of resources at the host level. Specify a requirement for the NFVO to support requesting the reservation of resources at the host level. CR drafts: NFVIFA(17)0001086 (VIM) Status: Obsolete NFVIFA(18)000146 (NFVO) Status: Obsolete |
IFA010 | January-2018 | Completed |
| 002 | Specify requirements for an interface specialized on NFVI management on the Or-Vi to support the reservation of resources at the host level. CR draft NFVIFA(18)000053 Status: Obsolete |
IFA005 | January-2018 | Completed |
| 003 | Specify an interface and its operations to support the reservation of resources at the host level. CR draft NFVIFA(18)000145r2 Status: Obsolete |
IFA005 | February-2018 | Completed |
| 004 | Extend Annex A.2 to introduce physical compute host reservation. CR draft NFVIFA(18)000205 Status: Obsolete |
IFA010 | March-2018 | Completed |
| 005 | Extend clause 6.3.2 Grant VNF Lifecycle Operation operation. CR draft NFVIFA(18)000206r2 Status: Obsolete |
IFA007 | March-2018 | Completed |
| 006 | Enhancements of capacity management due to new functionality of host reservation: - Specify a requirement for the VIM to support NFVI capacity management. - Specify a requirement for the NFVO to support NFVI capacity management. CR drafts: NFVIFA(18)000207r2 (NFVO) Status: Obsolete NFVIFA(18)000208r1 (VIM) Status: Obsolete |
IFA010 | March-2018 | Completed |
| 007 | Specify an interface (IFA005, clause 7.X) and its operations to support Compute Hosts Capacity Management. CR draft NFVIFA(18)000364 Status: Obsolete |
IFA005 | March-2018 | Completed |
| 008 | A new interface and its operations may be needed in IFA013 for notifications from the NFVO related to resource capacity shortage. CR drafts: NFVIFA(18)000365r1 Status: Obsolete NFVIFA(18)000418 Status: Obsolete |
IFA013 | March-2018 | Completed |
Issues
Support host reservation when SOL014 supports reservation.-> resolved NFVSOL(22)000165Capacity mgmt of SOL014 is missing as NFVSOL(22)000521r1-> resolved NFVSOL(23)000196 and NFVSOL(23)000266
Security Considerations
List of security considerations implied by the feature.
FEAT10: Mgmt & Connectivity Multi-Site Services (MCMSS)
Overview
| Feature Prime |
Hiroshi Dempo, Zarrar Yousaf (NEC) (stage 2) |
| Feature description | Following the recommendations written in IFA022, this feature is to specify management requirements, interfaces and information models to support connectivity for Multi-Site Services |
| Target Release | Stage 2:
Release 3 drop 2 (2018-12) Release 3 (without SOL014 and SOL019) Release 4 |
| Impacted WIs | Stage 2: IFA005, IFA007, IFA010, IFA011, IFA013, IFA014, IFA022, IFA032 Stage 3: SOL014, SOL003, SOL005, SOL001, SOL006, SOL017, SOL019 |
| Mega-CRs | Stage 2:MegaCR Index available in NFVIFA(18)0001117r3 - IFA005 MegaCR in NFVIFA(18)0001111r2 - IFA007 MegaCR in NFVIFA(18)0001112r4 - IFA010 MegaCR in NFVIFA(18)0001107r2 - IFA013 MegaCR in NFVIFA(18)0001110r4 - IFA014 MegaCR in NFVIFA(18)0001113r2 |
| Related/Dependent Features | N/A |
| New Specification | Stage 2: IFA032 Stage 3: SOL017, SOL019 (stop) |
| Status | Stage 2: Completed, Stage 3: complated release 3(SOL001, SOL003, SOL005, SOL006, SOL009, SOL017) ongoing release 4 (SOL014 stop SOL019 |
| Contributions | Stage2:
All feature contributions Stage3: SOL001 NFVSOL(19)000792r1 SOL003 NFVSOL(19)000732 and NFVSOL(21)000363 SOL005 NFVSOL(19)000734, NFVSOL(20)000080, NFVSOL(20)000081, NFVSOL(20)000082r2, NFVSOL(20)000235r1, NFVSOL(20)000252 and NFVSOL(19)000817 SOL006 NFVSOL(20)000115 SOL009 NFVSOL(21)000153 SOL014 (ongoing) new report SOL017 (completed) new specifcation SOL019 (ongoing) |
| Feature team | Stage 2: - Hiroshi Dempo (NEC Europe Ltd.) - Zarrar Yousaf (NEC Europe Ltd.) - Lei Zhu (Huawei Tech (UK) Co., Ltd. - Ulrich Kleber (Huawei Tech (UK) Co., Ltd. - Marc Flauw (HPE) - Joan Triay (DOCOMO) Stage 3: - Zarrar Yousaf (NEC Europe Ltd.) - Joan Triay (DOCOMO) |
| 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.
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | - Approve FEAT10 and new WI draft titled “Reference point between NFVO and WIM- Interface and Information Model Specification" | None | Oct-2017 | Done |
| 002 |
- Approve IFA022 as a stable draft
|
IFA022 | Dec-2017 | Done |
| 003 |
- Specify general and functional recommendations for Multi-Site Service
|
IFA010 | Jan/ 2018 | Completed |
| 004 |
- Specify Os-Ma-Nfvo reference point interface and information model specification for Multi-Site Service
|
IFA013 | Mar-2018 | Completed |
| 005 |
- Specify Or-Vi reference point interfaces and information model specification between NFVO and VIM for Multi-Site Service
|
IFA005 | Mar-2018 | Completed |
| 006 |
- Specify enhancements to Or-Vnfm ref. point interfaces and information model to address the case of VNF multi-site deployment. - Make relevant changes to the scope and overview sections to include the support for Multi-site Service on Or-Vnfm reference point
|
IFA007 | Mar-2018 | Completed |
| 007 | - Specify parameters for the VNFD file relevant for the support of Multi-Site Service
" No CRs received" |
IFA011 | May-2018 | Closed |
| 008 | - Specify parameters for the NSD file relevant for the support of Multi-Site Service
|
IFA014 | May-2018 | Completed |
| 009 |
- Specify Or-Vi reference point interfaces and information model specification between NFVO and WIM for Multi-Site Service
NOTE: As written in ID#2, naming of the ref. point is FFS. Purpose of the specification is to focus on virtualised network resource management subset of existing IFA005, and necessary extensions/enhancements particular to managing resources in the WAN |
IFA032 | May-2018 | Completed |
Issues
List of issues raised based on the feature implementation.
- All topics can start from the beginning but the progress needs to be managed on the action IDs (e.g. individual mega CRs and new deliverable basis)
- The target dates are set according to the requirement categories in IFA022 (CRs for general, functional, reference point and information element, descriptor, or new deliverable)
- Discussion for IFA032 may take more time than CRs but finalise before the 1st drop of Release 3.
Security Considerations
List of security considerations implied by the feature.
Stage 3 Implementation Plan
| ID | Action | Impacted WI(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Specification of multi-site connectivity support in SOL003: - Add specification for Multi-Site Connectivity Services: NFVSOL(19)000732. Status: approved - Bug fix: NFVSOL(21)000363. Status: approved at SOL#174 |
SOL003 | Dec. 2019 | Completed |
| 002 | Specification of multi-site connectivity support in SOL005: - Add specification for Multi-Site Connectivity Services: NFVSOL(19)000734, NFVSOL(20)000080, NFVSOL(20)000081. Status: approved at SOL#128 - Add Annex of multi-site connectivity: NFVSOL(20)000082r2, - Resolve EN: NFVSOL(20)000235r1, NFVSOL(20)000252, NFVSOL(19)000817 Status: approved |
SOL005 | Dec. 2019 | Completed |
| 003 | Specification of multi-site connectivity support in SOL descriptors: - SOL001ed331 FEAT10 Add specification for Multi-Site Connectivity Services: NFVSOL(19)000792r1. Status: approved at SOL#121 - SOL006ed331 FEAT10 Add specification for Multi-Site Connectivity Services: NFVSOL(20)000115. Status: approved at SOL#128 |
SOL001, SOL006 | Dec. 2019 | Completed |
| 004 | Specification of multi-site connectivity support in SOL014: - TBD |
SOL014 | TBD | Not started |
| 005 | Report and profiling of stage 3 solutions addressing IFA032 requirements. General structure of the report: - SOL017 skeleton: NFVSOL(19)000360r1. Status: approved at SOL#102. - SOL017 scope: NFVSOL(19)000361r1. Status: approved at SOL#102. - IFA032 Overview Clause 4.2: NFVSOL(19)000548r1. Status: approved at SOL#111 EA. - IFA032 Overview for Capacity, Performance and Fault Management interfaces for Clause 4.2: NFVSOL(19)000592. Status: approved at SOL#115. |
SOL017 | Dec. 2019 | Completed |
| 006 | Profiling of IETF ACTN stage 3 solutions addressing IFA032 requirements: - IETF ACTN Overview: NFVSOL(19)000506r3. Status: approved at SOL#115. - Clause 4.3.2.3 Mapping concepts with ACTN: NFVSOL(19)000573. Status: approved at SOL#115. - IETF ACTN profiling: NFVSOL(20)000501r5, NFVSOL(20)000464r7, NFVSOL(20)000535r6, NFVSOL(20)000629r1, NFVSOL(20)000632r1, NFVSOL(20)000634r1, NFVSOL(20)000633r2, NFVSOL(20)000654r1, NFVSOL(20)000656r1, NFVSOL(20)000666r2, NFVSOL(20)000657r1, NFVSOL(20)000658r2 Status: approved - IETF ACTN Analysis: - IETF ACTN Architecture: - IETF ACTN Annex: NFVSOL(20)000655, NFVSOL(21)000024 - IETF ACTN Recommendation: NFVSOL(20)000771r1 - Resolve EN and others: NFVSOL(20)000668, NFVSOL(20)000669, NFVSOL(21)000023, NFVSOL(21)000016r1, NFVSOL(21)000017r1 |
SOL017 | Feb. 2020 | Completed |
| 007 | Profiling of TAPI stage 3 solutions addressing IFA032 requirements: - TAPI Overview: NFVSOL(19)000605r2. Status: approved at SOL#115. - TAPI Analysis: NFVSOL(20)000321r3, NFVSOL(20)000325r1, NFVSOL(20)000572, NFVSOL(20)000672r1, NFVSOL(20)000683, NFVSOL(20)000677, NFVSOL(20)000589r1 |
SOL017 | Feb. 2020 | Completed |
| 008 | Stage3 of Profiling specification of solutions for Multi-site Connectivity Services based on Abstraction and Control of TE Networks (ACTN)
- Skeleton: NFVSOL(21)000651r3 Status: approved - next steps: NFVSOL(22)000369 Noted |
SOL019 | STOP | |
| 009 | Specification of WIM support in SOL009:
- NFVSOL(21)000153: Approved |
SOL009 | Completed |
FEAT13: Report on Architectural enhancement for VNF License Management support and use of VNF licenses
Overview
| Feature Prime | Abinash Vishwakarma, Netcracker |
| Feature description | IFA034 work will perform impact analysis of VNF Licenses on the NFV-MANO. The output of this work will be used to create CRs on the NFV-MANO.
Initial study of License Management was done by EVE010, the output of EVE010 will be used as baseline for this IFA034. |
| Target release | Release 3 drop 3 |
| Impacted WIs | Stage2: IFA011
Stage3: SOL004 |
| MegaCRs | N/A (only 1 CR for IFA011) |
| Related/Dependent Features | NA |
| Status | Stage2: completed
Stage3: completed |
| Contributions | Stage2
IFA011 NFVIFA(22)000534r3 Stage3 SOL004 NFVSOL(22)000359r4 |
| Feature team | Abinash Vishwakarma (Netcracker)
Janusz, Pieczerak, Orange Etienne, Steinert, Orange Oliver, Le Grand, Orange Anne-Marie Praden, Gemalto Martin, Liepert, Gemalto |
| Last update | 2023-01-01 |
FEAT16: Service Availability Level
Overview
| Feature Prime | Stefan Arntzen (Huawei) |
| Feature description | This feature adds the functions needed to assign resources with defined reliability characteristics to NSs with special reliability requirements. It also allows to achieve an optimized assignment of resources with defined availability characteristics to multiple VNFs and NSs (belonging to the same slice) |
| Target Release | Stage 2: Release 3 drop 3 (2019-06)
Stage 3: Release 3 (2019-12) |
| Impacted WIs | Stage 2: IFA010, IFA014
Stage 3: SOL001, SOL006 |
| MegaCRs | Stage 2:MegaCR Index available in NFVIFA(19)000746
IFA010: NFVIFA(19)000480r8 Approved by email on July 15
|
| Related/Dependent Features | N/A |
| Status | Stage 2: Completed
Stage 3: Completed |
| Contributions | Stage2
All feature contributions Stage3 SOL001 NFVSOL(20)000067r1 SOL006 NFVSOL(20)000026r2 |
| Feature team | Shaoji Ni (Huawei) Maria Toeroe(Ericsson) Gerald Kunzmann (DOCOMO) Stefan Arntzen (Huawei) Janusz Pieczerak (Orange) Chidung Lac (Orange) |
| Last Updated | 2023-01-01 |
Stage 2 Implementation Plan
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Add terminology of the “service availability level (SAL)” and explain difference between FEAT05 Slicing
NFVIFA(19)000402r3 Status: Agreed FEAT (IFA#159) |
IFA010 | June-2019 | Completed |
| 002 | Specify requirements for the VIM to support the capability for supporting SAL for the assignment/reservation of resources. Specify requirements for the NFVO/VNFM to support SAL for requesting the assignment/reservation of resources.
NFVIFA(19)000296r1 Status: Noted (IFA#145) NFVIFA(19)000306r5 Status: Agreed FEAT (IFA#150) NFVIFA(19)000307r7 Status: Agreed FEAT (IFA#149) NFVIFA(19)000309r2 Status: Agreed FEAT (IFA#148) NFVIFA(19)000310r5 Status: Agreed FEAT (IFA#148) NFVIFA(19)000311r2 Status: Agreed FEAT (IFA#148) NFVIFA(19)000482r1 Status: Agreed FEAT (IFA#154)
NFVIFA(19)000502r9 Status: Agreed FEAT (IFA#156) NFVIFA(19)000590r4 Status: Agreed FEAT (IFA#157) |
IFA010 | June-2019 | Completed |
| 003 | Specify requirements for an NFVI resource management on the Or-Vi/Vi-Vnfm to support SAL for the assignment/reservation of resources. | IFA005/006 | December-2018 | Stopped. Not part of release 3 |
| 004 | Add the parameter of SAL into “VnfDF”, “vdu profile”, “VirtualLinkDescFlavour” of VNFD
|
IFA011 | December-2018 | Stopped |
| 005 | Add a requirement and the parameter of SAL into “Network service deployment flavour” of NSD
NFVIFA(19)000355r4 Status: Agreed FEAT (IFA#152) NFVIFA(19)000397r2 Status: Agreed FEAT (IFA#152) NFVIFA(19)000547r5 Status: Agreed FEAT (IFA#155) |
IFA014 | June-2019 | Completed |
| 006 | Specify operations of the assignment/reservation of resources in Or-Vi/Vi-Vnfm/Or-Vnfm/Ve-Vnfm interfaces to support SAL by adding the parameter of “SAL” into the Virtual resource assignment/reservation requests
NFVIFA(19)000399r3 Status: Agreed FEAT (IFA#152) NFVIFA(19)000408r2 Status: Agreed FEAT (IFA#152) NFVIFA(19)000417r6 Status: Agreed FEAT (IFA#152) NFVIFA(19)000419r4 Status: Agreed FEAT (IFA#152) NFVIFA(19)000472 Status: Agreed FEAT (IFA#155) NFVIFA(19)000474 Status: Agreed FEAT (IFA#155) NFVIFA(19)000467r1 Status: Agreed FEAT (IFA#154) NFVIFA(19)000466r4 Status: Agreed FEAT (IFA#155) NFVIFA(19)000473r2 Status: Agreed FEAT (IFA#155) |
IFA005/006/007/008 | February-2019 | Stopped. Not part of release 3 |
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 SAL(service_availability_level) in to NSD.
- NFVSOL(20)000067r1: Approved |
SOL001 | March-2018 | Completed |
| 002 | Add SAL(service_availability_level) in to NSD.
- NFVSOL(20)000026r2: Approved |
SOL006 | Completed |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature are described in: NFVSEC(19)000085r1 Status: agreed in SEC#151
FEAT17: Cloud-Native VNFs and Container Infrastructure management
Overview
| Feature Prime | Jörg Aelken (Ericsson LM) Ulrich Kleber (Huawei Technologies Co.,Ltd) |
| Feature description | The scope of the feature covers the following areas: - NFV Architecture support for VNFs which follow “cloud-native” design principles. |
| Target Release | Stage 2
Stage 3
|
| Impacted WIs | Stage 2: IFA007, IFA008, IFA010, IFA011, IFA013, IFA014, IFA036, IFA040, IFA052 Stage 3: SOL001, SOL002, SOL003, SOL006, SOL018, SOL020 |
| MegaCRs | Stage 2
|
| Related/Dependent Features | FEAT19 – NFV-Conn FEAT23 – MANO-SBA |
| New Specification | Stage 2
Stage 3
|
| Status |
Stage 2
Stage 3
|
| Contributions | Stage 2:
All stage 2 feature contributions Stage 3: Step 1 introduce CISM/CIR and OsContainer SOL018 contributions, SOL001ed421 and SOL001ed431, SOL002ed431, SOL003ed431, SOL005ed431, SOL006ed431, SOL009ed431 SOL020 |
| Feature team | Stage 2: Ulrich Kleber (Huawei Technologies Co.,Ltd) Jörg Aelken (Ericsson LM) Stage 3: Jörg Aelken (Ericsson LM) |
| 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.
Stage 2 - Step 1 (ed411)
| ID | Action | Impacted WI(s) | Target completion | Status |
|---|---|---|---|---|
| ST2-001 | Skeleton, scope, and term definitions for IFA040 (Clauses 1, 2, 3)
CR drafts: |
IFA040 | October - 2019 | Complete |
| ST2-002 | Overview and framework for OS container management and orchestration (Clause 4)
CR drafts: |
IFA040 | November - 2019 | Complete |
| ST2-003 | Skeleton and scope for IFA036 (Clause 1)
CR drafts: |
IFA036 | October - 2019 | Complete |
| ST2-004 | Enhance the VNFD and its VDU information element with attributes/information elements for the OS container resource model
CR drafts: |
IFA011ed411 | February - 2020 | Complete |
| ST2-005 | OS container NFV object model (Clause 5)
CR drafts: |
IFA040 | November - 2019 | Complete |
| ST2-007 | Specify the functional requirements for the CISM function
CR drafts: |
IFA010ed411 | January - 2020 | Complete |
| ST2-008 | Specify the functional requirements for the CIR function
CR drafts: |
IFA010ed411 | February - 2020 | Complete |
| ST2-009 | General CISM service requirements (Clauses 6.1, 6.2)
CR drafts: |
IFA040 | January - 2020 | Complete |
| ST2-010 | OS container management service interface requirements (Clauses 6.3, 6.4, 6.5, 6.6, 6.7)
CR drafts: |
IFA040 | January - 2020 | Complete |
| ST2-011 | General CIR service requirements (Clauses 7.1, 7.2)
CR drafts: |
IFA040 | December - 2019 | Complete |
| ST2-012 | OS container image management service interface requirements (Clause 7.3)
CR drafts: |
IFA040 | January - 2020 | Complete |
| ST2-013 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CISM function
CR drafts: |
IFA010ed411 | March - 2020 | Complete |
| ST2-014 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CIR function
CR drafts: |
IFA010ed411 | March - 2020 | Complete |
| ST2-015 | Extend the VNFM functional requirements for consuming the management service interfaces exposed by the CISM function
CR drafts: |
IFA010ed411 | March - 2020 | Complete |
Stage 2 - Step 2 (ed421)
| ID | Action | Impacted WI(s) | Target completion | Status |
|---|---|---|---|---|
| ST2-016 | Enhance the information models of the Or-Vnfm interfaces for OS container management and orchestration
CR drafts: |
IFA007ed421 | March - 2021 | Complete |
| ST2-017 | Enhance the information models of the Ve-Vnfm interfaces for OS container management and orchestration
CR drafts: |
IFA008ed421 | March - 2021 | Complete |
| ST2-018 | Extend the NFVO, VNFM, CISM functional requirements according to additional enhancements identified for FEAT17
CR drafts: |
IFA010ed421 | March - 2021 | Complete |
| ST2-019 | Extend the VNFD information model according to additional enhancements identified for FEAT17
CR drafts: |
IFA011ed421 | March - 2021 | Complete |
| ST2-020 | Enhance the information models of the Os-Ma-nfvo interfaces for OS container management and orchestration
CR drafts: |
IFA013ed421 | March - 2021 | Complete |
| ST2-021 | Enhance the information models of the NSD for OS container management and orchestration
CR drafts: |
IFA014ed421 | March - 2021 | Complete |
| ST2-022 | Extend the abstract NFV object model description and CISM/CIR service interface requirements according to additional enhancements identified for FEAT17
CR drafts: |
IFA040ed421 | March - 2021 | Complete |
Stage 2 - Step 3 (ed431)
| ID | Action | Impacted WI(s) | Target completion | Status |
|---|---|---|---|---|
| ST2-006 | Terminology and overview of management and orchestration of CIS cluster nodes (Clauses 3 and 4, Annex)
Concept discussions: CR drafts: |
IFA036 | June - 2022 | Completed |
| ST2-023 | Container cluster nodes management interface requirements (Clause 5)
CR drafts: |
IFA036 | June - 2022 | Completed |
| ST2-024 | CIS Cluster NFV object model (Clause 6)
CR drafts: |
IFA036 | June - 2022 | Completed |
| ST2-025 | CIS Cluster Node NFV object model (Clause 7)
CR drafts: |
IFA036 | June - 2022 | Completed |
| ST2-026 | Analyse and if necessary enhance VNFD and its VDU information element with attributes/information elements related to cluster and node affinity No enhancements required from CCM |
IFA011ed431 | March - 2022 | Completed |
| ST2-027 | Analyse and if necessary enhance NSD and constituent information elements with attributes/information elements related to cluster and node affinity No enhancements required from CCM |
IFA014ed431 | March - 2022 | Completed |
| ST2-028 | Specify the functional requirements for the CCM function
CR drafts: |
IFA010ed431 | March - 2022 | Completed |
| ST2-029 | Add requirements on CIS cluster node management for the CISM function
CR drafts: |
IFA010ed431 | March - 2022 | Completed |
| ST2-030 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CCM function CR drafts: |
IFA010ed431 | March - 2022 | Moved to step 4 |
| ST2-031 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CISM function related to CIS Cluster Node management CR drafts: |
IFA010ed431 | March - 2022 | Moved to step 4 |
| ST2-032 | Analyse and if necessary enhance the information models of the Os-Ma-nfvo interfaces for CIS Cluster management and CIS Cluster Node management CR drafts: |
IFA013ed431 | March - 2022 | Moved to step 4 |
| ST2-033 | Additional interface enhancements in step 3
CR drafts: NFVIFA(22)000127 (Agreed FEAT, IFA007) NFVIFA(22)000153 (Agreed FEAT, IFA007) NFVIFA(22)000155 (Agreed FEAT, IFA008) |
IFA007ed431, IFA008ed431, IFA011ed431, IFA013ed431 |
March - 2022 | Completed |
| ST2-034 | Workgroup review
CR drafts: |
IFA036 | July - 2022 | Completed |
Stage 2 - Step 4 (ed441)
| ID | Action | Impacted WI(s) | Target completion | Status |
|---|---|---|---|---|
| ST2-030 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CCM function CR drafts: |
IFA010ed441 | March - 2023 | Not started
(move to step 5) |
| ST2-031 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CISM function related to CIS Cluster Node management CR drafts: |
IFA010ed441 | March - 2023 | Not started
(move to step 5) |
| ST2-032 | Analyse and if necessary enhance the information models of the Os-Ma-nfvo interfaces for CIS Cluster management and CIS Cluster Node management CR drafts: |
IFA013ed441 | March - 2023 | Not started
(move to step 5) |
| ST2-035 | Provide additional workflows and examples
CR drafts: NFVIFA(22)000854r1 (Approved) NFVIFA(22)000949r3 (Approved) NFVIFA(22)000976r1 (Approved) NFVIFA(23)000002r1 (Approved) |
IFA036ed441 | March - 2023 | Completed |
| ST2-036 | Provide more details for some concepts in CCM, e.g. shared storage, clusters with multiple NFVI-Pops, clusters and
multiple domains, cluster-related measurements, etc. CR drafts: |
IFA036ed441,
IFA030ed441, IFA032ed441, IFA027ed441 |
Not started
(move to step 5) | |
| ST2-037 | Reliability considerations for CCM | IFA036ed441 | Not started
(move to step 5) | |
| ST2-038 | Security considerations for CCM | IFA036ed441 | Not started
(move to step 5) | |
| ST2-039 | Describe management of CCM
CR drafts: NFVIFA(23)000011 (IFA010, Approved) NFVIFA(23)000012 (IFA031, Approved) NFVIFA(23)000013 (IFA031, Approved) |
IFA010ed441
IFA031ed441 |
March - 2023 | Completed |
| ST2-040 | Additional enhancements in step 4
CR drafts: |
IFA011ed441 | March - 2023 | Completed |
Stage 2 - Step 5 (ed451)
| ID | Action | Impacted WI(s) | Target completion | Status |
|---|---|---|---|---|
| ST2-030 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CCM function CR drafts: |
IFA010 | Not started | |
| ST2-031 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CISM function related to CIS Cluster Node management CR drafts: |
IFA010 | Not started | |
| ST2-032 | Analyse and if necessary enhance the information models of the Os-Ma-nfvo interfaces for CIS Cluster management and CIS Cluster Node management CR drafts: |
IFA013 | Not started | |
| ST2-036 | Provide more details for some concepts in CCM, e.g. shared storage, clusters with multiple NFVI-Pops, clusters and
multiple domains, cluster-related measurements, etc. CR drafts: |
IFA036,
IFA030, IFA032, IFA027 |
Not started | |
| ST2-037 | Reliability considerations for CCM | IFA036 | Not started | |
| ST2-038 | Security considerations for CCM | IFA036 | Not started | |
| ST2-041 | CCM southbound interface | IFA052 | Ongoing |
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 Stage3 Step1
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| ST3-001 | introduce OsContainer
- NFVSOL(21)000011r8 - NFVSOL(21)000018r6 - NFVSOL(21)000020r2 - NFVSOL(21)000223 - NFVSOL(21)000246r1 - NFVSOL(21)000374 - NFVSOL(21)000252r3 - NFVSOL(21)000436r2 - NFVSOL(21)000481r1 - NFVSOL(21)000097r9 - NFVSOL(21)000440r2 - NFVSOL(21)000622r1 introduce MCIOP - NFVSOL(21)000064r5 - NFVSOL(21)000246r1 - NFVSOL(21)000480 - NFVSOL(21)000487 - NFVSOL(21)000491r1 - NFVSOL(21)000617r1 - NFVSOL(21)000152r5 introduce MCIO - NFVSOL(21)000451r1 - NFVSOL(22)000096r1 - NFVSOL(22)000112r1 enhance container network - NFVSOL(21)000019r4 - NFVSOL(21)000021r4 - NFVSOL(21)000238r2 |
SOL001 | January-2022 | Completed |
| ST3-002 | extends Grant and introduce CISM/CIR | SOL003 | July-2022 | Completed |
| ST3-003 | introduces MCIO
enhance CP for container network |
SOL003 | July-2022 | Completed |
| ST3-004 | introduces MCIO
- NFVSOL(22)000089 (684r1 mirror) - NFVSOL(22)000120r1 (053r4 mirror) enhance CP for container network - NFVSOL(22)000177 (482 mirror) - NFVSOL(22)000052 (040 mirror) - NFVSOL(22)000107 (092 mirror) - NFVSOL(22)000171r1 (139r2 mirror) - NFVSOL(22)000501r1 (500r1 mirror) |
SOL002 | July-2022 | Completed |
| ST3-005 | introduce CISM/CIR
- NFVSOL(22)000037r1 (367r2 mirror) introduces MCIO - NFVSOL(22)000073 (684r1 mirror) - NFVSOL(22)000121r1 (053r4 mirror) enhance CP for container network - NFVSOL(22)000154r4 (482 mirror) - NFVSOL(22)000122 (040 and 092 mirror) - NFVSOL(22)000172 (139r2 mirror) - NFVSOL(22)000514r1 (500r1 mirror) |
SOL005 | July-2022 | Completed |
| ST3-006 | DP: prestudy of stage3
DP: CISM API object map |
SOL018 | July-2022 | Completed |
| ST3-007 | introduce CISM | SOL009 | July-2022 | Completed |
| ST3-008 | introduce OsContainer
introduce MCIOP introduce MCIO |
SOL006 | Completed | |
| ST3-009 | - NFVSOL(23)000318: on-boarding
- NFVSOL(23)000285r3: NS instantiation - NFVSOL(23)000297r1: NS termination - NFVSOL(23)000317: VNF Scaling - NFVSOL(23)000073r3: Change external VNF connectivity |
SOL016 | January-2023 | Completed |
SOL Stage3 Step2
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| ST3-010 | introduce CCM | SOL020 | ongoing |
Issues
Feature implementation approach
This feature implementation plan proposes to implement the feature according to its scope from the latest NFV Release-4 “Strawman of Release 4 definition”.
Due to the complexity of the feature and its implementation, the feature will be implemented in a stepwise approach. The feature steps are bundling dependent solutions in different work items/specifications. The solutions for one feature step impacting existing specifications will be delivered by Mega-CR’s. There will be one Mega-CR per impacted specification per feature step and all Mega-CR’s for one feature step will be delivered together with dependent new specifications.
The current plan bundles the following solutions together:
- Stage 2 - Step 1: IFA040 and related Rel-4 Mega-CRs on existing specifications
- Stage 2 - Step 2: IFA036 and related Rel-4 Mega-CRs on existing specifications
Background Information
This feature was originally planned as ETSI NFV Release-3 delivery.
According to its definition, the ETSI NFV Release 3 includes objectives:
- To specify requirements and enhancements to NFV Architectural Framework to support PaaS features.
- To specify non-functional parameters to classify and characterize VNF cloud-native implementations.
They are reflected in the following two features and corresponding work items:
| Feature ID | Title | Work Item |
|---|---|---|
| R03.F19 | NFV Architecture PaaS (NFVPAAS) | IFA029 |
| R03.F20 | Cloud-Native VNF (VNFCLOUD) | EVE011 |
During the work on the two work items it was discovered that both features are very much related and the envisioned solutions and implementations might overlap and will target the same impacted work items.
During discussions in IFA#73 it was further identified that EVE011, even though it is normative, should be considered as stage 1 requirements on cloud-native on a high abstraction level without taking the actual implementation into consideration. It was further identified in this meeting that IFA029 as a GR looks at architectural aspects of both Cloud Native and PaaS.
Meanwhile, both work items, EVE011 and IFA029, have been concluded and approved by the ISG NFV plenary as NFV Release-3 deliveries. It was further decided by the ISG NFV plenary to carry over the normative specifications for stage 2 and 3 of this feature with a modified scope according to the “Strawman of Release 4 definition” into NFV Release-4.
Security Considerations
The work item DGS/NFV-SEC023 “Network Functions Virtualisation (NFV) Release 4; Security; Container Security Specification” was approved by the ISG NFV to investigate the security considerations for OS container technologies and provide a respective specification.
It is expected that applicable container security aspects will be handled by this work item.
FEAT18: Security
Overview
| Feature Prime | Mark Shepherd (Tencastle) |
| Feature description | To address security challenges arising in NFV, particularly in terms of isolation of sensitive functions and security management and monitoring |
| Target Release | Release 3 drop X (2019-06-30) |
| Impacted WIs | Stage 1: SEC009, SEC011, SEC012, SEC013
Stage 2: IFA026, IFA033, Future work items: consider whether SOL or TST items would be appropriate. |
| MegaCRs | tbd |
| Related/Dependent Features | Enh01.01 Certficate Management |
| Status | Ongoing (25% complete) |
| Contributions | All feature contributions Agreed content (direct links to search-URLs to be added later) |
| Feature team | Alex Leadbeater (Rapporteur), BT
Leslie Willis (Rapporteur), BT Mark Shepherd, Tencastle |
| Last Updated | 2023-01-01 |
Implementation Plan
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Complete requirements in IFA026 | IFA026 | November 2018 | Open |
| 002 | Map requirements from IFA026 into IFA033 and assign to each interface | IFA026
IFA033 |
November 2018 | Open |
| 003 | Complete all of IFA026 and identify all interfaces in IFA033 | IFA026
IFA033 |
December 2018 | Open |
| 004 | introduce ADMF
introduce NFV SC |
IFA010 | Not started | |
| 005 | new interface for NFV SC
new interface for LI controller and SM |
IFA033 | Not started | |
| 006 | Add ADMF and NFV SC
Add interface for NFV SC, LI controller and SM |
NFV006 | Not started | |
| 007 | IFA008 | Not started | ||
| 008 | IFA013 | Not started |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
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:
The scope of IFA043 (Release 5) covers the following areas:
|
| 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 : | ||||
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 | 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 (70%) 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 | 2023-09-22 |
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 |
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). | NFV003 | Jun-2023 | Not started |
| 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). | IFA011 | Jun-2023 | Not started |
| 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: available |
IFA049 | Jan-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: available |
IFA049 | Jan-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 WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Add version dependancy to VNFD and NSD
- NFVSOL(22)000189: Approved - NFVSOL(22)000225: Approved |
SOL001 | 2022-April | Completed |
| 002 | Add version dependancy to VNFD and NSD
- NFVSOL(22)000305: Approved |
SOL006 | 2022-April | Completed |
| 003 | Add version dependency to VNF LCM and NS LCM | SO005 | 2022-April | Completed |
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 and define the type of OAM functions for VNFs that can be generalized and be provided as a “generic function” supporting the provisioning, connectivity, configuration and monitoring of VNFs on a virtualized platform. The feature will also determine possible solutions to realize such generic OAM functions, e.g., by leveraging PaaS capabilities. The result report will include, if necessary, recommendations for requirements and architectural enhancements. |
| Target Release | Stage 2: Release 4 (July 2023)
Stage 3: Release 4 (2024-X-X) |
| Impacted WIs | Stage 2: none
Stage 3: none |
| MegaCRs | Stage 2:
Stage 3: none |
| Related/Dependent Features | FEAT17: cloud-native VNF and NFV architecture PaaS
FEAT21: 5GNFV |
| New Specifcations | Stage 2: IFA049
Stage 3: Not started |
| Status | Stage 2: 100% completed
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 | Skeleton, scope, and term definitions (Clauses 1, 2, 3)
CR drafts: |
IFA049 | Completed | |
| 002 | Overview and framework for Generic OAM functions (Clause 4)
Approved CRs: |
IFA049 | Completed | |
| 003 | Specify the functional requirements for Generic OAM functions (Clause 5)
Approved CRs: |
IFA049 | Completed | |
| 004 | Specify the interface requirements for Generic OAM functions (Clause 6) and information elements (Clause 7)
Approved CRs: |
IFA049 | Completed | |
| 006 | Specify service interaction with VNF (Clause 8)
Approved CRs: NFVIFA(22)000872r1NFVIFA(22)000756r2 |
IFA049 | December-2022 | Completed |
| 007 | Specify Descriptors for Generic OAM functions (Clause 9)
Approved CRs: NFVIFA(23)000175r1NFVIFA(23)000195r1NFVIFA(23)000175NFVIFA(22)000938r3 |
IFA049 | December-2022 | Completed |
| 008 | Editorial cleanup
NFVIFA(23)000486r1 NFVIFA(23)000476r1 NFVIFA(23)000475r1 NFVIFA(23)000331r1 NFVIFA(23)000305r1 NFVIFA(23)000189r1 NFVIFA(23)000188 NFVIFA(23)000182 NFVIFA(23)000138r1 |
IFA049 | March-2020 | Completed |
SOL
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | tbd | SOL | xxx | 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.
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
|
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 | IFA048 | Done | |
| 007 | General
Example of policy model Review |
IFA048 | Done | |
| 008 | Policy management alignment with IFA048 | 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.
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: Release 4 drop ed461 (Mar 2024) |
| Impacted WIs | Stage 2: IFA005, IFA006, IFA007, IFA008, IFA013, IFA036, IFA040
Stage 3: SOL002, SOL003, SOL005, SOL018, SOL014 |
| MegaCRs | Stage 2: None
Stage 3: None |
| Related/Dependent Features | FEAT24 on "Generic VNF OAM" |
| New Specifcations | Stage 2: ETSI GS NFV-IFA 045
Stage 3: None |
| Status | Stage 2: IFA045 completed, IFA CRs ongoing (total 90%)
Stage 3: ongoing |
| 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-11-08 |
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: - NFVIFA(23)000686r1 IFA007ed461 FEAT28 add reference to IFA045: approved in IFA#355 - NFVIFA(23)000687r1 IFA008ed461 FEAT28 add reference to IFA045: approved in IFA#355 - NFVIFA(23)000688r1 IFA013ed461 FEAT28 add reference to IFA045: approved in IFA#355 - NFVIFA(23)000710 IFA005ed461 FEAT28 add reference to IFA045 - NFVIFA(23)000711 IFA006ed461 FEAT28 add reference to IFA045 - NFVIFA(23)000712 IFA032ed461 FEAT28 add reference to IFA045 - NFVIFA(23)000713 IFA036ed461 FEAT28 add reference to IFA045 |
IFA | Dec-2023 | On going |
| 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
SOL
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Add reference from Alarms to IFA045
- NFVSOL(23)000350r2 SOL003ed461 FEAT28 add reference to IFA045: approved in SOL#265 - NFVSOL(23)000351r1 SOL002ed461 FEAT28 add reference to IFA045: approved in SOL#265 - NFVSOL(23)000352r1 SOL005ed461 FEAT28 add reference to IFA045: approved in SOL#265 |
SOL002
SOL003 SOL005 SOL014 SOL020 |
Mar-2024 | ongoing |
Issues
- IFA040ed451 does not have FM service interface that refers to IFA045.
Security Considerations
List of security considerations implied by the feature.
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.
Resolve open comments on the contribution in IFA;IFA almost feature agrees (first step) the contribution;Seek feedback from SEC;After resolving open comments on the contribution in SEC, SEC endorse the contribution and back to step 1.IFA feature agrees (second step) the contribution with confirmation from SEC.
- 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
- SEC agrees individual CRs.
- IFA agrees bulk CRs with new draft baseline for 1 week.
- (Option) If IFA comments technical change, SEC/IFA agrees by email for 3days.
- Upload new draft
- Existing IFA spec (IFA responsibility)
- IFA006/007/008/011/013/040
- (Potential) IFA014
- IFA agree individual CRs
- SEC agree same CRs
- (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 |
| |
| 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:index
New interface |
Enh01.01: Certificate Management
- Information about the planned schedule and potential specification impacts is available in contribution NFVIFA(21)000843r2/NFVSEC(21)000071r2：Enhancement Proposal on Certificate Management Security Enhancement
- Noted in IFA#258
- Discussion paper of direction for Stage 2 in IFA & SEC joint session NFVIFA(21)001053r1/NFVSEC(21)000094r6: Enh01.01 DP for IFA and SEC joint session
- IFA#264 check open issues -> SEC review -> IFA#274 Noted - agreed Suggestion#1 (NFV specifies both option) and Suggestion#2(registration usecase is starting points)
- Discussion paper for the stage2 level working specs on Certificate Management: NFVSEC(22)000024: Enh01.01 DP for proposing to work on IFA026/IFA033 as for SEC related architecture and RPs/IFs
- SEC#207 - agreed to work on IFA026/IFA033 for Certificate Management
- SEC#207 - noted clear separation between SM and Certificate Management needed.
- asuumed that the contirbutions on IFA026/033 worked in SEC WG first
- Discussion paper NFVSEC(22)000032r2: "Enh01.01 Discussion on Certificate Management IFA specs impacts and work plan"
- Enh01.01 DP for identifying the impacted specs and work role/step between IFA and SEC in IFA/SEC joint session on NFV#38 (SEC#210/IFA#287).
- Endorsed on
- SEC works, will be sent to IFA for approval
- IFA026 on Basic use case / Basic concept and architectural aspects including IFA010 existing featagreedCRs
- IFA033
- update SEC021/022/023/025, if necessary
- IFA works, will be back to SEC for endorsement
- IFA006/008
- (Potential) IFA013/007/011/014
- SEC works, will be sent to IFA for approval
- Discussion paper NFVSEC(22)000059r5: "Enh01.01 Supporting material for Use Cases "
- NFV#39/SEC#215- DP Noted
- Agreed to remove "proxy mode" for VNF OAM certificate an VNFCI certificate due to lack of support.
- Agreed on the keys (public and private keys) generation process for both NFV-MANO cert at NFV-MANO entities and VNF OMA cert/VNFCI cert at VNFM, included as part of CSR process, and done at each of NFV-MANO entities for NFV-MANO certificate, done at VNFM for VNF OAM certificate/VNFCI certificate.
- Agreed on that the registration of NFV-MANO entities for NFV-MANO certificates, done by OSS.
- Discussion paper NFVSEC(23)0000008 "ENH0101 documentation overview"
- SEC#221- DP noted
- SEC chairman will take up the matter at the TSC level on on how best to proceed with the IFA review of IFA026 and IFA033. One-shot review is not efficient for IFA, since sending each and every contribution is also not very efficient as it will overwhelm IFA time and resourcess.
- Discussion paper NFVIFA(23)000459r2 "Enh01.01 remaining issues and future plan" in IFA-SEC joint session.
- Agreed target of ed451
- Target of stable is 21-Jun (IFA) and 22-Jun (SEC) and review MegaCR in both IFA and SEC
- Agreed improved agreement process for inter WGs
- Discussion paper NFVSEC(23)000134 "Discussion Paper on way forward for IFA026 & IFA033 Interfaces"
- SEC#231 - noted.
- Information about the plan NFVSEC(23)000143: "Proposal milestone of IFA026/IFA033"
Stage1/2
| ID | Action | impacted WI(s) | Target | Status |
|---|---|---|---|---|
| 001 | develop usecase for direct mode of VNFCI certficate and VNF OAM certificate.
|
IFA026 | ed451 | Done |
| 001-1 | Add revoke usecase for direct mode of VNFCI certficate and VNF OAM certificate. | IFA026 | ed511 | Not started |
| 002 | develop usecase for delegation mode of VNFCI certificate and VNF OAM certificate.
|
IF026 | ed451 | Done |
| 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 | develop usecase for NFV-MANO certificate.
|
IFA026 | ed451 | Done |
| 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 | Add functional requirements for the certirficate mgmt.
- functional requirements
- Architecture
|
IFA026
IFA010 |
ed451 | Done |
| 006-1 | Update functional requirements for the certificate mgmt. | IFA026
IFA010 |
ed511 | Not started |
| 007 | General
- Overview/ToC
- clean up EN
|
IFA026 | Done | |
| 008 | Add interface for certificate management to CMF.
|
IFA033 | ed451 | Done |
| 009 | Add Register Operation
|
IFA033 | ed451 | Done |
| 009-1 | Add Deregister Operation | IFA033 | ed511 | Not started |
| 010 | Add CSR Operation
|
IFA033 | ed451 | Done |
| 010-1 | Add Revoke Operation | IFA033 | ed511 | Not started |
| 011 | Add Vnfm-Cm reference point
|
IFA033 | ed451 | Done |
| 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 | Enhance VNFD to support certificate mgmt.
|
IFA011 | ed451 | Done |
| 018-1 | Update VNFD to support revoke and renew | IFA011 | ed511 | Not started |
| 019 | Enhance VNF LCM to support certificate mgmt.
|
IFA006
IFA007 IFA008 IFA040 |
ed451 | Done |
| 019-1 | Update VNF LCM to support revoke and renew | IFA006
IFA007 IFA008 IFA040 |
ed511 | Not started |
| 020 | Enhance NS LCM to support certificate mgmt.
|
IFA013 | ed451 | Done |
| 020-1 | Update NS LCM to support revoke and renew | IFA013 | ed511 | Not started |
| 021 | Enhance MANO mgmt to support certificate mgmt.
|
IFA031 | ed451 | Done |
Stage3
| ID | Action | Impacted WI(s) | Status |
|---|---|---|---|
| 001 | Enhance VNFD to support certificate mgmt.
|
SOL001
SOL006 |
SOL001 Done
SOL006 postpone |
| 002 | Enhance VNF LCM to support certificate mgmt.
|
SOL002
SOL003 |
Done |
| 003 | Enhance NS LCM to support certificate mgmt.
|
SOL005 | Done |
| 004 | Enhance VR mgmt
|
SOL014 | Done |
| 005 | Enhance MCIO mgmt
|
SOL018 | Postpone |
| 006 | Enhance MANO mgmt
|
SOL009 | Done |
| 007 | Update MANO procedure
|
SOL016 | Done |
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 |
|
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:
============= Mega CRs Approved ========
Stage 3:
| ||
| 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:
============= Mega CRs Approved ========
Stage3:
| ||
| ENH02.03 | NFV-MANO enhancement with Data flow mirroring | Release 4 | Stage 2 complete
Stage 3 complete |
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:
============= Mega CRs Approved ========
Stage3:
| ||
| 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:
============= Mega CRs for approval========
Stage3:
| ||
| 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:
============= Mega CRs for approval========
Stage3:
| ||
| 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:
Stage3:
|