Feature Tracking: Difference between revisions

From NFVwiki
((Mirroring the nfvprivatewiki))
(Mirroring the nfvprivatewiki)
Line 4: Line 4:
{| class="wikitable"
{| class="wikitable"
|-
|-
| Current mirror date: 2020.09.07|| '''This page is a mirror of the [https://nfvprivatewiki.etsi.org/index.php?title=Feature_Tracking 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.''' <BR>Links to contributions will require authentication with an ETSI Online Account.
| Current mirror date: 2020.11.10|| '''This page is a mirror of the [https://nfvprivatewiki.etsi.org/index.php?title=Feature_Tracking 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.''' <BR>Links to contributions will require authentication with an ETSI Online Account.
|}
|}


Line 1,906: Line 1,906:
- Enhance information model for containerized VNFs both using bare metal or nested virtualization technologies
- Enhance information model for containerized VNFs both using bare metal or nested virtualization technologies
|-
|-
| '''Target Release''' || '''Stage 2 Step 1:''' Release 4 Drop #1 (NFV#31e, September 2020)<br />'''Stage 2 Step 2:''' Release 4 Drop #2 (after NFV#31e, November 2020)<br />'''Stage 3:''' Release 4 (target date tbd)<br />
| '''Target Release''' || '''Stage 2 Step 1:''' Release 4 Drop #1 (after NFV#31e, October 2020)<br />'''Stage 2 Step 2:''' Release 4 Drop #2 (after NFV#32e, January 2021)<br />'''Stage 3:''' Release 4 (target date tbd)<br />
|-
|-
| '''Impacted WIs''' || '''Stage 2:''' IFA007, IFA008, IFA010, IFA011, IFA013, IFA014<br />
| '''Impacted WIs''' || '''Stage 2:''' IFA007, IFA008, IFA010, IFA011, IFA013, IFA014<br />
'''Stage 3:''' tbd
'''Stage 3:''' tbd
|-
|-
| '''MegaCRs''' || '''Stage 2 Step 1:'''<br /> IFA010ed411 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000478r2_IFA010ed411_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(20)000478r2] (Approved) <br />
| '''MegaCRs''' || '''Stage 2 Step 1:'''<br /> IFA010ed411 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000478r2_IFA010ed411_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(20)000478r2] (Approved) <br />[https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/010/04.01.01_60/gs_NFV-IFA010v040101p.pdf New edition IFA010ed411] <br />
IFA011ed411 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000479r6_IFA011ed411_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(20)000479r6] (Approved) <br />
IFA011ed411 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000479r6_IFA011ed411_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(20)000479r6] (Approved) <br />
IFA011ed411 Additional CR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000442r5_FEAT17-IFA011ed411-New_CP_type_to_model_networking_MCIOs.docx NFVIFA(20)000442r5] (Approved) <br />
[https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/011/04.01.01_60/gs_NFV-IFA011v040101p.pdf New edition IFA011ed411] <br />
'''Stage 2 Step 2:'''<br /> IFAyyy MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019//blackhole.doc NFVIFA(19)000yyy] (CR Status) <br />
'''Stage 2 Step 2:'''<br /> IFAyyy MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019//blackhole.doc NFVIFA(19)000yyy] (CR Status) <br />


'''Stage 3:'''<br /> SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//blackhole.doc NFVSOL(20)000zzz] (CR Status)  
'''Stage 3:'''<br /> SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//blackhole.doc NFVSOL(20)000zzz] (CR Status)  
Line 1,919: Line 1,922:
| '''Related/Dependent Features''' || FEAT19 – NFV-Conn <br />FEAT23 – MANO-SBA
| '''Related/Dependent Features''' || FEAT19 – NFV-Conn <br />FEAT23 – MANO-SBA
|-
|-
| '''New Specification ''' || '''Stage 2 Step 1:'''<br /> DGS/NFV-IFA040 - Requirements for service interfaces and object model for OS container management and orchestration specification <br />
| '''New Specification ''' || '''Stage 2 Step 1:'''<br /> [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/040/04.01.01_60/gs_NFV-IFA040v040101p.pdf DGS/NFV-IFA040] - Requirements for service interfaces and object model for OS container management and orchestration specification <br />
'''Stage 2 Step 2:'''<br /> DGS/NFV-IFA036 - Specification of requirements for the management and orchestration of container cluster nodes <br />
'''Stage 2 Step 2:'''<br /> DGS/NFV-IFA036 - Specification of requirements for the management and orchestration of container cluster nodes <br />


Line 1,925: Line 1,928:
|-
|-
| '''Status''' ||  
| '''Status''' ||  
'''Stage 2 Step 1:''' Ongoing (90% completed) <br />
'''Stage 2 Step 1:''' Completed <br />
'''Stage 2 Step 2:''' Ongoing (15% completed) <br />
'''Stage 2 Step 2:''' Ongoing (25% completed) <br />
'''Stage 3:''' Waiting for Stage 2
'''Stage 3:''' Waiting for Stage 2
|-
|-
Line 1,934: Line 1,937:
'''Stage 3:''' Name (Company)  
'''Stage 3:''' Name (Company)  
|-
|-
| '''Last Updated''' || 2020-08-21
| '''Last Updated''' || 2020-11-09
|}
|}


Line 1,987: Line 1,990:
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020//NFVIFA(20)000395r2_FEAT17-IFA011ed411-Add_MCIOP_profile.docx NFVIFA(20)000395r2] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020//NFVIFA(20)000395r2_FEAT17-IFA011ed411-Add_MCIOP_profile.docx NFVIFA(20)000395r2] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000434r2_FEAT17-IFA011ed411-Change_cardinality_of_intCpd_in_Vdu.docx NFVIFA(20)000434r2] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000434r2_FEAT17-IFA011ed411-Change_cardinality_of_intCpd_in_Vdu.docx NFVIFA(20)000434r2] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020//NFVIFA(20)000442r2_FEAT17-IFA011ed411-New_CP_type_to_model_networking_MCIOs.docx NFVIFA(20)000442r2] (Available)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020//NFVIFA(20)000442r5_FEAT17-IFA011ed411-New_CP_type_to_model_networking_MCIOs.docx NFVIFA(20)000442r5] (Approved)<br />
  || IFA011 || February - 2020 || Ongoing
  || IFA011 || February - 2020 || Complete
|-
|-
| ST2-005 || OS container NFV object model (Clause 5)
| ST2-005 || OS container NFV object model (Clause 5)
Line 2,015: Line 2,018:
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000524r1_IFA036_Annex_on_container_related_services.docx NFVIFA(20)000524r1] (Approved) <br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000524r1_IFA036_Annex_on_container_related_services.docx NFVIFA(20)000524r1] (Approved) <br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000525r3_IFA036_Clause_3_1_Term_Definitions.docx NFVIFA(20)000525r3] (Approved) <br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000525r3_IFA036_Clause_3_1_Term_Definitions.docx NFVIFA(20)000525r3] (Approved) <br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020//NFVIFA(20)000558_IFA036_Clause_3_1__Term_Definitions_of_CCM.docx NFVIFA(20)000558] (Available) <br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020//NFVIFA(20)000558r2_IFA036_Clause_3_1__Term_Definitions_of_CCM.docx NFVIFA(20)000558r2] (Approved) <br />
  || IFA036 || August - 2020 || Ongoing
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000688r1_IFA036_Enhance_Clause_4_to_cover_input_from_discussion_paper.docx NFVIFA(20)000688r1] (Approved) <br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000697r1_IFA036_Update_for_Annex_A.docx NFVIFA(20)000697r1] (Approved) <br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000730r1_IFA036_4_2_2_Lifecycle_management_for_CIS_cluster.docx NFVIFA(20)000730r1] (Approved) <br />
  || IFA036 || November - 2020 || Ongoing  
|-
|-
| ST2-007 || Specify the functional requirements for the CISM function
| ST2-007 || Specify the functional requirements for the CISM function
Line 2,081: Line 2,087:
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020//NFVIFA(20)000356r1_FEAT17-IFA010ed411-7_2_1_VNFM_requirements_for_granting_name.docx NFVIFA(20)000356r1] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020//NFVIFA(20)000356r1_FEAT17-IFA010ed411-7_2_1_VNFM_requirements_for_granting_name.docx NFVIFA(20)000356r1] (FEAT agreed)<br />
  || IFA010 || March - 2020 || Complete
  || IFA010 || March - 2020 || Complete
|-
| ||'''FEAT17 Stage 2 - Step 2'''|| || ||
|-
|-
| ST2-016 || Enhance the information models of the Or-Vnfm interfaces for OS container management and orchestration
| ST2-016 || Enhance the information models of the Or-Vnfm interfaces for OS container management and orchestration
Line 2,090: Line 2,098:
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000411r1_FEAT17-IFA007ed411-Clause_8_3_2_Enhance_ResourceDefinition_w.docx NFVIFA(20)000411r1] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000411r1_FEAT17-IFA007ed411-Clause_8_3_2_Enhance_ResourceDefinition_w.docx NFVIFA(20)000411r1] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000437_FEAT17-IFA007ed411-Update_cardinality_of_software_image_attr.docx NFVIFA(20)000437] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000437_FEAT17-IFA007ed411-Update_cardinality_of_software_image_attr.docx NFVIFA(20)000437] (FEAT agreed)<br />
  || IFA007 || June - 2020 || Ongoing
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000560_FEAT17-IFA007ed411-Clause_6_3_2_Enhance_Grant_VNF_LCM_operat.docx NFVIFA(20)000560] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000678r6_FEAT17-IFA007ed421-Clause_8_5_Enhance_VNF_runtime_informatio.docx NFVIFA(20)000678r6] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000711r1_FEAT17_IFA007ed421_exceptions_for_link_port_creation.docx NFVIFA(20)000711r1] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000731r1_FEAT17-IFA007ed421-CISM__CIR_and_MCIOP_repository_access_inf.docx NFVIFA(20)000731r1] (FEAT agreed)<br />
  || IFA007 || December - 2020 || Ongoing
|-
|-
| ST2-017 || Enhance the information models of the Ve-Vnfm interfaces for OS container management and orchestration
| ST2-017 || Enhance the information models of the Ve-Vnfm interfaces for OS container management and orchestration
CR drafts: <br />
CR drafts: <br />
  || IFA008 || June - 2020 || Open
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000771_FEAT17_IFA008ed421_Mirror_of_711__exceptions_for_link_port_c.docx NFVIFA(20)000771] (Available)<br />
  || IFA008 || December - 2020 || Ongoing
|-
|-
| ST2-018 || Enhance the information models of the Os-Ma-nfvo interfaces for OS container management and orchestration
| ST2-018 || Enhance the information models of the Os-Ma-nfvo interfaces for OS container management and orchestration
CR drafts: <br />
CR drafts: <br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000410r1_FEAT17-IFA013ed411-Align_access_information_for_VNF_package_.docx NFVIFA(20)000410r1] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000410r1_FEAT17-IFA013ed411-Align_access_information_for_VNF_package_.docx NFVIFA(20)000410r1] (FEAT agreed)<br />
  || IFA013 || June - 2020 || Ongoing
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000706r3_FEAT17-IFA013ed421-Clause_8_3_3_Enhance_VNF_runtime_informat.docx NFVIFA(20)000706r3] (FEAT agreed)<br />
  || IFA013 || December - 2020 || Ongoing
|-
|-
| ST2-019 || Enhance the information models of the NSD for OS container management and orchestration
| ST2-019 || Enhance the information models of the NSD for OS container management and orchestration
CR drafts: <br />
CR drafts: <br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020//NFVIFA(20)000471r3_FEAT_17-IFA014ed411-External-VirtualLink-Model.docx NFVIFA(20)000471r3] (FEAT agreed)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020//NFVIFA(20)000471r4_FEAT_17-IFA014ed411-External-VirtualLink-Model.docx NFVIFA(20)000471r4] (FEAT agreed)<br />
  || IFA014 || September- 2020 || Ongoing
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000719r1_FEAT17-IFA014ed421-Add_container_namespace_affinity-group_sc.docx NFVIFA(20)000719r1] (FEAT agreed)<br />
|-
  || IFA014 || December- 2020 || Ongoing
| ||'''FEAT17 Stage 2 - Step 2'''|| || ||
|-
|-
| ST2-020 || Container cluster nodes management interface requirements (Clause 5)
| ST2-020 || Container cluster nodes management interface requirements (Clause 5)
CR drafts: <br />
CR drafts: <br />
  || IFA036 || August - 2020 || Open
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000609r5_IFA036_Clause_5_1_Requirements_of_CCM.docx NFVIFA(20)000609r5] (Approved)<br />
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020/NFVIFA(20)000625r1_IFA036_5_x_Service_interface_requirements_for_CIS_instance_m.docx NFVIFA(20)000625r5] (Approved)<br />
  || IFA036 || November - 2020 || Ongoing
|-
|-
| ST2-021 || CIS Cluster NFV object model (Clause 6)
| ST2-021 || CIS Cluster NFV object model (Clause 6)
CR drafts: <br />
CR drafts: <br />
  || IFA036 || September - 2020 || Open
  || IFA036 || December - 2020 || Open
|-
|-
| ST2-022 || CIS Cluster Node NFV object model (Clause 7)
| ST2-022 || CIS Cluster Node NFV object model (Clause 7)
CR drafts: <br />
CR drafts: <br />
  || IFA036 || September - 2020 || Open
  || IFA036 || December - 2020 || Open
|-
|-
| ST2-023 || Analyse and if necessary enhance VNFD and its VDU information element with attributes/information elements related to cluster and node affinity  
| ST2-023 || Analyse and if necessary enhance VNFD and its VDU information element with attributes/information elements related to cluster and node affinity  
CR drafts: <br />
CR drafts: <br />
  || IFA011 || October - 2020 || Open
  || IFA011 || December - 2020 || Open
|-
|-
| ST2-024 || Analyse and if necessary enhance NSD and constituent information elements with attributes/information elements related to cluster and node affinity
| ST2-024 || Analyse and if necessary enhance NSD and constituent information elements with attributes/information elements related to cluster and node affinity
CR drafts: <br />
CR drafts: <br />
  || IFA014 || October - 2020 || Open
  || IFA014 || December - 2020 || Open
|-
|-
| ST2-025 || Specify the functional requirements for the CCM function  
| ST2-025 || Specify the functional requirements for the CCM function  
CR drafts: <br />
CR drafts: <br />
  || IFA010 || September - 2020 || Open
  || IFA010 || January - 2021 || Open
|-
|-
| ST2-026 || Add requirements on CIS cluster node management for the CISM function  
| ST2-026 || Add requirements on CIS cluster node management for the CISM function  
CR drafts: <br />
CR drafts: <br />
  || IFA010 || September - 2020 || Open
  || IFA010 || January - 2021 || Open
|-
|-
| ST2-027 || Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CCM function  
| ST2-027 || Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CCM function  
CR drafts: <br />
CR drafts: <br />
  || IFA010 || September - 2020 || Open
  || IFA010 || January - 2021 || Open
|-
|-
| ST2-028 || Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CISM function related to CIS Cluster Node management  
| ST2-028 || Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CISM function related to CIS Cluster Node management  
CR drafts: <br />
CR drafts: <br />
  || IFA010 || September - 2020 || Open
  || IFA010 || January - 2021 || Open
|-
|-
| ST2-029 || Analyse and if necessary enhance the information models of the Os-Ma-nfvo interfaces for CIS Cluster management and CIS Cluster Node management
| ST2-029 || 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: <br />
CR drafts: <br />
  || IFA013 || October - 2020 || Open
  || IFA013 || January - 2021 || Open
|}
|}


Line 2,341: Line 2,356:
{| class="wikitable"
{| class="wikitable"
|-
|-
| '''Feature Prime''' || Name, Company, E-Mail
| '''Feature Prime''' || Haitao XIA (Huawei), xiahaitao@huawei.com
|-
|-
| '''Feature description''' || Short Description of the Feature
| '''Feature description''' || -  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 2:''' Release 3 (2018-X-X)
| '''Target Release''' || '''Stage 2:''' Release 4 (2021-01-15) Study to be completed
'''Stage 3:''' Release 3 (2019-X-X)
'''Stage 3:''' Release 4 (202x-X-X)
|-
|-
| '''Impacted WIs''' || '''Stage 2:''' IFAxx, IFAyy, SOLzz
| '''Impacted WIs''' || '''Stage 2:''' IFAxx, IFAyy, SOLzz
Line 2,359: Line 2,377:
SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//blackhole.doc NFVSOL(19)000zzz] (CR Status)  
SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//blackhole.doc NFVSOL(19)000zzz] (CR Status)  
|-
|-
| '''Related/Dependent Features''' || FEATxx <br />FEATyy
| '''Related/Dependent Features''' || FEAT07<br />FEATyy
|-
|-
|New Specifcations
|New Specifcations
Line 2,365: Line 2,383:
'''Stage 3:''' SOLaaa
'''Stage 3:''' SOLaaa
|-
|-
| '''Status''' || '''Stage 2:''' Completed
| '''Status''' || '''Stage 2:''' Ongoing (50% completed)
'''Stage 3:''' Ongoing (20% completed)
'''Stage 3:''' Not started
|-
|-
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org Agreed content]
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org Agreed content]
|-
|-
| '''Feature team''' || '''Stage 2:''' Name (Company)
| '''Feature team''' || '''Stage 2:''' Haitao XIA (Huawei)
'''Stage 3:''' Name (Company)  
'''Stage 3:''' Name (Company)  
|-
|-
| '''Last Updated''' || 20xx-xx-xx
| '''Last Updated''' || 2020-09-29
|}
|}


Line 2,385: Line 2,403:
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
|-
|-
| 001 || Add interface X in to IFA007. CR draft [LINK] || IFA || March-2018 || Open
| 001 || First GR (IFA041) draft introducing the skeleton and the scope.
|}
'''Accepted contributions:'''
'''SOL'''
 
{| class="wikitable sortable"
NFVIFA(19)000859r2, NFVIFA(19)000860r1
| IFA || October-2019 || Done
|-
|-
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
|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, NFVIFA(20)000017r1
|IFA
|February-2020
|Done
|-
|-
| 001 || Add interface X in to SOL001. CR draft [LINK] || SOL || March-2018 || Open
|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


=== Stage 3 Implementation Plan ===
'''Accepted contributions:'''
Items to consider in the implementation plan
 
* Detailed description what has to be done in which work item.
NFVIFA(20)000021, NFVIFA(20)000051r2, NFVIFA(20)000134r1, NFVIFA(20)000230r1, NFVIFA(20)000245r1,
* Timeplan of when the team plans to conclude a particular action in the implementation plan.
 
NFVIFA(20)000246r1, NFVIFA(20)000247r2, NFVIFA(20)000248r1, NFVIFA(20)000279r1, NFVIFA(20)000280r1,
 
NFVIFA(20)000319, NFVIFA(20)000281r3, NFVIFA(20)000472r2
 
'''Working in progress:'''
 
NFVIFA(20)000592  IFA041 5.3.1 5.4.1 Synchronize the use case list
 
NFVIFA(20)000622  5.3.x Use case on cross administrative domain management data analytics
 
NFVIFA(20)000651  4.3.3_TMF_Autonomous_Networks
 
NFVIFA(20)000652r1  5.5_Closed_loops
|IFA
|July-2020
|Ongoing
|-
|004
|Analysis of key issues related to use cases in Clause 5.
'''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
 
'''Working in progress:'''
 
NFVIFA(20)000566r3  6.3.x Analytics reporting mechanism
 
NFVIFA(20)000591  5.4 6.4 Aligning terminology with IFA036 GS
 
NFVIFA(20)000593  6.4.x Desired state of the MCIO
 
NFVIFA(20)000594r1  6.4.x Namespace quota
 
NFVIFA(20)000623r1  6.3.x Input data for the MDA process
 
NFVIFA(20)000624r1  6.3.x Output data from the MDA process
|IFA
|October-2020
|Ongoing
|-
|005
|Analysis of pontential architectural impacts on NFV-MANO.
|IFA
|December-2020
|Not started
|-
|006
|Recommendations and conclusion.
|IFA
|January-2021
|Not started
|}
'''SOL'''
'''SOL'''
{| class="wikitable sortable"
{| class="wikitable sortable"
Line 2,407: Line 2,494:
|}
|}


=== Issues ===
=== Stage 3 Implementation Plan ===
''List of issues raised based on the feature implementation.''
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'''
{| class="wikitable sortable"
|-
! 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 ===
=== Security Considerations ===
''List of security considerations implied by the feature.''
''List of security considerations implied by the feature.''
Line 2,419: Line 2,518:
| '''Feature Prime''' || Joan Triay (DOCOMO)
| '''Feature Prime''' || Joan Triay (DOCOMO)
|-
|-
| '''Feature description''' || Short Description of the Feature
| '''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 3 (2018-X-X)
| '''Target Release''' || '''Stage 2:''' TBD (Release 4 (2018-X-X))
'''Stage 3:''' Release 3 (2019-X-X)
'''Stage 3:''' TBD (Release 4 (2019-X-X))
|-
|-
| '''Impacted WIs''' || '''Stage 2:''' IFAxx, IFAyy, SOLzz
| '''Impacted WIs''' || '''Stage 2:''' TBD (IFAxx, IFAyy, SOLzz)
'''Stage 3:''' SOLzz
'''Stage 3:''' TBD (SOLzz)
|-
|-
| '''MegaCRs''' || '''Stage 2:'''
| '''MegaCRs''' || '''Stage 2:'''
IFAxxx MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//blackhole.doc NFVIFA(18)000xxx] (CR Status)  
TBD: IFAxxx MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//blackhole.doc NFVIFA(18)000xxx] (CR Status)  
IFAyyy MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//blackhole.doc NFVIFA(18)000yyy] (CR Status)  
IFAyyy MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//blackhole.doc NFVIFA(18)000yyy] (CR Status)  


'''Stage 3:'''
'''Stage 3:'''


SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//blackhole.doc NFVSOL(19)000zzz] (CR Status)  
TBD: SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//blackhole.doc NFVSOL(19)000zzz] (CR Status)  
|-
|-
| '''Related/Dependent Features''' || FEATxx <br />FEATyy
| '''Related/Dependent Features''' || FEAT17 on "Cloud-native VNF and container infrastructure management"
FEAT19 on "NFV connectivity"
|-
|-
|New Specifcations
|'''New Specifcations'''
|'''Stage 2:''' none
|'''Informative:''' DGR/NFV-IFA037
'''Stage 3:''' SOLaaa
'''Stage 2:''' TBD
'''Stage 3:''' TBD
|-
|-
| '''Status''' || '''Stage 2:''' Completed
| '''Status''' || '''Informative:''' ongoing
'''Stage 3:''' Ongoing (20% completed)
'''Stage 2:''' TBD
'''Stage 3:''' TBD
|-
|-
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org Agreed content]
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org Agreed content]
|-
|-
| '''Feature team''' || '''Stage 2:''' Name (Company)
| '''Feature team''' || '''Informative:''' Joan Triay (DOCOMO)
'''Stage 2:''' Name (Company)  
 
'''Stage 3:''' Name (Company)  
'''Stage 3:''' Name (Company)  
|-
|-
| '''Last Updated''' || 20xx-xx-xx
| '''Last Updated''' || 2020-10-25
|}
|}


=== Informative work ===
'''IFA'''
{| class="wikitable sortable"
|-
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
|-
| 001 || Add interface X in to IFA007. CR draft [LINK] || IFA || March-2018 || Open
|}
=== Stage 2 Implementation Plan ===
=== Stage 2 Implementation Plan ===
Items to consider in the implementation plan
Items to consider in the implementation plan
Line 2,461: Line 2,573:
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
|-
|-
| 001 || Add interface X in to IFA007. CR draft [LINK] || IFA || March-2018 || Open
| 001 || TBD || TBD || TBD || TBD
|}
|}
'''SOL'''
{| class="wikitable sortable"
|-
! 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 ===
=== Stage 3 Implementation Plan ===
Items to consider in the implementation plan
Items to consider in the implementation plan
Line 2,480: Line 2,584:
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
|-
|-
| 001 || Add interface X in to SOL001. CR draft [LINK] || SOL || March-2018 || Open
| 001 || TBD || TBD || TBD || TBD
|}
|}


Line 2,767: Line 2,871:
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
|-
|-
| 001 || VNFM exposed interface support Test Mode deployment || IFA || 2nd Half-2020 || Open
| 001 || Requirements for test information including in VNF Pacakge
* VNF package should contain references to dependent functions or services, which are machine readable and can be bound automatically to the particular VNF at deployment time into the test, staging, production environment. 
* VNF package should contain a testing section with various information concerning testing and DevOps 
* VNF Package should contain acceptance test descriptions. 
* VNF Package should contain acceptance test code that can be executed automatically after deployment into the various environments.
* VNF Package should contain information about a test execution framework what is capable to execute the test code included in the VNF Package. 
* VNF Package should contain a reference to the acceptance test results of the VNF Provider. 
* VNF Package should contain information about the operator environment, in which it makes sense to test.   
 
| IFA011 || 2nd Half-2020 || Open
|-
|-
| 002 || VNF should support to specify the test mode via configuration interface between VNFM and VNF || IFA || 2nd Half-2020 || Open
| 002 || VNF should support to specify the test mode via configuration interface between VNFM and VNF || IFA || 2nd Half-2020 || Open
Line 2,799: Line 2,912:
''List of security considerations implied by the feature.''
''List of security considerations implied by the feature.''


== ENH01: Security enhancements ==
== FEAT26: Policy Management Models ==
This section contains an overview of small and generic security enhancements to the ETSI NFV framework and their current status.
=== Overview ===
{| class="wikitable"
{| class="wikitable"
|+
!ID
!Name
!Status
!Contact
!Descirption
!Contributions
|-
|-
|ENH01.xx
| '''Feature Prime''' || Chen Wang, China Mobile, wangchenyj@chinamobile.com
|New security enhancement
|{Proposal,Under development, Completed, Closed}
|Foo Bar (ACME) <foo.bar@acme.org>
|A short description of the feaure
|
* List
* of
* related
* CRs
|-
|-
|
| '''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''' || '''Stage 2:''' Release 4 (2021-04-15) Study to be completed
|
'''Stage 3:''' Release 4 (202x-X-X)
|
|-
|
| '''Impacted WIs''' || '''Stage 2:''' IFA005/006/007/008/013/030
|
'''Stage 3:''' SOL012
|
|-
|}
| '''MegaCRs''' || '''Stage 2:'''


== ENH02: Special technical enhancements ==
'''Stage 3:'''
This section contains an overview of small and generic technical enhancements to the ETSI NFV framework and their current status.
{| class="wikitable"
|-
|+
| '''Related/Dependent Features''' || FEAT07
!ID
|-
!Name
|New Specifcations
!Status
|'''Stage 2:''' IFA042
!Contact
'''Stage 3:'''
!Description
|-
!Contributions
| '''Status''' || '''Stage 2:''' Ongoing(40% completed)
'''Stage 3:''' Not started
|-
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org Agreed content]
|-
|-
|ENH02.01
| '''Feature team''' || '''Stage 2:''' Chen Wang (China Mobile)
|NFV-MANO enhancement with SDN-based networking
'''Stage 3:''' Name (Company)
|Under development
|
{| class="wikitable"
|Wang  Ruixue, <wangruixue@chinamobile.com>
|-
|-
|Li Shitao,<lishitao@huawei.com>
| '''Last Updated''' || 2020-10-09
|}
|}
|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 Implementation Plan ===
|
0Items to consider in the implementation plan
* NFVIFA(19)000858r4 : feature proposal (accepted)
* Detailed description what has to be done in which work item.
* NFVIFA(19)000966r2: adding RD IE in IFA014, available
* Timeplan of when the team plans to conclude a particular action in the implementation plan.
* NFVIFA(19)0001018: new requirements to IFA010, available
'''IFA'''
* NFVIFA(20)000240r1: adding new routing resource as a new type of network resources: FEAT Agreed (IFA#190)
{| class="wikitable sortable"
* NFVIFA(20)000239r1: discussion paper for adding routing resource, available
|-
* NFVIFA(20)000313r3: adding a new RoutingResorceData for describing a routing resource, FEAT Agreed (IFA#197)
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
* NFVIFA(20)000314r3: adding the Routing resource in the Update Virtualised Network Resource operation, FEAT Agreed (IFA#197)  
|-
|-
|ENH02.02
| 001 || First GR (IFA041) draft introducing the skeleton and the scope.
|NFV-MANO enhancement for NS feasibility check
'''Accepted contributions:'''
|Under development
|Junichi Kawasaki <ju-kawasaki@kddi.com>, Kenichi Ogaki <ke-oogaki@kddi.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.
NFVIFA(20)000553r2
| IFA || August-2020 || Done
|-
|002
|Analysis of existing SDOs and Open Source Community policy models
'''Accepted contributions:'''


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.
NFVIFA(20)000615r2 NFVIFA(20)000616r6 NFVIFA(20)000617r1


This work suggests to enhance the Os-Ma-nfvo reference point to supporting the feasibility check of Network Service.
NFVIFA(20)000618r2 NFVIFA(20)000619r2 NFVIFA(20)000620r1


|
NFVIFA(20)000621r1
* NFVIFA(20)000187r2: New enhancement proposal (accepted)
|IFA
* NFVIFA(20)000084a1r6: Discussion paper for option with extending existing operations (Noted)
|November-2020
* NFVIFA(20)000084r7: Changes to InstantiateNsRequest and UpdateNsRequest (FEAT agreed)
|Ongoing
* NFVIFA(20)000332r3: Extending NsLcmOperationOccurrenceNotification (FEAT agreed)
* NFVIFA(20)000372r2: Support for modifying schedule time of scheduled operation (FEAT agreed)
* NFVIFA(20)000397r2: New requirements to IFA010 (FEAT agreed)
*
|-
|-
|ENH02.03
|003
|NFV-MANO enhancement with Data flow mirroring
|NFV-MANO policy model potential requirements analysis
|Under development
Analysis of existing SDOs and Open Source Community policy models
|Chen Shaofan  <chenshaofan@chinamobile.com>,
|IFA
|January-2021
|Ongoing
|-
|004
|Analysis and Recommendations
|IFA
|Feburary-2021
|Not started
|}
 
'''SOL'''
{| class="wikitable sortable"
|-
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
|-
||||||| ||
|}
 
=== 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'''
{| class="wikitable sortable"
|-
! ID !! Action !! Impacted WG(s) !! Target completion !! Status
|-
||||||| ||
|}


Li Shitao <lishitao@huawei.com>
=== Issues ===
|This new enhancement proposes to enhance the NFV-MANO functionality to enable data flow mirroring management during the timeframe of Release 4.
''List of issues raised based on the feature implementation.''


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.
=== 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.
{| class="wikitable"
|+
!ID
!Name
!Status
!Contact
!Descirption
!Contributions
|-
|ENH01.xx
|New security enhancement
|{Proposal,Under development, Completed, Closed}
|Foo Bar (ACME) <foo.bar@acme.org>
|A short description of the feaure
|
* List
* of
* related
* CRs
|-
|
|
|
|
|
|
|-
|
|
|
|
|
|
|}
 
== ENH02: Special technical enhancements ==
This section contains an overview of small and generic technical enhancements to the ETSI NFV framework and their current status.
{| class="wikitable"
|+
!ID
!Name
!Status
!Contact
!Description
!Contributions
|-
|ENH02.01
|NFV-MANO enhancement with SDN-based networking
|Under development
|
{| class="wikitable"
|Wang  Ruixue, <wangruixue@chinamobile.com>
|-
|Li Shitao,<lishitao@huawei.com>
|}
|This new enhancement proposes to enhance the NFV-MANO functionality related to virtualised network management, lifecycle management and template information model to support the integration of SDN-based network in the framework of NFV-MANO during the timeframe of Release 4.
This work suggests to specify the SDN-based network resources in the NSD and VNFD model in order to use the different type of network to provision the network connection requirements at the design time.
 
This work also suggests to enhance Os-Ma-nfvo, Or-Vi and Or-Vnfm reference points in order to manage the lifecycle of the different type of network.
|
* NFVIFA(19)000858r4 : feature proposal (accepted)
* NFVIFA(19)000966r2: adding RD IE in IFA014, available
* NFVIFA(19)0001018: new requirements to IFA010, FEAT Agreed (IFA#202)
* NFVIFA(20)000240r2: adding new routing resource as a new type of network resources: FEAT Agreed (IFA#208)
* NFVIFA(20)000239r1: discussion paper for adding routing resource, available
* NFVIFA(20)000313r3: adding a new RoutingResorceData for describing a routing resource, FEAT Agreed (IFA#197)
* NFVIFA(20)000314r3: adding the Routing resource in the Update Virtualised Network Resource operation, FEAT Agreed (IFA#197)
* NFVIFA(20)000517r3: discussion paper for NSD model for supporting Routing resource: available
|-
|ENH02.02
|NFV-MANO enhancement for NS feasibility check
|Under development
|Junichi Kawasaki <ju-kawasaki@kddi.com>, Kenichi Ogaki <ke-oogaki@kddi.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.
 
|
* NFVIFA(20)000187r2: New enhancement proposal (accepted)
* NFVIFA(20)000084a1r6: Discussion paper for option with extending existing operations (Noted)
* NFVIFA(20)000084r7: Changes to InstantiateNsRequest and UpdateNsRequest (FEAT agreed)
* NFVIFA(20)000332r3: Extending NsLcmOperationOccurrenceNotification (FEAT agreed)
* NFVIFA(20)000372r2: Support for modifying schedule time of scheduled operation (FEAT agreed)
* NFVIFA(20)000397r2: New requirements to IFA010 (FEAT agreed)
 
===== ============= CRs for approval ======== =====
* NFVIFA(20)000662: IFA013ed421 MegaCR ENH02.02 NS feasibility check
* NFVIFA(20)000397r2: New requirements to IFA010 (FEAT agreed)
*
|-
|ENH02.03
|NFV-MANO enhancement with Data flow mirroring
|Under development
|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.
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.
|NFVIFA(20)000402r3: New enhancement proposal (accepted)
|
* NFVIFA(20)000402r3: New enhancement proposal (accepted)
* NFVIFA(20)000491r7_ENH02.03_IFA010_release_4_enhancement_adding_new_requirement_to_NFVO （FEAT agreed）
* NFVIFA(20)000492r7_ENH02_03_IFA005_release_4_enhancement_adding_new_requirement（FEAT agreed）
* NFVIFA(20)000561r5_ENH02.03_IFA005_new parameters for Deletion of Data Flow Mirroring Job（FEAT agreed）
* NFVIFA(20)000563r6_ENH02.03_IFA005_new parameters for Query of Data Flow Mirroring Job（FEAT agreed）
* NFVIFA(20)000610r4_ENH02.03_IFA005_new parameters for updating of Data Flow Mirroring Job（FEAT agreed）
|-
|ENH02.04
|Invariant identification of NSD constituents
|Not started
|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.
|
|}
|}

Revision as of 11:51, 10 November 2020


Introduction

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

Feature Overview

Feature Overview and Status
Feature Stage 1 Stage 2 Stage 3
FEAT01: NFV-MANO Upgrades ongoing (Rel 4) not started not started
FEAT02: VNF software modification completed (Rel 3) completed (Rel 3) partially completed (Rel 3)

See note 1.

FEAT03: NFVI software modification completed (Rel 3) completed (Rel 3) ongoing (Rel 3)
FEAT04: Host Reservation n/a completed (Rel 3) completed (Rel 3)
FEAT05 Network Slicing completed (Rel 3) completed (Rel 3) ongoing (Rel 3)
FEAT06: Enhancement Network Service (NS) Package n/a (part of Rel 2) n/a (part of Rel 2) n/a (part of Rel 2)
FEAT07: MANO Policy Management (MANO_PLC) completed (Rel 3) completed (Rel 3) ongoing (Rel 3)
FEAT08: Support of composite NS across multi-domain (MANOMD_NS) completed (Rel 3) completed (Rel 3) completed (Rel 3)
FEAT10: Mgmt & Connectivity Multi-Site Services (MCMSS) completed (Rel 3) completed (Rel 3) partially completed (Rel 3).

See note 2.

FEAT11: NFV_M&M (NFV-MANO management) completed (Rel 3) completed (Rel 3) completed (Rel 3)
FEAT12: Enhancement support for MEC in NFV deployments n/a completed (Rel 3).

See note 3.

completed (Rel 3).

See note 3.

FEAT13: Licensing ongoing (Rel 4) not started not started
FEAT15: VNF Snapshotting completed (Rel 3) completed (Rel 3) completed (Rel 3).

See note 1.

FEAT16: Service Availability Level n/a completed (Rel 3) completed (Rel 3)
FEAT17: Cloud-Native VNFs and Container Infrastructure management completed (Rel 3) ongoing (Rel 4) not started (Rel 4)
FEAT18: Security completed (Rel 3) ongoing (Rel 3).

See note 3.

not started
FEAT19: NFV-Connect ongoing (Rel 4) not started not started
FEAT20: Auto ongoing (Rel 4) not started not started
FEAT21: 5GNFV ongoing (Rel 4) not started not started
FEAT22: M-Tenant ongoing (Rel 4) not started not started
FEAT23: MANO-SBA ongoing (Rel 4) not started not started
FEAT24: VNF-OAM ongoing (Rel 4) not started not started
FEAT25: VNF-CI not started not started not started
FEAT26: Policy-models not started not started not started
ENH01: Security enhancements n/a n/a n/a
ENH02: Special technical enhancements ongoing (Rel 4) ongoing (Rel 4) not started
NOTE 1: The specification of other "non-core" parts of the feature is ongoing.

NOTE 2: The specification of the NFV-MANO APIs and NFV Descriptors is completed. Profiling of "protocol and data models" for the interfaces exposed by WIM is ongoing.

NOTE 3: Additional specification/enhancements have been carried over to Release 4.

Introduction

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

  • Link to Release 3 implementation process
    • Link to the "consolidated IFA Release 3 Feature plan". Refer to NFVIFA(17)000914 and revisions. Latest version NFVIFA(17)000914r4
  • Training for Feature Primes
    • Process
    • Wiki editing
  • Naming conventions: e.g. FEAT00_IFA007_[Contribution name]
  • To build a link to all contributions belonging to a feature, replace FEAT99 in the link stated below with the Feature short name for your feature e.g. FEAT15:
 https://portal.etsi.org/Contribution.aspx?Tb_Id=789&searchText=FEAT99&IncludeSubTb=True&sort=pk_contribution&sortorder=DESC&NbItemsPerPage=50&Year=2017,2018,2019
  • Note: Agreed content can be added to Pseudo meeting --> If the access is restricted, this may only work within a workgroup.
  • Related/Dependent Features: Please indicate other features which relate to the ongoing work. Details can be given in the implementation plan or in the issues section.
ETSI NFV Feature Tracking Wiki cropped.png

FEATxx: Feature Title

Overview

Feature Prime Name, Company, E-Mail
Feature description Short Description of the Feature
Target Release Stage 2: Release 3 (2018-X-X)

Stage 3: Release 3 (2019-X-X)

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 Add interface X in to IFA007. CR draft [LINK] IFA March-2018 Open

SOL

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

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.

FEAT02: VNF software modification

Overview

Feature Prime Stefan Arntzen, Huawei
Feature description This feature addresses the initiation and the coordination of the software modification process related to VNFs. Goal is to minimise the impact of software modification on service availability.
Target Release Release 3
Impacted WIs IFA007, IFA008, IFA011, IFA013, IFA010 (not approved)
MegaCRs MegaCR Index in NFVIFA(19)000117r1

IFA007: NFVIFA(19)000059r4 Status: Approved MegaCR (IFA#137)

IFA008: NFVIFA(19)000058 Status: Approved MegaCR (IFA#137)

IFA010: NFVIFA(19)000060 Status: Approved MegaCR (IFA#137)

IFA011: NFVIFA(19)000061r3 Status: Approved MegaCR (IFA#137)

IFA013: NFVIFA(19)000077r3 (single contribution for IFA013)

Related/Dependent Features N/A
Status Completed
Contributions All feature contributions
Agreed content
Feature team Stefan Arntzen (Huawei)
Maria Toeroe (Ericsson)
Shaoji Ni (Huawei)

Dmytro Gassanov (NEC)

Lijuan Chen (ZTE)

Gerald Kunzmann (DOCOMO)

Joan Triay (DOCOMO)

Last Updated 2019-02-06

Implementation Plan

Items to consider in the implementation plan

  • Detailed description what has to be done in which work item.
  • Timeplan of when the team plans to conclude a particular action in the implementation plan.
ID Action Impacted WG(s) Target completion Status
001 Add functionality description of VNF software modification synchronisation in to IFA010.

CR drafts:

NFVIFA(18)000869r3 Status: Agreed FEAT (IFA#124)

NFVIFA(19)000051r2 Status: Agreed FEAT (IFA#136)

IFA010 January-2019 Completed
002 Define metadata to allow to synchronize the software modification process

CR drafts:

- NFVIFA(18)000936r2 Status: Agreed FEAT (IFA#125)

- NFVIFA(18)0001037r1 Status: Agreed FEAT (IFA#129)

- NFVIFA(18)0001122r3 Status: Agreed FEAT (IFA#136)

- NFVIFA(18)0001125r2 Status: Agreed FEAT (IFA#132)

- NFVIFA(18)0001126r1 Status: Agreed FEAT (IFA#132)

- NFVIFA(18)0001149r1 Status: Agreed FEAT (IFA#134)

- NFVIFA(18)0001150r2 Status: Agreed FEAT (IFA#134)

- NFVIFA(18)0001151r6 Status: Agreed FEAT (IFA#137)

- NFVIFA(18)0001155r4 Status: Agreed FEAT (IFA#135)

- NFVIFA(18)0001156 Status: NOTED in drafting call #05

- NFVIFA(19)000049r1 Status: not handled in v3.2.1

- NFVIFA(19)000056 Status: not handled in v3.2.1

- NFVIFA(19)000082 Status: Agreed FEAT (IFA#137)

- NFVIFA(19)000083r2 Status: Agreed FEAT (IFA#137)

- NFVIFA(19)000101r2 Status: Agreed FEAT (IFA#137)

- NFVIFA(19)000105r1 Status: Agreed FEAT (IFA#137)

IFA011 January-2019 Completed
003 Derive the requirements from REL006 for an interface for the coordination of VNF software modifications actions on the Or-Vnfm reference point IFA007 December-2018 Completed
004 Derive the requirements from REL006 for an interface for the coordination of VNF software modifications actions on the Ve-Vnfm reference point IFA008 December-2018 Completed
005 Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vnfm reference point

CR drafts:

- NFVIFA(18)000937r3 Status: Agreed FEAT (IFA#125)

- NFVIFA(18)000935r2 Status: Agreed FEAT (IFA#125)

- NFVIFA(18)0001154r2 Status: Agreed FEAT (IFA#135)

- NFVIFA(19)000115r1 Status: Agreed FEAT (IFA#137)

IFA007 January-2019 Completed
006 Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Ve-Vnfm reference point

CR drafts:

- NFVIFA(18)000938 Status: Obsolete (superseeded by 107r2)

- NFVIFA(19)000106 Status: Agreed FEAT (IFA#137)

- NFVIFA(19)000107r2 Status: Agreed FEAT (IFA#137)

- NFVIFA(19)000116 Status: Agreed FEAT (IFA#137)

IFA008 January-2019 Completed
007 Add annex with information flows to document the procedures for the VNF software modifications

CR drafts (IFA007):

- NFVIFA(18)000933r6: Status: Agreed FEAT (IFA#128)

- NFVIFA(19)000094r1 Status: Agreed FEAT (IFA#137)

- NFVIFA(19)000096r1 Status: Agreed FEAT (IFA#137)

- NFVIFA(19)000097r3 Status: Agreed FEAT (IFA#137)

CR drafts (IFA013):

- NFVIFA(18)000934 Status: not handled in v3.2.1

IFA007,

IFA013

January-2019 Completed
008 Finalize CRs for the changes from 001, 002, 005, 006, 007 and create MegaCRs IFA February-2019 Completed
009 Security analysis:

- NFVIFA(18)0001147r1 Status: Agreed by SEC WG

IFA January-2019 Completed
010 Requirements and operations for NS LCM interface:

- NFVIFA(19)000077r3 Status: Agreed FEAT (IFA#137)

IFA013 January-2019 Completed

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT03: NFVI software modification

Overview

Feature Prime Maria Toeroe (Ericsson), Gerald Kunzmann (DOCOMO)
Feature description This feature addresses the support for the coordination of the NFVI software modification process with the VNFs hosted on the NFVI in order to minimize impact on service availability.
Target Release Stage 2: Release 3 drop 3 (2019-06)

Stage 3: Release 3 (2019-12)

Impacted WIs IFA005, IFA006, IFA007, IFA008, IFA010, IFA011
MegaCRs Stage 2:

IFA005: NFVIFA(19)000455 Baseline (Approved in IFA#159)
IFA006: NFVIFA(19)000040r8 Baseline (Approved in IFA#159)

IFA007: N/A (was NFVIFA(19)000456 (Draft))
IFA008: NFVIFA(19)000454r2 Baseline (Approved in IFA#159)

IFA010: NFVIFA(19)000038r7 Baseline (Approved in IFA#159)
IFA011: NFVIFA(19)000039r7 Baseline (Approved in IFA#159) + NFVIFA(19)000319r3 (Approved in IFA#160)

Stage 3:

<tbd>

Related/Dependent Features N/A
Status Stage 2: Approved (IFA#159). MegaCR Index available in NFVIFA(19)000603r1

Stage 3: Not started

Contributions Stage 2:

All feature contributions
Agreed content

Stage 3:

<tbd>

Feature team Stage 2:

Maria Toeroe (Ericsson)
Stefan Arntzen (Huawei)
Shaoji Ni (Huawei)
Mehmet Toy (Verizon)
Gerald Kunzmann (DOCOMO)

Stage 3:

<tbd>

Last Updated 2019-07-15

Stage 2 Implementation Plan

ID Action Impacted WG(s) Target completion Status
001 Based on REL006 add functionality description of NFVI software modification support to IFA010 for the VIM, VNFM and NFVO.
CR Drafts:

NFVIFA(18)000283r2 Status: Withdrawn
NFVIFA(18)000285r5 Status: Agreed

NFVIFA(18)000631r4 Status: Agreed

NFVIFA(18)000875r2 Status: Withdrawn

NFVIFA(19)000092r1 Status: Agreed FEAT (IFA#141)

NFVIFA(19)000287r3 Status: Agreed FEAT (IFA#148)

NFVIFA(19)000345r2 Status: Agreed FEAT (IFA#149)

NFVIFA(19)000360r7 Status: Agreed FEAT (IFA#152)

NFVIFA(19)000361r6 Status: Agreed FEAT (IFA#152)

NFVIFA(19)000377r5 Status: Agreed FEAT (IFA#152)

NFVIFA(19)000384r3 Status: Agreed FEAT (IFA#152)

NFVIFA(19)000400r1 Status: Agreed FEAT (IFA#152)

NFVIFA(19)000426r2 Status: Agreed FEAT (IFA#152)

NFVIFA(19)000464r7 Status: Agreed FEAT (IFA#155)

NFVIFA(19)000539r1 Status: Agreed FEAT (IFA#155)

NFVIFA(19)000571 Status: Agreed FEAT (IFA#157)

NFVIFA(19)000577 Status: Agreed FEAT (IFA#157)

IFA010 June 2019 Started
002 Based on REL006 specify the requirements for an interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vi reference point IFA005 December-2018 Open
003 Based on REL006 specify the requirements for an interface for the coordination of the NFVI software modifications with the hosted VNFs on the Vi-Vnfm reference point IFA006 December-2018 Open
004 Based on REL006 specify the requirements for an interface for the coordination of the NFVI software modifications with the hosted VNFs on the Ve-Vnfm reference point IFA008 December-2018 Open
005 Based on REL006 specify the requirements for an interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vnfm reference point IFA007 December-2018 Open
006 Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vi reference point.
CR Drafts:
NFVIFA(18)000763 Status: Withdrawn

NFVIFA(19)000003r1 Status: Obsolete

NFVIFA(19)000052r2 Status: Obsolete

IFA005 June 2019 Started
007 Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Vi-Vnfm reference point.
CR Drafts:
NFVIFA(18)000296r9 Status: Agreed

NFVIFA(18)000762r1 Status: Withdrawn

NFVIFA(18)000987r18 Status: Withdrawn
NFVIFA(18)0001053r4 Status: Agreed

NFVIFA(18)0001054r4 Status: Agreed

NFVIFA(19)000033 Status: Agreed

NFVIFA(19)000066r14 Status: NOTED (IFA#144)

NFVIFA(19)000067r7 Status: NOTED (IFA#144)
NFVIFA(19)000068r6 Status: NOTED (IFA#144)

NFVIFA(19)000318r4 Status: Agreed FEAT (IFA#148)

NFVIFA(19)000449r3 Status: Agreed FEAT (IFA#153)

NFVIFA(19)000460r5 Status: Agreed FEAT (IFA#155)

NFVIFA(19)000462r5 Status: Agreed FEAT (IFA#155)

NFVIFA(19)000461r1 Status: Agreed FEAT (IFA#157)

NFVIFA(19)000463r1 Status: Agreed FEAT (IFA#154)

NFVIFA(19)000551r4 Status: Agreed FEAT (IFA#154)

NFVIFA(19)000563r1 Status: Agreed FEAT (IFA#154)

IFA006 June 2019 Started
008 Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Ve-Vnfm reference point.
CR Drafts:
NFVIFA(18)000761r1 Status: Withdrawn
NFVIFA(18)000990r13 Status: Withdrawn
NFVIFA(18)000991r13 Status: Withdrawn
NFVIFA(18)000989r7 Status: Withdrawn
NFVIFA(19)000002r6 Status: replaced by NFVIFA(19)000241
NFVIFA(19)000075 Status: Withdrawn

NFVIFA(19)000102r8 Status: Agreed FEAT (IFA#144)

NFVIFA(19)000240 Status: Noted (IFA#144)

NFVIFA(19)000241 Status: Noted (IFA#144)

NFVIFA(19)000371r9 Status: Agreed FEAT (IFA#152)

IFA008 June 2019 Started
009 Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vnfm reference point.
CR Drafts:
NFVIFA(18)000764 Status: Withdrawn
NFVIFA(19)000004 Status: Withdrawn
NFVIFA(19)000069 Status: Agreed FEAT (IFA#141)

NFVIFA(19)000260 Status: Noted (IFA#144)

NFVIFA(19)000515 Status: Candidate for Agreed FEAT in IFA#155

IFA007 June 2019 Started
010 Specify the VNF constraints parameters for NFVI software modifications in the VNFD.
CR Drafts:
NFVIFA(18)000456r5 Status: Agreed FEAT (IFA#129)
NFVIFA(18)000873r3 Status: Agreed FEAT (IFA#129)
NFVIFA(19)000091 Status: Agreed FEAT (IFA#141)
NFVIFA(19)000090r2 Status: Agreed FEAT (IFA#144)
NFVIFA(19)000087 Status: Agreed FEAT (IFA#141)

NFVIFA(19)000265r1 Status: Agreed FEAT (IFA#144)

NFVIFA(19)000319r3 Status: Agreed FEAT (IFA#148)

IFA011 June 2019 Started

Stage 3 Implementation Plan

Items to consider in the implementation plan

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

SOL

ID Action Impacted WG(s) Target completion Status
001 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

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

FEAT04: Host Reservation

Overview

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

Implementation Plan

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

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

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT05 Network Slicing

Overview

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

Feature Prime Anatoly Andrianov (Nokia), Cristina Badulescu (Ericsson), Ulrich Kleber (Huawei), Bhumip Khasnabish (ZTE)
Feature description EVE to IFA REL SEC Feature NFVSLICE EVE012 network slicing

Support Network Slicing by defining the necessary requirements and enhancements of interfaces, as discussed in NFV(17)000252.

Target Release Release 3 Drop 2
Impacted WIs IFA010, IFA013, IFA014, IFA024
MegaCRs MegaCR for IFA010: NFVIFA(18)000844r7_IFA010_MegaCR_FEAT05_Slicing.docx

MegaCR for IFA013: NFVIFA(19)000014r1_IFA013_MegaCR_FEAT05_Slicing.docx
Only one CR for IFA014: NFVIFA(18)000653r4_FEAT05__IFA014_add_priority_to_NSD
Only one CR for IFA024: NFVIFA(18)0001091_FEAT05_IFA024_Add_Slicing_Touchpoint
MegaCR Index: NFVIFA(19)000016r1_FEAT05_MegaCR_Index.docx

Related/Dependent Features After analysis and LS exchange with 3GPP no dependencies for the time frame of this feature are seen anymore.
Status Completed
Reliability Review Done in REL#270 on January 15, 2019
Security Review Reviewed in SEC#139 on January 24, 2019
See NFVIFA(19)000054r2_FEAT05_security_considerations.docx
or NFVSEC(19)000008r1_FEAT05_security_considerations.zip
Contributions Latest status on Feature Dashboard
Feature team

Anatoly Andrianov, Nokia
Cristina Badulescu, Ericsson
Bhumip Khasnabish, ZTE
Ulrich Kleber, Huawei
Sibylle Schaller, NEC
Zarrar Yousaf, NEC
Gerald Kunzmann, DOCOMO Communications Lab
Stage 3/SOL WG: Arturo Martin de Nicolas

Last Updated 2019-01-28

Summary of decisions / agreed concepts

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

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

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

Overview Liaison Exchange

Specific Liaisons with 3GPP SA5 on Network Slicing

Summary of the answers:

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

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

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

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

Open questions collected:

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

Other Liaisons with SA5

LS received in cc, but containing valuable inputs:

Liaisons with other SDOs

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

Implementation Plan

ID Action Impacted WG(s) Target completion Status
001 Add Functional requirements to support NFVSLICE in IFA010


CR Drafts agreed:
- NFVIFA(18)000049r3_FEAT05_IFA010_Add_Requirements_from_Slicing_to_NFVO_and_VNFM status: FEAT AGREED (IFA#89)
- NFVIFA(18)000120r5_FEAT05_IFA010_General_Functional_Requirements status: FEAT AGREED (IFA#125)
- NFVIFA(18)000172_FEAT05_IFA010_Requirements__Network_Connections_NFVI_PoPs Routed to FEAT10 and FEAT AGREED (IFA#104)
- NFVIFA(18)000478r2_FEAT05_IFA010_CR_UseCases_for_Network_Slicing FEAT AGREED (IFA#105)
- NFVIFA(18)000692r2_FEAT05_IFA010__Scaling_Use_Cases_for_Network_Slicing_in_Anne FEAT AGREED (IFA#116)
- NFVIFA(18)000699r4_FEAT05_IFA010__Use_case__Re-instantation_of_multiple_NS_inst FEAT AGREED (IFA#122)
- NFVIFA(18)000732r2_FEAT05_IFA010_priority-based_NS_resource_Mngmnt_by_NFVO FEAT AGREED (IFA#118)
- NFVIFA(18)000847r2_FEAT05_IFA010__Consider_priorities_during_resource_reservati FEAT AGREED (IFA#122)
- NFVIFA(18)000848r1_FEAT05_IFA010__Consider_priorities_during_VNF_Lifecycle_Oper FEAT AGREED (IFA#122)
- NFVIFA(18)000849r1_FEAT05_IFA010__Consider_priorities_during_NS_scaling FEAT AGREED (IFA#122)
- NFVIFA(18)000850r1_FEAT05_IFA010__Consider_priorities_in_a_multiple_administrat FEAT AGREED (IFA#122)
- NFVIFA(18)000867r5_FEAT05_IFA010_priority_support_in_allowance_management FEAT AGREED (IFA#125)
- NFVIFA(18)000868r1_FEAT05_IFA010_priority_support_in_scheduled_NS_lifecycle_ope FEAT AGREED (IFA#122)
- NFVIFA(18)000879r1_Restructuring_Annex_of_IFA010__FEAT05_proposal_.docx APPROVED (IFA#125)
- NFVIFA(18)000963r3_FEAT05_IFA010__Use_case__Instantiation_of_NS_in_parallel_to FEAT AGREED in IFA#128
- NFVIFA(18)0001000r3_FEAT05_IFA010_Clarification_on_Resource_Conflict_Resolution to be FEAT AGREED in IFA#129
- NFVIFA(18)0001065r2_FEAT05_IFA010__Use_case__Resolving_a_conflict_by_pre-empting.docx FEAT AGREED in IFA#129
- NFVIFA(18)0001089r1_FEAT05_IFA010_Annex_NS_sharing_conclusions.docx FEAT AGREED in IFA#129
- NFVIFA(18)000252r7_FEAT05_IFA010_Annex_Use_of_NFV_Constructs_in_Network_Slicing FEAT AGREED in IFA#131
- NFVIFA(18)0001119r2_FEAT05_IFA010_Editorial_alignment_of_use_cases.docx FEAT AGREED in IFA#131
- NFVIFA(18)0001123r1_FEAT05_IFA010_Add_LCM_coordination_interface_to_use_cases.docx FEAT AGREED in IFA#131
- NFVIFA(18)0001139r2_FEAT05_IFA010_Annex_D_1_Introduction_to_general_use_cases.zip FEAT AGREED in IFA#131
- NFVIFA(18)0001140r1_FEAT05_IFA010_Add_requirements_on_isolation.docx FEAT AGREED in IFA#131
- NFVIFA(18)0001148_FEAT05_IFA010_Add_use_of_NsLcmCapacityShortageNotification.docx FEAT AGREED in IFA#133

IFA010 Jan-2019 Completed
002 Identify and add new parameters for NSD to allow support of the network slice and network slice subnet.


CR Drafts agreed:
- NFVIFA(18)000653r4_FEAT05__IFA014_add_priority_to_NSD FEAT AGREED in IFA#129

IFA014 Jan-2019 Completed
003 Investigate whether any new parameters in VNFD may be needed. IFA011 Jan-2019 No update needed
Completed
004 Investigate whether any new parameters in Os-Ma-Nfvo reference point may be needed to realize NFVSLICE lifecycle capabilities which include:

- Determining the requirements on the lifecycle of the Network Service used as part of a Network Slice

- Determining the requirements for the lifecycle of the Network Service used as part of a Network Slice Subnet

IFA013 Jan-2019 No update needed
Completed
005 Investigate whether any new parameters in Os-Ma-Nfvo reference point may be needed to realize NFVSLICE feature capabilities which include:

- Determining the requirements for policy handling for Network Service instance

- Determining the requirements for performance and fault data handling

- Determining the requirements for LCM handling


CR Drafts:
- NFVIFA(18)0001008r1_FEAT05_IFA013__NsLcmOperationOccurenceNotification_in_case_o.docx FEAT AGREED in IFA#129
- NFVIFA(18)0001141_FEAT05_IFA013_Add_shortage_notification_.docx FEAT AGREED in IFA#133

Note: According to EVE012 further analysis is necessary on whether there is any impact on the IFA013

IFA013 Jan-2019 Completed
006 Investigate whether any new parameters in Or-Vi reference point may be needed to realize NFVSLICE feature capabilities which include:

- Determining the resource requirements for Network Service instance - Communicating resource prioritization related data

IFA005 Jan-2019 No update needed
Completed
007 Investigate whether any new parameters in Vnfm-Vi reference point may be needed to realize NFVSLICE feature capabilities which include:

- Determining the resource requirements for VNF/C instances - Communicating resource prioritization related data

IFA006 Jan-2019 No update needed
Completed
008 Investigate whether any enhancements are needed for Application and Service Management Interface

and Information Model Specification.

IFA012 Jan-2019 Completed:
No change needed:
Use cases will be covered in IFA010, Touchpoints in IFA024.
Not necessary to re-open Document in drop 2.
009 Investigate whether any Security requirements may be needed to realize the following features:


Resource isolation for security reasons and per allocation policy:
At Network Service level
At VNF level
At NFVI level
Isolation of network service management for multiple tenants


Security review available in NFVIFA(19)000054_FEAT05_security_considerations.docx

Note: Affected documents to be discussed with SEC WG

SEC012 Jan-2019 No update need to be initiated from FEAT05
Completed
010 Reliability requirements to realize the following features:

- The NS instantiation which is used in the creation of a network slice instance, or in the network slice subnet instance
- Maintaining the reliability of NS supporting the network slice instance during and after resource changes
- Applying the reliability requirements and policies associated with network slice instance or the network slice subnet instance,
throughout the lifecycle management of the Network Service instance

As discussed with REL WG on Sept.30 2018,
all reliability aspects will be analysed and covered by the REL010 work item.
Impacts on IFA documents cannot be analysed in drop 2 time frame. Thus these can only be done (if necessary) in a second phase of FEAT05.


Reliability review was conducted with REL WG on January 15, 2019 in meeting REL#270

REL010 June-2019 Completed
Delegate to REL10
No CR in drop 2 from FEAT05
011 The touchpoint between NFV and network slice management functions needs to be specified.

The diagram illustrating it can be found in LS from SA5 NFV(18)000282_Reply_LS_from_3GPP_SA5_on_GSMA_Network_Slicing_Use_Case_Requ


CR Drafts:
- NFVIFA(18)0001091_FEAT05_IFA024_Add_Slicing_Touchpoint.zip

IFA024 Feb-2019 Completed

CRs abandoned

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

Other Contributions

Stage 3 Implementation Plan

ID Action Impacted WI(s) Target completion Status
001 Add priority to NS node type.NFVSOL(19)000799r2 SOL001 December-2019 Completed
002 Add priority to NSD.NFVSOL(19)000854 SOL006 December-2019 Completed
003 Introduce new NsLcmCapacityShortageNotification type SOL005 February-2020 Ongoing

Issues

List of issues raised based on the feature implementation.

Security Considerations

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

FEAT06: Enhancement Network Service (NS) Package

Overview

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

Feature Prime Bhumip Khasnabish (ZTE), Haibin Chu (Ericsson) and Yaoye Zhang (Huawei)
Feature description An NS Package is an archive including the meta-model descriptors NSD and other files (scripts, security materials, possible rules, policies, NS over multi-tenants, etc.), that are required to manage an NS from design to test/verification to validation/certification to runtime management; the holistic end-to-end NS lifecycle, as discussed in NFV(17)000247.
Target Release same as DGS/NFV-SOL007 (1H-2019)
Impacted WIs IFA010, IFA012 (TBC), IFA013, and IFA014.
Note-1: We identify the impacted specifications in IFA WG only. The impacted specifications in other WGs (e.g. SOL, TST, SEC, REL, etc) needs to be addressed separately and the chairs of SOL and TST WGs have been informed. We will follow up the impacts on SEC and REL WGs.

Note-2: The impact on IFA012 is dependent on the ISG's decision whether IFA012 is released as GS or GR by the end of Y2017.

Mega-CRs IFA010 [not available]
IFA012 [not available]
IFA013 [not available]
IFA014 [not available]
Related/Dependent Features FEATxx
FEATyy
New Specification No new WI is expected in IFA WG.

Name of New Specification in SOL WG is DGS/NFV-SOL007 (NSD file structure spec., based on NFVIFA(18)000174/NFVIFA(17)000879, NFVSOL(17)000711 and NFV(18)000066/NFV(17)000364; created on 2018-03-01 and approved on 2018-03-12).]
The scope of this work item [DGS/NFV-SOL007] is to specify the Network Service Descriptor file structure and naming conventions for the different files, fulfilling the requirements specified in ETSI GS NFV-IFA 014. The work item deliverable will contain normative provisions.
WI Status [In Progress; to be completed by 1H-2019].

Status Ongoing (as DGS/NFV-SOL007)
Contributions All feature contributions
Agreed content
Feature team Bhumip Khasnabish (ZTE)
Haibin Chu (Ericsson)
Yaoye Zhang (Huawei)
Maopeng Zhang (ZTE)
Lingli Deng (CMCC)
Last Updated 2018-10-01

Implementation Plan

Items to consider in the implementation plan

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

Issues

List of issues raised based on the feature implementation.

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

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

Security Considerations

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

FEAT07: MANO Policy Management (MANO_PLC)

Overview

Feature Prime Haitao Xia (Huawei)
Feature description This feature addresses the interface operation definition when policy management is introduced to NFV-MANO
Target Release Release 3 drop 1 (2018-06)
Impacted WIs IFA010
IFA013
IFA007
IFA008
IFA005
IFA006
Mega-CRs

IFA013 MegaCR in NFVIFA(18)000429r1 (Approved)
IFA007 MegaCR in NFVIFA(18)000430r1 (Approved)
IFA008 MegaCR in NFVIFA(18)000431r1 (Approved)
IFA005 MegaCR in NFVIFA(18)000432r1 (Approved)
IFA006 MegaCR in NFVIFA(18)000433r1 (Approved)
IFA010 MegaCR in NFVIFA(18)000455r3 (Approved)

Related/Dependent Features no dependency
Status Completed. MegaCR Index available in NFVIFA(18)000492r1
Contributions All feature contributions
Agreed content
Feature team Haitao Xia (Huawei)
Last Updated 2018-06-07

Implementation Plan

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

ID Action Impacted WG(s) Target completion Status
001 Add functional requirements of policy management for the NFVO, VNFM and VIM

IFA010 CRs (Status: Feature Agreed)
NFVIFA(18)000018r3
NFVIFA(18)000029r2

IFA010 Jan-2018 Completed
002 Specify a new interface of policy management over Os-Ma-nfvo reference point, including the interface requirements, policy management operations and corresponding information model

IFA013 CRs (Status: Obsolete)
NFVIFA(18)000032r3
NFVIFA(18)000088r1
NFVIFA(18)000089r1
NFVIFA(18)000094r6
NFVIFA(18)000165r4
NFVIFA(18)000186r2
NFVIFA(18)000187
NFVIFA(18)000213r1
NFVIFA(18)000481r1

IFA013 Mar-2018 Completed
003 Derive policy management interface over Nfvo-vnfm, Ve-Vnfm, Nfvo-Vi, Vi-vnfm reference point (mirror CRs to IFA013GS) based on the output of IFA013 interface operation definition

IFA007 mirror CRs (Status: Obsolete)
NFVIFA(18)0000272
NFVIFA(18)0000273
NFVIFA(18)0000274
NFVIFA(18)0000275r1
NFVIFA(18)0000276r1
NFVIFA(18)0000277
NFVIFA(18)0000278
IFA008 mirror CRs (Status: Obsolete)
NFVIFA(18)0000313
NFVIFA(18)0000314
NFVIFA(18)0000315r1
NFVIFA(18)0000316
NFVIFA(18)0000317
NFVIFA(18)0000318
NFVIFA(18)0000319
IFA005 mirror CRs (Status: Obsolete)
NFVIFA(18)0000340
NFVIFA(18)0000383
NFVIFA(18)0000385
NFVIFA(18)0000387
NFVIFA(18)0000389
NFVIFA(18)0000391
NFVIFA(18)0000393
IFA006 mirror CRs (Status: Obsolete)
NFVIFA(18)0000341
NFVIFA(18)0000384
NFVIFA(18)0000386
NFVIFA(18)0000388
NFVIFA(18)0000390
NFVIFA(18)0000392
NFVIFA(18)0000394

IFA007/IFA008/IFA005/IFA006 May-2018 Completed
004 Define information model enhancement to the NFV descriptor (e.g., NSD) when necessary

Conclusion: Based on the discussion output of NFVIFA(18)000135r1,there is no necessity to introduce policy descriptor to the NSD information model

IFA014 Feb-2018 Completed

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

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

Overview

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

New deliverable IFA030GS Approved

Contributions All feature contributions
Agreed content
Feature team Haitao Xia (Huawei)
Arturo Martin de Nicolas (Ericsson)
Bhumip Khasnabish (ZTE)
Last Updated 2018-09-01

Implementation Plan

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

ID Action Impacted WG(s) Target completion Status
001 Determine the content skeleton and input for introduction

Approved contributions:
NFVIFA(17)0001172r3
NFVIFA(17)0001176r2

IFA030 Jan-2018 Completed
002 Add NFVO functional requirement description derived from Table 6.3-2 of IFA028 to IFA010

IFA010 CRs (Status: Obsolete)
NFVIFA(18)000042r3
NFVIFA(18)000050r5

IFA010 May-2018 Completed
003 Add interface requirement description of Or-Or reference point derived from Table 6.3-1 of IFA028

Approved contributions:
NFVIFA(18)000056r1
NFVIFA(18)000041r2
NFVIFA(18)000167
NFVIFA(18)000337

IFA030 Apr-2018 Completed
004 Define Or-Or interface functions of NSD management, NS LCM, NS PM and NS FM which are derived from IFA013 GS and necessary adaptation is made

Approved contributions:
NFVIFA(18)000077r1
NFVIFA(18)000338

IFA030 Apr-2018 Completed
005 Define Or-Or interface functions of NS lifecycle granting and NS instance usage notification

Approved contributions:
NFVIFA(18)000097r3
NFVIFA(18)000112r2

IFA030 Apr-2018 Completed
006 Develop Or-Or operational flows as informative Annex (when necessary)

Conclusion: No operational flows are expected to be included in IFA030 GS:
1. Align with the same definition style of other interface specifications;
2. IFA028 report has already provided the flows for reference.

IFA030 Mar-2018 Completed
007 New GS (IFA030) clean-up, EN resolution

Approved Contributions:
NFVIFA(18)000441r1
NFVIFA(18)000442r1
NFVIFA(18)000443
NFVIFA(18)000444r1
NFVIFA(18)000447

IFA030 May-2018 Completed

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

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

Overview

Feature Prime

Hiroshi Dempo, Zarrar Yousaf (NEC) (stage 2)
Zarrar Yousaf (NEC), Joan Triay (DOCOMO) (stage 3)

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)
Stage 3: TBD
Impacted WIs Stage 2: IFA005, IFA007, IFA010, IFA011, IFA013, IFA014, IFA022, IFA032
Stage 3: SOL014, SOL003, SOL005, SOL001, SOL006, SOL017
Mega-CRs Stage 2:
- 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, others TBD
Status Stage 2: Completed, MegaCR Index available in NFVIFA(18)0001117r3
Stage 3: Ongoing
Contributions All feature contributions
Agreed content
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 2019-11-18

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

Status: Published
Document: Report on Management and Connectivity for Multi-Site Services
 IFA022 Dec-2017 Done
003

- Specify general and functional recommendations for Multi-Site Service
- Describe architectural and functional outline of Multi-Site Service (e.g. as a new annex)

  • Approved
None
  • Agreed
IFA#89: CR NFVIFA(18)000079r2
IFA#89: CR NFVIFA(18)000080r1
IFA#89: CR NFVIFA(18)000081r1
IFA#100: CR NFVIFA(18)000262r2
IFA#100: CR NFVIFA(18)000263r1
IFA#100: CR NFVIFA(18)000264r2
IFA#100: CR NFVIFA(18)000265r1
IFA#100: CR NFVIFA(18)000266r1
IFA#105: CR NFVIFA(18)000172r6
  • In discussion
 IFA010 Jan/ 2018 Completed
004

- Specify Os-Ma-Nfvo reference point interface and information model specification for Multi-Site Service
- Make relevant changes to the scope and overview sections to include the support for Multi-site Service on Os-a-Nfvo reference point.

  • Approved
None
  • Agreed
IFA#99: CR NFVIFA(18)000129r3
IFA#100: CR NFVIFA(18)000155r1
  • In discussion
None
 IFA013 Mar-2018 Completed
005

- Specify Or-Vi reference point interfaces and information model specification between NFVO and VIM for Multi-Site Service
- Make relevant changes to the scope and overview sections to include the support for Multi-site Service

  • Approved
IFA#118: CR NFVIFA(18)000780r3
  • Agreed
None
  • In discussion
None
 IFA005 Mar-2018 Completed
006

- Specify enhancements to Or-Vnfm ref. point interfaces and information model to address the case of VNF multi-site deployment. - Make relevant changes to the scope and overview sections to include the support for Multi-site Service on Or-Vnfm reference point

  • Approved
None
  • Agreed
IFA#99 CR NFVIFA(18)000128r5
  • In discussion
None
 IFA007 Mar-2018 Completed
007 - Specify parameters for the VNFD file relevant for the support of Multi-Site Service

" No CRs received"

IFA011 May-2018 Closed
008 - Specify parameters for the NSD file relevant for the support of Multi-Site Service
  • Approved
None
  • Agreed
IFA#89: CR NFVIFA(18)000117
IFA#89: CR NFVIFA(18)000118r1
  • In discussion
None
 IFA014 May-2018 Completed
009

- Specify Or-Vi reference point interfaces and information model specification between NFVO and WIM for Multi-Site Service

  • Approved
IFA#89: NFVIFA(18)000159r1
IFA#100: NFVIFA(18)000413
IFA#100: NFVIFA(18)000414r1
IFA#100: NFVIFA(18)000415
IFA#100: NFVIFA(18)000416r1
IFA#100: NFVIFA(18)000417
IFA#105: NFVIFA(18)000496r2
IFA#105: NFVIFA(18)000497r3
IFA#105: NFVIFA(18)000524r4
IFA#105: NFVIFA(18)000558r1
IFA#105: NFVIFA(18)000582r1
IFA#108: NFVIFA(18)000702r1
IFA#118: NFVIFA(18)000781r2
IFA#118: NFVIFA(18)000782r1
IFA#118: NFVIFA(18)000783r2
IFA#118: NFVIFA(18)000784r2
IFA#118: NFVIFA(18)000785r2
IFA#118: NFVIFA(18)000786
IFA#118: NFVIFA(18)000787r1
IFA#118: NFVIFA(18)000788
IFA#118: NFVIFA(18)000826r1
IFA#125: NFVIFA(18)000912r1
IFA#125: NFVIFA(18)000913r1
IFA#125: NFVIFA(18)000916r3
IFA#125: NFVIFA(18)000951r1
  • Agreed
None
  • In discussion
None

NOTE: As written in ID#2, naming of the ref. point is FFS. Purpose of the specification is to focus on virtualised network resource management subset of existing IFA005, and necessary extensions/enhancements particular to managing resources in the WAN

IFA032 May-2018 Completed

Issues

List of issues raised based on the feature implementation.

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

Security Considerations

List of security considerations implied by the feature.

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: open		 SOL003 Dec. 2019 Ongoing
002 Specification of multi-site connectivity support in SOL005:
- Add specification for Multi-Site Connectivity Services: NFVSOL(19)000734. Status: open		 SOL005 Dec. 2019 Ongoing
003 Specification of multi-site connectivity support in SOL descriptors:
- SOL001ed331 FEAT10 Add specification for Multi-Site Connectivity Services: NFVSOL(19)000792. Status: open.
SOL001, SOL006 Dec. 2019 Not started
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.
- TBD		 SOL017 Dec. 2019 Ongoing
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.
- TBD		 SOL017 Feb. 2020 Ongoing
007 Profiling of TAPI stage 3 solutions addressing IFA032 requirements:
- TAPI Overview: NFVSOL(19)000605r2. Status: approved at SOL#115.
- TBD		 SOL017 Feb. 2020 Ongoing

FEAT11: NFV_M&M (NFV-MANO management)

Overview

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

Implementation Plan

ID Action Impacted WI(s) Target completion Status
001 Specify high-level requirement for the NFV Architectural Framework to support the management of NFV-MANO functional entities.

Contributions:
- CR draft: NFVIFA(17)0001065 status: FEAT AGREED at IFA#79
- IFA010 megaCR FEAT11 on NFV-MANO management: NFVIFA(18)000576 Status: APPROVED at IFA#104		 IFA010 Nov-2017 Completed
002 Specify a requirement set for the NFVO, the VNFM, as well as the VIM as a managed entity to support NFV-MANO fault, performance, configuration and information, state and log management by a managing entity.

Contributions:
CR draft: NFVIFA(17)0001066 status: FEAT AGREED at IFA#79
- IFA010 megaCR FEAT11 on NFV-MANO management: NFVIFA(18)000576 Status: APPROVED at IFA#104		 IFA010 Nov-2017 Completed
003 Skeleton, scope and introduction description for the new deliverable.

Contributions:
- Skeleton overview/draft: NFVIFA(17)0001067r1 Status: for discussion and NOTED
- Skeleton: NFVIFA(18)000009r1 Status: APPROVED at IFA#83
- Scope: NFVIFA(18)000046 status: APPROVED at IFA#84
 IFA031 Nov-2017 Completed
004 Add description of the general framework and interfaces for NFV-MANO management using as a reference “Solution D” and “Solution E” descriptions available in clauses 7.1.4 and 7.1.5 of ETSI GR NFV-IFA 021.

Contributions:
- NFVIFA(17)0001068 status: APPROVED at IFA#79
- Relationship NFV-MANO services and interfaces: NFVIFA(18)000351 status: APPROVED at IFA#100		 IFA031 Nov-2017 Completed
005 Specify a requirement set for the different interfaces to be supported, which include:
- NFV-MANO fault management interface
- NFV-MANO performance management interface
- NFV-MANO configuration and information management interface
- NFV-MANO state management interface, and
- NFV-MANO log management interface.

Contributions:
- Requirement set: NFVIFA(17)0001069 Status: APPROVED at IFA#79
- Overview and conventions: NFVIFA(18)000085 Status: APPROVED at IFA#87		 IFA031 Dec-2017 Completed
006 Specify the NFV-MANO functional entity information elements that will be reused in multiple interface definitions using as a reference the “Solution A” description available in clause 7.1.1 of ETSI GR NFV-IFA 021.

Contributions:
- For configuration and information mgmt: NFVIFA(18)000015r4 Status: APPROVED at IFA#84
- For performance mgmt: NFVIFA(18)000047r1 Status: APPROVED at IFA#84
- For state mgmt: NFVIFA(18)000086r3 Status: APPROVED at IFA#89
- For fault mgmt: NFVIFA(18)000215r2 Status: APPROVED at IFA#93
- For log mgmt: NFVIFA(18)000219r3 Status: APPROVED at IFA#98		 IFA031 Dec-2017 Completed
007 Specify the interface for NFV-MANO configuration management using as a reference the “Solution F” description in clause 7.1.6.5 of ETSI GR NFV-IFA 021.

Contributions:
- Configuration I/F and related IE: NFVIFA(18)000015r4 Status: APPROVED at IFA#84
- Clause 6.2.3 adding filter for QueryConfigInfo operation: NFVIFA(18)000498 Status: APPROVED at IFA#103		 IFA031 Jan-2018 Completed
008 Specify the interface for NFV-MANO performance management using as a reference the “Solution F” description available in clause 7.1.6.4 of ETSI GR NFV-IFA 021.

Contributions:
- Performance I/F and related IE: NFVIFA(18)000047r1 Status: APPROVED at IFA#84		 IFA031 Jan-2018 Completed
009 Specify the interface for NFV-MANO fault management using as a reference the “Solution F” description available in clause 7.1.6.3 and the fault reporting information modelling in “Solution B” in clause 7.1.2 of ETSI GR NFV-IFA 021.

Contributions:
-Fault I/F and related IE: NFVIFA(18)000215r2 Status: APPROVED at IFA#93		 IFA031 Feb-2018 Completed
010 Specify the interface for NFV-MANO state management using as a reference the “Solution F” description available in clause 7.1.6.6.

Contributions:
- State I/F and related IE: NFVIFA(18)000086r3 Status: APPROVED at IFA#89		 IFA031 Feb-2018 Completed
011 Specify the interface for NFV-MANO log management using as a reference the “Solution F” description available in clause 7.1.6.7.

Contributions
- Log I/F and related IE: NFVIFA(18)000219r3 Status: APPROVED at IFA#98		 IFA031 Mar-2018 Completed
012 Specify the definitions of performance metrics using as a reference the “Solution C” description available in clause 7.1.3 of ETSI GR NFV-IFA 021.

Contributions:
- Performance measurement definitions template: NFVIFA(18)000225r2 Status: APPROVED at IFA#94
- Measured objects: NFVIFA(18)000226r1 Status: APPROVED at IFA#94
- NFV-MANO entity resource measurements: NFVIFA(18)000227r1 Status: APPROVED at IFA#94
- Managed objects for performance measurements: NFVIFA(18)000292 Status: APPROVED at IFA#96
- NFV-MANO service measurements: NFVIFA(18)000293 Status: APPROVED at IFA#96
- NFV-MANO interface producer measurements: NFVIFA(18)000294r3 Status: APPROVED at IFA#98
- NFV-MANO interface consumer measurements: NFVIFA(18)000295r3 Status: APPROVED at IFA#98
- Additional managed objects: NFVIFA(18)000350r1 Status: APPROVED at IFA#100		 IFA031 Mar-2018 Completed
013 Resolution of editor's notes and final review of the document draft.

Contributions:
- Clause 7 EN resolution dependency state information: NFVIFA(18)000405 Status: APPROVED at IFA#100
- Clause 7 EN resolution MANO configuration information element: NFVIFA(18)000406r1 Status: APPROVED at IFA#100
- Clause 7 EN resolution list of interfaces: NFVIFA(18)000434 Status: APPROVED at IFA#100
- Clause 6, 7, and 8 EN resolution on PmJob and Threshold Objects: NFVIFA(18)000436 Status: APPROVED at IFA#100
- Clause 8.2 adding ManoInterfaceConsumer measured object NFVIFA(18)000437r1 Status: APPROVED at IFA#100
- Clause 8 EN resolution PM description improvements: NFVIFA(18)000438r1 Status: APPROVED at IFA#100
- Adding Annex for information flows with flow related to configuration: NFVIFA(18)000449 Status: APPROVED at IFA#100
- Clause 6.2.3 adding filter for QueryConfigInfo operation: NFVIFA(18)000498 Status: APPROVED at IFA#103
- Clause 5 and 6 adding query subscriptions operations: NFVIFA(18)000499 Status: APPROVED at IFA#103
- Clause 6 EN resolution aligning terminate subscription operation: NFVIFA(18)000500 Status: APPROVED at IFA#103
- Clause 7 EN resolution information specific info objects: NFVIFA(18)000501 Status: APPROVED at IFA#103
- Clause 6 and 7 EN resolution log report condition and location: NFVIFA(18)000502 Status: APPROVED at IFA#103
- Clause 7.2.10 EN resolution ManoService and ManoInterface: NFVIFA(18)000544 Status: APPROVED at IFA#104
- Clause 7.2.4 EN resolution apiEndpoint: NFVIFA(18)000545r2 Status: APPROVED at IFA#104
- Clause 3 adding definitions and abbreviations: NFVIFA(18)000528r3 Status: APPROVED at IFA#104
- Clause 4.3 and 7.2, update description and clarifications of NFV-MANO service and interface: NFVIFA(18)000543r2 Status: APPROVED at IFA#104
- Clause 8 EN resolution and improvements to workflow measurements: NFVIFA(18)000572 Status: APPROVED at IFA#104
- Clause 8 correcting measurement unit: NFVIFA(18)000573 Status: APPROVED at IFA#104
- General consistency review: NFVIFA(18)000574 Status: APPROVED at IFA#104
- Multiple clauses deletion guideline EN: NFVIFA(18)000575 Status: APPROVED at IFA#104
- Clause 7.3.2 Change later specification statement: NFVIFA(18)000623 Status: APPROVED at IFA#104
- General consistency review for IFA031 v0.5.0: NFVIFA(18)000677 Status: APPROVED at IFA#107
- Clause 5 Consistency review alignment interface reqs: NFVIFA(18)000678 Status: APPROVED at IFA#107
- Clause 7 generalize IE clauses: NFVIFA(18)000679 Status: APPROVED at IFA#107
- Clause 7 Consistency review missing mandatory statements for notifications: NFVIFA(18)000680 Status: APPROVED at IFA#107
- Clause 7 Consistency review writable attributes: NFVIFA(18)000681r1 Status: APPROVED at IFA#107
- Clauses 5 and 7 Clean-up related heartbeat functionality and addressing and EN: NFVIFA(18)000682 Status: APPROVED at IFA#107		 IFA031 May-2018 Completed
014 Review of security aspects. Security-related editor's notes are available throughout the IFA031 GS draft. The contributions needed to resolve those editor's notes which are specific to security topics will be listed here.

Contributions:
- Clause 9 security considerations: NFVIFA(18)000538r2 Status: APPROVED at IFA#108
- Multiple clauses EN resolution consumer and securityInfo: NFVIFA(18)000578r1 Status: APPROVED at IFA#104		 IFA031 Jun-2018 Completed

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

Issues

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

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

Other issues:

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

Security Considerations

List of security considerations implied by the feature.

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

FEAT15: VNF Snapshotting

Overview

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

Stage 2 Implementation Plan

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

Stage 3 Implementation Plan

ID Action Impacted WI(s) Target completion Status
001 Specification of VNF snapshot operations in the VNF LCM API of SOL003:
- Adding snapshot operations and flows: NFVSOL(18)000638r1. Status: approved
- Adding snapshot related resources and methods NFVSOL(18)000639r1. Status: approved
- Adding snapshot related data types: NFVSOL(18)000640r1. Status: approved
- Adding revert snapshot operation: NFVSOL(19)000249. Status: approved
- Fixes to the create VNF snapshot task: NFVSOL(19)000298r1. Status: approved
- Fixes to VNF snapshot data types: NFVSOL(19)000299. Status: approved
- Improving the snapshot creation process: NFVSOL(19)000353r2. Status: approved		 SOL003 Dec. 2019 Clompleted
002 Specification of VNF snapshot operations in the VNF LCM API of SOL002 (mostly mirroring SOL003):
- Adding snapshot operations, flows, resources and data types: NFVSOL(19)000233. Status: approved
- Adding snapshot operations, flows, resources and data types related to revert to snapshot: NFVSOL(19)000339. Status: approved
- Mirror of 299: fixes to VNF snapshot data types: NFVSOL(19)000518. Status: approved
- Mirror of 353r2: Improving snapshot creation process: NFVSOL(19)000519. Status: approved
- Bug fix on top of 233 and 339: NFVSOL(19)000520. Status: approved		 SOL002 Dec. 2019 Completed
003 Specification of VNF snapshot operations in the NS LCM API of SOL005:
- Adding snapshot operations and data types as part of NS LCM: NFVSOL(19)000252r1. Status: approved
- Data types for DeleteVnfSnapshotData and RevertVnfToSnapshotData: NFVSOL(19)000335. Status: approved		 SOL005 Dec. 2019 Ongoing
004 Specification of VNF snapshot package operations in the SOL003:
- New clause for the VNF Snapshot Pkg API: NFVSOL(19)000288r1. Status: approved
- Adding resource structure and methods for VNF Snapshot Pkg API: NFVSOL(19)000289r1. Status: approved
- Flows, resource, methods and data types for VNF snapshot pkg mgmt creation: NFVSOL(19)000290. Status: approved
- Flows, resource, methods and data types for VNF snapshot pkg mgmt query, update and delete: NFVSOL(19)000291r1. Status: approved
- Flows, resource, methods and data types for VNF snapshot pkg mgmt upload and fetch: NFVSOL(19)000292r1. Status: approved
- Flows, resource, methods and data types for VNF snapshot pkg mgmt fetch artifact: NFVSOL(19)000293. Status: approved
- Flows, resource, methods and data types for VNF snapshot pkg mgmt build: NFVSOL(19)000294r1. Status: approved
- Flows, resource, methods and data types for VNF snapshot pkg mgmt extract: NFVSOL(19)000354r1. Status: approved		 SOL003 Dec. 2019 Completed
005 Specification of the VNFC snapshot package management interface in SOL002:
- TBD		 SOL002 Dec. 2019 Not started
006 Specification of the VNF snapshot package management interface in SOL005:
- TBD		 SOL005 Dec. 2019 Not started
007 Specification of the VNF snapshot related operations in the VNFD and NSD of SOL001:
- TBD		 SOL001 Dec. 2019 Not started
008 Specification of the VNF snapshot related operations in the VNFD and NSD of SOL006:
- TBD		 SOL006 Dec. 2019 Not started
009 Specification of the VNF snapshot packaging:
- SOL010 skeleton: NFVSOL(18)000599. Status: approved
- SOL010 scope: NFVSOL(18)000600. Status: approved
- Adding references:
-- NFVSOL(18)000601. Status: approved
-- NFVSOL(18)000648. Status: approved

- Definitions and concepts:
-- NFVSOL(19)000122r1. Status: approved
-- NFVSOL(18)000719r3. Status: open
-- NFVSOL(19)000258. Status: open

- High-level VNF snapshot package format and structure requirements (clause 4.1 and 4.2):
-- NFVSOL(18)000646. Status: approved
-- NFVSOL(18)000647r3. Status: approved

- VNF snapshot package file contents (clause 4.3):
-- NFVSOL(19)000238r1. Status: approved
-- NFVSOL(19)000244r2. Status approved
-- NFVSOL(19)000056. Status: open

- Security aspects of VNF snapshot package:
-- TBD

- Examples and annexes:
-- NFVSOL(18)000748r3. Status: open		 SOL010 Dec. 2019 Ongoing

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT12: Enhancement support for MEC in NFV deployments

Overview

Feature Prime Uwe Rauschenbach, Nokia
Feature description Update to selected NFV interfaces. The intent is to define extensions which can be used to specify how ETSI MEC can be deployed in an NFV environment, allowing to run MEC applications on the NFVI besides

VNFs, and re-using ETSI NFV MANO components to perform common MANO tasks on the MEC applications.

3 parts:

  • Small Os-Ma enhancements (to be started, waiting for MEC requirements)
  • Small Ve-Vnfm enhancements (finalized, can re-use LCM coordination interface that has been defined as part of updating FEAT15 in IFA008ed321)
  • Support for Non-MANO artifact sets in VNF package (finalized IFA011/SOL004 ed251)
Target Release Release 3 (2019)
Impacted WIs IFA013, IFA008, IFA011, SOL005, SOL002, SOL004
MegaCRs For part 3: Related content already included in Rel 2 maintenance (V 2.4.1)

For part 2

For part 1

Related/Dependent Features FEAT15 (LCM coordination interface that is part of VNF Snapshot)
Status Ongoing (70% complete)
Contributions All feature contributions
  • NFVIFA(17)000900r3_IFA011ed241_3rd_party_VNF_Package_extensions
  • NFVSOL(17)000585r3_SOL004_non_MANO_artifact_sets
  • NFVIFA(18)0001024r2_IFA008ed321_-_Remove_ConfirmVnfSnapshot__Add_LCM_Coordinatio

Agreed content

  • NFVIFA(17)000900r3_IFA011ed241_3rd_party_VNF_Package_extensions
  • NFVSOL(17)000585r3_SOL004_non_MANO_artifact_sets
  • NFVIFA(18)0001024r2_IFA008ed321_-_Remove_ConfirmVnfSnapshot__Add_LCM_Coordinatio
Feature team Uwe Rauschenbach, Nokia

Yang Xu, Huawei

Pekka Kuure, Nokia

Anatoly Andrianov, Nokia

Last Updated 2019-02-18

Implementation Plan

Items to consider in the implementation plan

  • Detailed description what has to be done in which work item.
  • Timeplan of when the team plans to conclude a particular action in the implementation plan.
ID Action Impacted WI(s) Target completion Status
001 Add needed MEC extensions to IFA013 (placement control). IFA013 tbd Open
002 Add needed MEC extensions to SOL005 (placement control). SOL005 tbd Open
003 Add requirement for 3rd party VNF package extension mechanism to IFA011. IFA011 Feb 2018 Complete
004 Add specification for 3rd party VNF package extension mechanism to SOL004. SOL004 Feb 2018 Complete
005 Add needed MEC extensions to IFA008 (graceful termination). IFA008 Feb 2019 Complete, pending MEC confirmation
006 Add needed MEC extensions to SOL002 (to allow standardizing graceful termination). SOL002 tbd Open

Issues

Delay on MEC side in providing requirements.

Security Considerations

List of security considerations implied by the feature.

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
MegaCRs TODO, will be based on the IFA034 report
Related/Dependent Features NA
Status Ongoing 20%
Contributions
Feature team Abinash Vishwakarma (Netcracker)

Janusz, Pieczerak, Orange

Etienne, Steinert, Orange

Oliver, Le Grand, Orange

Anne-Marie Praden, Gemalto

Martin, Liepert, Gemalto

Last update 2019-04-16

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

IFA010: NFVIFA(19)000480r8 Approved by email on July 15
IFA014: NFVIFA(19)000526r6 Approved by email on July 15

Stage 3: <tbd>

Related/Dependent Features N/A
Status Stage 2: Approved in IFA#160; MegaCR Index available in NFVIFA(19)000746

Stage 3: Not started

Contributions All feature contributions
Agreed content
Feature team Shaoji Ni (Huawei)
Maria Toeroe(Ericsson)
Gerald Kunzmann (DOCOMO)
Stefan Arntzen (Huawei)
Janusz Pieczerak (Orange)
Chidung Lac (Orange)
Last Updated 2019-07-16

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(18)000970 Status: replaced by NFVIFA(19)000402r1

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(18)0001027r1 Status: Agreed FEAT (IFA#133)

NFVIFA(19)000274r1] Status: Noted, replaced by NFVIFA(19)000306 (IFA#144)

NFVIFA(19)000296r1 Status: Noted (IFA#145)

NFVIFA(19)000306r5 Status: Agreed FEAT (IFA#150)

NFVIFA(19)000307r7 Status: Agreed FEAT (IFA#149)

NFVIFA(19)000309r2 Status: Agreed FEAT (IFA#148)

NFVIFA(19)000310r5 Status: Agreed FEAT (IFA#148)

NFVIFA(19)000311r2 Status: Agreed FEAT (IFA#148)

NFVIFA(19)000482r1 Status: Agreed FEAT (IFA#154)

NFVIFA(19)000504r1 Status: Withdrawn

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

NFVIFA(19)000357r3 Status: Withdrawn

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 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 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.
- Enhance NFV-MANO capabilities to support container technologies based on DGR/NFV-IFA029.
- Enhance NFV-MANO capabilities for container management and orchestration
- Enhance information model for containerized VNFs both using bare metal or nested virtualization technologies

Target Release Stage 2 Step 1: Release 4 Drop #1 (after NFV#31e, October 2020)
Stage 2 Step 2: Release 4 Drop #2 (after NFV#32e, January 2021)
Stage 3: Release 4 (target date tbd)
Impacted WIs Stage 2: IFA007, IFA008, IFA010, IFA011, IFA013, IFA014

Stage 3: tbd

MegaCRs Stage 2 Step 1:
IFA010ed411 MegaCR NFVIFA(20)000478r2 (Approved)
New edition IFA010ed411

IFA011ed411 MegaCR NFVIFA(20)000479r6 (Approved)
IFA011ed411 Additional CR NFVIFA(20)000442r5 (Approved)
New edition IFA011ed411
Stage 2 Step 2:
IFAyyy MegaCR NFVIFA(19)000yyy (CR Status)


Stage 3:
SOLzzz MegaCR NFVSOL(20)000zzz (CR Status)

Related/Dependent Features FEAT19 – NFV-Conn
FEAT23 – MANO-SBA
New Specification Stage 2 Step 1:
DGS/NFV-IFA040 - Requirements for service interfaces and object model for OS container management and orchestration specification

Stage 2 Step 2:
DGS/NFV-IFA036 - Specification of requirements for the management and orchestration of container cluster nodes

Stage 3: tbd

Status

Stage 2 Step 1: Completed
Stage 2 Step 2: Ongoing (25% completed)
Stage 3: Waiting for Stage 2

Contributions All feature contributions
Feature team Stage 2: Ulrich Kleber (Huawei Technologies Co.,Ltd)
Jörg Aelken (Ericsson LM)

Stage 3: Name (Company)

Last Updated 2020-11-09

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 WI(s) Target completion Status
FEAT17 Stage 2 - Step 1
ST2-001 Skeleton, scope, and term definitions for IFA040 (Clauses 1, 2, 3)

CR drafts:
NFVIFA(19)000803r2 (Approved)
NFVIFA(19)000804r1 (Approved)
NFVIFA(19)000844r2 (Approved)
NFVIFA(19)000880 (Approved)
NFVIFA(20)000019 (Approved)
NFVIFA(20)000087 (Approved)
NFVIFA(20)000150 (Approved)

 IFA040 October - 2019 Complete
ST2-002 Overview and framework for OS container management and orchestration (Clause 4)

CR drafts:
NFVIFA(19)000847r2 (Approved)
NFVIFA(19)000849r2 (Approved)
NFVIFA(20)000076r1 (Approved)
NFVIFA(20)000149 (Approved)
NFVIFA(20)000175r2 (Approved)

 IFA040 November - 2019 Complete
ST2-003 Skeleton and scope for IFA036 (Clause 1)

CR drafts:
NFVIFA(19)000845r1 (Approved)
NFVIFA(19)000846 (Approved)
NFVIFA(19)000893 (Approved)
NFVIFA(19)000945r3 (Approved)
NFVIFA(20)000469r4 (Approved)

 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:
NFVIFA(19)000499r17 (FEAT agreed)
NFVIFA(20)000063r2 (FEAT agreed)
NFVIFA(20)000077r1 (FEAT agreed)
NFVIFA(20)000170r1 (FEAT agreed)
NFVIFA(20)000212r5 (FEAT agreed)
NFVIFA(20)000213r4 (FEAT agreed)
NFVIFA(20)000395r2 (FEAT agreed)
NFVIFA(20)000434r2 (FEAT agreed)
NFVIFA(20)000442r5 (Approved)

 IFA011 February - 2020 Complete
ST2-005 OS container NFV object model (Clause 5)

CR drafts:
NFVIFA(19)000870 (Approved)
NFVIFA(19)000873r5 (Approved)
NFVIFA(19)000909 (Approved)
NFVIFA(19)000913r1 (Approved)
NFVIFA(19)000914r2 (Approved)
NFVIFA(19)000920r1 (Approved)
NFVIFA(19)000924r1 (Approved)
NFVIFA(20)000075 (Approved)
NFVIFA(20)000182r2 (Approved)
NFVIFA(20)000190r1 (Approved)

 IFA040 November - 2019 Complete
ST2-006 Terminology and overview of management and orchestration of CIS cluster nodes (Clauses 3 and 4)

Concept discussions:
NFVIFA(20)000361r2 (Noted)
NFVIFA(20)000456r1 (Noted)

CR drafts:
NFVIFA(20)000520r3 (Approved)
NFVIFA(20)000522r3 (Approved)
NFVIFA(20)000523r2 (Approved)
NFVIFA(20)000524r1 (Approved)
NFVIFA(20)000525r3 (Approved)
NFVIFA(20)000558r2 (Approved)
NFVIFA(20)000688r1 (Approved)
NFVIFA(20)000697r1 (Approved)
NFVIFA(20)000730r1 (Approved)

IFA036 November - 2020 Ongoing
ST2-007 Specify the functional requirements for the CISM function

CR drafts:
NFVIFA(20)000020 (FEAT agreed)
NFVIFA(20)000025 (FEAT agreed)
NFVIFA(20)000026r1 (FEAT agreed)
NFVIFA(20)000027 (FEAT agreed)
NFVIFA(20)000028r2 (FEAT agreed)

 IFA010 January - 2020 Complete
ST2-008 Specify the functional requirements for the CIR function

CR drafts:
NFVIFA(20)000030 (FEAT agreed)
NFVIFA(20)000095r1 (FEAT agreed)

 IFA010 February - 2020 Complete
ST2-009 General CISM service requirements (Clauses 6.1, 6.2)

CR drafts:
NFVIFA(19)000974 (Approved)
NFVIFA(20)000015 (Approved)

 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:
NFVIFA(19)0001015r1 (Approved)
NFVIFA(20)000003r3 (Approved)
NFVIFA(20)000005r3 (Approved)
NFVIFA(20)000006r3 (Approved)
NFVIFA(20)000016 (Approved)
NFVIFA(20)000062 (Approved)
NFVIFA(20)000151r2 (Approved)
NFVIFA(20)000176 (Approved)
NFVIFA(20)000178r2 (Approved)

 IFA040 January - 2020 Complete
ST2-011 General CIR service requirements (Clauses 7.1, 7.2)

CR drafts:
NFVIFA(19)0001016r2 (Approved)

 IFA040 December - 2019 Complete
ST2-012 OS container image management service interface requirements (Clause 7.3)

CR drafts:
NFVIFA(19)0001016r2 (Approved)
NFVIFA(20)000062 (Approved)
NFVIFA(20)000094r1 (Approved)

 IFA040 January - 2020 Complete
ST2-013 Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CISM function

CR drafts:
NFVIFA(20)000228r2 (FEAT agreed)

 IFA010 March - 2020 Complete
ST2-014 Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CIR function

CR drafts:
NFVIFA(20)000227 (FEAT agreed)

 IFA010 March - 2020 Complete
ST2-015 Extend the VNFM functional requirements for consuming the management service interfaces exposed by the CISM function

CR drafts:
NFVIFA(20)000238 (FEAT agreed)
NFVIFA(20)000241 (FEAT agreed)
NFVIFA(20)000264r1 (FEAT agreed)
NFVIFA(20)000356r1 (FEAT agreed)

 IFA010 March - 2020 Complete
FEAT17 Stage 2 - Step 2
ST2-016 Enhance the information models of the Or-Vnfm interfaces for OS container management and orchestration

CR drafts:
NFVIFA(20)000357r1 (FEAT agreed)
NFVIFA(20)000381 (FEAT agreed)
NFVIFA(20)000394r1 (FEAT agreed)
NFVIFA(20)000409r1 (FEAT agreed)
NFVIFA(20)000411r1 (FEAT agreed)
NFVIFA(20)000437 (FEAT agreed)
NFVIFA(20)000560 (FEAT agreed)
NFVIFA(20)000678r6 (FEAT agreed)
NFVIFA(20)000711r1 (FEAT agreed)
NFVIFA(20)000731r1 (FEAT agreed)

 IFA007 December - 2020 Ongoing
ST2-017 Enhance the information models of the Ve-Vnfm interfaces for OS container management and orchestration

CR drafts:
NFVIFA(20)000771 (Available)

 IFA008 December - 2020 Ongoing
ST2-018 Enhance the information models of the Os-Ma-nfvo interfaces for OS container management and orchestration

CR drafts:
NFVIFA(20)000410r1 (FEAT agreed)
NFVIFA(20)000706r3 (FEAT agreed)

 IFA013 December - 2020 Ongoing
ST2-019 Enhance the information models of the NSD for OS container management and orchestration

CR drafts:
NFVIFA(20)000471r4 (FEAT agreed)
NFVIFA(20)000719r1 (FEAT agreed)

 IFA014 December- 2020 Ongoing
ST2-020 Container cluster nodes management interface requirements (Clause 5)

CR drafts:
NFVIFA(20)000609r5 (Approved)
NFVIFA(20)000625r5 (Approved)

 IFA036 November - 2020 Ongoing
ST2-021 CIS Cluster NFV object model (Clause 6)

CR drafts:

IFA036 December - 2020 Open
ST2-022 CIS Cluster Node NFV object model (Clause 7)

CR drafts:

IFA036 December - 2020 Open
ST2-023 Analyse and if necessary enhance VNFD and its VDU information element with attributes/information elements related to cluster and node affinity

CR drafts:

IFA011 December - 2020 Open
ST2-024 Analyse and if necessary enhance NSD and constituent information elements with attributes/information elements related to cluster and node affinity

CR drafts:

IFA014 December - 2020 Open
ST2-025 Specify the functional requirements for the CCM function

CR drafts:

IFA010 January - 2021 Open
ST2-026 Add requirements on CIS cluster node management for the CISM function

CR drafts:

IFA010 January - 2021 Open
ST2-027 Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CCM function

CR drafts:

IFA010 January - 2021 Open
ST2-028 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 January - 2021 Open
ST2-029 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 January - 2021 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
ST3-001 tbd tbd tbd Open

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 Active work items: IFA026, IFA033, SEC019.

Future work items: consider whether SOL or TST items would be appropriate.

Existing work items: SEC009, SEC011, SEC012, SEC013.

MegaCRs tbd
Related/Dependent Features None
Status Ongoing (25% complete)
Contributions All feature contributions
Agreed content

(direct links to search-URLs to be added later)

Feature team Alex Leadbeater (Rapporteur), BT

Leslie Willis (Rapporteur), BT

Mark Shepherd, Tencastle

Last Updated 2018-10-19

Implementation Plan

ID Action Impacted WG(s) Target completion Status
001 Complete requirements in IFA026 IFA026 November 2018 Open
002 Map requirements from IFA026 into IFA033 and assign to each interface IFA026

IFA033

November 2018 Open
003 Complete all of IFA026 and identify all interfaces in IFA033 IFA026

IFA033

December 2018 Open
004 Complete IFA033 IFA0233 May 2019 Open

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT19: NFV-Conn

Overview

Feature Prime Name, Company, E-Mail
Feature description Short Description of the Feature
Target Release Stage 2: Release 3 (2018-X-X)

Stage 3: Release 3 (2019-X-X)

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 Add interface X in to IFA007. CR draft [LINK] IFA March-2018 Open

SOL

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

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.

FEAT20: Auto

Overview

Feature Prime Haitao XIA (Huawei), xiahaitao@huawei.com
Feature description - 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 2: Release 4 (2021-01-15) Study to be completed

Stage 3: Release 4 (202x-X-X)

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 FEAT07
FEATyy
New Specifcations Stage 2: none

Stage 3: SOLaaa

Status Stage 2: Ongoing (50% completed)

Stage 3: Not started

Contributions All feature contributions
Agreed content
Feature team Stage 2: Haitao XIA (Huawei)

Stage 3: Name (Company)

Last Updated 2020-09-29

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 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, NFVIFA(20)000017r1

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)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

Working in progress:

NFVIFA(20)000592 IFA041 5.3.1 5.4.1 Synchronize the use case list

NFVIFA(20)000622 5.3.x Use case on cross administrative domain management data analytics

NFVIFA(20)000651 4.3.3_TMF_Autonomous_Networks

NFVIFA(20)000652r1 5.5_Closed_loops

IFA July-2020 Ongoing
004 Analysis of key issues related to use cases in Clause 5.

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

Working in progress:

NFVIFA(20)000566r3 6.3.x Analytics reporting mechanism

NFVIFA(20)000591 5.4 6.4 Aligning terminology with IFA036 GS

NFVIFA(20)000593 6.4.x Desired state of the MCIO

NFVIFA(20)000594r1 6.4.x Namespace quota

NFVIFA(20)000623r1 6.3.x Input data for the MDA process

NFVIFA(20)000624r1 6.3.x Output data from the MDA process

IFA October-2020 Ongoing
005 Analysis of pontential architectural impacts on NFV-MANO. IFA December-2020 Not started
006 Recommendations and conclusion. IFA January-2021 Not started

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

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: TBD (Release 4 (2018-X-X))

Stage 3: TBD (Release 4 (2019-X-X))

Impacted WIs Stage 2: TBD (IFAxx, IFAyy, SOLzz)

Stage 3: TBD (SOLzz)

MegaCRs Stage 2:

TBD: IFAxxx MegaCR NFVIFA(18)000xxx (CR Status) IFAyyy MegaCR NFVIFA(18)000yyy (CR Status)

Stage 3:

TBD: SOLzzz MegaCR NFVSOL(19)000zzz (CR Status)

Related/Dependent Features FEAT17 on "Cloud-native VNF and container infrastructure management"

FEAT19 on "NFV connectivity"

New Specifcations Informative: DGR/NFV-IFA037

Stage 2: TBD Stage 3: TBD

Status Informative: ongoing

Stage 2: TBD Stage 3: TBD

Contributions All feature contributions
Agreed content
Feature team Informative: Joan Triay (DOCOMO)

Stage 2: Name (Company)

Stage 3: Name (Company)

Last Updated 2020-10-25

Informative work

IFA

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

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 TBD TBD TBD TBD

Stage 3 Implementation Plan

Items to consider in the implementation plan

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

SOL

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

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT22: M-Tenant

Overview

Feature Prime Ulrich Kleber, Huawei, Ulrich.kleber@huawei.com
Feature description Start with use cases where multiple users consume services from the same NFV-MANO environment and implement necessary enhancements in the NFV-MANO stack.
Target Release Stage 1: Release 4

Stage 2: Release 4 (2020-X-X)
Stage 3: Release 4 (2020-X-X)

Impacted WIs Stage 1: EVE018

Stage 2: tbd
Stage 3: tbd

MegaCRs Stage 2: IFAxxx MegaCR NFVIFA(18)000xxx (CR Status)

IFAyyy MegaCR NFVIFA(18)000yyy (CR Status)
Stage 3: SOLzzz MegaCR NFVSOL(19)000zzz (CR Status)

Related/Dependent Features FEATxx
FEATyy
New Specifcations Stage 1: EVE018

Stage 2: none
Stage 3: none

Status Stage 1: Ongoing (20% completed)

Stage 2: Not started Stage 3: Not started

Contributions All feature contributions
Agreed content
Feature team Stage 1: U.Kleber (Huawei)

Stage 2: Name (Company)
Stage 3: Name (Company)

Last Updated 2019-12-20

Stage 2 Implementation Plan

Items to consider in the implementation plan

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

IFA

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

SOL

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

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.

FEAT23: M-SBA

Overview

Feature Prime Name, Company, E-Mail
Feature description Short Description of the Feature
Target Release Stage 2: Release 3 (2018-X-X)

Stage 3: Release 3 (2019-X-X)

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 Add interface X in to IFA007. CR draft [LINK] IFA March-2018 Open

SOL

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

Stage 3 Implementation Plan

Items to consider in the implementation plan

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

SOL

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

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT24: VNF-OAM

Overview

Feature Prime Gerald Kunzmann, DOCOMO, kunzmann@docomolab-euro.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 3 (May 2020)

Stage 3: Release 3 (2020-X-X)

Impacted WIs Stage 2: IFAxx, IFAyy

Stage 3: SOLzz

MegaCRs Stage 2:

EVE019 GR

IFA0xx

Stage 3:

SOLzzz MegaCR NFVSOL(19)000zzz (CR Status)

Related/Dependent Features FEAT17: cloud-native VNF and NFV architecture PaaS
New Specifcations Stage 2: none

Stage 3: SOLaaa

Status Stage 2: Ongoing (10% completed)

Stage 3: Not started

Contributions All feature contributions
Agreed content
Feature team Stage 2: Bertrand Souville (DOCOMO)

Stage 3: Name (Company)

Last Updated 2020-01-13

Stage 2 Implementation Plan

Items to consider in the implementation plan

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

IFA

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

SOL

ID Action Impacted WG(s) Target completion Status
001 Add interface X in to SOL001. CR draft [LINK] SOL March-2020 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
  • VNF package should contain references to dependent functions or services, which are machine readable and can be bound automatically to the particular VNF at deployment time into the test, staging, production environment.
  • VNF package should contain a testing section with various information concerning testing and DevOps
  • VNF Package should contain acceptance test descriptions.
  • VNF Package should contain acceptance test code that can be executed automatically after deployment into the various environments.
  • VNF Package should contain information about a test execution framework what is capable to execute the test code included in the VNF Package.
  • VNF Package should contain a reference to the acceptance test results of the VNF Provider.
  • VNF Package should contain information about the operator environment, in which it makes sense to test.
 IFA011 2nd Half-2020 Open
002 VNF should support to specify the test mode via configuration interface between VNFM and VNF IFA 2nd Half-2020 Open
003 When a common test framework is used , it's recommended that VNF should support standardized test API IFA 1st Half-2021 Open

SOL

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

Stage 3 Implementation Plan

Items to consider in the implementation plan

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

SOL

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

Issues

List of issues raised based on the feature implementation.

Security Considerations

List of security considerations implied by the feature.

FEAT26: Policy Management Models

Overview

Feature Prime Chen Wang, China Mobile, wangchenyj@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 Stage 2: Release 4 (2021-04-15) Study to be completed

Stage 3: Release 4 (202x-X-X)

Impacted WIs Stage 2: IFA005/006/007/008/013/030

Stage 3: SOL012

MegaCRs Stage 2:

Stage 3:

Related/Dependent Features FEAT07
New Specifcations Stage 2: IFA042

Stage 3:

Status Stage 2: Ongoing(40% completed)

Stage 3: Not started

Contributions All feature contributions
Agreed content
Feature team Stage 2: Chen Wang (China Mobile)

Stage 3: Name (Company)

Last Updated 2020-10-09

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 (IFA041) draft introducing the skeleton and the scope.

Accepted contributions:

NFVIFA(20)000553r2

IFA 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

NFVIFA(20)000621r1

IFA November-2020 Ongoing
003 NFV-MANO policy model potential requirements analysis

Analysis of existing SDOs and Open Source Community policy models

IFA January-2021 Ongoing
004 Analysis and Recommendations IFA Feburary-2021 Not started

SOL

ID Action Impacted WG(s) Target completion Status

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

Issues

List of issues raised based on the feature implementation.

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.

ID Name Status Contact Descirption Contributions
ENH01.xx New security enhancement {Proposal,Under development, Completed, Closed} Foo Bar (ACME) <foo.bar@acme.org> A short description of the feaure
  • List
  • of
  • related
  • CRs

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 Status Contact Description Contributions
ENH02.01 NFV-MANO enhancement with SDN-based networking Under development
Wang Ruixue, <wangruixue@chinamobile.com>
Li Shitao,<lishitao@huawei.com>
This new enhancement proposes to enhance the NFV-MANO functionality related to virtualised network management, lifecycle management and template information model to support the integration of SDN-based network in the framework of NFV-MANO during the timeframe of Release 4.

This work suggests to specify the SDN-based network resources in the NSD and VNFD model in order to use the different type of network to provision the network connection requirements at the design time.

This work also suggests to enhance Os-Ma-nfvo, Or-Vi and Or-Vnfm reference points in order to manage the lifecycle of the different type of network.

  • NFVIFA(19)000858r4 : feature proposal (accepted)
  • NFVIFA(19)000966r2: adding RD IE in IFA014, available
  • NFVIFA(19)0001018: new requirements to IFA010, FEAT Agreed (IFA#202)
  • NFVIFA(20)000240r2: adding new routing resource as a new type of network resources: FEAT Agreed (IFA#208)
  • NFVIFA(20)000239r1: discussion paper for adding routing resource, available
  • NFVIFA(20)000313r3: adding a new RoutingResorceData for describing a routing resource, FEAT Agreed (IFA#197)
  • NFVIFA(20)000314r3: adding the Routing resource in the Update Virtualised Network Resource operation, FEAT Agreed (IFA#197)
  • NFVIFA(20)000517r3: discussion paper for NSD model for supporting Routing resource: available
ENH02.02 NFV-MANO enhancement for NS feasibility check Under development Junichi Kawasaki <ju-kawasaki@kddi.com>, Kenichi Ogaki <ke-oogaki@kddi.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.

  • NFVIFA(20)000187r2: New enhancement proposal (accepted)
  • NFVIFA(20)000084a1r6: Discussion paper for option with extending existing operations (Noted)
  • NFVIFA(20)000084r7: Changes to InstantiateNsRequest and UpdateNsRequest (FEAT agreed)
  • NFVIFA(20)000332r3: Extending NsLcmOperationOccurrenceNotification (FEAT agreed)
  • NFVIFA(20)000372r2: Support for modifying schedule time of scheduled operation (FEAT agreed)
  • NFVIFA(20)000397r2: New requirements to IFA010 (FEAT agreed)
============= CRs for approval ========
  • NFVIFA(20)000662: IFA013ed421 MegaCR ENH02.02 NS feasibility check
  • NFVIFA(20)000397r2: New requirements to IFA010 (FEAT agreed)
ENH02.03 NFV-MANO enhancement with Data flow mirroring Under development 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.

  • NFVIFA(20)000402r3: New enhancement proposal (accepted)
  • NFVIFA(20)000491r7_ENH02.03_IFA010_release_4_enhancement_adding_new_requirement_to_NFVO （FEAT agreed）
  • NFVIFA(20)000492r7_ENH02_03_IFA005_release_4_enhancement_adding_new_requirement（FEAT agreed）
  • NFVIFA(20)000561r5_ENH02.03_IFA005_new parameters for Deletion of Data Flow Mirroring Job（FEAT agreed）
  • NFVIFA(20)000563r6_ENH02.03_IFA005_new parameters for Query of Data Flow Mirroring Job（FEAT agreed）
  • NFVIFA(20)000610r4_ENH02.03_IFA005_new parameters for updating of Data Flow Mirroring Job（FEAT agreed）
ENH02.04 Invariant identification of NSD constituents Not started 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.

Retrieved from "https://nfvwiki.etsi.org/index.php?title=Feature_Tracking&oldid=3682"