Feature Tracking: Difference between revisions
Martindenico (talk | contribs) |
No edit summary |
||
Line 3: | Line 3: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| Current mirror date: | | Current mirror date: 2023.06.12|| '''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 12: | Line 12: | ||
!Stage 1 | !Stage 1 | ||
!Stage 2 | !Stage 2 | ||
!Stage 3 | !Stage 3 (note 6) | ||
|- | |- | ||
|FEAT01: NFV-MANO Upgrades | |FEAT01: NFV-MANO Upgrades | ||
Line 19: | Line 19: | ||
|not started | |not started | ||
|- | |- | ||
|[[Feature Tracking#FEAT02: VNF software modification|FEAT02: VNF software modification]] | | style="background: gray;" |[[Feature Tracking#FEAT02: VNF software modification|FEAT02: VNF software modification]] | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|- | |- | ||
|[[Feature Tracking#FEAT03: NFVI software modification|FEAT03: NFVI software modification]] | | style="background: gray;" |[[Feature Tracking#FEAT03: NFVI software modification|FEAT03: NFVI software modification]] | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|- | |- | ||
|[[Feature Tracking#FEAT04: Host Reservation|FEAT04: Host Reservation]] | |[[Feature Tracking#FEAT04: Host Reservation|FEAT04: Host Reservation]] | ||
Line 33: | Line 33: | ||
|completed (Rel 3) | |completed (Rel 3) | ||
|completed (Rel 3) | |completed (Rel 3) | ||
See note 1. | |||
|- | |- | ||
|[[Feature Tracking#FEAT05 Network Slicing|FEAT05 Network Slicing]] | | style="background: gray;" |[[Feature Tracking#FEAT05 Network Slicing|FEAT05 Network Slicing]] | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|- | |- | ||
|[[Feature Tracking#FEAT06: Enhancement Network Service .28NS.29 Package|FEAT06: Enhancement Network Service (NS) Package]] | | style="background: gray;" |[[Feature Tracking#FEAT06: Enhancement Network Service .28NS.29 Package|FEAT06: Enhancement Network Service (NS) Package]] | ||
|n/a (part of Rel 2) | | style="background: gray;" |n/a (part of Rel 2) | ||
|n/a (part of Rel 2) | | style="background: gray;" |n/a (part of Rel 2) | ||
|n/a (part of Rel 2) | | style="background: gray;" |n/a (part of Rel 2) | ||
|- | |- | ||
|[[Feature Tracking#FEAT07: MANO Policy Management .28MANO PLC.29|FEAT07: MANO Policy Management (MANO_PLC)]] | | style="background: gray;" |[[Feature Tracking#FEAT07: MANO Policy Management .28MANO PLC.29|FEAT07: MANO Policy Management (MANO_PLC)]] | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|- | |- | ||
|[[Feature Tracking#FEAT08: Support of composite NS across multi-domain .28MANOMD NS.29|FEAT08: Support of composite NS across multi-domain (MANOMD_NS)]] | | style="background: gray;" |[[Feature Tracking#FEAT08: Support of composite NS across multi-domain .28MANOMD NS.29|FEAT08: Support of composite NS across multi-domain (MANOMD_NS)]] | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|- | |- | ||
|[[Feature Tracking#FEAT10: Mgmt .26 Connectivity Multi-Site Services .28MCMSS.29|FEAT10: Mgmt & Connectivity Multi-Site Services (MCMSS)]] | |[[Feature Tracking#FEAT10: Mgmt .26 Connectivity Multi-Site Services .28MCMSS.29|FEAT10: Mgmt & Connectivity Multi-Site Services (MCMSS)]] | ||
Line 60: | Line 61: | ||
See note 2. | See note 2. | ||
|- | |- | ||
|[[Feature Tracking#FEAT11: NFV M.26M .28NFV-MANO management.29|FEAT11: NFV_M&M (NFV-MANO management)]] | | style="background: gray;" |[[Feature Tracking#FEAT11: NFV M.26M .28NFV-MANO management.29|FEAT11: NFV_M&M (NFV-MANO management)]] | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|- | |- | ||
|[[Feature Tracking#FEAT12: Enhancement support for MEC in NFV deployments|FEAT12: Enhancement support for MEC in NFV deployments]] | | style="background: gray;" |[[Feature Tracking#FEAT12: Enhancement support for MEC in NFV deployments|FEAT12: Enhancement support for MEC in NFV deployments]] | ||
|n/a | | style="background: gray;" |n/a | ||
|completed (Rel 3). | | style="background: gray;" |completed (Rel 3). | ||
|completed (Rel 3). | | style="background: gray;" |completed (Rel 3). | ||
|- | |- | ||
|[[Feature Tracking#FEAT13: Report on Architectural enhancement for VNF License Management support and use of VNF licenses|FEAT13: Licensing]] | | style="background: gray;" |[[Feature Tracking#FEAT13: Report on Architectural enhancement for VNF License Management support and use of VNF licenses|FEAT13: Licensing]] | ||
|completed (Rel 4) | | style="background: gray;" |completed (Rel 4) | ||
| | | style="background: gray;" |completed (Rel 4) | ||
| | | style="background: gray;" |completed (Rel 4) | ||
|- | |- | ||
|[[Feature Tracking#FEAT15: VNF Snapshotting|FEAT15: VNF Snapshotting]] | | style="background: gray;" |[[Feature Tracking#FEAT15: VNF Snapshotting|FEAT15: VNF Snapshotting]] | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3). | | style="background: gray;" |completed (Rel 3). | ||
See note 1. | <s>See note 1.</s> | ||
|- | |- | ||
|[[Feature Tracking#FEAT16: Service Availability Level|FEAT16: Service Availability Level]] | | style="background: gray;" |[[Feature Tracking#FEAT16: Service Availability Level|FEAT16: Service Availability Level]] | ||
|n/a | | style="background: gray;" |n/a | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|completed (Rel 3) | | style="background: gray;" |completed (Rel 3) | ||
|- | |- | ||
|[[Feature Tracking#FEAT17: Cloud-Native VNFs and Container Infrastructure management|FEAT17: Cloud-Native VNFs and Container Infrastructure management]] | |[[Feature Tracking#FEAT17: Cloud-Native VNFs and Container Infrastructure management|FEAT17: Cloud-Native VNFs and Container Infrastructure management]] | ||
Line 94: | Line 95: | ||
|completed (Rel 3) | |completed (Rel 3) | ||
|completed:<br>architecture (Rel 3),<br>interfaces (Rel 4). | |completed:<br>architecture (Rel 3),<br>interfaces (Rel 4). | ||
See note 3. | <s>See note 3.</s> | ||
|not started | |not started | ||
|- | |- | ||
Line 138: | Line 139: | ||
|- | |- | ||
|[[Feature Tracking#FEAT26: Policy Management Models|FEAT26: Policy-models]] | |[[Feature Tracking#FEAT26: Policy Management Models|FEAT26: Policy-models]] | ||
|completed (Rel 4) | |||
|completed (Rel 4) | |completed (Rel 4) | ||
|ongoing (Rel 4) | |ongoing (Rel 4) | ||
|- | |- | ||
|[[Feature Tracking#FEAT27: NFV for vRAN|FEAT27: NFV for vRAN]] | |[[Feature Tracking#FEAT27: NFV for vRAN|FEAT27: NFV for vRAN]] | ||
Line 162: | Line 163: | ||
|not started | |not started | ||
|- | |- | ||
|FEAT31: Flexible VNF deployment | |[[Feature Tracking#FEAT31: Flexible VNF deployment|FEAT31: Flexible VNF deployment]] | ||
|ongoing (Rel 5) | |ongoing (Rel 5) | ||
|not started | |not started | ||
Line 187: | Line 188: | ||
|not started | |not started | ||
|- | |- | ||
|[[Feature Tracking#ENH02: Special technical enhancements|ENH02: Special technical enhancements]]<br>See note 4. | |[[Feature Tracking#ENH02: Special technical enhancements|ENH02: Special technical enhancements]] (Rel 4)<br>See note 4. | ||
|completed (Rel 4) | |completed (Rel 4) | ||
|completed (Rel 4) | |completed (Rel 4) | ||
| | |completed (Rel 4) | ||
|- | |||
|[[Feature Tracking#ENH02: Special technical enhancements|ENH02: Special technical enhancements]] (Rel 5)<br>See note 4. | |||
|none applied yet (Rel 5) | |||
|not started | |||
|not started | |||
|- | |- | ||
| colspan="4" |NOTE 1: The specification of other "non-core" parts of the feature is ongoing.<br>NOTE 2: The specification of the NFV-MANO APIs and NFV Descriptors is completed. Informative profiling of "protocol and data models" for the interfaces exposed by WIM is completed. Normative profiling of "protocol and data models" is ongoing.<br>NOTE 3: void.<br>NOTE 4: Concrete enhancement features and their status is available [[Feature Tracking#ENH02: Special technical enhancements|here]].<br>NOTE 5: Concrete security enhancement features and their status is available [[Feature Tracking#ENH01: Security enhancements|here]] | | colspan="4" |NOTE 1: The specification of other "non-core" parts of the feature is ongoing.<br>NOTE 2: The specification of the NFV-MANO APIs and NFV Descriptors is completed. Informative profiling of "protocol and data models" for the interfaces exposed by WIM is completed. Normative profiling of "protocol and data models" is ongoing.<br>NOTE 3: void.<br>NOTE 4: Concrete enhancement features and their status is available [[Feature Tracking#ENH02: Special technical enhancements|here]].<br>NOTE 5: Concrete security enhancement features and their status is available [[Feature Tracking#ENH01: Security enhancements|here]] | ||
NOTE 6: Detailed changes for SOL API are described in ETSI GS NFV-SOL 002 Annex E, ETSI GS NFV-SOL 003 Annex F and ETSI GS NFV-SOL 005. | |||
|} | |} | ||
* Overview of each feature: [https://docbox.etsi.org/isg/nfv/open/Other/ReleaseDocumentation Release Document] | |||
* Snapshot of Release 4 ed441/ed451 plan: [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000520r1_Status_tracking_of_feature_for_ed441.pptx NFVSOL(22)000520r1] and [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000944r1_Rel-4_feature_stage_2_status.pptx NFVIFA(22)000944r1] | |||
== Introduction == | == Introduction == | ||
Line 684: | Line 693: | ||
| '''Related/Dependent Features''' || N/A | | '''Related/Dependent Features''' || N/A | ||
|- | |- | ||
| '''Status''' || Completed. | | '''Status''' || '''Stage2:''' Completed. MegaCR Index available in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018/NFVIFA(18)000475r1_FEAT04_MegaCR_Index.docx NFVIFA(18)000475r1] | ||
'''Stage3:''' Completed. See Issues. | |||
MegaCR Index available in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018/NFVIFA(18)000475r1_FEAT04_MegaCR_Index.docx NFVIFA(18)000475r1] | |||
|- | |- | ||
| '''Contributions''' || '''Stage2:''' | | '''Contributions''' || '''Stage2:''' | ||
Line 701: | Line 709: | ||
| '''Feature team''' || Arturo Martin De Nicolas (Ericsson LM)<br />Bertrand Souville (DOCOMO Communications Lab.)<br />Joan Triay (DOCOMO Communications Lab.) | | '''Feature team''' || Arturo Martin De Nicolas (Ericsson LM)<br />Bertrand Souville (DOCOMO Communications Lab.)<br />Joan Triay (DOCOMO Communications Lab.) | ||
|- | |- | ||
| '''Last Updated''' || | | '''Last Updated''' || 2023-01-01 | ||
|} | |} | ||
Line 731: | Line 739: | ||
=== Issues === | === Issues === | ||
* Support host reservation when SOL014 supports reservation. | * <s>Support host reservation when SOL014 supports reservation.</s> -> resolved [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000165_SOL014e371_New_data_models_for_Compute_Resource_Reservation_.docx NFVSOL(22)000165] | ||
* Capacity mgmt of SOL014 is missing as [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000520r1_Status_tracking_of_feature_for_ed441.pptx NFVSOL(22)000521r1] | |||
=== Security Considerations === | === Security Considerations === | ||
Line 757: | Line 766: | ||
| '''Related/Dependent Features''' || After analysis and LS exchange with 3GPP no dependencies for the time frame of this feature are seen anymore. | | '''Related/Dependent Features''' || After analysis and LS exchange with 3GPP no dependencies for the time frame of this feature are seen anymore. | ||
|- | |- | ||
| '''Status''' || Completed | | '''Status''' || '''Stage2:''' Completed | ||
'''Stage3:''' Completed | |||
|- | |- | ||
| '''Reliability Review''' || Done in REL#270 on January 15, 2019 | | '''Reliability Review''' || Done in REL#270 on January 15, 2019 | ||
Line 763: | Line 773: | ||
| '''Security Review''' || Reviewed in SEC#139 on January 24, 2019 <br>See [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019/NFVIFA(19)000054r2_FEAT05_security_considerations.docx NFVIFA(19)000054r2_FEAT05_security_considerations.docx]<br>or [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2019/NFVSEC(19)000008r1_FEAT05_security_considerations.zip NFVSEC(19)000008r1_FEAT05_security_considerations.zip] | | '''Security Review''' || Reviewed in SEC#139 on January 24, 2019 <br>See [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019/NFVIFA(19)000054r2_FEAT05_security_considerations.docx NFVIFA(19)000054r2_FEAT05_security_considerations.docx]<br>or [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2019/NFVSEC(19)000008r1_FEAT05_security_considerations.zip NFVSEC(19)000008r1_FEAT05_security_considerations.zip] | ||
|- | |- | ||
| '''Contributions''' || Latest status on [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000100r9_FEAT05_Dashboard.pptx Feature Dashboard] | | '''Contributions''' || '''Stage2:''' | ||
Latest status on [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000100r9_FEAT05_Dashboard.pptx Feature Dashboard] '''Stage3:''' | |||
SOL001 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000159_SOL001ed351_FEAT05_Adding_priority_to_NSD.docx NFVSOL(21)000159] and [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//NFVSOL(19)000799r2_SOL001ed331_FEAT05_Adding_priority_to_NSD.docx NFVSOL(19)000799r2] SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000109r8_SOL005ed351_FEAT05_Flow_of_NS_LCM_operations_with_pre-emptio.zip NFVSOL(21)000109r8], [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000110r3_SOL005ed351_FEAT05_Introduction_of_the_Capacity_Shortage_Not.docx NFVSOL(21)000110r3], [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000111r4_SOL005ed351_FEAT05_Addition_of_priority_in_NS_data_types.docx NFVSOL(21)000111r4] and [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000283r1_SOL005ed351_FEAT05_Mirror_of_182_Add_enumeration_values_of_L.docx NFVSOL(21)000283r1] | |||
SOL006 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//NFVSOL(19)000854_SOL006ed331_FEAT05_Add_priority_in_NS.docx NFVSOL(19)000854]([https://forge.etsi.org/rep/nfv/SOL006/-/merge_requests/67 Issue#11]) and [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000112_SOL006ed351_FEAT05_Add_priority_in_NSD_IFA014.docx NFVSOL(21)000112]([https://forge.etsi.org/rep/nfv/SOL006/-/merge_requests/89 Issue#32]) | |||
|- | |- | ||
| '''Feature team''' || | | '''Feature team''' || | ||
Line 774: | Line 789: | ||
Gerald Kunzmann, DOCOMO Communications Lab<br> Stage 3/SOL WG: Arturo Martin de Nicolas | Gerald Kunzmann, DOCOMO Communications Lab<br> Stage 3/SOL WG: Arturo Martin de Nicolas | ||
|- | |- | ||
| '''Last Updated''' || | | '''Last Updated''' || 2023-01-01 | ||
|} | |} | ||
Line 1,084: | Line 1,099: | ||
| '''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 [https://docbox.etsi.org/ISG/NFV/05-CONTRIBUTIONS/2017//NFV(17)000247_IFA_to_IFA_Enhancement_NS_Package.docx NFV(17)000247]. | | '''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 [https://docbox.etsi.org/ISG/NFV/05-CONTRIBUTIONS/2017//NFV(17)000247_IFA_to_IFA_Enhancement_NS_Package.docx NFV(17)000247]. | ||
|- | |- | ||
| '''Target Release''' || same as DGS/NFV-SOL007 (1H-2019) | | '''Target Release''' || Release 2 | ||
<s>same as DGS/NFV-SOL007 (1H-2019)</s> | |||
|- | |- | ||
| '''Impacted WIs''' || IFA010, IFA012 (TBC), IFA013, and IFA014. <br> 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. | | '''Impacted WIs''' || '''Stage2''' | ||
IFA010, IFA012 (TBC), IFA013, and IFA014. <br> 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. | 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. | ||
'''Stage3''' | |||
SOL005, SOL007 | |||
|- | |- | ||
| '''Mega-CRs''' || | | '''Mega-CRs''' || N/A | ||
|- | |- | ||
| '''Related/Dependent Features''' || | | '''Related/Dependent Features''' || | ||
|- | |- | ||
| '''New Specification ''' || No new WI is expected in IFA WG. <br /> | | '''New Specification ''' || '''Stage2:''' | ||
No new WI is expected in IFA WG. <br />'''Stage3:''' | |||
Name of New Specification in SOL WG is [https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=54501 DGS/NFV-SOL007] (NSD file structure spec., based on NFVIFA(18)000174/NFVIFA(17)000879, | Name of New Specification in SOL WG is [https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=54501 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).]<br /> | NFVSOL(17)000711 and NFV(18)000066/NFV(17)000364; created on 2018-03-01 and approved on 2018-03-12).]<br /> | ||
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. <br /> | 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. <br /> | ||
WI Status [In Progress; to be completed by 1H-2019]. | <s>WI Status [In Progress; to be completed by 1H-2019].</s> | ||
|- | |- | ||
| '''Status''' || | | '''Status''' || '''Stage3:''' completed | ||
|- | |- | ||
| '''Contributions''' || [http://https://portal.etsi.org All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | | '''Contributions''' || '''Stage2:''' | ||
[http://https://portal.etsi.org All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | |||
'''Stage3:''' | |||
SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//NFVSOL(19)000567r5_SOL005ed271_NSD_archive_and_PNFD_archive_management_changes.zip NFVSOL(19)000567r5] | |||
new specfication SOL007 | |||
|- | |- | ||
| '''Feature team''' || Bhumip Khasnabish (ZTE) <br /> Haibin Chu (Ericsson)<br /> Yaoye Zhang (Huawei)<br /> Maopeng Zhang (ZTE)<br /> Lingli Deng (CMCC)<br /> | | '''Feature team''' || Bhumip Khasnabish (ZTE) <br /> Haibin Chu (Ericsson)<br /> Yaoye Zhang (Huawei)<br /> Maopeng Zhang (ZTE)<br /> Lingli Deng (CMCC)<br /> | ||
|- | |- | ||
| '''Last Updated''' || | | '''Last Updated''' || 2023-01-01 | ||
|} | |} | ||
Line 1,157: | Line 1,186: | ||
| '''Target Release''' || Release 3 drop 1 (2018-06) | | '''Target Release''' || Release 3 drop 1 (2018-06) | ||
|- | |- | ||
| '''Impacted WIs''' || IFA010 | | '''Impacted WIs''' || '''Stage2:''' | ||
IFA010, IFA013, IFA007, IFA008, IFA005, IFA006 <br />'''Stage3:''' | |||
SOL012 | |||
|- | |- | ||
| '''Mega-CRs''' || | | '''Mega-CRs''' || | ||
Line 1,165: | Line 1,197: | ||
IFA005 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000432r1_FEAT07_IFA005_MegaCR_Support_of_policy_management_interface.doc NFVIFA(18)000432r1] (Approved) <br> | IFA005 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000432r1_FEAT07_IFA005_MegaCR_Support_of_policy_management_interface.doc NFVIFA(18)000432r1] (Approved) <br> | ||
IFA006 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000433r1_FEAT07_IFA006_MegaCR_Support_of_policy_management_interface.doc NFVIFA(18)000433r1] (Approved) <br> | IFA006 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000433r1_FEAT07_IFA006_MegaCR_Support_of_policy_management_interface.doc NFVIFA(18)000433r1] (Approved) <br> | ||
IFA010 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000455r3_FEAT07_IFA010_MegaCR_Support_of_policy_management_interface.doc NFVIFA(18)000455r3] (Approved) | IFA010 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000455r3_FEAT07_IFA010_MegaCR_Support_of_policy_management_interface.doc NFVIFA(18)000455r3] (Approved) | ||
|- | |- | ||
| '''Related/Dependent Features''' || no dependency | | '''Related/Dependent Features''' || no dependency | ||
|- | |- | ||
| '''Status''' || Completed. MegaCR Index available in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000492r1_FEAT07_MegaCR_Index.docx NFVIFA(18)000492r1] <br> | | '''Status''' || '''Stage2:''' Completed. MegaCR Index available in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000492r1_FEAT07_MegaCR_Index.docx NFVIFA(18)000492r1] <br>'''Stage3:''' Completed. new specification SOL012 | ||
|- | |- | ||
| '''Contributions''' || [http://https://portal.etsi.org All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | | '''Contributions''' || [http://https://portal.etsi.org All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | ||
Line 1,175: | Line 1,207: | ||
| '''Feature team''' || Haitao Xia (Huawei) | | '''Feature team''' || Haitao Xia (Huawei) | ||
|- | |- | ||
| '''Last Updated''' || | | '''Last Updated''' || 2023-01-01 | ||
|} | |} | ||
Line 1,260: | Line 1,292: | ||
| '''Target Release''' || Release 3 drop 1 (2018-06) | | '''Target Release''' || Release 3 drop 1 (2018-06) | ||
|- | |- | ||
| '''Impacted WIs''' || IFA010 | | '''Impacted WIs''' || '''Stage2:''' | ||
IFA010, IFA030 (new deliverable) | |||
'''Stage3:''' | |||
new specification SOL011 | |||
|- | |- | ||
| '''Mega-CRs''' || IFA010 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000425r1_FEAT08_IFA010_MegaCR_Support_of_composite_NS_across_multi-do.doc NFVIFA(18)000425r1] (Approved) <br> | | '''Mega-CRs''' || IFA010 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000425r1_FEAT08_IFA010_MegaCR_Support_of_composite_NS_across_multi-do.doc NFVIFA(18)000425r1] (Approved) <br> | ||
Line 1,266: | Line 1,303: | ||
| '''Related/Dependent Features''' || no dependency | | '''Related/Dependent Features''' || no dependency | ||
|- | |- | ||
| '''Status''' || Completed | | '''Status''' || '''Stage2:''' Completed. MegaCR Index available in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000515r2_FEAT08_MegaCR_Index.docx NFVIFA(18)000515r2]. New deliverable IFA030GS Approved <br>'''Stage3:''' Completed. New specfication SOL011 | ||
New deliverable IFA030GS Approved <br> | |||
|- | |- | ||
| '''Contributions''' || [http://https://portal.etsi.org All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | | '''Contributions''' || [http://https://portal.etsi.org All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | ||
Line 1,273: | Line 1,309: | ||
| '''Feature team''' || Haitao Xia (Huawei)<br />Arturo Martin de Nicolas (Ericsson)<br />Bhumip Khasnabish (ZTE) | | '''Feature team''' || Haitao Xia (Huawei)<br />Arturo Martin de Nicolas (Ericsson)<br />Bhumip Khasnabish (ZTE) | ||
|- | |- | ||
| '''Last Updated''' || | | '''Last Updated''' || 2023-01-01 | ||
|} | |} | ||
Line 1,347: | Line 1,383: | ||
| '''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 | | '''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) <br /> '''Stage 3:''' | | '''Target Release''' || '''Stage 2:''' | ||
Release 3 drop 2 (2018-12) <br />'''Stage 3:''' | |||
Release 3 (without SOL014 and SOL019) | |||
Release 4 | |||
|- | |- | ||
| '''Impacted WIs''' || '''Stage 2:''' IFA005, IFA007, IFA010, IFA011, IFA013, IFA014, IFA022, IFA032 <br /> '''Stage 3:''' SOL014, SOL003, SOL005, SOL001, SOL006, SOL017 | | '''Impacted WIs''' || '''Stage 2:''' IFA005, IFA007, IFA010, IFA011, IFA013, IFA014, IFA022, IFA032 <br /> '''Stage 3:''' SOL014, SOL003, SOL005, SOL001, SOL006, SOL017, SOL019 | ||
|- | |- | ||
| '''Mega-CRs''' || '''Stage 2:'''<br />- IFA005 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)0001111r2_IFA005_MegaCR_FEAT010_Or-Vi_ref_point_interface_specificatio.docx NFVIFA(18)0001111r2]<br />- IFA007 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)0001112r4_IFA007_MegaCR_FEAT010_Or-Vnfm_ref_point_interface_specificat.zip NFVIFA(18)0001112r4]<br />- IFA010 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)0001107r2_IFA010_MegaCR_FEAT010__General_and_functional_requirements_f.docx NFVIFA(18)0001107r2]<br />- IFA013 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)0001110r4_IFA013_MegaCR_FEAT010_Os-Ma-Nfvo_specification_for_Multi-Sit.zip NFVIFA(18)0001110r4]<br />- IFA014 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)0001113r2_IFA014_MegaCR_FEAT010_Specify_parameters_for_the_NSD_file_re.docx NFVIFA(18)0001113r2] | | '''Mega-CRs''' || '''Stage 2:'''<br />- IFA005 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)0001111r2_IFA005_MegaCR_FEAT010_Or-Vi_ref_point_interface_specificatio.docx NFVIFA(18)0001111r2]<br />- IFA007 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)0001112r4_IFA007_MegaCR_FEAT010_Or-Vnfm_ref_point_interface_specificat.zip NFVIFA(18)0001112r4]<br />- IFA010 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)0001107r2_IFA010_MegaCR_FEAT010__General_and_functional_requirements_f.docx NFVIFA(18)0001107r2]<br />- IFA013 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)0001110r4_IFA013_MegaCR_FEAT010_Os-Ma-Nfvo_specification_for_Multi-Sit.zip NFVIFA(18)0001110r4]<br />- IFA014 MegaCR in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)0001113r2_IFA014_MegaCR_FEAT010_Specify_parameters_for_the_NSD_file_re.docx NFVIFA(18)0001113r2] | ||
Line 1,355: | Line 1,396: | ||
| '''Related/Dependent Features''' || N/A | | '''Related/Dependent Features''' || N/A | ||
|- | |- | ||
| '''New Specification''' || '''Stage 2:''' IFA032<br />'''Stage 3:''' SOL017, | | '''New Specification''' || '''Stage 2:''' IFA032<br />'''Stage 3:''' SOL017, SOL019 | ||
|- | |- | ||
| '''Status''' || '''Stage 2:''' Completed, MegaCR Index available in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)0001117r3_FEAT010_MegaCR_Index.docx NFVIFA(18)0001117r3]<br />'''Stage 3:''' | | '''Status''' || '''Stage 2:''' Completed, | ||
MegaCR Index available in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)0001117r3_FEAT010_MegaCR_Index.docx NFVIFA(18)0001117r3]<br />'''Stage 3:''' | |||
complated release 3(SOL001, SOL003, SOL005, SOL006, SOL009, SOL017) | |||
ongoing release 4 (SOL014, SOL019) | |||
|- | |- | ||
| '''Contributions''' || [http://https://portal.etsi.org All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | | '''Contributions''' || '''Stage2:''' | ||
[http://https://portal.etsi.org All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | |||
'''Stage3:''' | |||
SOL001 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//NFVSOL(19)000792r1_SOL001ed331_FEAT10_Add_specification_for_Multi-Site_Connecti.docx NFVSOL(19)000792r1] | |||
SOL003 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//NFVSOL(19)000732_SOL003ed331_FEAT10_Add_specification_for_Multi-Site_Connecti.docx NFVSOL(19)000732] and [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000363_SOL003ed361_FEAT10_Correction_about_multi-VIM_support.docx NFVSOL(21)000363] | |||
SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//NFVSOL(19)000734_SOL005ed331_FEAT10_Add_specification_for_Multi-Site_Connecti.docx NFVSOL(19)000734], [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//NFVSOL(20)000080_SOL005ed331_FEAT10_Specification_of_WanConnectionData.docx NFVSOL(20)000080], [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//NFVSOL(20)000081_SOL005ed331_FEAT10_Handling_of_WAN_connectivity_information.docx NFVSOL(20)000081], [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//NFVSOL(20)000082r2_SOL005ed331_FEAT10_Annex_multi-site_connectivity.zip NFVSOL(20)000082r2], [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//NFVSOL(20)000235r1_SOL005ed331_FEAT10_Addressing_technical_EN_on_MSCS_support.docx NFVSOL(20)000235r1], [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//NFVSOL(20)000252_SOL005ed331_FEAT10_Addressing_EN_in_MSCS_informative_annex.docx NFVSOL(20)000252] and [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//NFVSOL(19)000817_SOL005ed331_FEAT10_Bug_fixes_and_clarifications.docx NFVSOL(19)000817] | |||
SOL006 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//NFVSOL(20)000115_SOL006ed331_FEAT10_-_IFA014_Augment_anti-affinity_scope.docx NFVSOL(20)000115] | |||
SOL009 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000153_SOL009ed351_Release_alignment_with_FEAT10_multi-site_connect.docx NFVSOL(21)000153] | |||
SOL014 (ongoing) | |||
new report SOL017 (completed) | |||
new specifcation SOL019 (ongoing) | |||
|- | |- | ||
| '''Feature team''' || '''Stage 2:'''<br />- Hiroshi Dempo (NEC Europe Ltd.)<br />- Zarrar Yousaf (NEC Europe Ltd.)<br />- Lei Zhu (Huawei Tech (UK) Co., Ltd.<br />- Ulrich Kleber (Huawei Tech (UK) Co., Ltd.<br />- Marc Flauw (HPE)<br />- Joan Triay (DOCOMO)<br />'''Stage 3:'''<br />- Zarrar Yousaf (NEC Europe Ltd.)<br />- Joan Triay (DOCOMO) | | '''Feature team''' || '''Stage 2:'''<br />- Hiroshi Dempo (NEC Europe Ltd.)<br />- Zarrar Yousaf (NEC Europe Ltd.)<br />- Lei Zhu (Huawei Tech (UK) Co., Ltd.<br />- Ulrich Kleber (Huawei Tech (UK) Co., Ltd.<br />- Marc Flauw (HPE)<br />- Joan Triay (DOCOMO)<br />'''Stage 3:'''<br />- Zarrar Yousaf (NEC Europe Ltd.)<br />- Joan Triay (DOCOMO) | ||
Line 1,801: | Line 1,866: | ||
| '''Target Release''' || Release 3 (2019) | | '''Target Release''' || Release 3 (2019) | ||
|- | |- | ||
| '''Impacted WIs''' || IFA013, IFA008, IFA011 | | '''Impacted WIs''' || '''Stage2:''' | ||
IFA013, IFA008, IFA011 | |||
'''Stag3:''' | |||
SOL005, SOL002, SOL004 | |||
|- | |- | ||
| '''MegaCRs''' || For part 3: Related content already included in Rel 2 maintenance (V 2.4.1) | | '''MegaCRs''' || For part 3: Related content already included in Rel 2 maintenance (V 2.4.1) | ||
Line 1,825: | Line 1,895: | ||
* NFVSOL(17)000585r3_SOL004_non_MANO_artifact_sets | * NFVSOL(17)000585r3_SOL004_non_MANO_artifact_sets | ||
* NFVIFA(18)0001024r2_IFA008ed321_-_Remove_ConfirmVnfSnapshot__Add_LCM_Coordinatio | * NFVIFA(18)0001024r2_IFA008ed321_-_Remove_ConfirmVnfSnapshot__Add_LCM_Coordinatio | ||
'''Stage3:''' | |||
SOL002 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//NFVSOL(20)000128_SOL002ed331_forward_port_of_99r1_API_uniformity_wrt_graceful.docx NFVSOL(20)000128] | |||
SOL004 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2017//NFVSOL(17)000585r3_SOL004_non-MANO_artifact_sets.docx NFVSOL(17)000585r3] | |||
SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//NFVSOL(20)000053r1_SOL005ed331_MECinNFV_placement_constraint_update.docx NFVSOL(20)000053r1] | |||
'''Others:''' | |||
MEC API development platform: [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2017//NFVSOL(17)000402_ETSI_MEC_API_dev_platform.pdf NFVSOL(17)000402] | |||
TOSCA model of AppD in MEC and: [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000078_Slides_for_joint_call_with_ETSI_MEC_on_MEC037.pptx SOL NFVSOL(22)000078] | |||
NFV Registries of [https://nfvwiki.etsi.org/index.php?title=Non_MANO_artifact_sets Non MANO artifact sets] (no registry for MEC yet) | |||
|- | |- | ||
| '''Feature team''' || Uwe Rauschenbach, Nokia | | '''Feature team''' || Uwe Rauschenbach, Nokia | ||
Line 1,907: | Line 1,993: | ||
|- | |- | ||
|'''Impacted WIs''' | |'''Impacted WIs''' | ||
| | |'''Stage2''': IFA011 | ||
'''Stage3''': SOL004 | |||
|- | |- | ||
|'''MegaCRs''' | |'''MegaCRs''' | ||
|TODO, will be based on the IFA034 report | |<s>TODO, will be based on the IFA034 report</s> | ||
N/A (only 1 CR for IFA011) | |||
|- | |- | ||
|'''Related/Dependent Features''' | |'''Related/Dependent Features''' | ||
Line 1,916: | Line 2,005: | ||
|- | |- | ||
|'''Status''' | |'''Status''' | ||
| | |'''Stage2''': completed | ||
'''Stage3''': completed | |||
|- | |- | ||
|'''Contributions''' | |'''Contributions''' | ||
| | |'''Stage2''' | ||
IFA011 [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000534r3_IFA011ed441_Optional_license_info_IFA034_followup.docx NFVIFA(22)000534r3] | |||
'''Stage3''' | |||
SOL004 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000359r4_SOL004ed441_Optional_license_info_IFA034_followup.docx NFVSOL(22)000359r4] | |||
|- | |- | ||
|'''Feature team''' | |'''Feature team''' | ||
Line 1,934: | Line 2,030: | ||
|- | |- | ||
|'''Last update''' | |'''Last update''' | ||
| | |2023-01-01 | ||
|} | |} | ||
Line 1,949: | Line 2,045: | ||
|- | |- | ||
| '''Impacted WIs''' || '''Stage 2:''' IFA010, IFA014 | | '''Impacted WIs''' || '''Stage 2:''' IFA010, IFA014 | ||
'''Stage 3:''' SOL001, SOL006 | |||
|- | |- | ||
| '''MegaCRs''' || '''Stage 2:''' | | '''MegaCRs''' || '''Stage 2:''' | ||
IFA010: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019/NFVIFA(19)000480r8_IFA010_MegaCR_FEAT16_SAL.docx NFVIFA(19)000480r8] Approved by email on July 15<br /> | IFA010: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019/NFVIFA(19)000480r8_IFA010_MegaCR_FEAT16_SAL.docx NFVIFA(19)000480r8] Approved by email on July 15<br /> | ||
IFA014: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019/NFVIFA(19)000526r6_IFA014_MegaCR_FEAT16_SAL.docx NFVIFA(19)000526r6] Approved by email on July 15 | IFA014: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019/NFVIFA(19)000526r6_IFA014_MegaCR_FEAT16_SAL.docx NFVIFA(19)000526r6] Approved by email on July 15 | ||
'''Stage 3:''' <tbd> | <s>'''Stage 3:''' <tbd></s> | ||
|- | |- | ||
| '''Related/Dependent Features''' || N/A | | '''Related/Dependent Features''' || N/A | ||
|- | |- | ||
| '''Status''' || '''Stage 2:''' Approved in IFA#160; MegaCR Index available in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019/NFVIFA(19)000746_FEAT16_MegaCR_Index.docx NFVIFA(19)000746] | | '''Status''' || '''Stage 2:''' Approved in IFA#160; MegaCR Index available in [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019/NFVIFA(19)000746_FEAT16_MegaCR_Index.docx NFVIFA(19)000746] | ||
'''Stage 3:''' | '''Stage 3:''' Completed | ||
|- | |- | ||
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx?Tb_Id=831&searchText=FEAT16&IncludeSubTb=False&sort=pk_contribution&sortorder=DESC&NbItemsPerPage=50&Year=2019,2018 All feature contributions]<br />[https://portal.etsi.org Agreed content] | | '''Contributions''' || '''Stage2''' | ||
[https://portal.etsi.org/Contribution.aspx?Tb_Id=831&searchText=FEAT16&IncludeSubTb=False&sort=pk_contribution&sortorder=DESC&NbItemsPerPage=50&Year=2019,2018 All feature contributions]<br />[https://portal.etsi.org Agreed content] | |||
'''Stage3''' | |||
SOL001 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//NFVSOL(20)000067r1_SOL001ed331_FEAT16_Adding_SAL_to_NSD.docx NFVSOL(20)000067r1] | |||
SOL006 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//NFVSOL(20)000026r2_SOL006ed331_FEAT16_SAL.docx NFVSOL(20)000026r2] | |||
|- | |- | ||
| '''Feature team''' || Shaoji Ni (Huawei)<br />Maria Toeroe(Ericsson)<br />Gerald Kunzmann (DOCOMO)<br />Stefan Arntzen (Huawei)<br />Janusz Pieczerak (Orange) <br />Chidung Lac (Orange) <br /> | | '''Feature team''' || Shaoji Ni (Huawei)<br />Maria Toeroe(Ericsson)<br />Gerald Kunzmann (DOCOMO)<br />Stefan Arntzen (Huawei)<br />Janusz Pieczerak (Orange) <br />Chidung Lac (Orange) <br /> | ||
|- | |- | ||
| '''Last Updated''' || | | '''Last Updated''' || 2023-01-01 | ||
|} | |} | ||
Line 2,087: | Line 2,191: | ||
- 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 (after NFV#31e, October 2020) | | '''Target Release''' || '''Stage 2''' | ||
* '''Step 1:''' Release 4 Drop #1 ed411 (after NFV#31e, October 2020) | |||
* '''Step 2:''' Release 4 Drop #2 ed421 (after NFV#34e, April 2021) | |||
* '''Step 3:''' Release 4 Drop #3 ed431 (after NFV#37e, March 2022) | |||
* '''Step 4''': Release 4 Drop #4 ed441 (NFV#41, March 2023) | |||
'''Stage 3''' | |||
* '''Step 1:''' Release 4 ed421 (SOL001) and ed431 (SOL002, SOL003, SOL006, SOL018) (July 2022) | |||
* '''Step 2:''' Release 4 ed441 (ongoing) | |||
|- | |- | ||
| '''Impacted WIs''' || '''Stage 2:''' IFA007, IFA008, IFA010, IFA011, IFA013, IFA014<br /> | | '''Impacted WIs''' || '''Stage 2:''' IFA007, IFA008, IFA010, IFA011, IFA013, IFA014, IFA036, IFA040, IFA052<br />'''Stage 3:''' SOL001, SOL002, SOL003, SOL006, SOL018, SOL020 | ||
'''Stage 3:''' SOL001, SOL002, SOL003, SOL006, SOL018 | |||
|- | |- | ||
| '''MegaCRs''' || '''Stage 2 Step 1:''' | | '''MegaCRs''' || '''Stage 2''' | ||
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) | * '''Step 1 (ed411):''' | ||
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) | ** 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), [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/010/04.01.01_60/gs_NFV-IFA010v040101p.pdf New edition IFA010ed411] | ||
[https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/011/04.01.01_60/gs_NFV-IFA011v040101p.pdf New edition IFA011ed411] | ** 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), 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), [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/011/04.01.01_60/gs_NFV-IFA011v040101p.pdf New edition IFA011ed411] | ||
''' | * '''Step 2 (ed421):''' | ||
''' | ** IFA007ed421 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000196r5_IFA007ed421_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(21)000196r5] (Approved), [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/007/04.02.01_60/gs_nfv-ifa007v040201p.pdf New edition IFA007ed421] | ||
** IFA008ed421 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000200r2_IFA008ed421_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(21)000200r2] (Approved), [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/008/04.02.01_60/gs_nfv-ifa008v040201p.pdf New edition IFA008ed421] | |||
** IFA010ed421 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000197r2_IFA010ed421_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(21)000197r2] (Approved), [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/010/04.02.01_60/gs_nfv-ifa010v040201p.pdf New edition IFA010ed421] | |||
** IFA011ed421 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000203r1_IFA011ed421_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(21)000203r1] (Approved), [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/011/04.02.01_60/gs_nfv-ifa011v040201p.pdf New edition IFA011ed421] | |||
** IFA013ed421 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000204_IFA013ed421_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(21)000204] (Approved), [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/013/04.02.01_60/gs_nfv-ifa013v040201p.pdf New edition IFA013ed421] | |||
** IFA014ed421 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000205r1_IFA014ed421_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(21)000205r1] (Approved), [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/014/04.02.01_60/gs_nfv-ifa014v040201p.pdf New edition IFA014ed421] | |||
* '''Step 3 (ed431):''' | |||
** IFA007ed431 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000190r1_IFA007ed431_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(22)000190r1] (Approved), [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/007/04.03.01_60/gs_NFV-IFA007v040301p.pdf New edition IFA007ed431] | |||
** IFA008ed431 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000194r1_IFA008ed431_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(22)000194r1] (Approved), [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/008/04.03.01_60/gs_NFV-IFA008v040301p.pdf New edition IFA008ed431] | |||
** IFA010ed431 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000197r4_IFA010ed431_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(22)000197r4] (Approved), [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/010/04.03.01_60/gs_NFV-IFA010v040301p.pdf New edition IFA010ed431] | |||
** IFA013ed431 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000198r1_IFA013ed431_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVIFA(22)000198r1] (Approved), [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/013/04.03.01_60/gs_NFV-IFA013v040301p.pdf New edition IFA013ed431] | |||
'''Stage 3 Step 1:'''<br /> SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//blackhole.doc NFVSOL(20)000zzz] (CR Status) | '''Stage 3''' | ||
* '''Step 1:'''<br /> SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//blackhole.doc NFVSOL(20)000zzz] (CR Status) | |||
|- | |- | ||
| '''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:''' | | '''New Specification ''' || '''Stage 2''' | ||
''' | * '''Step 1 (ed411):''' | ||
''' | ** [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 | ||
* '''Step 2 (ed421):''' | |||
'''Stage 3 Step 1:''' | ** [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/040/04.02.01_60/gs_nfv-ifa040v040201p.pdf RGS/NFV-IFA040ed421]- Requirements for service interfaces and object model for OS container management and orchestration specification | ||
* '''Step 3 (ed431):''' | |||
** [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/036/04.03.01_60/ DGS/NFV-IFA036ed431] - Specification of requirements for the management and orchestration of container cluster nodes | |||
** [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/040/04.03.01_60/gs_nfv-ifa040v040301p.pdf RGS/NFV-IFA040ed431]- Requirements for service interfaces and object model for OS container management and orchestration specification | |||
* '''Step 4 (ed441):''' | |||
** RGS/NFV-IFA036ed441 - Specification of requirements for the management and orchestration of container cluster nodes | |||
** RGS/NFV-IFA040ed441- Requirements for service interfaces and object model for OS container management and orchestration specification | |||
* '''Step 5 (ed451):''' | |||
** DGS/NFV-IFA052 - CCM-VIM Interoperability Interface and Information Model Specification | |||
'''Stage 3''' | |||
* '''Step 1:''' | |||
** [https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/018/04.03.01_60/ DGS/NFV-SOL018ed431] - Profiling specification of protocol and data model solutions for OS Container management and orchestration | |||
* '''Step 2:''' | |||
** DGS/NFV-SOL020 - Protocols and Data Models Specification of protocols and data models for Container Infrastructure Service Cluster Management CCM stage 3 | |||
|- | |- | ||
| '''Status''' || | | '''Status''' || | ||
'''Stage 2 Step 1:''' Completed | '''Stage 2''' | ||
''' | * '''Step 1:''' Completed | ||
''' | * '''Step 2:''' Completed | ||
'''Stage 3 Step 1:''' Ongoing | * '''Step 3:''' Completed | ||
* '''Step 4:''' Ongoing (40% completed) | |||
'''Stage 3''' | |||
* '''Step 1:''' Completed | |||
* '''Step 2:''' Ongoing | |||
|- | |- | ||
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx?Tb_Id=831&searchText=FEAT17%20IFA040%20IFA036&IncludeSubTb=False&sort=pk_contribution&sortorder=DESC&NbItemsPerPage=50&Year=2019,2020,2021,2022 All stage 2 feature contributions]<br /> | | '''Contributions''' || '''Stage 2:''' | ||
[https://portal.etsi.org/Contribution.aspx?Tb_Id=848&searchText=FEAT17%20SOL018&IncludeSubTb=False&sort=pk_contribution&sortorder=DESC&NbItemsPerPage=50&Year=2021,2022 | [https://portal.etsi.org/Contribution.aspx?Tb_Id=831&searchText=FEAT17%20IFA040%20IFA036&IncludeSubTb=False&sort=pk_contribution&sortorder=DESC&NbItemsPerPage=50&Year=2019,2020,2021,2022 All stage 2 feature contributions]<br /> | ||
'''Stage 3:''' | |||
Step 1 introduce CISM/CIR and OsContainer | |||
[https://portal.etsi.org/Contribution.aspx?Tb_Id=848&searchText=FEAT17%20SOL018&IncludeSubTb=False&sort=pk_contribution&sortorder=DESC&NbItemsPerPage=50&Year=2021,2022 SOL018 contributions], SOL001ed421 and SOL001ed431, SOL002ed431, SOL003ed431, SOL005ed431, SOL006ed431, SOL009ed431 <br />Step2 introduce CCM | |||
SOL020 | |||
|- | |- | ||
| '''Feature team''' || '''Stage 2:''' Ulrich Kleber (Huawei Technologies Co.,Ltd)<br />Jörg Aelken (Ericsson LM) | | '''Feature team''' || '''Stage 2:''' Ulrich Kleber (Huawei Technologies Co.,Ltd)<br />Jörg Aelken (Ericsson LM) | ||
'''Stage 3:''' Jörg Aelken (Ericsson LM) | '''Stage 3:''' Jörg Aelken (Ericsson LM) | ||
|- | |- | ||
| '''Last Updated''' || | | '''Last Updated''' || 2023-01-24 | ||
|} | |} | ||
Line 2,129: | Line 2,275: | ||
* Timeplan of when the team plans to conclude a particular action in the implementation plan. | * Timeplan of when the team plans to conclude a particular action in the implementation plan. | ||
==== Stage 2 - Step 1 ==== | ==== Stage 2 - Step 1 '''(ed411)''' ==== | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
Line 2,257: | Line 2,403: | ||
|| IFA010ed411 || March - 2020 || Complete | || IFA010ed411 || March - 2020 || Complete | ||
|} | |} | ||
==== Stage 2 - Step 2 ==== | ==== Stage 2 - Step 2 '''(ed421)''' ==== | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
Line 2,317: | Line 2,463: | ||
|| IFA040ed421 || March - 2021 || Complete | || IFA040ed421 || March - 2021 || Complete | ||
|} | |} | ||
==== Stage 2 - Step 3 ==== | ==== Stage 2 - Step 3 '''(ed431)''' ==== | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
Line 2,445: | Line 2,591: | ||
|- | |- | ||
| ST2-026 || Analyse and if necessary enhance VNFD and its VDU information element with attributes/information <br />elements related to cluster and node affinity | | ST2-026 || Analyse and if necessary enhance VNFD and its VDU information element with attributes/information <br />elements related to cluster and node affinity | ||
|| IFA011ed431 || March - 2022 || | No enhancements required from CCM<br /> | ||
|| IFA011ed431 || March - 2022 || Completed | |||
|- | |- | ||
| ST2-027 || Analyse and if necessary enhance NSD and constituent information elements with attributes/information <br />elements related to cluster and node affinity | | ST2-027 || Analyse and if necessary enhance NSD and constituent information elements with attributes/information <br />elements related to cluster and node affinity | ||
No enhancements required from CCM<br /> | |||
|| IFA014ed431 || March - 2022 || | || IFA014ed431 || March - 2022 || Completed | ||
|- | |- | ||
| ST2-028 || Specify the functional requirements for the CCM function | | ST2-028 || Specify the functional requirements for the CCM function | ||
Line 2,473: | Line 2,620: | ||
CR drafts: <br /> | CR drafts: <br /> | ||
|| IFA010ed431 || March - 2022 || | || IFA010ed431 || March - 2022 || Moved to step 4 | ||
|- | |- | ||
| ST2-031 || Extend the NFVO functional requirements for consuming the management service interfaces <br />exposed by the CISM function related to CIS Cluster Node management | | ST2-031 || Extend the NFVO functional requirements for consuming the management service interfaces <br />exposed by the CISM function related to CIS Cluster Node management | ||
CR drafts: <br /> | CR drafts: <br /> | ||
|| IFA010ed431 || March - 2022 || | || IFA010ed431 || March - 2022 || Moved to step 4 | ||
|- | |- | ||
| ST2-032 || Analyse and if necessary enhance the information models of the Os-Ma-nfvo interfaces <br />for CIS Cluster management and CIS Cluster Node management | | ST2-032 || Analyse and if necessary enhance the information models of the Os-Ma-nfvo interfaces <br />for CIS Cluster management and CIS Cluster Node management | ||
CR drafts: <br /> | CR drafts: <br /> | ||
|| IFA013ed431 || March - 2022 || | || IFA013ed431 || March - 2022 || Moved to step 4 | ||
|- | |- | ||
| ST2-033 || Additional interface enhancements in step 3 | | ST2-033 || Additional interface enhancements in step 3 | ||
CR drafts: <br /> | CR drafts: <br />[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000855r7_FEAT17_IFA007ed431_NAD_id.docx NFVIFA(21)000855r7] (Agreed FEAT, IFA007) <br />[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000027r1_FEAT17_IFA007ed431_VnfExtCpConfig_typo_correction.docx NFVIFA(22)000027r1] (Agreed FEAT, IFA007) | ||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000855r7_FEAT17_IFA007ed431_NAD_id.docx NFVIFA(21)000855r7] (Agreed FEAT, IFA007) <br /> | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000027r1_FEAT17_IFA007ed431_VnfExtCpConfig_typo_correction.docx NFVIFA(22)000027r1] (Agreed FEAT, IFA007) <br /> | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000127_IFA007ed431_FEAT17_Conveying_StorageClassName.docx NFVIFA(22)000127] (Agreed FEAT, IFA007) | ||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000014r2_FEAT17_IFA008ed431_Mirror_of__21_855_NAD_id.docx NFVIFA(22)000014r2] (Agreed FEAT, IFA008) <br /> | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000048_FEAT17_IFA008ed431_VnfExtCpConfig_typo_correction.docx NFVIFA(22)000048] (Agreed FEAT, IFA008) <br /> | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000153_FEAT17_IFA007ed431_ResourceHandle_namespace.docx NFVIFA(22)000153] (Agreed FEAT, IFA007)<br />[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000014r2_FEAT17_IFA008ed431_Mirror_of__21_855_NAD_id.docx NFVIFA(22)000014r2] (Agreed FEAT, IFA008) <br />[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000048_FEAT17_IFA008ed431_VnfExtCpConfig_typo_correction.docx NFVIFA(22)000048] (Agreed FEAT, IFA008) | ||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000012_IFA011ed431_Mcio_data.docx NFVIFA(22)000012] ( | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000026r3_FEAT17_IFA013ed431_Mirror_of__21_855_NAD_id.docx NFVIFA(22)000026r3] (Agreed FEAT, IFA013) <br /> | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000155_FEAT17_IFA008ed431_Mirror_of_153-_ResourceHandle_namespace.docx NFVIFA(22)000155] (Agreed FEAT, IFA008)<br />[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000012_IFA011ed431_Mcio_data.docx NFVIFA(22)000012] (Agreed FEAT, IFA011) <br />[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000026r3_FEAT17_IFA013ed431_Mirror_of__21_855_NAD_id.docx NFVIFA(22)000026r3] (Agreed FEAT, IFA013) <br />[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000156_FEAT17_IFA013ed431_Mirror_of_153-_ResourceHandle_namespace.docx NFVIFA(22)000156] (Agreed FEAT, IFA013) | ||
|| IFA007ed431, <br />IFA008ed431, <br />IFA011ed431, <br />IFA013ed431 || March - 2022 || | || IFA007ed431, <br />IFA008ed431, <br />IFA011ed431, <br />IFA013ed431 || March - 2022 || Completed | ||
|- | |- | ||
| ST2-034 || Workgroup review | | ST2-034 || Workgroup review | ||
Line 2,524: | Line 2,671: | ||
|} | |} | ||
=== Stage | === Stage 2 - Step 4 '''(ed441)''' === | ||
''' | |||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|- | |- | ||
! ID !! Action !! Impacted | ! ID !! Action !! Impacted WI(s) !! Target completion !! Status | ||
|- | |||
|ST2-030 | |||
|Extend the NFVO functional requirements for consuming the management service interfaces <br />exposed by the CCM function | |||
CR drafts: | |||
|IFA010ed441 | |||
|March - 2023 | |||
|Not started | |||
(move to step 5) | |||
|- | |- | ||
| | |ST2-031 | ||
| | |Extend the NFVO functional requirements for consuming the management service interfaces <br />exposed by the CISM function related to CIS Cluster Node management | ||
CR drafts: <br /> | |||
|IFA010ed441 | |||
|March - 2023 | |||
|Not started | |||
(move to step 5) | |||
|- | |||
|ST2-032 | |||
|Analyse and if necessary enhance the information models of the Os-Ma-nfvo interfaces <br />for CIS Cluster management and CIS Cluster Node management | |||
CR drafts: | |||
|IFA013ed441 | |||
|March - 2023 | |||
|Not started | |||
(move to step 5) | |||
|- | |||
| ST2-035 || Provide additional workflows and examples | |||
CR drafts: | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000854r1_IFA036ed441_B_2_Improvements_on_creating_CIS_cluster_flow.docx NFVIFA(22)000854r1] (Approved) | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(22)000949r3_IFA036ed441_B_x_Deploy_CCEC_on_a_CIS_cluster.docx NFVIFA(22)000949r3] (Approved) | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000976r1_IFA036ed441_3_1_Definition_of_term_daemon_object_modificatio.docx NFVIFA(22)000976r1] (Approved) | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000002r1_IFA036ed441_Improve_text_in_clause_B_5.docx NFVIFA(23)000002r1] (Approved) | |||
|| IFA036ed441 || March - 2023 | |||
| Completed | |||
|- | |||
|ST2-036 | |||
|Provide more details for some concepts in CCM, e.g. shared storage, clusters with multiple NFVI-Pops, clusters and | |||
multiple domains, cluster-related measurements, etc. | |||
CR drafts: | |||
|IFA036ed441, | |||
IFA030ed441, | |||
IFA032ed441, | |||
IFA027ed441 | |||
| | |||
|Not started | |||
(move to step 5) | |||
|- | |- | ||
| | |ST2-037 | ||
|Reliability considerations for CCM | |||
|IFA036ed441 | |||
| | |||
|Not started | |||
(move to step 5) | |||
|- | |- | ||
| | |ST2-038 | ||
|Security considerations for CCM | |||
|IFA036ed441 | |||
| | |||
|Not started | |||
(move to step 5) | |||
|- | |- | ||
| | |ST2-039 | ||
|Describe management of CCM | |||
CR drafts: | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000011_IFA010ed441_Adding_CCM_into_NFV-MANO_mgmt.docx NFVIFA(23)000011] (IFA010, Approved) | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000012_IFA031ed441_Adding_CCM_into_NFV-MANO_mgmt_interfaces.docx NFVIFA(23)000012] (IFA031, Approved) | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000013_IFA031ed441_Adding_CCM_related_managed_objects_for_PM_metric.docx NFVIFA(23)000013] (IFA031, Approved) | |||
|IFA010ed441 | |||
IFA031ed441 | |||
|March - 2023 | |||
|Completed | |||
|- | |- | ||
| ''' | |ST2-040 | ||
|Additional enhancements in step 4 | |||
CR drafts: <br />[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000022r1_Feat17_IFA011ed441_support_of_floating_IP_address_for_contai.docx NFVIFA(23)000022r1] (Approved, IFA011) | |||
|IFA011ed441 | |||
|March - 2023 | |||
|Completed | |||
|} | |||
=== Stage 2 - Step 5 '''(ed451)''' === | |||
{| class="wikitable sortable" | |||
|- | |- | ||
! ID !! Action !! Impacted WI(s) !! Target completion !! Status | |||
|- | |- | ||
| | |ST2-030 | ||
|Extend the NFVO functional requirements for consuming the management service interfaces <br />exposed by the CCM function | |||
CR drafts: | |||
|IFA010 | |||
| | |||
|Not started | |||
|- | |- | ||
| | |ST2-031 | ||
|Extend the NFVO functional requirements for consuming the management service interfaces <br />exposed by the CISM function related to CIS Cluster Node management | |||
CR drafts: <br /> | |||
|IFA010 | |||
| | |||
|Not started | |||
|- | |- | ||
| | |ST2-032 | ||
|Analyse and if necessary enhance the information models of the Os-Ma-nfvo interfaces <br />for CIS Cluster management and CIS Cluster Node management | |||
CR drafts: | |||
|IFA013 | |||
| | |||
|Not started | |||
|- | |- | ||
| | |ST2-036 | ||
|Provide more details for some concepts in CCM, e.g. shared storage, clusters with multiple NFVI-Pops, clusters and | |||
multiple domains, cluster-related measurements, etc. | |||
CR drafts: | |||
|IFA036, | |||
IFA030, | |||
IFA032, | |||
IFA027 | |||
| | |||
|Not started | |||
|- | |- | ||
|ST2-037 | |||
|Reliability considerations for CCM | |||
|IFA036 | |||
| | |||
|Not started | |||
|- | |- | ||
| | |ST2-038 | ||
|Security considerations for CCM | |||
|IFA036 | |||
| | |||
|Not started | |||
|- | |- | ||
| | |ST2-041 | ||
| | |CCM southbound interface | ||
| | |IFA052 | ||
| | |||
| | |Ongoing | ||
| | |} | ||
=== Stage 3 Implementation Plan === | |||
Items to consider in the implementation plan | |||
* Detailed description what has to be done in which work item. | |||
* Timeplan of when the team plans to conclude a particular action in the implementation plan. | |||
'''SOL Stage3 Step1''' | |||
{| class="wikitable sortable" | |||
|- | |- | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | |||
|- | |- | ||
| | | ST3-001 || introduce OsContainer | ||
- NFVSOL(21)000011r8 - NFVSOL(21)000018r6 | |||
- NFVSOL(21)000020r2 - NFVSOL(21)000223 | |||
- NFVSOL(21)000246r1 - NFVSOL(21)000374 | |||
- NFVSOL(21)000252r3 - NFVSOL(21)000436r2 | |||
- NFVSOL(21)000481r1 - NFVSOL(21)000097r9 | |||
- NFVSOL(21)000440r2 - NFVSOL(21)000622r1 | |||
introduce MCIOP - NFVSOL(21)000064r5 | |||
- NFVSOL(21)000246r1 - NFVSOL(21)000480 | |||
- NFVSOL(21)000487 - NFVSOL(21)000491r1 | |||
- NFVSOL(21)000617r1 - NFVSOL(21)000152r5 | |||
introduce MCIO - NFVSOL(21)000451r1 | |||
- NFVSOL(22)000096r1 - NFVSOL(22)000112r1 | |||
enhance container network - NFVSOL(21)000019r4 | |||
- NFVSOL(21)000021r4 - NFVSOL(21)000238r2 | |||
| SOL001 || January-2022 || Completed | |||
|- | |- | ||
| | |ST3-002 | ||
|extends Grant and introduce CISM/CIR | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000367r2_SOL003ed421_FEAT17_Cloud-native_VNFs.docx NFVSOL(21)000367r2] | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000492_SOL003ed431_FEAT17_improve_the_description_of_vimConnectionI.docx NFVSOL(21)000492] | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000118_SOL003ed431_FEAT17_Conveying_StorageClassName.docx NFVSOL(22)000118] | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000163_FEAT17_SOL003ed431_SwImageIdentifier.docx NFVSOL(22)000163] | |||
|SOL003 | |||
|July-2022 | |||
|Completed | |||
|- | |- | ||
| | |ST3-003 | ||
|introduces MCIO | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000684r1_SOL003ed431_FEAT17_Add_data_type_McioInfo_.docx NFVSOL(21)000684r1] | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000053r4_FEAT17_SOL003ed431_ResourceHandle.docx NFVSOL(22)000053r4] | |||
enhance CP for container network | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000482r4_SOL003ed431_NAD_id.docx NFVSOL(21)000482r4] | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000040_SOL003ed431_FEAT17_Runtime_modelling_of_VirtualCp.docx NFVSOL(22)000040] | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000092_SOL003ed431_FEAT17_Add_data_type_VirtualCpInfo.docx NFVSOL(22)000092] | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000139r2_FEAT17_SOL003ed431_CpProtocolData.docx NFVSOL(22)000139r2] | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000500r1_FEAT17_SOL003ed441_deletion_or_disconnection_of_cp_instances.docx NFVSOL(22)000500r1] | |||
|SOL003 | |||
|July-2022 | |||
|Completed | |||
|- | |- | ||
| | |ST3-004 | ||
|introduces MCIO | |||
| | - [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000089_SOL002ed431_FEAT17_Mirror_of_684r1_Add_data_type_McioInfo.docx NFVSOL(22)000089] (684r1 mirror) | ||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000120r1_FEAT17_SOL002ed431_Mirror_of_053_ResourceHandle.docx NFVSOL(22)000120r1] (053r4 mirror) | |||
enhance CP for container network | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000177_Feat17_SOL002ed431_Mirror_of__21_482_NAD_id.docx NFVSOL(22)000177] (482 mirror) | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000052_SOL002ed431_Mirror_of_040_FEAT17_Runtime_modelling_of_Virtua.docx NFVSOL(22)000052] (040 mirror) | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000107_SOL002ed431_Mirror_of_092_FEAT17_Add_data_type_VirtualCpInfo.docx NFVSOL(22)000107] (092 mirror) | |||
|- | - [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000171r1_FEAT17_SOL002ed431_mirror_of_CR_139_CpProtocolData.docx NFVSOL(22)000171r1] (139r2 mirror) | ||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000501r1_FEAT17_SOL002ed441_Mirror_of_500_-_deletion_or_disconnection.docx NFVSOL(22)000501r1] (500r1 mirror) | |||
|SOL002 | |||
|July-2022 | |||
|Completed | |||
|- | |- | ||
| | |ST3-005 | ||
|introduce CISM/CIR | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000037r1_SOL005ed431_FEAT17_Cloud-native_VNFs.docx NFVSOL(22)000037r1] (367r2 mirror) | |||
introduces MCIO | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000073_SOL005ed431_Mirror_of_684r1_FEAT17_Add_data_type_McioInfo.docx NFVSOL(22)000073] (684r1 mirror) | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000121r1_FEAT17_SOL005ed431_Mirror_of_053_ResourceHandle.docx NFVSOL(22)000121r1] (053r4 mirror) | |||
enhance CP for container network | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000154r4_SOL005ed431_FEAT17_Cloud-native_VNFs.docx NFVSOL(22)000154r4] (482 mirror) | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000122_SOL005ed431_FEAT17_Runtime_modelling_of_VirtualCp.docx NFVSOL(22)000122] (040 and 092 mirror) | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000172_SOL005ed431_FEAT17_mirror_of_139r2_CpProtocolData.docx NFVSOL(22)000172] (139r2 mirror) | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000514r1_FEAT17_SOL005ed441_Mirror_of_500_Deletion_or_disconnection_o.docx NFVSOL(22)000514r1] (500r1 mirror) | |||
| | |SOL005 | ||
| | |July-2022 | ||
| | |Completed | ||
|- | |- | ||
| | |ST3-006 | ||
|DP: prestudy of stage3 | |||
| | - [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//NFVSOL(20)000757r1_FEAT17_stage_3_and_NWI_discussion.pptx NFVSOL(20)000757r1] | ||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2020//NFVSOL(20)000797r2_Consolidated_Views_on_Formats_for_FEAT17_Rel_4_Stage_3_.pptx NFVSOL(20)000797r2] | |||
DP: CISM API object map | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000516_Discussion_Paper_-_FEAT17_SOL001SOL018_MCIOP_Configurable_pa.pptx NFVSOL(21)000516] | |||
| | |||
| | - [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000344_SOL018_CISM_API_input_parameter_discussion_paper.pptx NFVSOL(21)000344] | ||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000362_DiscussionPaper_SOL018_CISM_API_object_map_for_input_param.pptx NFVSOL(21)000362] | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000483r1_DiscussionPaper_SOL018_CISM_API_object_map_for_Network_MCIO.pptx NFVSOL(21)000483r1] | |||
[https://portal.etsi.org/Contribution.aspx?Tb_Id=848&searchText=FEAT17%20SOL018&IncludeSubTb=False&sort=pk_contribution&sortorder=DESC&NbItemsPerPage=50&Year=2021,2022 all contributions for SOL018] | |||
|SOL018 | |||
|July-2022 | |||
|Completed | |||
|- | |- | ||
| | |ST3-007 | ||
| | |introduce CISM | ||
| | - [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000123_SOL009ed431_Adding_CISM_into_NFV-MANO_mgmt__interfaces.docx NFVSOL(22)000123] | ||
| | |||
| | - [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000201_SOL009ed431_Resolution_of_CismSpecificInfo_related_editor_s_.docx NFVSOL(22)000201] | ||
|SOL009 | |||
|July-2022 | |||
|Completed | |||
|- | |- | ||
| | |ST3-008 | ||
|introduce OsContainer | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000260r1_SOL006ed431_Cloud-Native_VNFs_OSContainerDesc_and_minor_chan.docx NFVSOL(22)00260r1] | |||
| | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000262r1_SOL006ed431_Adding_MegaCR_FEAT17_Cloud-native_VNFs.docx NFVSOL(22)000262r1] | |||
introduce MCIOP | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000261_SOL006ed431_Adding_MCIOP_Profile_and_minor_changes_.docx NFVSOL(22)000261] | |||
introduce MCIO | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000324_SOL006ed431_Implementation_of_Mcio_data_from_IFA011ed431_.docx NFVSOL(22)000324] - [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000269r1_SOL006ed431_New_CP_type_to_model_networking_MCIOs.docx NFVSOL(22)000269r1] | |||
|SOL006 | |||
| | |||
|Completed | |||
|- | |- | ||
| | |ST3-009 | ||
|- | | | ||
| | |SOL016 | ||
|January-2023 | |||
|ongoing | |||
|} | |||
=== Issues === | |||
==== Feature implementation approach ==== | |||
This feature implementation plan proposes to implement the feature according to its scope from the latest NFV Release-4 “Strawman of Release 4 definition”. | |||
Due to the complexity of the feature and its implementation, the feature will be implemented in a stepwise approach. The feature steps are bundling dependent solutions in different work items/specifications. The solutions for one feature step impacting existing specifications will be delivered by Mega-CR’s. There will be one Mega-CR per impacted specification per feature step and all Mega-CR’s for one feature step will be delivered together with dependent new specifications. | |||
- | The current plan bundles the following solutions together: | ||
* Stage 2 - Step 1: IFA040 and related Rel-4 Mega-CRs on existing specifications | |||
* Stage 2 - Step 2: IFA036 and related Rel-4 Mega-CRs on existing specifications | |||
==== Background Information ==== | |||
This feature was originally planned as ETSI NFV Release-3 delivery.<br /> | |||
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: | |||
{| class="wikitable" | |||
|- | |- | ||
! 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 === | |||
{| class="wikitable" | |||
|- | |||
| '''Feature Prime''' || Mark Shepherd (Tencastle) | |||
|- | |||
| '''Feature description''' || To address security challenges arising in NFV, particularly in terms of isolation of sensitive functions and security management and monitoring | |||
|- | |||
| '''Target Release''' || Release 3 drop X (2019-06-30) | |||
|- | |- | ||
| ''' | | '''Impacted WIs''' || '''Stage 1:''' SEC009, SEC011, SEC012, SEC013 | ||
'''Stage 2:''' IFA026, IFA033, <s>SEC019.</s> , IFA008, IFA013 | |||
'''Stage 3:''' TBD | |||
Future work items: consider whether SOL or TST items would be appropriate. | |||
|- | |||
| '''MegaCRs''' || tbd | |||
|- | |- | ||
| '''Related/Dependent Features''' || Enh01.01 Certficate Management | |||
|''' | |||
|- | |- | ||
| '''Status''' || | | '''Status''' || Ongoing (25% complete) | ||
|- | |- | ||
| '''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] | ||
(direct links to search-URLs to be added later) | |||
|- | |- | ||
| '''Feature team''' || | | '''Feature team''' || Alex Leadbeater (Rapporteur), BT | ||
Leslie Willis (Rapporteur), BT | |||
Mark Shepherd, Tencastle | |||
|- | |- | ||
| '''Last Updated''' || | | '''Last Updated''' || 2023-01-01 | ||
|} | |} | ||
=== | === Implementation Plan === | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|- | |- | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 || | | 001 || Complete requirements in IFA026 || IFA026 || November 2018 || Open | ||
| | |||
|- | |- | ||
|002 | |002 | ||
| | |Map requirements from IFA026 into IFA033 and assign to each interface | ||
|IFA026 | |||
IFA033 | |||
|November 2018 | |||
|Open | |||
| | |||
| | |||
|- | |- | ||
|003 | |003 | ||
| | |Complete all of IFA026 and identify all interfaces in IFA033 | ||
|IFA026 | |||
IFA033 | |||
|December 2018 | |||
|Open | |||
|- | |||
|004 | |||
|introduce ADMF | |||
- | introduce NFV SC | ||
|IFA010 | |||
| | |||
|Not started | |||
|- | |||
|005 | |||
|new interface for NFV SC | |||
- | new interface for LI controller and SM | ||
|IFA033 | |||
| | |||
|Not started | |||
|- | |||
|006 | |||
|Add ADMF and NFV SC | |||
Add interface for NFV SC, LI controller and SM | |||
|NFV006 | |||
| | |||
|Not started | |||
|- | |||
|007 | |||
| | |||
|IFA008 | |||
| | |||
|Not started | |||
|- | |||
|008 | |||
| | |||
|IFA013 | |||
| | |||
|Not started | |||
|} | |||
=== Issues === | |||
''List of issues raised based on the feature implementation.'' | |||
=== Security Considerations === | |||
| | ''List of security considerations implied by the feature.'' | ||
| | |||
| | == FEAT19: NFV-Conn == | ||
=== Overview === | |||
{| class="wikitable" | |||
|- | |||
| '''Feature Prime''' || Manchang Ju (ZTE), ju.manchang@zte.com.cn | |||
Hammad Zafar (NEC), Hammad.Zafar@neclab.eu | |||
|- | |- | ||
| | | '''Feature description''' || The scope of IFA038 (Release 4) covers the following areas: | ||
a) investigating aspects of network connectivity for container-based VNF, | |||
''' | |||
b) determining the enhancement related to NFV descriptors and NFV-MANO functional aspects for the management of network connectivity of containerized VNFs, | |||
c) determining the enhancement related to NFV-MANO interfaces for the management of OS container multiple networks. | |||
The scope of IFA035 (Release 4) covers the following areas: | |||
* A “flatter” networking to remove complex L1 and L2 network layering dependencies for the network functions. | |||
* Exposure of high-performance overlay network capabilities to network functions. | |||
* Support of dynamic routing capabilities in the network. | |||
* Enable more dynamic network provisioning and reconfiguration “end-to-end”, within and across sites. | |||
* Minimize manual intervention for network provisioning, while increasing automation. | |||
The scope of IFA043 (Release 5) covers the following areas: | |||
* Analyse the telecom specific use cases (e.g., interconnectivity among operators, connectivity for containers realizing vRAN, etc.) | |||
* The scenarios, requirements and solutions applicable to the container networking for NFV system are proposed for the maximum reuse of open source technologies | |||
* The enhancement of OS container multiple networks management | |||
* Define network policy for effective isolation of networks | |||
* Automated network orchestration for container networking | |||
|- | |||
| '''Target Release''' || '''Stage 2 Step 1 :''' Release 4 drop 3 (2022-02) | |||
'''Stage 2 Step 2 :''' Release 4 drop 5 (2023-07) | |||
'''Stage 3 Step 2:''' Release 4 ed431 (2022-07) | |||
|- | |||
| '''Impacted WIs''' || '''Stage 2:''' IFA010, IFA007, IFA011, IFA013, IFA014 | |||
'''Stage 3:''' SOL001, SOL002, SOL003, SO005, SOL006 | |||
|- | |||
| '''MegaCRs''' || '''Stage 2 Step 1 (drop3):''' | |||
IFA010 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000179_IFA010ed431_MegaCR_FEAT19a_container_networking.docx NFVIFA(22)000179] (Approved at IFA#276) | |||
IFA040 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000180_IFA040ed431_MegaCR_FEAT19a_container_networking.docx NFVIFA(22)000180] (Approved at IFA#276) | |||
|- | |- | ||
| | | '''Related/Dependent Features''' || FEAT17 | ||
| | |- | ||
''' | |New Specifcations | ||
|'''Informative''': [https://www.etsi.org/deliver/etsi_gr/NFV-IFA/001_099/038/04.01.01_60/ ETSI GR NFV-IFA 038] , ETSI GR NFV-IFA 035 (ongoing), ETSI GR NFV-IFA 043 (ongoing) | |||
'''Normative''': not required | |||
|- | |||
| '''Status''' || '''Stage 2 Step 1:''' Completed | |||
'''Stage 2 Step 2:''' Ongoing | |||
'''Stage 3 Step 1:''' Completed | |||
|- | |||
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | |||
|- | |||
| '''Feature team''' || '''Stage 2:''' Manchang Ju (ZTE), Hammad Zafar (NEC), Baoguo Xie(ZTE) | |||
'''Stage 3:''' Name (Company) | |||
|- | |- | ||
| | | '''Last Updated''' || 2023-01-01 | ||
|} | |||
''' | |||
=== Stage 1 Informative Work Plan === | |||
Informative work in ETSI GR NFV-IFA 035(October 2019 - June 2023) | |||
'''IFA035''' | |||
''' | |||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|- | |- | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 || | | 001 || Complete Clause 4 . CR draft [LINK] || IFA || March-2018 || Open | ||
|} | |} | ||
'''IFA043''' | |||
Informative work in ETSI GR NFV-IFA 043(July 2021 - July 2023) | |||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|- | |- | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 || | | 001 || First GR draft introducing the skeleton and the scope. | ||
'''Accepted contributions:''' | |||
NFVIFA(21)000786r1, NFVIFA(21)000787r1 | |||
'' | | IFA || October-2021 || Done | ||
|- | |||
|002 | |||
|Problem statement and introducion | |||
'''Accepted contributions:''' | |||
NFVIFA(21)000961r2, NFVIFA(21)000962r2 | |||
'' | |IFA | ||
|December-2021 | |||
|Done | |||
|- | |||
|003 | |||
|Use case for CCM preconfigures cluster network | |||
'''Accepted contributions:''' | |||
NFVIFA(22)000159r4 | |||
|IFA | |||
|April-2022 | |||
|Done | |||
|- | |- | ||
| ''' | |004 | ||
|Network policy and use case for re-configuration of secondary container cluster network | |||
'''Accepted contributions:''' | |||
NFVIFA(22)000897, NFVIFA(22)898r4 | |||
|IFA | |||
|December-2022 | |||
|Done | |||
|- | |- | ||
| | |005 | ||
|Solutions for re-configuration of secondary container cluster networks and pre-configuration of secondary container cluster networks | |||
|IFA | |||
|June-2023 | |||
|ongoing | |||
|- | |- | ||
| | |006 | ||
|support of network policies, Potential architectural enhancements | |||
|IFA | |||
|June-2023 | |||
|Not started | |||
|- | |- | ||
| | |007 | ||
|Recommendations related to NFV descriptors and other artefacts if needed | |||
Recommendations on architectural framework if needed | |||
Recommendations on functional aspects if needed | |||
|IFA | |||
|July-2023 | |||
|Not started | |||
|} | |||
=== Stage 2 Implementation Plan === | |||
Informative work in ETSI GR NFV-IFA 038(October 2019 - November 2021) | |||
'''IFA038''' | |||
{| 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 | ||
|} | |||
Normative work plan (December 2021- February 2022) | |||
{| class="wikitable" | |||
|'''ID''' | |||
|'''Action''' | |||
|'''Impacted WI(s)''' | |||
|'''Target completion''' | |||
|'''Status''' | |||
|- | |- | ||
| | |001 | ||
| | |Add general functional requirements for management of connectivity for multiple networks. | ||
Add functional requirements for the NFVO, VNFM and CISM to support of the management of network connectivity of containerized VNFs. | |||
|IFA010 | |||
|Dec-2021 | |||
|Completed | |||
|- | |- | ||
| | |002 | ||
|Add functional requirements for the VNFM, and interface and information model specification for the VNF LCM to support OS container multiple networks. | |||
|IFA007 | |||
|July-2023 | |||
|Not started | |||
|- | |- | ||
| | |003 | ||
|Add requirements and modelling for the VNFD and NSD to support describing the properties for one or more secondary container cluster internal/external networks. | |||
Add requirements and modelling for the VNFD and NSD to support describing the information for associating the VLD with the declarative descriptors of secondary container cluster internal/external networks. | |||
Add resource requirements for the VNFD to support describing load balancers associated to network MCIOs. | |||
|IFA011, | |||
IFA014 | |||
|July-2023 | |||
|Not started | |||
|- | |- | ||
| | |004 | ||
|Add functional requirements to the NFVO, and interface and information model specification to the VNF LM or NS LCM to support OS container multiple networks. | |||
|IFA013 | |||
|July-2023 | |||
|Not started | |||
|- | |- | ||
| | |005 | ||
|} | |Add service interface requirements related to OS container multiple networks management to the CISM, to support the configuration and management of OS container multiple networks. | ||
|IFA040 | |||
=== | |Jan-2022 | ||
''' | |Completed | ||
|- | |||
| colspan="5" |NOTE : | |||
|} | |||
=== Stage 3 Implementation Plan === | |||
Items to consider in the implementation plan | |||
* Detailed description what has to be done in which work item. | |||
* Timeplan of when the team plans to conclude a particular action in the implementation plan. | |||
'''SOL''' | |||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|- | |- | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 || | | 001 || enhance CP for container network (FEAT17) | ||
- SOL003 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000482r4_SOL003ed431_NAD_id.docx NFVSOL(21)000482r4] | |||
- SOL002 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000177_Feat17_SOL002ed431_Mirror_of__21_482_NAD_id.docx NFVSOL(22)000177] (482r4 mirror) | |||
| SOL001, SOL002, SOL003, SOL005, SOL006 || July-2022 || Completed | |||
|- | |- | ||
| 002 | | |002 | ||
|introduce secondary container cluster network | |||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000357r1_SOL018_Missing_mapping_for_NAD.docx NFVSOL(22)000357r1] | |||
|SOL018 | |||
|July-2022 | |||
|Completed | |||
|} | |||
=== Issues === | |||
''List of issues raised based on the feature implementation.'' | |||
=== Security Considerations === | |||
''List of security considerations implied by the feature.'' | |||
== FEAT20: Auto == | |||
=== Overview === | |||
{| class="wikitable" | |||
|- | |- | ||
| | | '''Feature Prime''' || Haitao XIA (Huawei), xiahaitao@huawei.com | ||
|- | |- | ||
| | | '''Feature description''' || The scope of the feature covers the following areas: | ||
- NFV-MANO support for managing autonomous networks. | |||
- Enabling higher level of automation for NFV-MANO. | |||
- Intent-based principles for external exposure network services management. | |||
|- | |- | ||
| | | '''Target Release''' || '''Stage 1''': Release 4 informative work (2021-08-17) Published as [https://www.etsi.org/deliver/etsi_gr/NFV-IFA/001_099/041/04.01.01_60/gr_nfv-ifa041v040101p.pdf ETSI GR NFV-IFA 041 v4.1.1]. | ||
'''Stage 2 Step 1:''' MDAF related specs (IFA047) target release v4.4.1, | |||
'''Stage 2 Step 2:''' Intent management related specs (IFA050) target release v4.5.1. | |||
'''Stage 3:''' Release 4 (202x-X-X) | |||
|- | |- | ||
| | | '''Impacted WIs''' || '''Stage 2:''' IFA010ed441 (for MDAF functional requirements), IFA010ed451 (for Intent Management functional requirements) | ||
'''Stage 3:''' SOLzz | |||
|- | |- | ||
| | | '''MegaCRs''' || '''Stage 2:''' | ||
IFA010 MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//blackhole.doc NFVIFA(18)000xxx] (CR Status, to be created) | |||
'''Stage 3:''' | |||
SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//blackhole.doc NFVSOL(19)000zzz] (CR Status) | |||
|- | |- | ||
| | | '''Related/Dependent Features''' || FEAT07<br />FEAT26 | ||
|- | |- | ||
| | |New Specifcations | ||
|'''Stage 2:''' IFA047 (MDAF service interfaces specification); IFA050 (Intent management service interface specification) | |||
'''Stage 3:''' SOLaaa | |||
|- | |- | ||
| | | '''Status''' || '''Stage 1:''' Informative work completed (delivered in IFA041) | ||
'''Stage 2 Step 1:''' Normative work is ongoing, targeted to be completed until 2023 Q2. | |||
'''Stage 2 Step 2:''' | |||
'''Stage 3:''' Not started | |||
|- | |- | ||
| | | '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | ||
|- | |- | ||
| | | '''Feature team''' || '''Stage 2:''' Haitao XIA (Huawei), Cristina BADULESCU (Ericsson), Joan TRIAY (Docomo),Rajavarma BHYRRAJU (Ericsson), | ||
Jiachen ZHANG (China Mobile), Shen GAO (China Telecom), Shitao LI (Huawei) | |||
'''Stage 3:''' Name (Company) | |||
|- | |- | ||
| | | '''Last Updated''' || 2022-12-30 | ||
|} | |} | ||
=== Stage 2 Implementation Plan === | === Stage 2 Implementation Plan === | ||
Informative work in ETSI GR NFV-IFA 041(October 2019 - May 2021) | |||
'''IFA041''' | |||
''' | |||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|- | |- | ||
! ID !! Action !! Impacted | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 || | | 001 || First GR (IFA041) draft introducing the skeleton and the scope. | ||
'''Accepted contributions:''' | |||
NFVIFA(19)000859r2, NFVIFA(19)000860r1 | |||
| IFA || October-2019 || Done | |||
|- | |- | ||
| 002 | | |002 | ||
|Overview of related work in NFV-MANO and other SDOs. | |||
'''Accepted contributions:''' | |||
NFVIFA(19)000959, NFVIFA(19)000960r1, NFVIFA(19)000961r2, NFVIFA(19)000962r2, | |||
NFVIFA(19)000963r2, | |||
|IFA | |||
|February-2020 | |||
|Done | |||
| | |||
| | |||
| | |||
|- | |- | ||
|003 | |003 | ||
| | |Use cases related to NFV-MANO autonomous management, mainly include three categories: | ||
- | - Intent based NS management | ||
- Management Data Analytics assisted management | |||
- Autonomous container infrastructure management | |||
'''Accepted contributions:''' | |||
NFVIFA(20)000017r1, NFVIFA(20)000021, NFVIFA(20)000051r2, NFVIFA(20)000134r1, NFVIFA(20)000230r1, NFVIFA(20)000245r1, | |||
NFVIFA(20)000246r1, NFVIFA(20)000247r2, NFVIFA(20)000248r1, NFVIFA(20)000279r1, NFVIFA(20)000280r1, | |||
NFVIFA(20)000319, NFVIFA(20)000281r3, NFVIFA(20)000472r2, NFVIFA(20)000591, NFVIFA(20)000592, NFVIFA(20)000622r1, | |||
NFVVIFA(20)000720r3, NFVIFA(20)000781r1, NFVIFA(20)000782r1 | |||
|IFA | |||
|November-2020 | |||
|Done | |||
|- | |- | ||
| | |004 | ||
| | |Analysis of key issues related to use cases in Clause 6. | ||
'''Accepted contributions:''' | |||
NFVIFA(20)000353r1, NFVIFA(20)000354r2, NFVIFA(20)000355r1, NFVIFA(20)000416r2, NFVIFA(20)000418r2, | |||
NFVIFA(20)000445r1, NFVIFA(20)000446r1, NFVIFA(20)000447r1, NFVIFA(20)000557, NFVIFA(20)000566r3, | |||
|- | |||
| | NFVIFA(20)000593, NFVIFA(20)000594r3, NFVIFA(20)000623r4, NFVIFA(20)000624r1, NFVIFA(20)000729r3, | ||
NFVIFA(20)000732r3, NFVIFA(21)000793r1, NFVIFA(20)000878r1, NFVIFA(20)000879r1, NFVIFA(21)000013 | |||
NFVIFA(21)000014r2, NFVIFA(21)000022r1, NFVIFA(21)000058r1 | |||
|IFA | |||
|February-2021 | |||
|Done | |||
|- | |- | ||
| | |005 | ||
|Analysis of pontential architectural impacts on NFV-MANO in clause 7. | |||
'''Accepted contributions:''' | |||
NFVIFA(20)000794r1, NFVIFA(20)000797r3, NFVIFA(21)000060, NFVIFA(21)000062r7, NFVIFA(21)000133r2, | |||
NFVIFA(21)000134r5, NFVIFA(21)000135r2, NFVIFA(21)000149r7 | |||
|IFA | |||
|May-2021 | |||
|Done | |||
|- | |- | ||
| ''' | |006 | ||
|Recommendations and conclusion in clause 8. | |||
'''Accepted contributions:''' | |||
NFVIFA(21)000073, NFVIFA(21)000280r1, NFVIFA(21)000281r3, NFVIFA(21)000284r2, NFVIFA(21)000285r2, | |||
NFVIFA(21)000321r3, NFVIFA(21)000322r1, NFVIFA(21)000413 | |||
|IFA | |||
|May-2021 | |||
|Done | |||
|} | |||
Normative work plan (October 2021- June 2022) | |||
* Not urgent for ISG NFV to start the stage 2 normative work, need more close observation/analysis on 3GPP SA5 R17 related normative work (IDMS and MDAS) and FEAT23 output on MANO SBA. | |||
* One or two new group specifications are expected to carry stage 2 normative work on intent management and MDA interfaces. | |||
* MDA input information model improvement related normative work has been kicked off by FEAT28/IFA045 development. | |||
'''IFA047/IFA050''' | |||
(IFA047 development in March 2022 to January 2023, IFA050 development in July 2022 to June 2023) | |||
{| class="wikitable sortable" | |||
|- | |- | ||
| | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
| | |- | ||
| 001 || IFA047 first draft including the skeleton and scope || IFA || March-2022 || Done | |||
|- | |||
|002 | |||
|IFA047 interface requirements specification | |||
|IFA | |||
|May-2022 | |||
|Done | |||
|- | |||
|003 | |||
|IFA047 interface operations specification | |||
|IFA | |||
|November-2022 | |||
|Done | |||
|- | |||
|004 | |||
|IFA047 annex on use cases (stable draft) and IFA010ed441 megaCR | |||
|IFA | |||
|December-2022 | |||
|Done | |||
|- | |- | ||
| | |005 | ||
|IFA050 first draft including the skeleton and scope | |||
|IFA | |||
|July-2022 | |||
|Done | |||
|- | |- | ||
| | |006 | ||
|IFA050 use cases | |||
|IFA | |||
|January-2023 | |||
|Ongoing | |||
|- | |- | ||
| | |007 | ||
|IFA050 interface requirements specification | |||
|IFA | |||
|January-2023 | |||
|Planned | |||
|- | |- | ||
| | |008 | ||
|IFA050 interface operations specifications and IFA010ed451 megaCR | |||
|IFA | |||
|June-2023 | |||
|Planned | |||
|} | |} | ||
=== Stage | === Stage 3 Implementation Plan === | ||
Items to consider in the implementation plan | Items to consider in the implementation plan | ||
* Detailed description what has to be done in which work item. | * 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. | * Timeplan of when the team plans to conclude a particular action in the implementation plan. | ||
''' | '''SOL''' | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|- | |- | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 || Add interface X in to | | 001 || Add interface X in to SOL001. CR draft [LINK] || SOL || March-2018 || Open | ||
|} | |} | ||
=== Issues === | === Issues === | ||
''List of issues raised based on the feature implementation.'' | ''List of issues raised based on the feature implementation.'' | ||
=== Security Considerations === | === Security Considerations === | ||
'' | ''N/A.'' | ||
== | == FEAT21: 5GNFV == | ||
=== Overview === | === Overview === | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| '''Feature Prime''' || | | '''Feature Prime''' || Joan Triay (DOCOMO) | ||
|- | |- | ||
| '''Feature description''' || | | '''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 | | '''Target Release''' || '''Stage 2:''' Release 4 (2023/07)<br />'''Stage 3:''' TBD (Release 4 (2023/XX)) | ||
'''Stage 3:''' Release | |||
|- | |- | ||
| '''Impacted WIs''' || '''Stage 2:''' | | '''Impacted WIs''' || '''Stage 2:''' IFA010, IFA013, IFA014, IFA011, IFA007, IFA008, IFA049<br />'''Stage 3:''' TBD (SOLzz) | ||
'''Stage 3:''' TBD | |||
|- | |- | ||
| '''MegaCRs''' || '''Stage 2:''' | | '''MegaCRs''' || '''Stage 2:'''<br />ed431: includes action 007 of stage 2 work, i.e. "Add enhancements related to NSD processing"<br />- IFA010: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000186r1_IFA010ed431_FEAT21_MegaCR.docx NFVIFA(22)000186r1] IFA010ed431 FEAT21 MegaCR --> Approved at IFA#277<br />- IFA013: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000187r2_IFA013ed431_FEAT21_MegaCR.docx NFVIFA(22)000187r2] IFA013ed431 FEAT21 MegaCR --> Approved at IFA#277<br />- IFA014: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000188r1_IFA014ed431_FEAT21_MegaCR.docx NFVIFA(22)000188r1] IFA014ed431 FEAT21 MegaCR --> Approved at IFA#277<br />- MegaCR Index: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000248r2_FEAT21_stage_2_set__1_in_ed431_MegaCR_Index.docx NFVIFA(22)000248r2] FEAT21 stage 2 set #1 in ed431 MegaCR Index<br />ed441: no updates<br />ed451:<br />- IFA010: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000010r3_IFA010ed451_FEAT21_MegaCR_for_PaaS_Services_aspects.docx NFVIFA(23)000010r3] IFA010ed451 FEAT21 MegaCR for PaaS Services aspects<br />- IFA007: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000347r3_IFA007ed451_FEAT21_MegaCR_for_PaaS_Services_aspects.docx NFVIFA(23)000347r3] IFA007ed451 FEAT21 MegaCR for PaaS Services aspects<br />- IFA008: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000419r1_IFA008ed451_FEAT21_MegaCR_for_PaaS_Services_aspects.docx NFVIFA(23)000419r1] IFA008ed451 FEAT21 MegaCR for PaaS Services aspects<br />- IFA011: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000346r3_IFA011ed451_FEAT21_MegaCR_for_PaaS_Services_aspects.docx NFVIFA(23)000346r3] IFA011ed451 FEAT21 MegaCR for PaaS Services aspects<br />- IFA013: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000418r2_IFA013ed451_FEAT21_MegaCR_for_PaaS_Services_aspects.docx NFVIFA(23)000418r2] IFA013ed451 FEAT21 MegaCR for PaaS Services aspects<br />- IFA014: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000389r1_IFA014ed451_FEAT21_MegaCR_for_PaaS_Services_aspects.docx NFVIFA(23)000389r1] IFA014ed451 FEAT21 MegaCR for PaaS Services aspects<br /> | ||
|- | |- | ||
| '''Related/Dependent Features''' || | | '''Related/Dependent Features''' || FEAT17 on "Cloud-native VNF and container infrastructure management" | ||
FEAT19 on "NFV connectivity" | |||
|- | |- | ||
|New Specifcations | |'''New Specifcations''' | ||
|'''Informative:''' DGR/NFV- | |'''Informative:''' DGR/NFV-IFA037<br />'''Stage 2:''' None (currently)<br />'''Stage 3:''' TBD | ||
'''Stage 2:''' | |||
'''Stage 3:''' TBD | |||
|- | |- | ||
| '''Status''' || '''Informative:''' | | '''Status''' || '''Informative:''' completed<br />'''Stage 2:''' ongoing (70%)<br />'''Stage 3:''' ongoing (20%)<br /> | ||
'''Stage 2:''' | |||
'''Stage 3:''' | |||
|- | |- | ||
| '''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:''' | | '''Feature team''' || '''Informative:''' Joan Triay (DOCOMO)<br />'''Stage 2:''' Joan Triay (DOCOMO)<br />'''Stage 3:''' Name (Company) | ||
'''Stage 3:''' Name (Company) | |||
|- | |- | ||
| '''Last Updated''' || | | '''Last Updated''' || 2023-06-08 | ||
|} | |} | ||
=== | === Informative work === | ||
'''IFA''' | '''IFA''' | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
Line 3,193: | Line 3,586: | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 || | | 001 || Skeleton and scope<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019//NFVIFA(19)000900_IFA037_skeleton.zip NFVIFA(19)000900] IFA037 skeleton --> Approved <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019//NFVIFA(19)000901_IFA037_Scope.docx NFVIFA(19)000901] IFA037 Scope --> Approved || IFA || Nov-2019 || Completed | ||
| | |- | ||
| 002 || Introduction and overview<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019//NFVIFA(19)0001021_IFA037_Clause_4_1_Introduction_to_5G_network.docx NFVIFA(20)0001021] IFA037 Clause 4.1 Introduction to 5G network --> Approved <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2019//NFVIFA(19)0001022_IFA037_Clause_4_2_Characteristics_of_5G_network.docx NFVIFA(20)0001022] IFA037 Clause 4.2 Characteristics of 5G network --> Approved <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020//NFVIFA(20)000830_IFA037_Clause_5_1_Introduction_to_characteristics.docx NFVIFA(20)000830] IFA037 Clause 5.1 Introduction to characteristics --> Approved || IFA || Jan-2020 || Completed | |||
|- | |||
| 003 || Profiling and analysis of characteristic: Network function modularization <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2020//NFVIFA(20)000760r1_IFA037_Clause_5_Adding_characteristic_NF_modularization.docx NFVIFA(20)000760r1] IFA037 Clause 5 Adding characteristic NF modularization --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000573_FEAT21_IFA037_Clause_5_2_Gap_analysis_modularization.docx NFVIFA(21)000573] FEAT21 IFA037 Clause 5.2 Gap analysis modularization --> Approved || IFA || Dec-2020 || Completed | |||
|- | |- | ||
| 004 || Characteristic: Service-based interfaces, communication and service mesh <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000100r1_IFA037_Clause_5_Adding_characteristic_SBI__communication_and.zip NFVIFA(21)000100r1] FEAT21 IFA037 Clause 5 Adding characteristic SBI, communication and service mesh --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000544_FEAT21_IFA037_Clause_5_3_Adding_missing_solutions_on_SBI__co.zip NFVIFA(21)000544] FEAT21 IFA037 Clause 5.3 Adding missing solutions on SBI, communication and mesh --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000574_FEAT21_IFA037_Clause_5_3_Gap_analysis_SBI.docx NFVIFA(21)000574] FEAT21 IFA037 Clause 5.3 Gap analysis SBI --> Approved || IFA || Feb-2021 || Completed | |||
|- | |- | ||
| | | 005 || Characteristic: Network slicing <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000099r3_FEAT21_IFA037_Clause_5_Adding_characteristic_network_slicing.zip NFVIFA(21)000099r3] FEAT21 IFA037 Clause 5 Adding characteristic network slicing --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000545_FEAT21_IFA037_Clause_5_4_Completing_solutions_of_network_sli.docx NFVIFA(21)000545] FEAT21 IFA037 Clause 5.4 Completing solutions of network slicing --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000575_FEAT21_IFA037_Clause_5_4_Gap_analysis_network_slicing.docx NFVIFA(21)000575] FEAT21 IFA037 Clause 5.4 Gap analysis network slicing --> Approved || IFA || Feb-2021 || Completed | ||
|- | |- | ||
| 006 || Characteristic: Convergent (3GPP and non-3GPP) access <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000522r1_FEAT21_IFA037_Clause_5_Adding_characteristic_Convergent__acc.docx NFVIFA(21)000522r1] FEAT21 IFA037 Clause 5 Adding characteristic Convergent access --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000594_FEAT21_IFA037_Clause_5_10_Gap_analysis_convergent_access.docx NFVIFA(21)000594] FEAT21 IFA037 Clause 5.10 Gap analysis convergent access --> Approved|| IFA || Jun-2021 || Completed | |||
|- | |- | ||
| | | 007 || Characteristic: Stateless NF, with separation of data processing from state <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000257_IFA037_Clause_5_Adding_characteristic_Stateless_NF.zip NFVIFA(21)000257] IFA037 Clause 5 Adding characteristic Stateless NF --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000592r1_FEAT21_IFA037_Clause_5_7_Gap_analysis_stateless_NF.docx NFVIFA(21)000592r1] FEAT21 IFA037 Clause 5.7 Gap analysis stateless NF --> Approved || IFA || Mar-2021 || Completed | ||
| | |||
|- | |- | ||
| | | 008 || Characteristic: Network capabilities exposure <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000502_FEAT21_IFA037_Clause_5_Adding_characteristic_Network_capabil.zip NFVIFA(21)000502] FEAT21 IFA037 Clause 5 Adding characteristic Network capabilities exposure --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000595r2_FEAT21_IFA037_Clause_5_8_Gap_analysis_Network_capabilities_e.docx NFVIFA(21)000595r2] FEAT21 IFA037 Clause 5.8 Gap analysis Network capabilities exposure --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000722r3_FEAT21_IFA037_Start_cleaning_up_EN_nef_non3gpp.docx NFVIFA(21)000722r3] FEAT21 IFA037 Start cleaning up EN_nef_non3gpp --> Approved || IFA || May-2021 || Completed | ||
|- | |- | ||
| | | 009 || Characteristic: Distribution of services across the network (local and centralized) <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000293r1_FEAT21_IFA037_Clause_5_Adding_characteristic_distribution_of.zip NFVIFA(21)000293r1] FEAT21 IFA037 Clause 5 Adding characteristic distribution of services across the network --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000576r1_FEAT21_IFA037_Clause_5_4_Gap_analysis_services_distribution.zip NFVIFA(21)000576r1] FEAT21 IFA037 Clause 5.4 Gap analysis services distribution --> Approved || IFA || Mar-2021 || Completed | ||
|- | |- | ||
| | | 010 || Characteristic: Unified authentication framework <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000329r1_IFA037_Clause_5_Adding_characteristic_Unified_authentication.docx NFVIFA(21)000329r1] IFA037 Clause 5 Adding characteristic Unified authentication framework --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000496r1_FEAT21_IFA037_5_6_Adding_potential_solutions_for_characteris.zip NFVIFA(21)000496r1] FEAT21 IFA037 5.6 Adding potential solutions for characteristic Unified authentication framework --> Approved || IFA || May-2021 || Completed | ||
|- | |- | ||
| | | 011 || Characteristic: Roaming capabilities <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000526_FEAT21_IFA037_Clause_5_Adding_characteristic_roaming.docx NFVIFA(21)000526] FEAT21 IFA037 Clause 5 Adding characteristic roaming --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000593_FEAT21_IFA037_Clause_5_9_cleaning_up_editor_notes.docx NFVIFA(21)000593] FEAT21 IFA037 Clause 5.9 cleaning up editor notes --> Approved || IFA || Jul-2021 || Completed | ||
|- | |- | ||
| | | 012 || Derivation of recommendations and conclusion <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000639r1_FEAT21_IFA037_Clause_6_1_Adding_recommendations_overview.docx NFVIFA(21)000639r1] FEAT21 IFA037 Clause 6.1 Adding recommendations overview --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000659r2_FEAT21_IFA037_Clause_6_Adding_recommendations_related_to_all.docx NFVIFA(21)000659r2] FEAT21 IFA037 Clause 6 Adding recommendations related to all characteristics --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000660_FEAT21_IFA037_Clause_7_Adding_Conclusion.docx NFVIFA(21)000660] FEAT21 IFA037 Clause 7 Adding Conclusion --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000660_FEAT21_IFA037_Clause_7_Adding_Conclusion.docx NFVIFA(21)000660] FEAT21 IFA037 Clause 7 Adding Conclusion --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000678r4_FEAT21_IFA037_Clause_6_Adding_recommendations_related_to_uni.docx NFVIFA(21)000678r4] FEAT21 IFA037 Clause 6 Adding recommendations related to unified authentication --> Approved || IFA || Jul-2021 || Completed | ||
[https:// | |||
|- | |- | ||
| ' | | 013 || Address remaining major technical editor's notes <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000543_FEAT21_IFA037_Start_cleaning_up_EN.docx NFVIFA(21)000543] FEAT21 IFA037 Start cleaning up EN --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000544_FEAT21_IFA037_Clause_5_3_Adding_missing_solutions_on_SBI__co.zip NFVIFA(21)000544] FEAT21 IFA037 Clause 5.3 Adding missing solutions on SBI, communication and mesh --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000545_FEAT21_IFA037_Clause_5_4_Completing_solutions_of_network_sli.docx NFVIFA(21)000545] FEAT21 IFA037 Clause 5.4 Completing solutions of network slicing --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000677r2_FEAT21_IFA037_Clause_5_6_addresses_Editor_s_Note_about_SEC00.docx NFVIFA(21)000677r2] FEAT21 IFA037 Clause 5.6 addresses Editor’s Note about SEC005 and gap analysis of unified authentication framework --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000698_FEAT21_IFA037_Clauses_5_4_2_2_and_6_5_addressing_EN_about_L2.docx NFVIFA(21)000698] FEAT21 IFA037 Clauses 5.4.2.2 and 6.5 addressing EN about L2 connectivity --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000722r3_FEAT21_IFA037_Start_cleaning_up_EN_nef_non3gpp.docx NFVIFA(21)000722r3] FEAT21 IFA037 Start cleaning up EN_nef_non3gpp --> Approved || IFA || Jun/Jul-2021 || Completed | ||
FEAT21: | |||
|- | |- | ||
| | | 014 || Final review <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000748r1_IFA037_Review_clause_1_3_4_editorial_clean-up.docx NFVIFA(21)000748r1] IFA037 Review clause 1,3,4 editorial clean-up --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000749r1_IFA037_Review_clause_5_editorial_clean-up.docx NFVIFA(21)000749r1] IFA037 Review clause 5 editorial clean-up --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000768r1_IFA037_Review_clause_6_editorial_clean-up.docx NFVIFA(21)000768r1] IFA037 Review clause 6 editorial clean-up --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000777_IFA037_Review_6_3_refining_recommendations_002_and_003.docx NFVIFA(21)000777] IFA037 Review 6.3 refining recommendations 002 and 003 --> Noted <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000796r1_IFA037_review_-_editorial_fixes_and_small_technical_wording_.zip NFVIFA(21)000796r1] IFA037 review - editorial fixes and small technical wording improvements --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000797_IFA037_review_-_comments_and_questions.zip NFVIFA(21)000797] IFA037 review - comments and questions --> Noted <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000798r2_IFA037_review_-_miscellaneous_technical_improvements.docx NFVIFA(21)000798r2] IFA037 review - miscellaneous technical improvements --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000807_FEAT21_IFA037_Clause_5_1_Statement_of_3GPP_Release_baseline_.docx NFVIFA(21)000807] FEAT21 IFA037 Clause 5.1 Statement of 3GPP Release baseline and update of references --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000809r1_FEAT21_IFA037_Clause_4_to_5_6_2_2_Minor_miscellaneous_change.docx NFVIFA(21)000809r1] FEAT21 IFA037 Clause 4 to 5.6.2.2 Minor miscellaneous changes --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000820r1_FEAT21_IFA037_Clauses_5_7_to_5_10_Miscellaneous_changes.zip NFVIFA(21)000820r1] FEAT21 IFA037 Clauses 5.7 to 5.10 Miscellaneous changes --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000821r1_FEAT21_IFA037_Clauses_6_Miscellaneous_changes_to_recommendat.docx NFVIFA(21)000821r1] FEAT21 IFA037 Clauses 6 Miscellaneous changes to recommendations --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000822_FEAT21_IFA037_Deleting_unused_clauses.docx NFVIFA(21)000822] FEAT21 IFA037 Deleting unused clauses --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000838_IFA037_review_-_removing_misleading_recommendations_.docx NFVIFA(21)000838] IFA037 review - removing misleading recommendations --> Noted <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000842r2_FEAT21_IFA037_Remaining_miscellaneous_changes_from_797_comme.zip NFVIFA(21)000842r2] FEAT21 IFA037 Deleting unused clauses --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000848r2_FEAT21_IFA037_Comments_missing_gap_associated_recommendation.docx NFVIFA(21)000848r2] FEAT21_IFA037_Comments_missing_gap_associated_recommendations --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000849_FEAT21_IFA037_Clause_5_6_Clarifying_security_aspects.zip NFVIFA(21)000849] FEAT21 IFA037 Clause 5.6 Clarifying security aspects --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000852_FEAT21_IFA037_Security_comments_in_clause_5_6.docx NFVIFA(21)000852] FEAT21 IFA037 Security comments in clause 5.6 --> Approved <br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000872r1_FEAT21_IFA037_security_recommendations_gap_5_5.docx NFVIFA(21)000872r1] FEAT21_IFA037_security_recommendations_gap 5.5 --> Agreed at IFA#256|| IFA || Aug/Sep-2021 || Completed | ||
| | |||
| | |||
| | |||
|} | |} | ||
Line 3,267: | Line 3,620: | ||
* Timeplan of when the team plans to conclude a particular action in the implementation plan. | * Timeplan of when the team plans to conclude a particular action in the implementation plan. | ||
'''IFA''' | '''IFA''' | ||
{| class="wikitable sortable" | |||
|- | |||
! ID !! Action !! Impacted WI(s) !! Target completion !! Status | |||
|- | |||
| 001 || Add functional requirements for the NFV architectural framework to include the support of inventory of VNF Common and Dedicated Services and platform/infrastructure capabilities (5gnfv.arch.001)<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)0001022r2_IFA010ed431_FEAT21_Adding_PaaS_Services_management.docx NFVIFA(21)0001022r2] IFA010ed431 FEAT21 Adding PaaS Services management --> FEAT Agreed at IFA#266 <br />- NFVIFA(22)000123 IFA010ed431 FEAT21 Adding PaaS Services management --> see action 005<br />Pending CRs:<br />- None | |||
| IFA010 || Jun-2023 || style="background: #A7F432;" | All CRs FEAT agreed | |||
|- | |||
| 002 || Add functional requirements for the NFV architectural framework to include the support of operator certificate management functions (5gnfv.arch.002), requirements on the operator certificate management functions to synchronize the LCM of the certificates with the LCM operations of the VNF/VNFC (5gnfv.func.008), and retrieval of VNF/VNFC runtime information from VNFM/NFVO (5gnfv.if.011). See note 2. || IFA010 || See ENH01.01 || See ENH01.01 | |||
|- | |||
| 003 || Add functional requirements to the VNFM, and interface and information model specification to the VNF LCM to support adding/removing VNF external CP that are not sub-ports of a trunk (5gnfv.func.001, 5gnfv.if.004). || IFA010, IFA007, IFA008 || Jun-2023 || style="background: red;" |Not started | |||
|- | |||
| 004 || Add requirements and modelling for the VNFD and NSD to support describing requirement to use VNF Common/Dedicated Services (5gnfv.desc.001). See note 3.<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)0001025_IFA011ed431_FEAT21_Adding_requirements_for_PaaS_Services.docx NFVIFA(21)0001025] IFA011ed431 FEAT21 Adding requirements for PaaS Services --> FEAT Agreed at IFA#265 <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)0001028r1_IFA014ed431_FEAT21_Adding_requirements_for_PaaS_Services.docx NFVIFA(21)0001028r1] IFA014ed431 FEAT21 Adding requirements for PaaS Services --> FEAT Agreed at IFA#266<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000276r1_FEAT21_IFA011_VNFD_modeling_to_use_PaaS_Services.docx NFVIFA(23)000276r1] FEAT21 IFA011 VNFD modeling to use PaaS Services: FEAT Agreed at IFA#332<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000277r2_FEAT21_IFA014_NSD_modeling_to_use_PaaS_Service.docx NFVIFA(23)000277r2] FEAT21 IFA014 NSD modeling to use PaaS Service: FEAT Agreed at IFA#335<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000351_IFA011ed451_FEAT21_VNFD_PaaS_Servivce_modeling_refinements_o.docx NFVIFA(23)000351] IFA011ed451 FEAT21 VNFD PaaS Servivce modeling refinements on top of 276r1: FEAT Agreed at IFA#335<br />Pending CRs:<br />- None | |||
| IFA011, IFA014 || Jun-2023 || style="background: #A7F432;" | All CRs FEAT agreed | |||
|- | |||
| 005 || Determining the mapping and requirements for the NFV architectural framework about the "PaaS service management function" (5gnfv.func.002). See note 3.<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000123r5_IFA010ed431_FEAT21_Mapping_of_PSM_and_NFV-MANO.docx NFVIFA(22)000123r5] IFA010ed431 FEAT21 Adding PaaS Services management --> FEAT Agreed at IFA#313<br />- Addressing editor's notes as shown in the interim MegaCR for IFA010 in contribution [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000010_IFA010ed441_FEAT21_MegaCR.docx NFVIFA(23)000010] [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000278r1_FEAT21_IFA010_Address_EN_about_PSM_framework.zip NFVIFA(23)000278r1] FEAT21 IFA010 Address EN about PSM framework: FEAT Agreed at IFA#332<br />Pending CRs:<br />- None | |||
| IFA010 || Jun-2023 || style="background: #A7F432;" | All CRs FEAT agreed | |||
|- | |||
| 006 || Add functional requirements to the VNFM and NFVO to support determining and triggering LCM for VNF Common/Dedicated Services (5gnfv.func.002, 5gnfv.func.003). See note 3.<br />Contributions:<br />- NFVIFA(22)000123r1 IFA010ed431 FEAT21 Adding PaaS Services management --> see action 005<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000279_FEAT21_IFA007_Enhance_granting_to_support_PaaS_Services_requ.docx NFVIFA(23)000279] FEAT21 IFA007 Enhance granting to support PaaS Services requirements for a VNF: FEAT Agreed at IFA#332<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000300_FEAT21_IFA007_Enhance_VnfInfo_to_support_PaaS_Services_infor.docx NFVIFA(23)000300] FEAT21 IFA007 Enhance VnfInfo to support PaaS Services information for a VNF: FEAT Agreed at IFA#332<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000301_FEAT21_IFA013_Enhance_NsInfo_to_support_PaaS_Services_inform.docx NFVIFA(23)000301] FEAT21 IFA013 Enhance NsInfo to support PaaS Services information for a VNF and NS: FEAT Agreed at IFA#332<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000409__Mirror_of_300__FEAT21_IFA008_Enhance_VnfInfo_to_support_Paa.docx NFVIFA(23)000409] (Mirror of 300) FEAT21 IFA008 Enhance VnfInfo to support PaaS Services information for a VNF: Almost FEAT agreed at IFA#336<br />Pending CRs:<br />- None | |||
| IFA010, IFA007, IFA008, IFA013 || Jun-2023 || style="background: #A7F432;" | All CRs FEAT agreed | |||
|- | |||
| 007 || Add enhancements related to NSD processing: <br />- requirements and modelling on the NSD management interface to allow onboarding of an NSD even if not all VNF packages, nested NSDs and PNFDs have been previously on-boarded (5gnfv.func.004a),<br />- requirements and modelling on the NS LCM to handle the case of not all constituent elements being on-boarded (5gnfv.if.006),<br />- functional requirement to the NFVO to support processing information related to version dependencies between constituent VNF (5gnfv.func.004b),<br />- requirements for the NSD regarding whether NSD on-boarding can be performed even if not all referred VNF Packages, NSD and PNFDs are on-boarded (5gnfv.desc.007a), and<br />- requirements for the NSD to support information related to constituent VNF version dependencies (5gnfv.desc.007b). <br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000086r1_FEAT21-IFA010ed431-Clause_6_3_1_NFVO_support_for_version_dep.docx NFVIFA(22)000086r1] FEAT21-IFA010ed431-Clause 6.3.1 NFVO support for version dependency information --> FEAT Agreed at IFA#273 <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000100r1_FEAT21_IFA014ed431_Adding_version_dependencies.docx NFVIFA(22)000100r1] FEAT21 IFA014ed431 Adding version dependencies --> FEAT agreed at IFA#275 <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000101r1_FEAT21-IFA013ed431-Adding_version_dependencies_to_NS_LCM_ope.docx NFVIFA(22)000101r1] FEAT21-IFA013ed431-Adding version dependencies to NS LCM operations --> FEAT agreed at IFA#275 <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000178_FEAT21_IFA013ed431_Exposure_of_version_dependencies.docx NFVIFA(22)000178] FEAT21 IFA013ed431 Exposure of version dependencies --> FEAT Agreed at IFA#276<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000191r1_FEAT21-IFA014ed431-Clause_6_2_2_Add_flag_for_strict_NSD_onbo.docx NFVIFA(22)000191r1] FEAT21-IFA014ed431-Clause 6.2.2 Add flag for strict NSD onboarding --> Agreed at IFA#276 <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000192r1_FEAT21-IFA010ed431-Clause_6_6_1_NFVO_allow_lenient_NSD_onboa.docx NFVIFA(22)000192r1] FEAT21-IFA010ed431-Clause 6.6.1 NFVO allow lenient NSD onboarding --> FEAT Agreed at IFA#276 <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000189r1_FEAT21_IFA013ed431_precondition_about_onboarded_constituents.docx NFVIFA(22)000189r1] FEAT21 IFA013ed431 precondition about onboarded constituents --> FEAT Agreed at IFA#276|| IFA013, IFA010, IFA011, IFA014 || Nov-2021 || style="background: green;" |Completed in IFAed431 | |||
|- | |||
| 008 || Add requirements to extend the capability support of NFVO and VNFM to handle the modification of security groups of a particular VNF instance based on LCM actions performed on the corresponding VNF instance (5gnfv.func.005, 5gnfv.if.007) and updates on the relevant descriptors to indicate the mapping of security groups to target CP (5gnfv.desc.008). || IFA010, IFA007, IFA014 || Jun-2023 || style="background: red;" |Not started | |||
|- | |||
| 009 || Add enhancements to the VL construct to support additional services such as name resolution, communication security, etc. (5gnfv.desc.002).<br />Contributions:<br />- CR for IFA014 to address 5gnfv.desc.002 [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000406r1_FEAT21_IFA014ed451_Enhancing_VL_with_additional_capabilities.docx NFIFA(23)000406r1] FEAT21 IFA014ed451 Enhancing VL with additional capabilities (action 009): FEAT Agreed at IFA#337 || IFA014 || Jun-2023 || style="background: #A7F432;" | All CRs FEAT agreed | |||
|- | |||
| 010 || Add enhancements, requirements to address the capability to indicate, reuse and shared virtualised resources among VNF instances, including extensions to the granting LCM interface (5gnfv.desc.004, 5gnfv.desc.005, 5gnfv.if.005) and to the scaling of virtualised storage resources independently (5gnfv.desc.003).<br />Contributions:<br /> | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000008r1_IFA007ed441_FEAT21_Granting_for_shared_virtual_resource.docx NFVIFA(23)000008r1] IFA007ed441 FEAT21 Granting for shared virtual resource --> Almost FEAT Agreed at IFA#316<br /> | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000079r2_FEAT21_IFA011ed451_Add_scaling_model.zip NFVIFA(23)000079r2] FEAT21 IFA011ed451 Add scaling model --> Available<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000081r1_FEAT21_IFA011ed451_VNFD_for_storage_scaling.docx NFVIFA(23)000081r1] FEAT21 IFA011ed451 VNFD for storage scaling --> Available | |||
| IFA011, IFA014, IFA007 || Jun-2023 || style="background: orange;" |Ongoing | |||
|- | |||
| 011 || Add requirements and modelling to the NS LCM interface to address various capabilities:<br />- providing information about external L2 networks (5gnfv.if.001),<br />- providing location constraints of constituents of a VNF to be deployed (5gnfv.if.002),<br />- providing naming related information related to SAP or VNF external CP (5gnfv.if.003), and<br />- relevant descriptor enhancements in the VNFD/NSD for additional network properties (5gnfv.desc.006).<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000440_FEAT21_IFA013ed451_Providing_naming_related_information_for_.docx NFVIFA(23)000440] FEAT21 IFA013ed451 Providing naming related information for SAP or VnfExtCp (action 011): FEAT Agreed at IFA#337<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000441__mirror_of_440__FEAT21_IFA007ed451_Providing_naming_relating.docx NFVIFA(23)000441] (mirror of 440) FEAT21 IFA007ed451 Providing naming relating information for VnfExtCp (action 011): FEAT Agreed at IFA#337<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000442__mirror_of_440__FEAT21_IFA008ed451_Providing_naming_relating.docx NFVIFA(23)000442] (mirror of 440) FEAT21 IFA008ed451 Providing naming relating information for VnfExtCp (action 011): FEAT Agreed at IFA#337<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000439_FEAT21_IFA013ed451_Providing_location_constraints_of_VNF_con.docx NFVIFA(23)000439] FEAT21 IFA013ed451 Providing location constraints of VNF constituents (action 011): FEAT Agreed at IFA#337<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000438_FEAT21_IFA013ed451_Providing_information_about_external_L2_n.docx NFVIFA(23)000438] FEAT21 IFA013ed451 Providing information about external L2 networks (action 011): FEAT Agreed at IFA#337<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000437_FEAT21_IFA011ed451_Additional_network_properties_for_CPs__ac.docx NFVIFA(23)000437] FEAT21 IFA011ed451 Additional network properties for CPs (action 011): To be revised at IFA#337|| IFA013, IFA011, IFA014, IFA007, IFA008 || Jun-2023 || style="background: orange;" |Ongoing | |||
|- | |||
| 012 || Update the definition of VNF to clarify that a VNF can be used to deploy the implementation of a subset of an NF (5gnfv.func.007). || NFV003 || Jun-2023 || style="background: red;" |Not started | |||
|- | |||
| 013 || Enhancements to the VNFD to support describing requirements to use VNF Common/Dedicated Services related to authorization server (5gnfv.desc.009), CA (5gnfv.desc.010) and identify if VNF provides authorization server capabilities (5gnfv.desc.011). See notes 2 and 3. || IFA011 || Jun-2023 || style="background: red;" |Not started. Postponed to complete first ENH01.01 | |||
|- | |||
| 014 || Add functional requirements, interface requirements, interface modelling to cover the aspects of registering/unregistering client information in respective authorization server:<br />- NFVO requirements (5gnfv.func.006)<br />- VNF LCM interface (5gnfv.if.008)<br />- VNF Configuration interface (5gnfv.if.009 and 5gnfv.if.010)<br />See note 2.|| IFA010, IFA007, IFA008 || Jun-2023 || style="background: red;" |Not started. Postponed to complete first ENH01.01 | |||
|- | |||
| 015 || Document about the potential use of non-MANO artefacts describing the relationship of scaling aspects with the purposed services offered by the VNF (5gnfv.other.001). || IFA011 || Jun-2023 || style="background: red;" |Not started | |||
|- | |||
| 016 || Modeling of the PaaS Services descriptors for VNF Common/Dedicated services.<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000280_FEAT21_IFA049_Scope_and_skeleton_extension_for_future_IFA049.zip NFVIFA(23)000280] FEAT21 IFA049 Scope and skeleton extension for future IFA049 version to include PaaS Services management: available || IFA049|| Jan-2024 || style="background: orange;" |Ongoing | |||
|- | |||
| 017 || Specification of interfaces and information modeling of management of PaaS Services.<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000280_FEAT21_IFA049_Scope_and_skeleton_extension_for_future_IFA049.zip NFVIFA(23)000280] FEAT21 IFA049 Scope and skeleton extension for future IFA049 version to include PaaS Services management: available || IFA049|| Jan-2024 || style="background: orange;" |Ongoing | |||
|- | |||
| colspan="5" | NOTE 1: In the actions, references to relevant recommendations in ETSI GR NFV-IFA 037 v0.12.0 are provided for more information and details regarding the expected recommendation.<br />NOTE 2: This action might be performed via a specific "security enhancement" feature. If so, proper cross-referencing will be highlighted on the feature plan.<br />NOTE 3: Relationship with other features such as FEAT24 "Generic VNF OAM" and FEAT17 on aspects of "PaaS" will be evaluated to determine what feature work takes final responsibility to perform the specification in order to avoid overlapping specification. | |||
|- | |||
|} | |||
=== Stage 3 Implementation Plan === | |||
Items to consider in the implementation plan | |||
* Detailed description what has to be done in which work item. | |||
* Timeplan of when the team plans to conclude a particular action in the implementation plan. | |||
'''SOL''' | |||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|- | |- | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
|001 | | 001 || Add version dependancy to VNFD and NSD | ||
| | - [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000189_FEAT21_SOL001ed431_implementation.docx NFVSOL(22)000189]: Approved - [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000225_FEAT21_SOL001ed431_correction.docx NFVSOL(22)000225]: Approved | ||
| SOL001 || 2022-April || Completed | |||
[https://docbox.etsi.org/ISG/NFV/ | |||
| | |||
| | |||
| | |||
|- | |- | ||
|002 | |002 | ||
| | |Add version dependancy to VNFD and NSD | ||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000305_SOL006ed431_Version_Dependencies_from_IFA014ed431_FEAT21_Meg.docx NFVSOL(22)000305]: Approved | |||
|SOL006 | |||
|2022-April | |||
|Completed | |||
[https://docbox.etsi.org/ISG/NFV/ | |||
| | |||
| | |||
| | |||
|- | |- | ||
|003 | |003 | ||
| | |Add version dependency to VNF LCM and NS LCM | ||
- [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000173_SOL005ed431_FEAT21_NFV_support_for_5G.docx NFVSOL(22)000173] | |||
|SO005 | |||
|2022-April | |||
|Completed | |||
|} | |||
=== Issues === | |||
''List of issues raised based on the feature implementation.'' | |||
=== Security Considerations === | |||
''List of security considerations implied by the feature.'' | |||
== FEAT22: M-Tenant == | |||
=== Overview === | |||
{| class="wikitable" | |||
|- | |||
| '''Feature Prime''' || Ulrich Kleber, Huawei, Ulrich.kleber@huawei.com | |||
|- | |||
| '''Feature description''' || Start with use cases where multiple users consume services from the same NFV-MANO environment and implement necessary enhancements in the NFV-MANO stack. | |||
|- | |- | ||
| | | '''Target Release''' || '''Stage 1:''' Release 5 | ||
| | '''Stage 2:''' Release 5 (2021-X-X) <br> | ||
'''Stage 3:''' Release 5 (2021-X-X) | |||
|- | |- | ||
| | | '''Impacted WIs''' || '''Stage 1:''' EVE018 | ||
| | '''Stage 2:''' tbd <br> | ||
| | '''Stage 3:''' tbd | ||
|- | |- | ||
| | | '''MegaCRs''' || '''Stage 2:''' IFAxxx MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//blackhole.doc NFVIFA(18)000xxx] (CR Status) <br> | ||
| | IFAyyy MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//blackhole.doc NFVIFA(18)000yyy] (CR Status) <br> | ||
| | '''Stage 3:''' SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//blackhole.doc NFVSOL(19)000zzz] (CR Status) | ||
| | |- | ||
| | | '''Related/Dependent Features''' || | ||
|- | |||
|New Specifcations | |||
|'''Stage 1:''' EVE018 <br> | |||
'''Stage 2:''' none <br> | |||
'''Stage 3:''' none | |||
|- | |||
| '''Status''' || '''Stage 1:''' Ongoing (60% completed) | |||
'''Stage 2:''' Not started | |||
'''Stage 3:''' Not started | |||
|- | |||
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | |||
|- | |||
| '''Feature team''' || '''Stage 1:''' U.Kleber (Huawei) <br> | |||
'''Stage 2:''' Name (Company) <br> | |||
'''Stage 3:''' Name (Company) <br> | |||
|- | |||
| '''Last Updated''' || 2021-09-22 | |||
|} | |||
=== Stage 2 Implementation Plan === | |||
Items to consider in the implementation plan | |||
* Detailed description what has to be done in which work item. | |||
* Timeplan of when the team plans to conclude a particular action in the implementation plan. | |||
'''IFA''' | |||
{| class="wikitable sortable" | |||
|- | |- | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | |||
|- | |- | ||
| | | 001 || Add interface X in to IFA0xx. CR draft [LINK] || IFA || xx || Open | ||
|} | |} | ||
'''SOL''' | '''SOL''' | ||
Line 3,366: | Line 3,759: | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 || Add interface X in to | | 001 || Add interface X in to SOL0xx. CR draft [LINK] || SOL || xx || Open | ||
|} | |} | ||
Line 3,378: | Line 3,771: | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 || Add interface X in to | | 001 || Add interface X in to SOL0xx. CR draft [LINK] || SOL || xx || Open | ||
|} | |} | ||
Line 3,387: | Line 3,780: | ||
''List of security considerations implied by the feature.'' | ''List of security considerations implied by the feature.'' | ||
== | == FEAT23: M-SBA == | ||
=== Overview === | === Overview === | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| '''Feature Prime''' || | | '''Feature Prime''' || Janusz Pieczerak, Orange, janusz.pieczerak@orange.com | ||
|- | |- | ||
| '''Feature description''' || This feature | | '''Feature description''' || This feature studies the application of a Service-Based Architecture (SBA) design style to the NFV architectural framework and provides recommendations on the evolution of the ISG specifications structure to apply SBA design patterns to the NFV architectural framework. | ||
|- | |- | ||
| '''Target Release''' || '''Stage 2:''' Release | | '''Target Release''' || '''Stage 2:''' Release 5 (2022-12) | ||
'''Stage 3:''' Release | '''Stage 3:''' Release 5 (2024-X-X) | ||
|- | |- | ||
| '''Impacted WIs''' || '''Stage 2:''' | | '''Impacted WIs''' || '''Stage 2:''' TBD | ||
'''Stage 3:''' | '''Stage 3:''' TBD | ||
|- | |- | ||
| '''MegaCRs''' || '''Stage 2:''' | | '''MegaCRs''' || '''Stage 2:''' | ||
IFAxxx | IFAxxx | ||
'''Stage 3:''' | '''Stage 3:''' | ||
Line 3,409: | Line 3,801: | ||
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''' || | | '''Related/Dependent Features''' || None | ||
|- | |- | ||
|New Specifcations | |New Specifcations | ||
|'''Stage 2:''' | |'''Informative:''' DGR/NFV-IFA039 (published) | ||
'''Stage 3:''' | '''Stage 2:''' TBD | ||
'''Stage 3:''' TBD | |||
|- | |- | ||
| '''Status''' || '''Stage 2:''' | | '''Status''' || '''Informative:''' Completed (100%) | ||
'''Stage 3:''' | '''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:''' | | '''Feature team''' || '''Stage 2:''' Janusz Pieczerak (Orange) | ||
'''Stage 3:''' Name (Company) | '''Stage 3:''' Name (Company) | ||
|- | |- | ||
| '''Last Updated''' || | | '''Last Updated''' || 2022-12-06 | ||
|} | |} | ||
Line 3,435: | Line 3,829: | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 || | | 001 || Add interface X in to IFA007. CR draft [LINK] || IFA || 2023 || Open | ||
|} | |||
'''SOL''' | |||
{| class="wikitable sortable" | |||
|} | |||
'''SOL''' | |||
{| class="wikitable sortable" | |||
|- | |- | ||
! 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 || | | 001 || Add interface X in to SOL001. CR draft [LINK] || SOL || 2024 || Open | ||
|} | |} | ||
Line 3,467: | Line 3,848: | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 || | | 001 || Add interface X in to SOL001. CR draft [LINK] || SOL || March-2018 || Open | ||
|} | |} | ||
Line 3,476: | Line 3,857: | ||
''List of security considerations implied by the feature.'' | ''List of security considerations implied by the feature.'' | ||
== | == FEAT24: VNF-OAM == | ||
=== Overview === | === Overview === | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| '''Feature Prime''' || | | '''Feature Prime''' || Kostas Katsalis, DOCOMO, Katsalis@docomolab-euro.com & Yuhan Zhang, China Mobile, zhangyuhan@chinamobile.com | ||
|- | |- | ||
| '''Feature description''' || This feature will analyse | | '''Feature description''' || This feature will analyse and define the type of OAM functions for VNFs that can be generalized and be provided as a “generic function” supporting the provisioning, connectivity, configuration and monitoring of VNFs on a virtualized platform. The feature will also determine possible solutions to realize such generic OAM functions, e.g., by leveraging PaaS capabilities. The result report will include, if necessary, recommendations for requirements and architectural enhancements. | ||
|- | |- | ||
| '''Target Release''' || '''Stage 2:''' Release 4 ( | | '''Target Release''' || '''Stage 2:''' Release 4 (December 2022) | ||
'''Stage 3:''' Release 4 ( | '''Stage 3:''' Release 4 (2020-X-X) | ||
|- | |- | ||
| '''Impacted WIs''' || '''Stage 2:''' | | '''Impacted WIs''' || '''Stage 2:''' IFAxx, IFAyy | ||
'''Stage 3:''' | '''Stage 3:''' SOLzz | ||
|- | |- | ||
| '''MegaCRs''' || '''Stage 2:''' | | '''MegaCRs''' || '''Stage 2:''' | ||
[https://www.etsi.org/deliver/etsi_gr/NFV-EVE/001_099/019/04.01.01_60/gr_NFV-EVE019v040101p.pdf EVE019 GR] | |||
IFA0xx | |||
'''Stage 3:''' | '''Stage 3:''' | ||
SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2019//blackhole.doc NFVSOL(19)000zzz] (CR Status) | |||
|- | |- | ||
| '''Related/Dependent Features''' || | | '''Related/Dependent Features''' || FEAT17: cloud-native VNF and NFV architecture PaaS | ||
FEAT21: 5GNFV | |||
|- | |- | ||
|New Specifcations | |New Specifcations | ||
|'''Stage 2:''' | |'''Stage 2:''' IFA049 | ||
'''Stage 3:''' | '''Stage 3:''' SOLaaa | ||
|- | |- | ||
| '''Status''' || '''Stage 2:''' Ongoing( | | '''Status''' || '''Stage 2:''' Ongoing (10% completed) | ||
'''Stage 3:''' Not started | '''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:''' | | '''Feature team''' || '''Stage 2:''' Kostas Katsalis (DOCOMO), Yuhan Zhang (China Mobile) | ||
'''Stage 3:''' Name (Company) | '''Stage 3:''' Name (Company) | ||
|- | |- | ||
| '''Last Updated''' || | | '''Last Updated''' || 2022-10-02 | ||
|} | |} | ||
=== Stage 2 Implementation Plan === | === Stage 2 Implementation Plan === | ||
Items to consider in the implementation plan | |||
* Detailed description what has to be done in which work item. | * 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. | * Timeplan of when the team plans to conclude a particular action in the implementation plan. | ||
Line 3,521: | Line 3,907: | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 | | |001 | ||
|Skeleton, scope, and term definitions (Clauses 1, 2, 3) | |||
CR drafts: | |||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000283r2_FEAT24_IFA_049_skeleton.zip NFVIFA(22)000283r2] (Approved) | ||
| | |IFA049 | ||
| | |||
|Ongoing | |||
|- | |- | ||
|002 | |002 | ||
| | |Overview and framework for Generic OAM functions (Clause 4) | ||
CR drafts: | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000419r1_FEAT24_IFA049_Overview_of_the_VNF_generic_OAM_functions_fram.docx NFVIFA(22)000419r1] (Approved) | |||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000493r1_FEAT24_IFA049_requirements_for_the_generic_OAM_framework_.docx NFVIFA(22)000493r1] (Approved) | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000518_FEAT24_IFA049_generic_OAM_framework_considerations.docx NFVIFA(22)000518] (Approved) | ||
| | |IFA049 | ||
| | | | ||
| | |Ongoing | ||
|- | |- | ||
|003 | |003 | ||
| | |Specify the functional requirements for Generic OAM functions (Clause 5) | ||
CR drafts: | |||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000422r3_FEAT24_IFA049_Functional_requirements_for_VNF_generic_OAM_fu.docx NFVIFA(22)000422r3] (Approved) | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000435_Functional_requirements_for_VNF_generic_OAM_function_Network.docx NFVIFA(22)000435] (Approved) | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000441r3_FEAT24_IFA049_Functional_requirements_for_VNF_generic_OAM_Lo.docx NFVIFA(22)000441r3] (Approved) | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000443r3_FEAT24_IFA049_Functional_requirements_for_VNF_generic_OAM_Lo.docx NFVIFA(22)000443r3] (Approved) | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000444r3_FEAT24_IFA049_Functional_requirements_for_VNF_generic_OAM_Me.docx NFVIFA(22)000444r3] (Approved) | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000445r2_FEAT24_IFA049_Functional_requirements_for_VNF_generic_OAM_Me.docx NFVIFA(22)000445r2] (Approved) | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000475r2_FEAT24_IFA049_Functional_requirements_for_VNF_generic_OAM_fu.docx NFVIFA(22)000475r2] (Approved) | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000540r2_FEAT24_IFA049_Functional_requirements_for_VNF_generic_OAM_fu.docx NFVIFA(22)000540r2] (Approved) | ||
|IFA049 | |||
NFVIFA( | | | ||
|Ongoing | |||
| | |||
| | |||
| | |||
|- | |- | ||
|004 | |004 | ||
| | |Specify the interface requirements for Generic OAM functions (Clause 6) | ||
CR drafts: | |||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000541r2_FEAT24_IFA049_Interface_requirements_for_VNF_generic_OAM_fun.docx NFVIFA(22)000541r2] | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000542r2_FEAT24_IFA049_Interface_for_VNF_generic_OAM_Metric_Aggregato.docx NFVIFA(22)000542r2] | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000562_FEAT24_IFA049_Interace_requirement_VNF_generic_OAM_Metric_An.docx NFVIFA(22)000562] | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000567r1_FEAT24_IFA049_Interface_requirements_for_VNF_generic_OAM_fun.docx NFVIFA(22)000567r1] | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000593r1_FEAT24_IFA049_Interace_requirement_VNF_generic_OAM_Log_Analy.docx NFVIFA(22)000593r1] | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000594_FEAT24_IFA049_Interface_requirement_VNF_generic_OAM_Log_Aggr.docx NFVIFA(22)000594] | ||
NFVIFA( | [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000591r2_FEAT24_IFA049_Interface_requirements_for_VNF_generic_OAM_fun.docx NFVIFA(22)000591r2] | ||
|IFA049 | |||
| | |||
|Ongoing | |||
|- | |||
|005 | |||
|Specify information elements (Clause 7) | |||
|IFA049 | |||
|December-2022 | |||
|Open | |||
|- | |||
|006 | |||
|Specify service interaction with VNF (Clause 8) | |||
|IFA049 | |||
|December-2022 | |||
|Open | |||
|- | |||
|007 | |||
|Specify Descriptors for Generic OAM functions (Clause 9) | |||
|IFA049 | |||
|December-2022 | |||
|Open | |||
|- | |||
| 00x || Add interface X in to IFA007. CR draft [LINK] || IFA || March-2020 || Open | |||
|} | |||
'''SOL''' | |||
{| class="wikitable sortable" | |||
|- | |||
! 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''' | |||
{| 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 === | |||
''List of security considerations implied by the feature.'' | |||
NFVIFA( | == FEAT25: VNF-CI == | ||
=== Overview === | |||
{| class="wikitable" | |||
|- | |||
| '''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 [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) | |||
'''Stage 3:''' | |||
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 | |||
|- | |||
|New Specifcations | |||
|'''Stage 2:''' none | |||
'''Stage 3:''' SOLaaa | |||
|- | |||
| '''Status''' || '''Stage 2:''' Completed | |||
'''Stage 3:''' Ongoing (20% completed) | |||
|- | |||
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org 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''' | |||
{| class="wikitable sortable" | |||
|- | |||
! 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''' | |||
{| 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 === | |||
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 || 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 === | |||
{| class="wikitable" | |||
|- | |||
| '''Feature Prime''' || Lingli Deng, China Mobile, denglingli@chinamobile.com | |||
|- | |||
| '''Feature description''' || This feature will analyse existing policy information and data models and identify solutions that potentially could be applied to NFV-MANO; clarify the main alternatives for policy management (between NFV-MANO and OSS/BSS); determine the objectives and management alternatives for policy management applicable to NFV-MANO; identify policy expression information model applicable to NFV-MANO; identify policy expression data model applicable to NFV-MANO. | |||
|- | |||
| '''Target Release''' || '''Study:''' Release 4 (2021-04-15) Study to be completed | |||
'''Stage 2:''' Release 4 (2022-12-15) | |||
'''Stage 3:''' Release 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 | |||
|'''Study:''' [https://www.etsi.org/deliver/etsi_gr/NFV-IFA/001_099/042/ IFA042] | |||
'''Stage 2:''' [https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/048/ IFA048] | |||
'''Stage 3:''' | |||
|- | |||
| '''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] | |||
|- | |||
| | | '''Feature team''' || '''Stage 2:''' Chen Wang (China Mobile) | ||
| | '''Stage 3:''' Name (Company) | ||
| | |||
|- | |- | ||
| | | '''Last Updated''' ||2023-05-30 | ||
| | |||
| | |||
|} | |} | ||
''' | === 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''' | |||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|- | |- | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
||| | | 001 || First GR (IFA042) draft introducing the skeleton and the scope. | ||
'''Accepted contributions:''' | |||
NFVIFA(20)000553r2 | |||
| IFA042 || August-2020 || Done | |||
|- | |- | ||
|002 | |||
|Analysis of existing SDOs and Open Source Community policy models | |||
'''Accepted contributions:''' | |||
NFVIFA(20)000615r2 NFVIFA(20)000616r6 NFVIFA(20)000617r1 | |||
NFVIFA(20)000618r2 NFVIFA(20)000619r2 NFVIFA(20)000620r1 | |||
|IFA042 | |||
|November-2020 | |||
|Done | |||
|- | |- | ||
|| | |003 | ||
|NFV-MANO policy model potential requirements analysis | |||
Analysis of existing SDOs and Open Source Community policy models | |||
NFVIFA(21)000304 | |||
NFVIFA(21)000305r2 | |||
NFVIFA(21)000306r3 | |||
NFVIFA(21)000307r2 | |||
NFVIFA(21)000308r3 | |||
NFVIFA(21)000309r4 | |||
NFVIFA(21)000310r3 | |||
NFVIFA(21)000313r2_IFA042_5_4_1_Examples__Potential_Attributes_of_the_VNF_Auto- | |||
NFVIFA(21)000314r2_IFA042_5_4_2_Examples__Potential_Attributes_of_the_NS_Self-h | |||
NFVIFA(21)000315r3_IFA042_5_4_3_Examples__Potential_Attributes_of_the_Virtualiz | |||
NFVIFA(21)000316r2_IFA042_6_3_2_3_A_YANG_Data_Model_for_ECA_Policy_Management | |||
|IFA042 | |||
|January-2021 | |||
|Done | |||
|- | |- | ||
| | |004 | ||
|Analysis and Recommendations | |||
NFVIFA(21)000310r3_IFA042_5_3_1_General_Recommendations | |||
NFVIFA(21)000311r2_IFA042_5_3_2_Recommendations_for_Policy_Model_Information_El | |||
NFVIFA(21)000312r2_IFA042_5_3_3_Recommendations_for_Policy_Model_Attributes | |||
NFVIFA(21)000407r1 | |||
NFVIFA(21)000408 | |||
NFVIFA(21)000409r1 | |||
NFVIFA(21)000410r2 | |||
NFVIFA(21)000411r2 | |||
NFVIFA(21)000424r2 | |||
NFVIFA(21)000439r1 | |||
NFVIFA(21)000440r1 | |||
NFVIFA(21)000441r1 | |||
NFVIFA(21)000443r1 | |||
NFVIFA(21)000444r1 | |||
NFVIFA(21)000454r1 | |||
NFVIFA(21)000442r1 | |||
NFVIFA(21)000445r1 | |||
NFVIFA(21)000446r1 | |||
NFVIFA(21)000487r1 | |||
NFVIFA(21)000488r1 | |||
NFVIFA(21)000489r1 | |||
NFVIFA(21)000503r1 | |||
NFVIFA(21)000520r1 | |||
NFVIFA(21)000530r1 | |||
NFVIFA(21)000558r1 | |||
NFVIFA(21)000559r1 | |||
NFVIFA(21)000560r1 | |||
NFVIFA(21)000561r1 | |||
NFVIFA(21)000562 | |||
NFVIFA(21)000563r1 | |||
NFVIFA(21)000617r2 | |||
NFVIFA(21)000618r2 | |||
|IFA042 | |||
|Feburary-2021 | |||
|Done | |||
|- | |- | ||
| | |005 | ||
| | |Review | ||
NFVIFA(21)000674r1 | |||
NFVIFA(21)000675r1 | |||
NFVIFA(21)000699 | |||
NFVIFA(21)000701r2 | |||
NFVIFA(21)000700r1 | |||
NFVIFA(21)000727 | |||
NFVIFA(21)000728 | |||
NFVIFA(21)000729r1 | |||
NFVIFA(21)000730r1 | |||
|IFA042 | |||
|September-2021 | |||
|Done | |||
|- | |- | ||
| | |006 | ||
|Policy information model | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000254_FEAT26_IFA048_Clause_5_2_Policy_information_element.docx NFVIFA(22)000254] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000335r1_FEAT26_IFA048_Clause_5_4_Information_elements_related_to_Tas.docx NFVIFA(22)000335r1] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000333r3_FEAT26_IFA048_Clause_5_2_Policy_information_element.docx NFVIFA(22)000333r3] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000334r2_FEAT26_IFA048_Clause_5_3_Information_elements_related_to_Sta.docx NFVIFA(22)000334r2] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000382r1_FEAT26_IFA048_Update_to_Clause_5_1_Modeling_Overview.docx NFVIFA(22)000382r1] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000336r3_FEAT26_IFA048_Clause_5_5_Information_elements_related_to_Con.docx NFVIFA(22)000336r3] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000337r4_FEAT26_IFA048_Clause_5_6_Information_elements_related_to_Log.docx NFVIFA(22)000337r4] | |||
=== | - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000411_FEAT26_IFA048_update_clause_5_1.docx NFVIFA(22)000411] | ||
''' | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000410r1_FEAT26_IFA048_update_contextItemAccess.docx NFVIFA(22)000410r1] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000409r1_FEAT26_IFA048_combination_limitation_for_state_and_task.docx NFVIFA(22)000409r1] | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000408r1_FEAT26_IFA048__version_for_policy_IE.docx - NFVIFA(22)000408r1] | |||
|IFA048 | |||
| | |||
|Done | |||
|- | |||
|007 | |||
|General | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000385r1_FEAT26_IFA048_Remove_Duplicated_Clause_4_1.docx NFVIFA(22)000385r1] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000383r1_FEAT26_IFA048_Executive_Summary.docx NFVIFA(22)000383r1] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000384r2_FEAT26_IFA048_Scope.docx NFVIFA(22)000384r2] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000406r1_FEAT26_IFA048__Definition_of_terms__symbols_and_abbreviation.docx NFVIFA(22)000406r1] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000407r2_FEAT26_IFA048__Relation_with_IFA_040.docx NFVIFA(22)000407r2] | |||
Example of policy model | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000347r2_FEAT26_IFA048_Illustrative_ECA_policy_modelling_example.docx NFVIFA(22)000347r2] | |||
Review | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000743_FEAT26_IFA048_final_review_editorial_updates_part_A.docx NFVIFA(22)000743] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000744_FEAT26_IFA048_final_review_editorial_updates_part_B.docx NFVIFA(22)000744] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000745_FEAT26_IFA048_final_review_technical_updates_part_A.docx NFVIFA(22)000745] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000746_FEAT26_IFA048_final_review_technical_updates_part_B.docx NFVIFA(22)000746] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000740r1_FEAT26_IFA048_final_review_clean-up.docx NFVIFA(22)000740r1] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000776_FEAT26_IFA048_final_review_editorial_updates.docx NFVIFA(22)000776] | |||
|IFA048 | |||
| | |||
|Done | |||
|- | |||
|008 | |||
|Policy management alignment with IFA048 | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000024r1_IFA013ed441_Policy_management_alignment_with_IFA048.docx NFVIFA(23)000024r1] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000025r1__mirror_of_024__IFA007ed441_Policy_management_alignment_with.docx NFVIFA(23)000025r1] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000026r1__mirror_of_024__IFA008ed441_Policy_management_alignment_with.docx NFVIFA(23)000026r1] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000027r1__mirror_of_024__IFA005ed441_Policy_management_alignment_with.docx NFVIFA(23)000027r1] | |||
- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000028r1__mirror_of_024__IFA006ed441_Policy_management_alignment_with.docx NFVIFA(23)000028r1] | |||
|IFA005 | |||
IFA006 | |||
IFA007 | |||
IFA008 | |||
IFA013 | |||
| | |||
|Done | |||
|} | |||
=== Stage 3 Implementation Plan === | |||
Items to consider in the implementation plan | |||
* Detailed description what has to be done in which work item. | |||
* Timeplan of when the team plans to conclude a particular action in the implementation plan. | |||
'''SOL''' | |||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|- | |- | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ! ID !! Action !! Impacted WG(s) !! Target completion !! Status | ||
|- | |- | ||
| 001 | |001 | ||
|Study of solution | |||
| | |||
- NFVSOL(23)000084r1 | |||
|NWI | |||
| || | |||
|- | |- | ||
|002 | |||
|Policy management alignment with IFA048 | |||
- NFVSOL(23)000014 | |||
|SOL012 | |||
| | |||
|Done | |||
|- | |- | ||
| | |003 | ||
| | |Policy information model | ||
| | |||
| | |||
|Not started | |||
|- | |- | ||
|004 | |||
| | |Policy data model | ||
| | | | ||
| | |||
|Not started | |||
|} | |} | ||
Line 4,089: | Line 4,424: | ||
''List of security considerations implied by the feature.'' | ''List of security considerations implied by the feature.'' | ||
== | |||
== FEAT27: NFV for vRAN == | |||
=== Overview === | |||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| | | '''Feature Prime''' || Kostas Katsalis (DOCOMO EUL) | ||
| | |- | ||
| | | '''Feature description''' ||The scope of this feature covers the following areas: a) study the advances concerning the virtualization of the RAN and profile the NFV framework to determine how it can support virtualized RAN (vRAN) use cases, b) identify key technical challenges relevant to architectural, operational and management aspects, in case the NFV architectural framework is leveraged to support virtualization of the RAN, and c) provide recommendations for enhancements to the NFV architectural framework and its functionality, aiming to provide further support for vRAN use cases. | ||
| | |||
|- | |- | ||
| | | '''Target Release''' || '''Stage 2:''' TBD (Release 5 (2023-X-X)) | ||
| | '''Stage 3:''' TBD (Release 5 (2023-X-X)) | ||
|- | |||
| | | '''Impacted WIs''' || '''Stage 2:''' TBD (IFAxx, IFAyy, SOLzz) | ||
| | '''Stage 3:''' TBD (SOLzz) | ||
|- | |||
| | | '''MegaCRs''' || '''Stage 2:''' | ||
TBD: IFAxxx MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//blackhole.doc NFVIFA(21)000xxx] (CR Status) | |||
IFAyyy MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//blackhole.doc NFVIFA(21)000yyy] (CR Status) | |||
'''Stage 3:''' | |||
TBD: SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//blackhole.doc NFVSOL(21)000zzz] (CR Status) | |||
|- | |||
| '''Related/Dependent Features''' || FEAT17 on "Cloud-native VNF and container infrastructure management" | |||
FEAT19 on "NFV connectivity" | |||
FEAT21 on "5GNFV" | |||
|- | |- | ||
| | |'''New Specifcations''' | ||
| | |'''Informative:''' DGR/NFV-IFA046 | ||
| | '''Stage 2:''' TBD | ||
| | '''Stage 3:''' TBD | ||
| | |- | ||
| | | '''Status''' || '''Informative:''' ongoing (0%) | ||
| | '''Stage 2:''' TBD | ||
| | '''Stage 3:''' TBD | ||
|- | |||
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | |||
|- | |||
| '''Feature team''' || '''Informative:''' Kostas Katsalis (DOCOMO EUL) | |||
| | '''Stage 2:''' Name (Company) | ||
'''Stage 3:''' Name (Company) | |||
|- | |||
| '''Last Updated''' || 2023-02-06 | |||
|} | |||
=== Informative work === | |||
| | '''IFA''' | ||
{| class="wikitable sortable" | |||
|NFV-MANO | |- | ||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | |||
|- | |||
| 001 || Skeleton and scope<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000751r1_IFA046_Report_skeleton_on_NFV_support_for_virtualization_of_.zip NFVIFA(21)000751] IFA046 skeleton <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000806r1_FEAT27_IFA046_Scope.docx NFVIFA(21)000806] IFA037 Scope | |||
- NFVIFA(22)000749 scope update - NFVIFA(22)000865 review abbreviations | |||
| IFA || Dec-2022 || Completed | |||
|- | |||
| 002 || Overview and Introduction<br />- NFVIFA(21)0001032r2 introduction | |||
- NFVIFA(21)0001033r2 state of the art | |||
- NFVIFA(21)0001034r3 Clause adding vRAN characteristics | |||
- NFVIFA(21)0001035r2 problem statement | |||
* NFVIFA(19)000858r4 : feature proposal (accepted) | - NFVIFA(22)000752r1 addressing ENs_sec 4 | ||
* NFVIFA(19)000966r2: adding RD IE in IFA014, available | |||
* NFVIFA(19)0001018: new requirements to IFA010, FEAT Agreed (IFA#202) | - NFVIFA(22)000784 editorial cleanup | ||
* 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(22)000851 additional editorial cleanup | ||
* 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(22)000927r1 updating section1_section2_section3 | ||
* NFVIFA(20)000517r3: discussion paper for NSD model for supporting Routing resource: available | |||
- NFVIFA(22)000928r1 updating section 4 | |||
* IFA005: NFVIFA(20)000728r1 (Approved in NFVIFA#216) | | IFA ||Dec-2022 | ||
|- | | Completed | ||
|ENH02.02 | |- | ||
|NFV-MANO enhancement for NS feasibility check | | 003 || Identification and description of Key technical challenges | ||
|Release 4 | - NFVIFA(22)000141r1 introduction | ||
|Stage 2 complete | |||
|Junichi Kawasaki <ju-kawasaki@kddi.com>, Kenichi Ogaki <ke-oogaki@kddi.com>, Rajavarma Bhyrraju <rajavarma.bhyrraju@ericsson.com>, Cristina Badulescu <cristina.badulescu@ericsson.com>, Anatoly Andrianov <anatoly.andrianov@nokia.com>, Kleber Ulrich <Ulrich.Kleber@huawei.com> | - NFVIFA(22)000142r1 intro and challenges for architectural mappings | ||
|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(22)000143r1 solutions and gaps for architectural mappings | ||
- NFVIFA(22)000144r2 evaluation to key issue architectural mappings | |||
- NFVIFA(22)000251 O-RAN arch figure update | |||
- NFVIFA(22)000260r1 acceleration abstraction intro | |||
- NFVIFA(22)000261r3 packaging and descriptors introduction | |||
- NFVIFA(22)000306r1 challenges for acceleration abstraction | |||
- NFVIFA(22)000307r1 challenges for descriptors and packaging | |||
- NFVIFA(22)000318 Numbering challenges | |||
- NFVIFA(22)000319r2 introduction for ransport network management | |||
- NFVIFA(22)000325r3 solutions to key issue VNF descriptors and packaging | |||
- NFVIFA(22)000326r4 solutions for key issue acceleration abstraction | |||
- NFVIFA(22)000329 challenges for key issue transport network management | |||
- NFVIFA(22)000356 solutions to transport network management | |||
- NFVIFA(22)000364 updates to the structure of transport network management solutions | |||
- NFVIFA(22)000365r1background information about functional splits in Annex B | |||
- NFVIFA(22)000368 gap analysis for key issue transport network management | |||
- NFVIFA(22)000369r4 physical infrastructure management | |||
- NFVIFA(22)000416r1 gap analysis for key issue acceleration abstraction | |||
- NFVIFA(22)000417r1 gap analysis for key issue descriptors and packaging | |||
- NFVIFA(22)000420r3 additional solutions to key issue transport network management | |||
- NFVIFA(22)000436 evaluation to key issue transport network management | |||
- NFVIFA(22)000417r2 gap analysis for key issue descriptors and packaging | |||
- NFVIFA(22)000470 evaluation to key issue acceleration abstraction | |||
- NFVIFA(22)000490r2 gap analysis for CRDs in NFV | |||
- NFVIFA(22)000491r1 evaluation of PIM solutions | |||
- NFVIFA(22)000574 evaluation to key issue descriptors and packaging | |||
- NFVIFA(22)000678r1 MANO figures update based on NFV006 rel4 | |||
- NFVIFA(22)000679r3 additional clarification points for architectural mappings | |||
- NFVIFA(22)000680 CCDs in vRAN | |||
- NFVIFA(22)000683r3 solution for VNF Packaging - Different LCM-VNF Bundle | |||
- NFVIFA(22)000750 CRDs for CIS cluster | |||
- NFVIFA(22)000751 architectural mappings evaluation updates | |||
- NFVIFA(22)000753r1 addressing an EN in clause 5.1.2 | |||
- NFVIFA(22)000754 addressing ENs_sec 5.2.1 | |||
- NFVIFA(22)000764r2 Gap Analysis and Evaluation for SOL-C3-3 (VNF Bundle) | |||
- NFVIFA(22)000787 revision of AAL-part A | |||
- NFVIFA(22)000788 revision of AAL-part B | |||
- NFVIFA(22)000789 revision of AAL-part C | |||
- NFVIFA(22)000800 handling ENs for descriptors | |||
- NFVIFA(22)000806 transport network analysis ENs handling | |||
- NFVIFA(22)000809 Recommendations for solution SOL-C3-3 | |||
- NFVIFA(22)000823r2 solution for VNF LCM dependencies | |||
- NFVIFA(22)000929r1 updating section 5.1 | |||
- NFVIFA(22)000930r1 updating section 5.2.1 | |||
- NFVIFA(22)000931 updating section 5.2.2 | |||
- NFVIFA(22)000932 updating section 5.2.3 | |||
- NFVIFA(22)000933 updating section 5.2.4 | |||
- NFVIFA(22)000941 Notation for the VIM-CCM interactions in figures | |||
- NFVIFA(22)000960 updates on the virtual accelerator | |||
| IFA || Dec-2022 || Completed | |||
|- | |||
| 004 || Analysis of Use Cases (from other SDOs) | |||
- NFVIFA(21)0001069r1 use case analysis in Annex A | |||
- NFVIFA(22)000037r1 use case analysis in Annex A.3 (UC1-11) | |||
- NFVIFA(22)000038r1 use case analysis in Annex A.3(UC12-19) | |||
- NFVIFA(22)000140 analysis in Annex about Near RT RIC | |||
- NFVIFA(22)000935 updating Annexes | |||
| IFA || Dec-2022 || Completed | |||
|- | |||
| 005 || Recommendations | |||
- NFVIFA(22)000549 recommendations overview | |||
- NFVIFA(22)000581r1 recommendations for solutions | |||
- NFVIFA(22)000681r2 recommendations framework | |||
- NFVIFA(22)000682r1 recommendations functional aspects | |||
- NFVIFA(22)000684r2 recommendations descriptors | |||
- NFVIFA(22)000685r1 recommendations interfaces | |||
- NFVIFA(22)000686r3 recommendations collaboration | |||
- NFVIFA(22)000767 recommendation for CCM functionality | |||
- NFVIFA(22)000934 updating section 6 | |||
| IFA || Dec-2022 || Completed | |||
|- | |||
| 006 || Conclusion | |||
NFVIFA(22)000695r1 conclusions<br /> | |||
| IFA || Dec-2022 || Completed | |||
|} | |||
=== Stage 2 Implementation Plan === | |||
Items to consider in the implementation plan | |||
* Detailed description what has to be done in which work item. | |||
* Timeplan of when the team plans to conclude a particular action in the implementation plan. | |||
'''IFA''' | |||
{| class="wikitable sortable" | |||
|- | |||
! 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''' | |||
{| class="wikitable sortable" | |||
|- | |||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | |||
|- | |||
| 001 || TBD || TBD || TBD || TBD | |||
|} | |||
=== Issues === | |||
''List of issues raised based on the feature implementation.'' | |||
=== Security Considerations === | |||
''List of security considerations implied by the feature.'' | |||
== FEAT28: Fault management models == | |||
=== Overview === | |||
{| class="wikitable" | |||
|- | |||
| '''Feature Prime''' || WANG Chen (China Mobile) & TRIAY Joan (DOCOMO) | |||
|- | |||
| '''Feature description''' ||The proposed feature aims to extend the defined data model of alarms and values of attributes (e.g., fault type) to enhance the processing of failure information. In addition, the proposal will analyse, determine and enrich the fault management interfaces to provide and acquire information to/from fault management closed loops in between different NFV-MANO, platform and OSS layers. | |||
Thus, the objectives of the feature comprise: | |||
- Define the necessary vendor agnostic information and data models for alarms and event notifications. | |||
- Expose and relate the type, cause, and additional information of the faults with appropriate levels of severity of the violation, like critical, major, minor, warning as defined in the current Alarm information elements. | |||
- Enable automated fault detection and performance degradation analysis over complex and correlated metrics. | |||
NOTE: Alarms related to security violations are out of scope of this activity. | |||
|- | |||
| '''Target Release''' || '''Stage 2:''' TBD (Release 5 (2023-X-X)) | |||
'''Stage 3:''' TBD (Release 5 (2023-X-X)) | |||
|- | |||
| '''Impacted WIs''' || '''Stage 2:''' EVE019, IFA005/006/007/008/013 | |||
'''Stage 3:''' TBD (SOLzz) | |||
|- | |||
| '''MegaCRs''' || '''Stage 2:''' | |||
TBD: IFAxxx MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//blackhole.doc NFVIFA(21)000xxx] (CR Status) | |||
IFAyyy MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//blackhole.doc NFVIFA(21)000yyy] (CR Status) | |||
'''Stage 3:''' | |||
TBD: SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//blackhole.doc NFVSOL(21)000zzz] (CR Status) | |||
|- | |||
| '''Related/Dependent Features''' || FEAT24 on "Generic VNF OAM" | |||
|- | |||
|'''New Specifcations''' | |||
|'''Stage 2:''' DGS/NFV-IFA045 | |||
'''Stage 3:''' TBD | |||
|- | |||
| '''Status''' || '''Stage 2:''' ongoing (80%) | |||
'''Stage 3:''' TBD | |||
|- | |||
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | |||
|- | |||
| '''Feature team''' || '''Normative:''' WANG Chen (China Mobile) & Joan TRIAY (DOCOMO) | |||
'''Stage 2:''' Name (Company) | |||
'''Stage 3:''' Name (Company) | |||
|- | |||
| '''Last Updated''' || 2023-06-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. | |||
'''IFA''' | |||
{| class="wikitable sortable" | |||
|- | |||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | |||
|- | |||
| 001 || Skeleton and scope for the IFA045.<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000810_Proposed_ETSI_GS_skeleton_IFA045_FM_Models.zip NFVIFA(21)000810] Proposed ETSI GS skeleton IFA045 FM Models: approved <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000463_FEAT28_IFA045_Adding_scope.docx NFVIFA(23)000463] FEAT28 IFA045 Adding scope: approved|| IFA045 || Sept-2021 || style="background: green;" |Completed | |||
|- | |||
| 002 || Overview and introduction of IFA045 content (clause 4).<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000914_FEAT21_IFA045_Clause_4_Adding_introduction.docx NFVIFA(21)000914] FEAT28 IFA045 Clause 4 Adding introduction: approved|| IFA045|| Oct-2021 || style="background: green;" |Completed | |||
|- | |||
| 003 || Define the “alarm definition template” (clause 6). See note 1.<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)0001067r2_FEAT28_IFA045_clause_6_Alarm_definition_template.docx NFVIFA(21)0001067r2] FEAT28 IFA045 clause 6 Alarm definition template: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000506_FEAT28_IFA045_Add_Alarm_Definition_Template.docx NFVIFA(22)000506] FEAT28 IFA045 Add Alarm Definition Template: available || IFA045|| Nov-2021 || style="background: green;" |Completed | |||
|- | |||
| 004 || Development of use cases related to FM alarms (annex A.1).<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)000915_FEAT28_IFA045_Annex_A_1_2_Use_cases_VR_and_NFVI_alarms.zip NFVIFA(21)000915] FEAT28 IFA045 Annex A.1.2 Use cases VR and NFVI alarms: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021/NFVIFA(21)0001068r2_FEAT28_IFA045_A1_2_m_Use_case_about_packet_loss_alarm.docx NFVIFA(21)0001068r2] FEAT28 IFA045 A1.2.m Use case about packet loss alarm: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000045r1_FEAT28_IFA045_A1_2_m_Use_case_about_unavailable_storage_serv.docx NFVIFA(22)000045r1] FEAT28 IFA045 A1.2.m Use case about unavailable storage service alarm: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022//NFVIFA(22)000151_IFA045_A1_2_m_Use_case_about_network_link_anomaly_alarm.docx NFVIFA(22)000151] IFA045 A1.2.m Use case about network link anomaly alarm: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000152_FEAT28_IFA045_Annex_A_1_Use_cases_about_VNF_and_NS_alarms.zip NFVIFA(23)000152] FEAT28 IFA045 Annex A.1 Use cases about VNF and NS alarms: approved <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000443r1_FEAT28_IFA045_Clause_A_1_2_3_adding_annex_about_container_an.zip NFVIFA(23)000443r1] FEAT28 IFA045 Clause A.1.2.3 adding annex about container and cluster alarms: approved|| IFA045|| May-2023 || style="background: green;" |Completed | |||
|- | |||
| 005 || Development of use cases related to use of Alarms information (annex A.2).<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)0001043r1_IFA045_A_2_1_1_Use_case_about_generic_procedure_of_using_ala.docx NFVIFA(21)0001043r1] IFA045 A.2.1.1 Use case about generic procedure of using alarm information produced by the VIM: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)0001044r1_IFA045_A_2_1_2_Use_case_about_generic_procedure_of_using_ala.docx NFVIFA(21)0001044r1] IFA045 A.2.1.2 Use case about generic procedure of using alarm information produced by the VNFM: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)0001045r1_IF045_A_2_1_3_Use_case_about_generic_procedure_of_using_alar.docx NFVIFA(21)0001045r1] IFA045 A.2.1.3 Use case about generic procedure of using alarm information produced by the NFVO: approved || IFA045|| Mar-2021 || style="background: green;" |Completed | |||
|- | |||
| 006 || Definition of object types that can be fault monitored (clause 5). See note 1 and note 2.<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000911_FEAT28_IFA045_virtualised_resource_object_types.docx NFVIFA(22)000911] FEAT28 IFA045 virtualised resource object types: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000140r1_FEAT28_IFA045_VNF_NS_object_types.docx NFVIFA(23)000140r1] FEAT28 IFA045 VNF/NS object types: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000153_FEAT28_FM_and_alarms_for_containerized_work.pptx NFVIFA(23)000153] FEAT28 FM and alarms for containerized workloads: noted<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000271_FEAT28_IFA045_MSCS_object_types.docx NFVIFA(23)000271] FEAT28 IFA045 MSCS object types: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000275_FEAT28_IFA045_Discussion_about_CIS_cluster_management_object.pptx NFVIFA(23)000275] FEAT28 IFA045 Discussion about CIS cluster management object types: noted<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000391_FEAT28_IFA045_CIS_cluster_object_types.docx NFVIFA(23)000391] FEAT28 IFA045 CIS cluster object types: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000444_FEAT28_IFA045_additional_CIS_cluster_object_types.docx NFVIFA(23)000444] FEAT28 IFA045 additional CIS cluster object types: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000445_FEAT28_IFA045_containerized_workload_object_types.docx NFVIFA(23)000445] FEAT28 IFA045 containerized workload object types: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000398r1_FEAT28_IFA045_Clause_5_1_Introduction.docx NFVIFA(23)000398r1] FEAT28 IFA045 Clause 5.1 Introduction: approved || IFA045 || Jun-2023 || style="background: green;" |Completed | |||
|- | |||
| 007 || Alarm definitions (clause 7). See note 1 and note 2.<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000912r2_FEAT28_IFA045_VIM_alarms_baseline__common_definitions.docx NFVIFA(22)000912r2] FEAT28 IFA045 VIM alarms baseline: common definitions: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000913r1_FEAT28_IFA045_VIM_alarms_baseline__compute_and_CPU.docx NFVIFA(22)000913r1] FEAT28 IFA045 VIM alarms baseline: compute and CPU: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000914_FEAT28_IFA045_VIM_alarms_baseline__memory.docx NFVIFA(22)000914] FEAT28 IFA045 VIM alarms baseline: memory: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000915_FEAT28_IFA045_VIM_alarms_baseline__storage.docx NFVIFA(22)000915] FEAT28 IFA045 VIM alarms baseline: storage: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000916r1_FEAT28_IFA045_VIM_alarms_baseline__network_interface.docx NFVIFA(22)000916r1] FEAT28 IFA045 VIM alarms baseline: network interface: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000917_FEAT28_IFA045_VIM_alarms_baseline__network.docx NFVIFA(23)000917] FEAT28 IFA045 VIM alarms baseline: network: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000141r1_FEAT28_IFA045_VNFM_alarms_baseline__common_definitions.docx NFVIFA(23)000141r1] FEAT28 IFA045 VNFM alarms baseline: common definitions: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000143_FEAT28_IFA045_NFVO_alarms_baseline__common_definitions.docx NFVIFA(23)000143] FEAT28 IFA045 NFVO alarms baseline: common definitions: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000144_FEAT28_IFA045_VNFM_alarms_baseline__VNF.docx NFVIFA(23)000144] FEAT28 IFA045 VNFM alarms baseline: VNF: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000145_FEAT28_IFA045_VNFM_alarms_baseline__VNFC.docx NFVIFA(23)000145] FEAT28 IFA045 VNFM alarms baseline: VNFC: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000146_FEAT28_IFA045_VNFM_alarms_baseline__VNF_virtual_link.docx NFVIFA(23)000146] FEAT28 IFA045 VNFM alarms baseline: VNF virtual link: approved<br /> - [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000147r1_FEAT28_IFA045_VNFM_alarms_baseline__VNF_internal_CP.docx NFVIFA(23)000147r1] FEAT28 IFA045 VNFM alarms baseline: VNF internal CP: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000148r1_FEAT28_IFA045_VNFM_alarms_baseline__VNF_external_CP.docx NFVIFA(23)000148r1] FEAT28 IFA045 VNFM alarms baseline: VNF external CP: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000149_FEAT28_IFA045_NFVO_alarms_baseline__NS.docx NFVIFA(23)000149] FEAT28 IFA045 NFVO alarms baseline: NS: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000150r1_FEAT28_IFA045_NFVO_alarms_baseline__NS_virtual_link.docx NFVIFA(23)000150r1] FEAT28 IFA045 NFVO alarms baseline: NS virtual link: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000151_FEAT28_IFA045_NFVO_alarms_baseline__NS_service_access_point.docx NFVIFA(23)000151] FEAT28 IFA045 NFVO alarms baseline: NS service access point: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000272_FEAT28_IFA045_WIM_alarms_baseline__common_definitions.docx NFVIFA(23)000272] FEAT28 IFA045 WIM alarms baseline: common definitions: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000273_FEAT28_IFA045_WIM_alarms_baseline__MSCS.docx NFVIFA(23)000273] FEAT28 IFA045 WIM alarms baseline: MSCS: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000274_FEAT28_IFA045_WIM_alarms_baseline__MSNC.docx NFVIFA(23)000274] FEAT28 IFA045 WIM alarms baseline: MSNC: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000318r2_FEAT28_IFA045_VNFM_alarms_clarification.docx NFVIFA(23)000318r2] FEAT28 IFA045 VNFM alarms: clarification of virtual compute and MCIO based VNFC caused alarms: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000413r1_FEAT28_IFA045_Clause_7_1_Introduction.docx NFVIFA(23)000413r1] FEAT28 IFA045 Clause 7.1 Introduction: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000392r2_FEAT28_IFA045_CIS_cluster_alarms_baseline__common_definition.docx NFVIFA(23)000392r2] FEAT28 IFA045 CIS cluster alarms baseline: common definitions: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000393r1_FEAT28_IFA045_CCM_alarms_baseline__CIS_cluster.docx NFVIFA(23)000393r1] FEAT28 IFA045 CCM alarms baseline: CIS cluster: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000394r2_FEAT28_IFA045_CCM_alarms_baseline__CIS_cluster_node.docx NFVIFA(23)000394r2] FEAT28 IFA045 CCM alarms baseline: CIS cluster node: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000395r1_FEAT28_IFA045_CCM_alarms_baseline__CIS_cluster_storage.docx NFVIFA(23)000395r1] FEAT28 IFA045 CCM alarms baseline: CIS cluster storage: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000396r1_FEAT28_IFA045_CCM_alarms_baseline__CIS_cluster_network.docx NFVIFA(23)000396r1] FEAT28 IFA045 CCM alarms baseline: CIS cluster network: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000397r1_FEAT28_IFA045_CCM_alarms_baseline__MCCO.docx NFVIFA(23)000397r1] FEAT28 IFA045 CCM alarms baseline: MCCO: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000446_FEAT28_IFA045_CISM_alarms_baseline__common_definitions.docx NFVIFA(23)000446] FEAT28 IFA045 CISM alarms baseline: common definitions: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000447_FEAT28_IFA045_CISM_alarms_baseline__CISI.docx NFVIFA(23)000447] FEAT28 IFA045 CISM alarms baseline: CISI: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000448_FEAT28_IFA045_CISM_alarms_baseline__MCIO.docx NFVIFA(23)000448] FEAT28 IFA045 CISM alarms baseline: MCIO: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000400r1_FEAT28_IFA045_Updating_event_types_of_alarms_produced_by_VIM.docx NFVIFA(23)000400r1] FEAT28 IFA045 Updating event types of alarms produced by VIM: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000415_FEAT28_IFA045_Updating_event_types_of_alarms_produced_by_VNF.docx NFVIFA(23)000415] FEAT28 IFA045 Updating event types of alarms produced by VNFM: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000416_FEAT28_IFA045_Updating_event_types_of_alarms_produced_by_NFV.docx NFVIFA(23)000416] FEAT28 IFA045 Updating event types of alarms produced by NFVO: approved<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000417_FEAT28_IFA045_Updating_event_types_of_alarms_produced_by_WIM.docx NFVIFA(23)000417] FEAT28 IFA045 Updating event types of alarms produced by WIM: approved | |||
| IFA045 || Jun-2023 || style="background: green;" |Completed | |||
|- | |||
| 008 || Final review of IFA045 and addressing open editor's notes.<br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000401_FEAT28_IFA045_addressing_editorial_and_guideline_editor_s_no.docx NFVIFA(23)000401] FEAT28 IFA045 addressing editorial and guideline editor's note: approved <br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000399_FEAT28_IFA045_Clause_A_1_1_and_A_2_1_overview.docx NFVIFA(23)000399] FEAT28 IFA045 Clause A.1.1 and A.2.1 overview: approved|| IFA045 || Jun-Jul 2023 || style="background: orange;" |Ongoing | |||
|- | |||
| 009 || Alignment CRs to other NFV-IFA specifications.<br />Contributions:<br /> || IFA || Dec-2023 || Not started | |||
|- | |||
| colspan="5" |NOTE 1: It can run in parallel with the development of use cases, in particular if there are diverse object types and some of them are clarified with use cases at early stages. | |||
NOTE 2: Additional sub-task details could be defined to sequence or parallelize the work on different object types and associated alarm definitions, e.g., split by “NFV managed objects such as VR, MSCS, VNF, NS” or by “resource related domain, such as compute, storage, network”. | |||
|} | |||
=== Stage 3 Implementation Plan === | |||
Items to consider in the implementation plan | |||
* Detailed description what has to be done in which work item. | |||
* Timeplan of when the team plans to conclude a particular action in the implementation plan. | |||
'''SOL''' | |||
{| class="wikitable sortable" | |||
|- | |||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | |||
|- | |||
| 001 || TBD || TBD || TBD || TBD | |||
|} | |||
=== Issues === | |||
''List of issues raised based on the feature implementation.'' | |||
=== Security Considerations === | |||
''List of security considerations implied by the feature.'' | |||
== FEAT29: Green NFV == | |||
=== Overview === | |||
{| class="wikitable" | |||
|- | |||
| '''Feature Prime''' || Joan Triay (DOCOMO) | |||
|- | |||
| '''Feature description''' ||The scope of the feature covers the following areas:<br /> - Analyse aspects of NFV (VNF design, NFV-MANO and VNF operation, deployment configuration of NFV-MANO, NFVI, etc.) that have impact on energy consumption and those that can enable smart energy NFV and power saving features.<br />- Identify design guidelines needed for optimizing energy consumption.<br />- Specify enhancements to specifications on interfaces and information model, augment exposed KPIs and metrics to enable resources orchestration and VNF/NS LCM to operate following power saving policies. | |||
|- | |||
| '''Target Release''' || '''Stage 2:''' TBD (Release 5 (2021-X-X))<br />'''Stage 3:''' TBD (Release 5 (2021-X-X)) | |||
|- | |||
| '''Impacted WIs''' || '''Stage 2:''' TBD (IFAxx, IFAyy, SOLzz)<br />'''Stage 3:''' TBD (SOLzz) | |||
|- | |||
| '''MegaCRs''' || '''Stage 2:''' | |||
TBD: IFAxxx MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//blackhole.doc NFVIFA(18)000xxx] (CR Status) | |||
IFAyyy MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//blackhole.doc NFVIFA(18)000yyy] (CR Status) | |||
'''Stage 3:''' | |||
TBD: SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//blackhole.doc NFVSOL(19)000zzz] (CR Status) | |||
|- | |||
| '''Related/Dependent Features''' || FEAT20 on "Autonomous management" (Release 4)<br />FEAT07 on "Policy management framework" (Release 4)<br />FEAT26 on "Policy models" (Release 4) | |||
|- | |||
|'''New Specifications''' | |||
|'''Informative:''' DGR/NFV-EVE021<br />'''Stage 2:''' TBD<br />'''Stage 3:''' TBD | |||
|- | |||
| '''Status''' || '''Informative:''' ongoing (65%)<br />'''Stage 2:''' TBD<br />'''Stage 3:''' TBD | |||
|- | |||
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | |||
|- | |||
| '''Feature team''' || '''Informative:''' Joan Triay (DOCOMO)<br />'''Stage 2:''' Name (Company)<br />'''Stage 3:''' Name (Company) | |||
|- | |||
| '''Last Updated''' || 2023-06-08 | |||
|} | |||
=== Informative work === | |||
'''EVE''' | |||
{| class="wikitable sortable" | |||
|- | |||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | |||
|- | |||
| 001 || Skeleton and scope.<br /><br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2021//NFVEVE(21)000080_FEAT29_EVE021_Skeleton.zip NFVEVE(21)000080] FEAT29 EVE021 Skeleton: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2021//NFVEVE(21)000081_FEAT29_EVE021_Scope.docx NFVEVE(21)000081] FEAT29 EVE021 Scope: Approved || EVE (EVE021) || Oct-2021 || Completed | |||
|- | |||
| 002 || Introduction and overview<br />- Introduction to energy efficiency and global initiatives<br />- NFV and energy efficiency<br />- Other organizations work<br /><br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2021//NFVEVE(21)000107r1_FEAT29_EVE021_Clause_4_1_Introduction_to_energy_efficiency.docx NFVEVE(21)000107r1] FEAT29 EVE021 Clause 4.1 Introduction to energy efficiency: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2021//NFVEVE(21)000133r1_FEAT29_EVE021_Clause_4_2_NFV_and_energy_efficiency.docx NFVEVE(21)000133r1] FEAT29 EVE021 Clause 4.2 NFV and energy efficiency: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2021//NFVEVE(21)000134r1_FEAT29_EVE021_Clause_4_3_1_Energy_efficiency_in_3GPP.docx NFVEVE(21)000134r1] FEAT29 EVE021 Clause 4.3.1 Energy efficiency in 3GPP: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000017r1_Energy_Efficiency_-_clause_4_3.docx NFVEVE(22)000017r1] EVE021 Energy Efficiency - clause 4.3: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000027r1_FEAT29_-_EVE021_-_Proposed_update_to_clause_4_3.docx NFVEVE(22)000027r1] FEAT29 - EVE021 - Proposed update to clause 4.3: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000043_FEAT29_EVE021_Clause_2_2_correct_reference_of_DMTF_Redfish.docx NFVEVE(22)000043] FEAT29 EVE021 Clause 2.2 correct reference of DMTF Redfish: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000051_FEAT29_EVE021_Clause_2_2_additional_reference_for_DMTF_Redfi.zip NFVEVE(22)000051] FEAT29 EVE021 Clause 2.2 additional references for DMTF Redfish: Approved || EVE (EVE021) || Mar-2022 || Completed | |||
|- | |||
| 003 || Development of use cases. See note 1 and note 2.<br />- Network-wide and NFV-MANO aspects.<br />- Energy related measurements and runtime aspects.<br />- Energy-driven design<br />- Enabling smart energy usage and decision making.<br /><br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000037r1_FEAT29_EVE021_Clause_5_UC_resources_sleep_resume.docx NFVEVE(22)000037r1] FEAT29 EVE021 Clause 5 UC resources sleep resume: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000052r2_FEAT29_EVE021_Clause_5_UC_Power_saving_management_function_u.docx NFVEVE(22)000052r2] FEAT29 EVE021 Clause 5 UC Power saving management function under limited power supply: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000075r2_FEAT29_EVE021_Clause_5_UC_acquiring_infrastructure_power_con.docx NFVEVE(22)000075r2] FEAT29 EVE021 Clause 5 UC acquiring infrastructure power consumption data: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000076r2_FEAT29_EVE021_Clause_5_UC_acquiring_NFV_power_consumption_da.docx NFVEVE(22)000076r2] FEAT29 EVE021 Clause 5 UC acquiring NFV power consumption data: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000077r1_FEAT29_EVE021_Clause_5_UC_processing_power_state_driven_depl.docx NFVEVE(22)000077r1] FEAT29 EVE021 Clause 5 UC processing power state driven deployment: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000116r1_FEAT29_EVE021_Clause_5_UC_power_consumption_and_resources_pl.docx NFVEVE(22)000116r1] FEAT29 EVE021 Clause 5 UC power consumption and resources placement optimization: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000115r2_FEAT29_EVE021_Clause_5_UC_Restoration_management_from_resour.docx NFVEVE(22)000115r2] FEAT29 EVE021 Clause 5 UC Restoration management from resource reservation in power saving situations: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000162_FEAT29_EVE021_Clause_5_UC_on_dynamic_power_state_management.docx NFVEVE(22)000162] FEAT29 EVE021 Clause 5 UC on dynamic power state management: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000175_FEAT29_EVE021_Clause_5_UC_on_dynamic_power_state_management_.docx NFVEVE(22)000175] FEAT29 EVE021 Clause 5 UC on dynamic power state management - actors, conditions and flow description: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000101_FEAT29_EVE021_Clause_5_1_Overview_of_use_cases.docx NFVEVE(23)000101] FEAT29 EVE021 Clause 5.1 Overview of use cases: Agreed | |||
| EVE (EVE021) || Oct-2022 || Completed | |||
|- | |||
| 004 || Documentation of key issues. See note 1 and note 2.<br />- Energy consumption<br />- Energy efficiency management<br />- Energy efficient design<br />- Energy related metrics and KPI<br /><br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000096r1_FEAT29_EVE021_Clause_6_Key_issues.zip NFVEVE(22)000096r1] FEAT29 EVE021 Clause 6 Key issues: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000161r1_FEAT29_EVE021_Clause_6_Update_key_issues.docx NFVEVE(22)000161r1] FEAT29 EVE021 Clause 6 Update key issues: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000204_FEAT29_EVE021_Clause_6_Re-organize_questions_between_key_iss.docx NFVEVE(22)000204] FEAT29 EVE021 Clause 6 Re-organize questions between key issues: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000209_FEAT29_EVE021_Clause_6_Key_issues_related_to_CPU_power_state.docx NFVEVE(22)000209] FEAT29 EVE021 Clause 6 Key issues related to CPU power state management: Approved | |||
| EVE (EVE021) || Sep-2022 || Completed | |||
|- | |||
| 005 || Framework and potential solutions.<br /><br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000205_FEAT29_EVE021_Clause_7_1_Solutions_introduction.docx NFVEVE(22)000205] FEAT29 EVE021 Clause 7.1 Solutions introduction: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000199r2_FEAT29_EVE021_Clause_7_Solutions_key_issues__1_1_and__1_2.zip NFVEVE(22)000199r2] FEAT29 EVE021 Clause 7 Solutions key issues #1.1 and #1.2: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000206_FEAT29_EVE021_Clause_7_Solutions_key_issues__1_2.zip NFVEVE(22)000206] FEAT29 EVE021 Clause 7 Solutions key issues #1.2: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000219_FEAT29_EVE021_Clause_7_Solutions_key_issues__2_2_resources.zip NFVEVE(22)000219] FEAT29 EVE021 Clause 7 Solutions key issues #2.2 resources: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000220r1_FEAT29_EVE021_Clause_7_Solutions_key_issues__2_2_state_and_c.docx NFVEVE(22)000220r1] FEAT29 EVE021 Clause 7 Solutions key issues #2.2 state and config: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000221r1_FEAT29_EVE021_Clause_7_Solutions_key_issues__3_1_VNF_power_p.zip NFVEVE(22)000221r1] FEAT29 EVE021 Clause 7 Solutions key issues #3.1 VNF power profiles: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2022//NFVEVE(22)000222_FEAT29_EVE021_Clause_7_Solutions_key_issues__3_1_VNF_power_m.zip NFVEVE(22)000222] FEAT29 EVE021 Clause 7 Solutions key issues #3.1 VNF power management: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000041_FEAT29_EVE021_Clause_7_Solutions_key_issues__3_3_Power_state.docx NFVEVE(23)000041] FEAT29 EVE021 Clause 7 Solutions key issues #3.3 Power state based zones in NFVI: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000042_FEAT29_EVE021_Clause_7_Solutions_key_issue__2_1_Power_state_.docx NFVEVE(23)000042] FEAT29 EVE021 Clause 7 Solutions key issue #2.1 Power state aware allocation of compute resources: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000043r1_FEAT29_EVE021_Clause_7_Solutions_key_issues__2_1_energy_poli.docx NFVEVE(23)000043r1] FEAT29 EVE021 Clause 7 Solutions key issues #2.1 energy policies: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000044r1_FEAT29_EVE021_Clause_7_Solutions_key_issue__3_2_NFV-MANO_pow.docx NFVEVE(23)000044r1] FEAT29 EVE021 Clause 7 Solutions key issue #3.2 NFV-MANO power consumption: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000045_FEAT29_EVE021_Clauses_7_Updating_key_issues_by_existing_solu.docx NFVEVE(23)000045] FEAT29 EVE021 Clause 7 Updating key issues by existing solutions: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000046r1_FEAT29_EVE021_Clause_7_Solutions_key_issue__2_1_NFV-MANO_cap.docx NFVEVE(23)000046r1] FEAT29 EVE021 Clause 7 Solutions key issue #2.1 NFV-MANO capabilities: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000047_FEAT29_EVE021_Clause_7_1_Update_summary_of_solutions_and_rel.docx NFVEVE(23)000047] FEAT29 EVE021 Clause 7.1 Update summary of solutions and related key issues: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000051_FEAT29_EVE021_Clause_7_1_Update_summary_of_solutions_and_rel.docx NFVEVE(23)000051] FEAT29 EVE021 Clause 7.1 Update summary of solutions and related key issues (2nd round): Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023/NFVEVE(23)000065_FEAT29_EVE021_Clause_7_1_Further_update_summary_of_solutions.docx NFVEVE(23)000065] FEAT29 EVE021 Clause 7.1 Further update summary of solutions and related key issues (3nd round): Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023/NFVEVE(23)000066_FEAT29_EVE021_Clause_7_Solutions_key_issue__4_2_VIM_for_acqu.zip NFVEVE(23)000066] FEAT29 EVE021 Clause 7 Solutions key issue #4.2 VIM for acquiring VR power consumption: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023/NFVEVE(23)000067_FEAT29_EVE021_Clause_7_Solutions_key_issue__4_2_CISM_for_acq.zip NFVEVE(23)000067] FEAT29 EVE021 Clause 7 Solutions key issue #4.2 CISM for acquiring containerized power consumption: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023/NFVEVE(23)000068_FEAT29_EVE021_Clause_7_2_6_Update_solution_to_address_key_is.zip NFVEVE(23)000068] FEAT29 EVE021 Clause 7.2.6 Update solution to address key issue #4.3 of acquiring VNF power consumption: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023/NFVEVE(23)000069_FEAT29_EVE021_Clause_7_Solutions_key_issue__4_4_NFVO_for_acq.zip NFVEVE(23)000069] FEAT29 EVE021 Clause 7 Solutions key issue #4.4 NFVO for acquiring NS power consumption: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023/NFVEVE(23)000070_FEAT29_EVE021_Clause_7_Solutions_key_issue__4_2___4_3_and__4.zip NFVEVE(23)000070] FEAT29 EVE021 Clause 7 Solutions key issue #4.2, #4.3 and #4.4 NFV power manager for acquiring power consumption: Approved <br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000074_FEAT29_EVE021_Clause_7_1_Further_update_summary_of_solutions.docx NFVEVE(23)000074] FEAT29 EVE021 Clause 7.1 Further update summary of solutions (4th round): Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000078_FEAT29_EVE021_Clause_7_Solutions_key_issue__4_1_energy_effic.docx NFVEVE(23)000078] FEAT29 EVE021 Clause 7 Solutions key issue #4.1 energy efficiency of NFVI physical resources: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000081_FEAT29_EVE021_Clause_7_Solutions_key_issue__4_2_energy_effic.docx NFVEVE(21)000081] FEAT29 EVE021 Clause 7 Solutions key issue #4.2 energy efficiency and metrics of virtualised resources and containerized workloads: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000082_FEAT29_EVE021_Clause_7_Solutions_key_issue__4_3_energy_effic.docx NFVEVE(23)000082] FEAT29 EVE021 Clause 7 Solutions key issue #4.3 energy efficiency and metrics of VNF: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000083_FEAT29_EVE021_Clause_7_Solutions_key_issue__4_4_energy_effic.docx NFVEVE(23)000083] FEAT29 EVE021 Clause 7 Solutions key issue #4.4 energy efficiency and metrics of NS: Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000090_FEAT29_EVE021_Clause_7_1_Further_update_summary_of_solutions.docx NFVEVE(23)000090] FEAT29 EVE021 Clause 7.1 Further update summary of solutions (5th round): Approved<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000098r1_FEAT29_EVE021_Clause_7_Solutions_key_issue__4_1_PIM_for_acqu.zip NFVEVE(23)000098r1] FEAT29 EVE021 Clause 7 Solutions key issue #4.1 PIM for acquiring PR power consumption: Agreed<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000103_FEAT29_EVE021_Clause_7_3_Evaluation_of_solutions.docx NFVEVE(23)000103] FEAT29 EVE021 Clause 7.3 Evaluation of solutions: Available || EVE (EVE021) || May-2023 || Ongoing | |||
|- | |||
| 006 || Documentation of recommendations.<br /><br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000104_FEAT29_EVE021_Clause_8_Recommendations.docx NFVEVE(23)000104] FEAT29 EVE021 Clause 8 Recommendations: Available || EVE (EVE021) || Jun-2023 || Ongoing | |||
|- | |||
| 007 || Documentation of the conclusion.<br /><br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000105_FEAT29_EVE021_Clause_9_Conclusions.docx NFVEVE(23)000105] FEAT29 EVE021 Clause 9 Conclusions: Agreed || EVE (EVE021) || Jun-2023 || Completed | |||
|- | |||
| 008 || Final review of EVE021. See note 3.<br /><br />Contributions:<br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000052_FEAT29_EVE021_Clause_2_2_and_7_2_9_2_Fix_missing_reference.docx NFVEVE(23)000052] FEAT29 EVE021 Clause 2.2 and 7.2.9.2 Fix missing reference: Approved <br />- [https://docbox.etsi.org/ISG/NFV/EVE/05-CONTRIBUTIONS/2023//NFVEVE(23)000102r1_FEAT29_EVE021_Clean-up_of_various_editor_s_notes_and_empty_t.docx NFVEVE(23)000102r1] FEAT29 EVE021 Clean-up of various editor's notes and empty template clauses: Agreed || EVE (EVE021) || Jul-2023 || Ongoing | |||
|- | |||
| colspan="5" | NOTE 1: Minimum set of items to consider are listed.<br />NOTE 2: These tasks can run in parallel, since as we develop use cases, we can start documenting findings about related key issues.<br />NOTE 3: It may include addressing “minor” editor’s notes that do not require substantial new content. | |||
|} | |||
=== Stage 2 Implementation Plan === | |||
Items to consider in the implementation plan | |||
* Detailed description what has to be done in which work item. | |||
* Timeplan of when the team plans to conclude a particular action in the implementation plan. | |||
'''IFA''' | |||
{| class="wikitable sortable" | |||
|- | |||
! 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''' | |||
{| class="wikitable sortable" | |||
|- | |||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | |||
|- | |||
| 001 || TBD || TBD || TBD || TBD | |||
|} | |||
=== Issues === | |||
''List of issues raised based on the feature implementation.'' | |||
=== Security Considerations === | |||
''List of security considerations implied by the feature.'' | |||
== FEAT30: VNF configuration == | |||
=== Overview === | |||
{| class="wikitable" | |||
|- | |||
| '''Feature Prime''' || Bruno Chatras (Orange) | |||
|- | |||
| '''Feature description''' ||The scope of this feature covers the following areas: | |||
1) Provide guidelines on the use of the configuration options available in the NFV framework and the types of configuration data applicable to each of these options. | |||
2) Specify related enhancements to the set of ETSI NFV specifications needed to improve interoperability between VNFs and independently-developed VNF configuration management functions and further facilitate automation of VNF configuration. | |||
|- | |||
| '''Target Release''' || '''Stage 2:''' TBD (Release 5 (2022-X-X)) | |||
'''Stage 3:''' TBD (Release 5 (2023-X-X)) | |||
|- | |||
| '''Impacted WIs''' || '''Stage 2:''' TBD (IFAxx, IFAyy, SOLzz) | |||
'''Stage 3:''' TBD (SOLzz) | |||
|- | |||
| '''MegaCRs''' || '''Stage 2:''' | |||
TBD: IFAxxx MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//blackhole.doc NFVIFA(21)000xxx] (CR Status) | |||
IFAyyy MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//blackhole.doc NFVIFA(21)000yyy] (CR Status) | |||
'''Stage 3:''' | |||
TBD: SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//blackhole.doc NFVSOL(21)000zzz] (CR Status) | |||
|- | |||
| '''Related/Dependent Features''' || FEAT24 on "VNF generic OAM" | |||
|- | |||
|'''New Specifcations''' | |||
|'''Informative:''' DGR/NFV-EVE022 | |||
'''Stage 2:''' TBD | |||
'''Stage 3:''' TBD | |||
|- | |||
| '''Status''' || '''Informative:''' 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] | |||
|- | |||
| '''Feature team''' || '''Informative:''' Bruno Chatras (Orange) | |||
'''Stage 2:''' Name (Company) | |||
'''Stage 3:''' Name (Company) | |||
|- | |||
| '''Last Updated''' ||2022-12-06 | |||
|}'''EVE''' | |||
{| class="wikitable sortable" | |||
|- | |||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | |||
|- | |||
| 001 || Skeleton and scope<br />- [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000751r1_IFA046_Report_skeleton_on_NFV_support_for_virtualization_of_.zip NFVIFA(21)000751] EVE022 skeleton and scope <br /> || EVE || Sept-2021 || Completed | |||
|- | |||
| 002 || Overview and and use cases <br /> || EVE || Oct-2021 ||Completed | |||
|- | |||
| 003 || Analysis of Use Cases and Identification of Key Issues <br /> || EVE || Nov-2021 ||Completed | |||
|- | |||
| 004 || Solutions identification <br /> || EVE || March-2022 ||Completed | |||
|- | |||
| 005 || Solutions comparison <br /> || EVE || June-2022 ||Completed | |||
|- | |||
| 006 || Recommendations <br /> || EVE || Sep-2022 ||Completed | |||
|- | |||
|} | |||
=== Stage 2 Implementation Plan === | |||
Items to consider in the implementation plan | |||
* Detailed description what has to be done in which work item. | |||
* Timeplan of when the team plans to conclude a particular action in the implementation plan. | |||
'''IFA''' | |||
{| class="wikitable sortable" | |||
|- | |||
! 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''' | |||
{| class="wikitable sortable" | |||
|- | |||
! ID !! Action !! Impacted WG(s) !! Target completion !! Status | |||
|- | |||
| 001 || TBD || TBD || TBD || TBD | |||
|} | |||
=== Issues === | |||
''List of issues raised based on the feature implementation.'' | |||
=== Security Considerations === | |||
''List of security considerations implied by the feature.'' | |||
== FEAT31: Flexible VNF deployment == | |||
=== Overview === | |||
{| class="wikitable" | |||
|- | |||
| '''Feature Prime''' || Arturo Martin de Nicolas (Ericsson) | |||
|- | |||
| '''Feature description''' ||This feature enhances the flexibility of the VNF deployment by introducing parametrization of VNF deployment flavours. It covers the following areas | |||
1) Ability to specify in the VNFD which VDUs or groups of VDUs are optional for a particular deployment flavour | |||
2) Ability to specify in the VNFD which VDU attributes related to resource capacity are configurable | |||
3) Ability to specify in the NSD the selected optional VDUs or group of VDUs of a constituent VNF that are to be deployed | |||
4) Ability to specify in the NS LCM and VNF LCM interfaces the selected optional VDUs or group of VDUs to be deployed | |||
5) Ability to specify in the NS LCM and VNF LCM interfaces the selected values for VDU attributes related to resource capacity | |||
|- | |||
| '''Target Release''' || '''Stage 2:''' TBD (Release 5 (2023-X-X)) | |||
'''Stage 3:''' TBD (Release 5 (2023-X-X)) | |||
|- | |||
| '''Impacted WIs''' || '''Stage 2:''' | |||
IFA010 | |||
IFA011 | |||
IFA007 | |||
IFA008 | |||
IFA013 | |||
IFA014 | |||
'''Stage 3:''' | |||
SOL001 | |||
SOL002 | |||
SOL003 | |||
SOL005 | |||
SOL016? | |||
SOL018? | |||
|- | |||
| '''MegaCRs''' || '''Stage 2:''' | |||
TBD: IFAxxx MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//blackhole.doc NFVIFA(21)000xxx] (CR Status) | |||
IFAyyy MegaCR [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//blackhole.doc NFVIFA(21)000yyy] (CR Status) | |||
'''Stage 3:''' | |||
TBD: SOLzzz MegaCR [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//blackhole.doc NFVSOL(21)000zzz] (CR Status) | |||
|- | |||
| '''Related/Dependent Features''' || None | |||
|- | |||
|'''New Specifcations''' | |||
|'''Informative:''' IFA044 | |||
|- | |||
| '''Status''' || '''Informative:''' Completed | |||
'''Stage 2:''' Not started | |||
'''Stage 3:''' Not started | |||
|- | |||
| '''Contributions''' || [https://portal.etsi.org/Contribution.aspx All feature contributions]<br />[http://https://portal.etsi.org Agreed content] | |||
|- | |||
| '''Feature team''' || '''Stage 2:''' Arturo Martin de Nicolas (Ericsson) | |||
'''Stage 3:''' Arturo Martin de Nicolas (Ericsson) | |||
|- | |||
| '''Last Updated''' ||2023-01-10 | |||
|} | |||
=== Stage 2 Implementation Plan === | |||
Items to consider in the implementation plan | |||
* Detailed description what has to be done in which work item. | |||
* Timeplan of when the team plans to conclude a particular action in the implementation plan. | |||
'''IFA''' | |||
{| class="wikitable sortable" | |||
!ID | |||
!Action | |||
!Impacted WG(s) | |||
!Target | |||
completion | |||
!Status | |||
|- | |||
|001 | |||
|Add requirements on functional behaviour as per recommendations | |||
Vnfm.DepMod.001, Vnfm.ConfAttr.001 and Nfvo.DepMod.001 IFA044 clause 8.1. | |||
'''CRs:''' | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000126r2_FEAT31_IFA010ed451_Functional_requirements.docx NFV(23)000126r2] Status: Feat agreed in NFVIFA#325 | |||
|IFA010 | |||
|TBD | |||
|All CRs Feat agreed | |||
|- | |||
|002 | |||
|Introduce deployableModules in the VNFD as per recommendations VNFD.DepMod.001, | |||
VNFD.DepMod.002 and VNFD.DepMod.003 in IFA044 clause 8.2. | |||
'''CRs:''' | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000127r1_FEAT31_IFA011ed451_Introduction_of_deployable_modules.docx NFV(23)000127r1] Status: Feat agreed in NFVIFA#325 | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000206_FEAT31_IFA011ed451_Supported_operations_for_change_of_deploy.docx NFV(23)000206] Status: Feat agreed in NFVIFA#329 | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000128_FEAT31_IFA011ed451_Adding_deployable_modules_to_the_componen.docx NFV(23)000128] Status: Feat agreed in NFVIFA#325 | |||
|IFA011 | |||
|TBD | |||
|All CRs Feat agreed | |||
|- | |||
|002a | |||
|Add a provision in ScalingAspect IE to exclude combining VDUs that don't belong to the same deployable modules | |||
'''CRs:''' | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000264r2_FEAT31_IFA011ed451_Deployable_modules_relation_to_scaling_as.docx NFV(23)000264r2] Status: Feat agreed in NFVIFA#334 | |||
|IFA011 | |||
|TBD | |||
|All CRs Feat agreed | |||
|- | |||
|002b | |||
|Add a provision in MciopProfile IE to exclude combining VDUs that don't belong to the same deployable modules | |||
'''CRs:''' | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000270r2_FEAT31_IFA011ed451_deployable_modules_relation_to_MCIOPs.docx NFVIFA(23)000270r2] Status: Feat agreed in NFVIFA#334 | |||
|IFA011 | |||
| | |||
|All CRs Feat agreed | |||
|- | |||
|003 | |||
|Introduce support for indication that a VDU resource capacity related attribute is configurable | |||
and in which operations the value is modifiable as per recommendations VNFD.ConfAttr.001 | |||
and VNFD.ConfAttr.002 in IFA044 clause 8.2. | |||
'''CRs:''' | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000281r1_FEAT31_IFA011ed451_Configurable_VDU_capacity_related_attribu.docx NFV(23)000281r1] Status: Feat agreed in NFVIFA#333 | |||
|IFA011 | |||
|TBD | |||
|Started | |||
|- | |||
|004 | |||
|Introduce new attributes in VnfProfile and NsProfile for the support of the selection of deployableModules | |||
of the constituent VNFs as per recommendations NSD.DepMod.001, NSD.DepMod.002, NSD.DepMod.003, NSD.DepMod.004 in IFA044 clause 8.2. | |||
'''CRs:''' | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000131r2_FEAT31_IFA014ed451_Adding_deployable_modules_to_the_VNF_and_.docx NFV(23)000131r2] Status: Feat agreed in NFVIFA#327 | |||
|IFA014 | |||
|TBD | |||
|All CRs Feat agreed | |||
|- | |||
|005 | |||
|Introduce a new attribute in the VnfProfile to indicate whether it is allowed or not to modify values of VDU | |||
attributes related to resource capacity by means of NS LCM interface as per recommendation | |||
NSD.ConfAttr.001 in IFA044 clause 8.2. | |||
|IFA014 | |||
|TBD | |||
|Not started | |||
|- | |||
|006 | |||
|Introduce new parameters in VNF LCM operations Instantiate VNF, Change VNF flavour, Change current | |||
VNF package operation to convey the selection of deployableModules. as per recommendations | |||
Vnflcm.DepMod.001, Vnflcm.DepMod.003 and Vnflcm.DepMod.004 in IFA044 clause 8.3. | |||
'''CRs:''' | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000181r1_FEAT31_IFA007ed451_Adding_selection_of_deployable_modules_in.docx NFVIFA(23)000181r1] Status: Feat agreed in NFVIFA#327 | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000243_FEAT31_IFA008ed451_Mirror_of_181r1_Adding_selection_of_deplo.docx NFVIFA(23)000243] Status: Feat agreed in NFVIFA#332 | |||
|IFA007 | |||
IFA008 | |||
|TBD | |||
|All CRs Feat agreed | |||
|- | |||
|006a | |||
|Introduce provisions for how to handle instantiation or scale level information related to VNFCs that are not part of the selected deployable modules. | |||
CRs: | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000223r1_FEAT31_IFA007ed451_Handling_of_scale_or_instantiation_level_.docx NFVIFA(23)000223r1] Status: Feat agreed in NFVIFA#332 | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000359_FEAT31_IFA008ed451_Mirror_of_223_-_Handling_of_scale_or_inst.docx NFVIFA(23)000359] Status: Feat agreed in NFVIFA#337 | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000360r1_FEAT31_IFA013ed451_Mirror_of_223_-_Handling_of_scale_or_inst.docx NFVIFA(23)000360r1] Status: Feat agreed in NFVIFA#337 | |||
|IFA007 | |||
IFA008 | |||
| | |||
|All CRs Feat agreed | |||
|- | |||
|007 | |||
|Introduce new VNF LCM operation to support the modification of the selection (addition or removal) of | |||
deployableModules as per recommendation Vnflcm.DepMod.002 in IFA044 clause 8.3. | |||
'''CRs:''' | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000185r3_FEAT31_IFA007ed451_New_operation_for_the_selection_of_deploy.docx NFVIFA(23)000185r3] Status: Feat agreed in NFVIFA#329 | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000244_FEAT31_IFA008ed451_Mirror_of_185r3_New_operation_for_the_sel.docx NFVIFA(23)000244] Status: Feat agreed in NFVIFA#332 | |||
|IFA007 | |||
IFA008 | |||
|TBD | |||
|All CRs Feat agreed | |||
|- | |||
|007a | |||
|Introduce a new attribute in the VnfInfo or InstantiatedVnfInfo to indicate the deployable modules currently selected | |||
'''CRs:''' | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000199r1_FEAT31_IFA007ed451_Add_selectedDeployableModule_in_instantia.docx NFVIFA(23)000199r1] Status: Feat agreed in NFVIFA#330 | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000246_FEAT31_IFA008ed451_Mirror_of_199r1_Add_selectedDeployableMod.docx NFVIFA(23)000246] Status: Feat agreed in NFVIFA#332 | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000269_FEAT31_IFA013ed451_Mirror_of_199r1_Add_selectedDeployableMod.docx NFVIFA(23)000269] Status: Feat agreed in NFVIFA#332 | |||
|IFA007 | |||
IFA008 | |||
IFA013 | |||
|TBD | |||
|All CRs Feat agreed | |||
|- | |||
|007b | |||
|Add SelectVnfDeployableModules configuration parameters to VnfLcmOperationsConfiguration IE | |||
CRs: | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000226_FEAT31_IFA011ed451_Add_SelectVnfDeployableModules_configurat.docx NFVIFA(23)000226] Status: Feat agreed in NFVIFA#331 | |||
|IFA011 | |||
| | |||
|All CRs Feat agreed | |||
|- | |||
|008 | |||
|Introduce new parameters in VNF LCM operations Instantiate VNF, Change VNF flavour, Change current | |||
VNF package to convey selected values for VDU attributes related to resource capacity as per | |||
recommendations Vnflcm.ConfAttr.001, Vnflcm.ConfAttr.003 and Vnflcm.ConfAttr.004 in IFA044 | |||
clause 8.3. | |||
CRs: | |||
|IFA007 | |||
IFA008 | |||
|TBD | |||
|Not started | |||
|- | |||
|009 | |||
|Decide whether to use scale VNF operation or add a new VNF LCM operation to support the modification of | |||
selected values for VDU attributes related to resource capacity and add new parameters to the scale VNF | |||
operation or add new operation based on the decision, as per recommendation Vnflcm.ConfAttr.002 in | |||
IFA044 clause 8.3. | |||
|IFA007 | |||
IFA008 | |||
|TBD | |||
|Not started | |||
|- | |||
|010 | |||
|Add attributes to IEs used in the update NS operation to support conveying the selection of | |||
deployableModules as per recommendations Nslcm.DepMod.001, Nslcm.DepMod.002, Nslcm.DepMod.003, Nslcm.DepMod.004, Nslcm.DepMod.005, Nslcm.DepMod.006, Nslcm.DepMod.007 in IFA044 clause 8.3. | |||
CRs: | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000222_FEAT31_IFA013ed451_Adding_selection_of_deployable_modules_in.docx NFVIFA(23)000222] Status: Feat agreed in NFVIFA#331 | |||
|IFA013 | |||
|TBD | |||
|All CRs Feat agreed | |||
|- | |||
|011 | |||
|Add new NS update type to the update NS operation and corresponding new IE to support the modification | |||
of the selection of deployableModules as per recommendations Nslcm.DepMod.008 in IFA044 clause 8.3. | |||
CRs: | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000245r1_FEAT31_IFA013ed451_New_Update_NS_type_for_the_selection_of_d.docx NFVIFA(23)000245r1] Status: Feat agreed in NFVIFA#332 | |||
|IFA013 | |||
|TBD | |||
|All CRs Feat agreed | |||
|- | |||
|012 | |||
|Add attributes to IEs used in the update NS operation to support conveying selected values for VDU | |||
attributes related to resource capacity as per recommendations Nslcm.ConfAttr.001, Nslcm.ConfAttr.002, | |||
Nslcm.ConfAttr.003, Nslcm.ConfAttr.004, Nslcm.ConfAttr.005, Nslcm.ConfAttr.006, Nslcm.ConfAttr.007 | |||
in IFA044 clause 8.3. | |||
|IFA013 | |||
|TBD | |||
|Not started | |||
|- | |||
|013 | |||
|Decide whether to use scale NS operation or introduce new NS update type or use the new NS update | |||
type introduced in activity 011 to support the modification of selected values for VDU attributes related | |||
to resource capacity and add attributes to the new or existing IEs, depending on the decision, as per | |||
recommendation Nslcm.ConfAttr.008 in IFA044 clause 8.3. | |||
|IFA013 | |||
|TBD | |||
|Not started | |||
|- | |||
|014 | |||
|Add new parameters in the grant VNF lifecycle operation to convey the selected deployableModules as per | |||
recommendation VnfGrant.DepMod.001 in IFA044 clause 8.3. | |||
'''CRs:''' | |||
[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023/NFVIFA(23)000200r2_FEAT31_IFA007ed451_Add_selectedDeployableModule_in_the_grant.docx NFVIFA(23)000200r2] Status: Feat agreed in NFVIFA#330 | |||
|IFA007 | |||
|TBD | |||
|All CRs Feat agreed | |||
|- | |||
|015 | |||
|Add new parameters in the grant VNF lifecycle operation to convey values for VDU attributes related | |||
to resource capacity as per recommendation VnfGrant.ConfAttr.001 in IFA044 clause 8.3. | |||
|IFA007 | |||
|TBD | |||
|Not started | |||
|- | |||
|016 | |||
|Add SAP to deployable modules mapping information in the NSD | |||
'''CRs:''' | |||
NFVIFA(23)000388r1 | |||
|IFA014 | |||
|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''' | |||
{| class="wikitable sortable" | |||
!ID | |||
!Action | |||
!Impacted WG(s) | |||
!Target completion | |||
!Status | |||
|- | |||
|001 | |||
|Introduce deployableModules in the VNFD as per recommendations VNFD.DepMod.001, | |||
VNFD.DepMod.002 and VNFD.DepMod.003 in IFA044 clause 8.2. | |||
|SOL001 | |||
|TBD | |||
|Not started | |||
|- | |||
|002 | |||
|Introduce support for indication that a VDU resource capacity related attribute is configurable | |||
and in which operations the value is modifiable as per recommendations VNFD.ConfAttr.001 | |||
and VNFD.ConfAttr.002 in IFA044 clause 8.2 | |||
|SOL001 | |||
|TBD | |||
|Not started | |||
|- | |||
|003 | |||
|Introduce new attributes in VnfProfile and NsProfile for the support of the selection of deployableModules | |||
of the constituent VNFs as per recommendations NSD.DepMod.001, NSD.DepMod.002, NSD.DepMod.003, | |||
NSD.DepMod.004 in IFA044 clause 8.2. | |||
|SOL001 | |||
|TBD | |||
|Not started | |||
|- | |||
|004 | |||
|Introduce a new attribute in the VnfProfile to indicate whether it is allowed or not to modify values of VDU | |||
attributes related to resource capacity by means of NS LCM interface as per recommendation | |||
NSD.ConfAttr.001 in IFA044 clause 8.2. | |||
|SOL001 | |||
|TBD | |||
|Not started | |||
|- | |||
|005 | |||
|Introduce new parameters in VNF LCM operations Instantiate VNF, Change VNF flavour, Change current | |||
VNF package operation to convey the selection of deployableModules. as per recommendations | |||
Vnflcm.DepMod.001, Vnflcm.DepMod.003 and Vnflcm.DepMod.004 in IFA044 clause 8.3. | |||
|SOL003 | |||
SOL002 | |||
|TBD | |||
|Not started | |||
|- | |||
|006 | |||
|Introduce new VNF LCM operation to support the modification of the selection (addition or removal) of | |||
deployableModules as per recommendation Vnflcm.DepMod.002 in IFA044 clause 8.3. | |||
|SOL002 | |||
SOL003 | |||
|TBD | |||
|Not started | |||
|- | |||
|007 | |||
|Introduce new parameters in VNF LCM operations Instantiate VNF, Change VNF flavour, Change current | |||
VNF package to convey selected values for VDU attributes related to resource capacity as per | |||
recommendations Vnflcm.ConfAttr.001, Vnflcm.ConfAttr.003 and Vnflcm.ConfAttr.004 in IFA044 | |||
clause 8.3. | |||
|SOL002 | |||
SOL003 | |||
|TBD | |||
|Not started | |||
|- | |||
|008 | |||
|Introduce new parameters in the scale VNF operation or add new VNF LCM operation based on the | |||
decision taken in IFA (action 009 in the stage 2 implementation plan), as per recommendation | |||
Vnflcm.ConfAttr.002 in IFA044 clause 8.3. | |||
|SOL002 | |||
SOL003 | |||
|TBD | |||
|Not started | |||
|- | |||
|009 | |||
|Add attributes to datatypes used in the update NS operation to support conveying the selection of | |||
deployableModules as per recommendations Nslcm.DepMod.001, Nslcm.DepMod.002, Nslcm.DepMod.003, | |||
Nslcm.DepMod.004, Nslcm.DepMod.005, Nslcm.DepMod.006, Nslcm.DepMod.007 in IFA044 clause 8.3.. | |||
|SOL005 | |||
|TBD | |||
|Not started | |||
|- | |||
|010 | |||
|Add new NS update type to the update NS operation and corresponding datatype to support the modification | |||
of the selection of deployableModules as per recommendations Nslcm.DepMod.008 in IFA044 clause 8.3. | |||
|SOL005 | |||
|TBD | |||
|Not started | |||
|- | |||
|011 | |||
|Add attributes to datatypes used in the update NS operation to support conveying selected values for VDU | |||
attributes related to resource capacity as per recommendations Nslcm.ConfAttr.001, Nslcm.ConfAttr.002, | |||
Nslcm.ConfAttr.003, Nslcm.ConfAttr.004, Nslcm.ConfAttr.005, Nslcm.ConfAttr.006, Nslcm.ConfAttr.007 | |||
in IFA044 clause 8.3. | |||
|SOL005 | |||
|TBD | |||
|Not started | |||
|- | |||
|012 | |||
|Add attributes to the datatype used in scale NS operation, or in the new datatype introduced in | |||
SOL activity 010 or in a new datatype for a new update NS operation depending on the decision taken | |||
in IFA (action 013 in the stage 2 implementation plan) to support the modification of selected values for | |||
VDU attributes related to resource capacity as per recommendations Nslcm.ConfAttr.008 in | |||
IFA044 clause 8.3. | |||
|SOL005 | |||
|TBD | |||
|Not started | |||
|- | |||
|013 | |||
|Add new parameters in the grant VNF lifecycle operation to convey the selected deployableModules as per | |||
recommendation VnfGrant.DepMod.001 in IFA044 clause 8.3. | |||
|SOL003 | |||
|TBD | |||
|Not started | |||
|- | |||
|014 | |||
|Add new parameters in the grant VNF lifecycle operation to convey values for VDU attributes related | |||
to resource capacity as per recommendation VnfGrant.ConfAttr.001 in IFA044 clause 8.3. | |||
|SOL003 | |||
|TBD | |||
|Not started | |||
|} | |||
=== 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. | |||
'''Ways of Working for this security enhancement feature. Latest update made by [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000032r2_Enh01_01_Discussion_on_Certificate_Management_IFA_specs_impa.pptx NFVSEC(22)000032r2] at NFV#38/SEC#210''' | |||
# <s>Resolve open comments on the contribution in IFA;</s> | |||
# <s>IFA '''almost feature agrees''' (first step) the contribution;</s> | |||
# <s>Seek feedback from SEC;</s> | |||
# <s>After resolving open comments on the contribution in SEC, '''SEC endorse''' the contribution and back to step 1.</s> | |||
# <s>IFA '''feature agrees''' (second step) the contribution with confirmation from SEC.</s> | |||
# SEC approval, then will be sent to IFA for feat agreed/approval | |||
#* IFA026 on Basic use case / Basic concept and architectural aspects including IFA010 existing featagreedCRs | |||
#* IFA033 | |||
#* update SEC021/022/023/025, if necessary | |||
# IFA feat agreed/approval, will be sent back to SEC for endorsement | |||
#* IFA006/008 | |||
#* (Potential) IFA013/007/011/014 | |||
{| class="wikitable" | |||
|+ | |||
!ID | |||
!Name | |||
!Release | |||
!Status | |||
!Contact | |||
!Descirption | |||
!Contributions | |||
|- | |||
|ENH01.xx | |||
|New security enhancement | |||
| | |||
|{Proposal,Under development, Completed, Closed} | |||
|Foo Bar (ACME) <foo.bar@acme.org> | |||
|A short description of the feaure | |||
| | |||
* List | |||
* of | |||
* related | |||
* CRs | |||
|- | |||
|ENH01.01 | |||
|Certificate management | |||
|Release 4 | |||
|Under development | |||
|Yuya Kuno (DOCOMO) | |||
|The security enhancement aims to specify the capability to support certificate management by introducing OCMF (Operator Certificate Management Function) within the NFV MANO architecture and is enhancing the NFV-MANO reference points and functional blocks. OCMF enhances "Operator Certificate Enrolment Server" as defined in ETSI GR NFV-SEC 005. | |||
|Information about the planned schedule and potential specification impacts is available in contribution [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000843r2_Enhancement_Proposal_on_Certificate_Management_Security_Enha.docx NFVIFA(21)000843r2]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2021//NFVSEC(21)000071r2_Proposal_of_security_enhancement_for_IFA_on_certificate_mgmt.zip NFVSEC(21)000071r2]:Enhancement Proposal on Certificate Management Security Enhancement (Noted - IFA#258) | |||
Discussion paper of direction for Stage 2 in IFA & SEC joint session: [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)0001053r1_Enh01_01_DP_for_IFA_and_SEC_joint_session.pptx NFVIFA(21)001053r1]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2021//NFVSEC(21)000094r6_SEC_Review_on_Enh01_01_Discussion_about_Certificate_Manageme.zip NFVSEC(21)000094r6]:Enh01.01 DP for IFA and SEC joint session (IFA#264 check open issues -> SEC review -> IFA#274 Noted - agreed Suggestion#1 (NFV specifies both option) and Suggestion#2(registration usecase is starting points))) | |||
Discussion paper for the stage2 level working specs on Certificate Management: [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_04_13_WG_NFVSEC%23207/NFVSEC(22)000024_ENH01_Discussion_on_specs_approach_for_security_architecture.pptx NFVSEC(22)000024]:Enh01.01 DP for proposing to work on IFA026/IFA033 as for SEC related architecture and RPs/IFs (SEC#207 - agreed to work on IFA026/IFA033 for Certificate Management and noted clear separation between SM and Certificate Management needed. And also asuumed that the contirbutions on IFA026/033 worked in SEC WG first) | |||
Discussion paper [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000032r2_Enh01_01_Discussion_on_Certificate_Management_IFA_specs_impa.pptx NFVSEC(22)000032r2] "Enh01.01 Discussion on Certificate Management IFA specs impacts and work plan": Enh01.01 DP for identifying the impacted specs and work role/step between IFA and SEC in IFA/SEC joint session on NFV#38 (SEC#210/IFA#287). | |||
* Endorsed on | |||
** SEC works, will be sent to IFA for approval | |||
*** IFA026 on Basic use case / Basic concept and architectural aspects including IFA010 existing featagreedCRs | |||
*** IFA033 | |||
*** update SEC021/022/023/025, if necessary | |||
** IFA works, will be back to SEC for endorsement | |||
*** IFA006/008 | |||
*** (Potential) IFA013/007/011/014 | |||
Discussion paper [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_09_13_WG_NFVSEC%23215/NFVSEC(22)000059r5_IFA026_Supporting_material_for_Use_Cases.pptx NFVSEC(22)000059r5] "Enh01.01 Supporting material for Use Cases " in NFV#39/SEC#215: | |||
* DP Noted | |||
* Agreed to remove "proxy mode" for VNF OAM certificate an VNFCI certificate due to lack of support. | |||
* Agreed on the keys (public and private keys) generation process for both NFV-MANO cert at NFV-MANO entities and VNF OMA cert/VNFCI cert at VNFM, included as part of CSR process, and done at each of NFV-MANO entities for NFV-MANO certificate, done at VNFM for VNF OAM certificate/VNFCI certificate. | |||
* Agreed on that the registration of NFV-MANO entities for NFV-MANO certificates, done by OSS. | |||
Discussion paper [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023/NFVSEC(23)000008_DP_on_EN0101_documentation_overview.pptx NFVSEC(23)0000008] "ENH0101 documentation overview" in SEC#221. | |||
* DP noted | |||
* SEC chairman will take up the matter at the TSC level on on how best to proceed with the IFA review of IFA026 and IFA033. One-shot review is not efficient for IFA, since sending each and every contribution is also not very efficient as it will overwhelm IFA time and resourcess. | |||
* | |||
[[Feature Tracking#Enh01.01: Certificate Management|Individual CRs]] | |||
|- | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
|} | |||
=== Enh01.01: Certificate Management === | |||
'''Stage1/2''' | |||
{| class="wikitable" | |||
|+ | |||
!ID | |||
!Action | |||
!impacted WI(s) | |||
!Status | |||
|- | |||
|001 | |||
|develop usecase for direct mode of VNFCI certficate and VNF OAM certificate. | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000085r2_IFA026_Use_case_for_VNFCI_certificate_enrollment_in_direct-m.zip NFVSEC(22)000085r2]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026_Use_case_for_VNFCI_certificate_enrollment_in_direct-mode (SEC#220 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000119r1_IFA_026_5_2_4_2_1_-_VNFCI_certificate_management_in_direct_m.DOC NFVSEC(22)000119r1]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 5.2.4.2.1 - VNFCI certificate management in direct mode (SEC#220 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000121r1_IFA_026_use_case_for_VNFCI_certificate_enrollment_with_remot.docx NFVSEC(22)000121r1]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 use case for VNFCI certificate enrollment with remote-attestation in direct-mode (SEC#220 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000101r1_Enh01_01_IFA026_Certificate_renewal_in_direct-mode.docx NFVSEC(23)000101r1]/ : IFA026 Certificate renewal in direct-mode (SEC#230 Agreed.) | |||
|IFA026 | |||
| | |||
|- | |||
|002 | |||
|develop usecase for delegation mode of VNFCI certificate and VNF OAM certificate. | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_08_25_WG_NFVSEC%23214/NFVSEC(22)000054r5_IFA026_Use_case_for_Registration_of_VNFM_for_VNFCI_certifica.docx NFVSEC(22)000054r5]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 Registration of VNFM, VNFCI cert delegation mode (SEC#214 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_09_13_WG_NFVSEC%23215/NFVSEC(22)000069r2_IFA026_Use_case_for_CSR_for_VNFCI_certificate_in_delegation_.docx NFVSEC(22)000069r2]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 Use case for CSR for VNFCI certificate in delegation mode (SEC#215 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_09_13_WG_NFVSEC%23215/NFVSEC(22)000070r2_IFA026_Use_case_for_VNFCI_certificate_install_during_VNF_ins.docx NFVSEC(22)000070r2]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 Use case for VNFI certificate install during VNF instantiation for delegation mode (SEC#215 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_09_13_WG_NFVSEC%23215/NFVSEC(22)000071r2_IFA026_Use_case_for_VNFCI_certificate_install_after_VNF_inst.docx NFVSEC(22)000071r2]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 Use case for VNFI certificate install after VNF instantiation for delegation mode (SEC#215 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_09_13_WG_NFVSEC%23215/NFVSEC(22)000072r2_IFA026_Use_case_for_VNF_OAM_certificate_install_during_VNF_i.docx NFVSEC(22)000072r2]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 Use case for VNF OAM certificate install during VNF instantiation for delegation mode (SEC#215 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000103r1_IFA026_Update_on_Use_case_for_Registration_of_VNFM_for_VNFCI.docx NFVSEC(22)000103r1]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026_Update_on_Use_case_for_Registration_of_VNFM_for_VNFCI (SEC#217 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000079r1_Enh01_01_IFA026_5_2_4_2_2_Certificate_management__delegation.docx NFVSEC(23)000079r1]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000369_Enh01_01_IFA026ed451_bulk_CRs_to_resolve_ENs.zip NFVIFA(23)000369] :IFA026_5.2.4.2.2_Certificate management (delegation-mode) (IFA#336 Agreed) | |||
|IF026 | |||
| | |||
|- | |||
|003 | |||
|develop usecase for VNF Package certificate. | |||
|IFA026 | |||
|Not started | |||
|- | |||
|004 | |||
|develop usecase for NFV-MANO certificate. | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_09_13_WG_NFVSEC%23215/NFVSEC(22)000079r1_IFA026_Use_case_for_Registration_of_NFVO_for_MANO_certificat.docx NFVSEC(22)000079r1]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 Use case on Registration for NFVOfor MANO certificate (SEC#215 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_09_13_WG_NFVSEC%23215/NFVSEC(22)000080r2_IFA026_Use_case_on_CSR_for_NFVO__for_MANO_certificate.docx) NFVSEC(22)000080r2]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 Use case on CSR for NFVO, for MANO certificate (SEC#215 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_09_13_WG_NFVSEC%23215/NFVSEC(22)000081r2_IFA026_Use_case_for_Registration_of_VNFM_for_MANO_certificat.docx NFVSEC(22)000081r2]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 Use case on Registration for VNFM for MANO certificate (SEC#215 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_09_13_WG_NFVSEC%23215/NFVSEC(22)000082r3_IFA026_Use_case_on_CSR_for_VNFM__for_MANO_certificate.docx NFVSEC(22)000082r3]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 Use case on CSR for VNFM for MANO certificate (SEC#215 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_09_13_WG_NFVSEC%23215/NFVSEC(22)000083r2_IFA026_Use_case_for_Registration_of_VIM_for_MANO_certificate.docx NFVSEC(22)000083r2]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 Use case on Registration for VIM, for MANO certificate (SEC#215 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_09_13_WG_NFVSEC%23215/NFVSEC(22)000084r2_IFA026_Use_case_on_CSR_for_VIM_for_MANO_certificate.docx NFVSEC(22)000084r2]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 Use case on CSR for VIM, for MANO certificate (SEC#215 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000103_ENH01_01_IFA026_5_2_4_4_NFV_MANO_certificate_management.docx NFVSEC(23)000103]/ :IFA026_5.2.4.4_NFV MANO certificate management | |||
|IFA026 | |||
| | |||
|- | |||
|005 | |||
|develop usecase for Virtualised computation environment control plane certificate. | |||
|IFA026 | |||
|Not started | |||
|- | |||
|006 | |||
|Add functional requirements for the certirficate mgmt. | |||
- functional requirements | |||
* [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000835r5_IFA010ed431_support_certificate_mgmt.docx NFVIFA(21)000835r5]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2021//NFVSEC(21)000069r1_draft_CR_for_IFA010_to_support_certificate_mgmt.docx NFVSEC(12)000069] &[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2021//NFVSEC(21)000071r2_Proposal_of_security_enhancement_for_IFA_on_certificate_mgmt.zip NFVSEC(21)000071r2]: IFA010ed431 support certificate mgmt (SEC#194 endorsed -> IFA#257 FEAT Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000899r4_IFA010ed431_enhance_functional_requirements_to_support_certi.docx NFVIFA(21)000899r4]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2021//NFVSEC(21)000090r2_SEC_review_on_NFVIFA_21_000899r3.zip NFVSEC(21)000090r2]: IFA010ed431 enhance functional requirements to support certificate mgmt (IFA#260 FEAT almost Agreed -> SEC endorsed -> IFA#265 FEAT almost Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000935r2_Enh01_01_IFA010ed431_exchange_NFV-MANO_and_sub_CAs_certifica.docx NFVIFA(21)000935r2]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2021//NFVSEC(21)000089r1_SEC_review_on_NFVIFA_21_000935.zip NFVSEC(21)000089r1]: Enh01.01 IFA010ed431 exchange NFV-MANO and sub CAs certificate (IFA#260 FEAT almost Agreed -> SEC#199 endorsed -> IFA#265 FEAT almost Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2021//NFVIFA(21)000960r1_IFA010ed431_additions_to_support_certificate_management_in_c.docx NFVIFA(21)000960r1]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2021//NFVSEC(21)000085_Proposal_to_add_further_clarifications_for_support_of_cert_m.zip NFVSEC(21)000085]: FA010ed431 additions to support certificate management in clause 5.y (SEC#197 endorsed with further 3 expansions -> IFA available) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000044r2_Enh01_01_IFA026_direct_mode_with_HSM.docx NFVSEC(23)000044r2]/: IFA026 direct mode with HSM (SEC#230 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000099r1_Enh01_01_IFA026_Key_Attestation.docx NFVSEC(23)000099r1]/ : IFA026 Key Attestation | |||
- Architecture | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000121r1_IFA_026_use_case_for_VNFCI_certificate_enrollment_with_remot.docx NFVSEC(22)000116r2]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000220r2_Enh01_01_IFA026ed451_improve_introduction_and_functional_req.zip NFVIFA(23)000220r2]: IFA026 5.2.3 Certificate management architecture options (SEC#221 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000114r1_IFA026_5_2_1_2_General_Certificate_Management_Architecture.docx NFVSEC(22)000114r1]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 5.2.1.2 General Architecture (SEC#220 Agreed, IFA#324 Agreed) | |||
*[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000115_IFA026_5_2_2_Certificate_management_function_and_reference_p.docx NFVSEC(22)000115]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026_5_2_2_Certificate_management_function_and_reference_p (SEC#220 Agreed, IFA#324 Agreed) | |||
- General | |||
*[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_07_27_WG_NFVSEC%23213/NFVSEC(22)000053r3_IFA026_Re-structuring_TOC.docx NFVSEC(22)000053r3]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026 Re-structuring TOC (SEC#213 Agreed, IFA#324 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000095_IFA026_Annex_B_Requirements__Re-introduction_of_feat_agreed_.docx NFVSEC(22)000095]: IFA026_Requirements_AnnexB-IFAFeatAgreed (SEC#216 endorsed) | |||
*[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000096r5_IFA026_Annex_B_Requirements__Updates_on_the_feat_agreed_CRs.docx NFVSEC(22)000096r5]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA026_Requirements_AnnexB-Updates (SEC#220 Agreed, IFA#324 Agreed) | |||
*[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000120_IFA_026_appendix_-_certificate_profile_example.docx NFVSEC(22)000120]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000088r1_Enh01_01_IFA026_add_usecase_and_functional_requirements.zip NFVIFA(23)000088r1]: IFA 026 appendix - certificate profile example (SEC#220 Agreed, IFA#324 Agreed) | |||
*[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023/NFVSEC(23)000035_IFA026_remove_editor_notes_C_2_1.docx NFVSEC(23)000035]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000220r2_Enh01_01_IFA026ed451_improve_introduction_and_functional_req.zip NFVIFA(23)000220r2]: IFA026_remove_editor_notes_C_2_1 (SEC#223 Agreed) | |||
*[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000072_Enh01_01_IFA026_modification_5_2_6_General_requirements.docx NFVSEC(23)000072]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000369_Enh01_01_IFA026ed451_bulk_CRs_to_resolve_ENs.zip NFVIFA(23)000369] : IFA026_modification_5.2.6_General_requirements (IFA#336 Agreed) | |||
*[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000080r1_Enh01_01_IFA026_EN_clean_up_on_handling_the_key_pairs.docx NFVSEC(23)000080r1]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000369_Enh01_01_IFA026ed451_bulk_CRs_to_resolve_ENs.zip NFVIFA(23)000369] :IFA026_EN clean up on handling the key pairs (IFA#336 Agreed) | |||
*[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000081_IFA026_5_2_some_certificate_types_move_to_out_of_scope.docx NFVSEC(23)000081]/ :IFA026 5.2 some certificate types move to out of scope | |||
* | |||
|IFA026 | |||
IFA010 | |||
| | |||
|- | |||
|007 | |||
|Add interface for certificate management to CMF. | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/NFVSEC(22)000097r4_ENH01_01_IFA033ed441_Introduction_of_structure_for_Certifica.docx NFVSEC(22)0000097r4]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000845r4_ENH01_01_IFA033ed441_Introduction_of_structure_for_Certifica.docx NFVIFA(22)0000845r4]: IFA033ed441_Introduction_of_structure_for_Certification (SEC#220 Agreed/IFA#314 FEAT agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023/NFVSEC(23)000007_ENH01_01_IFA033ed441_11_1_IF_Specification_introduction.docx NFVSEC(23)0000007]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000321_Draft_GS_NFV-IFA033ed451_v4_4_2.zip NFVIFA(23)000321]: IFA033ed441_11_1_IF_Specification_introduction (SEC#221 Agreed, IFA#333 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023/NFVSEC(23)000006r3_ENH01_01_IFA033ed441_10_3_IF_Requirements.docx NFVSEC(23)000006r3]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000321_Draft_GS_NFV-IFA033ed451_v4_4_2.zip NFVIFA(23)000321]: IFA033ed441_10_3_IF_Requirements.docx (SEC#223 Agreed, IFA#333 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000039r2_ENH01_01_IFA033_add_11_2_2_description_certificate_managemen.docx NFVSEC(23)000039r2]/ :IFA033 add 11.2.2 description certificate management if in direct mode (SEC#226 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000076r1_ENH01_01_IFA033_fix_11_2_1_description.docx NFVSEC(23)000076r1]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000321_Draft_GS_NFV-IFA033ed451_v4_4_2.zip NFVIFA(23)000321]: IFA033 fix 11.2.1 description (SEC#228 Agreed, IFA#333 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000087r1_ENH01_01_IFA033ed442_11_2_1_Certificate_Management_IF.docx NFVSEC(23)000087r1]/: IFA033ed442 11.2.1 Certificate Management IF (SEC#228-bis Agreed) | |||
|IFA033 | |||
| | |||
|- | |||
|008 | |||
|Add Register Operation | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000010r2_ENH01_01_IFA033ed441_11_1_1_2_Register_Operation.docx NFVSEC(23)000010r2]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000321_Draft_GS_NFV-IFA033ed451_v4_4_2.zip NFVIFA(23)000321]: IFA033ed441 11.1.1.2 Register Operation (SEC#225 Agreed, IFA#333 Agreed) | |||
|IFA033 | |||
| | |||
|- | |||
|009 | |||
|Add CSR Operation | |||
* NFVSEC(23)000024r1 :IFA033 11.1.1.3 CSR Operation | |||
|IFA033 | |||
| | |||
|- | |||
|010 | |||
|Add Vnfm-Cm reference point | |||
* [https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000038r1_ENH01_01_IFA033_table_10_3_1-3_new_interface_requirement.docx NFVSEC(23)000038r1]/[https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000321_Draft_GS_NFV-IFA033ed451_v4_4_2.zip NFVIFA(23)000321]:IFA033 table 10.3.1-3 new interface requirement (SEC#225, IFA#333 Agreed) | |||
|IFA033 | |||
| | |||
|- | |||
|011 | |||
|Add Vnf-Cm reference point | |||
|IFA033 | |||
|Not started | |||
|- | |||
|012 | |||
|Enhance VNFD to support certificate mgmt. | |||
* [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000093r3_Enh01_01_IFA011ed451_add_certificateDesc.docx NFVIFA(23)000093r3]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000054r6_Enh01_01_IFA011ed451_add_certificateDesc.zip NFVSEC(23)000054r6] :IFA011ed451 add certificateDesc (IFA#335 FEAT agreed) | |||
|IFA011 | |||
| | |||
|- | |||
|013 | |||
|Enhance VNF LCM to support certificate mgmt. | |||
* [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000239r3_Enh01_01_IFA006ed451_add_certificateData.docx NFVIFA(23)000239r3]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000066r1_Enh01_01_IFA006ed451_add_certificateData.zip NFVSEC(23)000066r1] :IFA006ed451 add certificateData (SEC#228-bis Agreed, IFA#336 FEAT Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000225r2_Enh01_01_IFA007ed451_add_certificateConfigurationData__Mirro.docx NFVIFA(23)000225r2]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000060r3_Enh01_01_IFA007ed451_add_certificateConfigurationData__Mirro.zip NFVSEC(23)000060r3] :IFA007ed451 add certificateConfigurationData (IFA#335 FEAT agreed, SEC#228 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000236r2_Enh01_01_IFA007ed451_add_certificateInfo.docx NFVIFA(23)000236r2]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000061r3_Enh01_01_IFA007ed451_add_certificateInfo.zip NFVSEC(23)000061r3] :IFA007ed451 add certificateInfo (IFA#335 FEAT agreed, SEC#228 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000378r2_Enh01_01_IFA008ed451_CertificateData_and_Info__Mirror_of_225.docx NFVIFA(23)000378r2]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000096r1_Enh01_01_IFA008ed451_add_certificateConfigurationData__Mirro.zip NFVSEC(23)000096r1]: IFA008ed451 add certificateConfigurationData (IFA#337 FEAT agreed, SEC#230 Agreed) | |||
* [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000379_Enh01_01_IFA008ed451_add_certificateData__Mirror_of_239_.docx NFVIFA(23)000379]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000097_Enh01_01_IFA008ed451_add_certificateData__Mirror_of_IFA_239_.zip NFVSEC(23)000097] :IFA008ed451 add certificateData (IFA#337 FEAT Agreed, SEC#230 Agreed) | |||
|IFA006 | |||
IFA007 | |||
IFA008 | |||
| | |||
|- | |||
|014 | |||
|Enhance NS LCM to support certificate mgmt. | |||
* [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2023//NFVIFA(23)000092r2_Enh01_01_IFA013ed451_add_certificateConfigurationData.docx NFVIFA(23)000092r2]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2023//NFVSEC(23)000055r6_Enh01_01_IFA013ed451_add_certificateConfigurationData.zip NFVSEC(23)000055r6] :IFA013ed451 add certificateConfigurationData (IFA#335 FEAT agreed, SEC#228 Agreed) | |||
* NFVIFA(23)000332/ :IFA013ed451 add certificateInfo (IFA#336 almost Agreed) | |||
|IFA013 | |||
| | |||
|- | |||
|015 | |||
|Enhance MANO mgmt to support certificate mgmt. | |||
* [https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2022/NFVIFA(22)000160r2_ENH01_01_IFA031ed431_Register_Requirements_on_certificate_ma.docx NFVIFA000(22)160r2]/[https://docbox.etsi.org/ISG/NFV/SEC/05-CONTRIBUTIONS/2022/2022_03_17_WG_NFVSEC%23205/NFVSEC(22)000019r1_SEC_Review_on_Enh01_01_NFVIFA_22_000160r1.zip NFVSEC(22)000019r1]: IFA031ed431 adding "Requirements on Registration of VNF/VNFC and MANO functionaly entity" (IFA#275 IFA160r1 FEAT agreed -> SEC#205 endorsed as SEC19r1/IFA160r2 with modification) | |||
|IFA031 | |||
| | |||
|} | |||
'''Stage3''' | |||
{| class="wikitable" | |||
|+ | |||
!ID | |||
!Action | |||
!Impacted WI(s) | |||
!Status | |||
|- | |||
|001 | |||
|Enhance VNFD to support certificate mgmt. | |||
|SOL001 | |||
SOL006 | |||
| | |||
|- | |||
|002 | |||
|Enhance VNF LCM to support certificate mgmt. | |||
|SOL002 | |||
SOL003 | |||
| | |||
|- | |||
|003 | |||
|Enhancde NS LCM to support certificate mgmt. | |||
|SOL005 | |||
| | |||
|} | |||
== 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 | |||
!Release | |||
!Status | |||
!Contact | |||
!Description | |||
!Contributions | |||
|- | |||
|ENH02.01 | |||
|NFV-MANO enhancement with SDN-based networking | |||
|Release 4 | |||
|Stage 2 complete | |||
Stage 3 | |||
SOL001 completed | |||
| | |||
{| 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. | |||
|'''Stage 2:''' | |||
* NFVIFA(19)000858r4 : feature proposal (accepted) | |||
* NFVIFA(19)000966r2: adding RD IE in IFA014, available | |||
* NFVIFA(19)0001018: new requirements to IFA010, FEAT Agreed (IFA#202) | |||
* NFVIFA(20)000240r2: adding new routing resource as a new type of network resources: FEAT Agreed (IFA#208) | |||
* NFVIFA(20)000239r1: discussion paper for adding routing resource, available | |||
* NFVIFA(20)000313r3: adding a new RoutingResorceData for describing a routing resource, FEAT Agreed (IFA#197) | |||
* NFVIFA(20)000314r3: adding the Routing resource in the Update Virtualised Network Resource operation, FEAT Agreed (IFA#197) | |||
* NFVIFA(20)000517r3: discussion paper for NSD model for supporting Routing resource: available | |||
<nowiki>============= Mega CRs Approved ========</nowiki> | |||
* IFA005: NFVIFA(20)000728r1 (Approved in NFVIFA#216) | |||
* IFA010: NFVIFA(21)000030r3 (Approval in IFA#230) | |||
* IFA014: NFVIFA(21)000150r4 (Approval in IFA#230) | |||
'''Stage 3:''' | |||
* SOL001 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000074r4_SOL001ed431_enh02_01_adding_L2_Network_scope_in_NsAffinityRu.docx NFVSOL(22)000074r4] (Approved in SOL#197) | |||
* SOL014 ongoing | |||
|- | |||
|ENH02.02 | |||
|NFV-MANO enhancement for NS feasibility check | |||
|Release 4 | |||
|Stage 2 complete | |||
Stage 3 | |||
completed without SOL016 | |||
|Junichi Kawasaki <ju-kawasaki@kddi.com>, Kenichi Ogaki <ke-oogaki@kddi.com>, Rajavarma Bhyrraju <rajavarma.bhyrraju@ericsson.com>, Cristina Badulescu <cristina.badulescu@ericsson.com>, Anatoly Andrianov <anatoly.andrianov@nokia.com>, Kleber Ulrich <Ulrich.Kleber@huawei.com> | |||
|This new enhancement proposes to add the capability of feasibility check of Network Service to the lifecycle management during the timeframe of Release 4. | |||
This is required to support the requirements specified in step-3 of clause 5.1.21 in 3GPP TS28.531 (Management and provisioning of 5G network slicing), to check the feasibility of Network slice subnet by sending enquiry requests to MANO to determine availability of network constituents. | This 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. | ||
Line 4,237: | Line 5,753: | ||
This work suggests to enhance the Os-Ma-nfvo reference point to supporting the feasibility check of Network Service. | This work suggests to enhance the Os-Ma-nfvo reference point to supporting the feasibility check of Network Service. | ||
| | |'''Stage2:''' | ||
* NFVIFA(20)000187r2: New enhancement proposal (accepted, IFA#190) | * NFVIFA(20)000187r2: New enhancement proposal (accepted, IFA#190) | ||
* NFVIFA(20)000084a1r6: Discussion paper for option with extending existing operations (Noted, IFA#196) | * NFVIFA(20)000084a1r6: Discussion paper for option with extending existing operations (Noted, IFA#196) | ||
Line 4,248: | Line 5,764: | ||
* NFVIFA(20)000662r2: IFA013ed421 MegaCR ENH02.02 NS feasibility check (Accepted - IFA#217) | * NFVIFA(20)000662r2: IFA013ed421 MegaCR ENH02.02 NS feasibility check (Accepted - IFA#217) | ||
* NFVIFA(20)000397r2: New requirements to IFA010 (Accepted - IFA#213) | * NFVIFA(20)000397r2: New requirements to IFA010 (Accepted - IFA#213) | ||
'''Stage3:''' | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000549r1_SOL005ed431_ENH02_02_Update_of_data_types.docx NFVSOL(21)000549r1] (Approved in SOL#197) | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000551r1_SOL005ed431_ENH02_02_Update_of_POST_in_instantiate_and_updat.docx NFVSOL(21)000551r1] (Approved in SOL#197) | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000550r2_SOL005ed431_ENH02_02_Definition_of_data_types.docx NFVSOL(21)000550r2] (Approved in SOL#197) | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(21)000548r4_SOL005ed431_ENH02_02_Flow_of_NS_LCM_operations_with_feasibil.zip NFVSOL(21)000548r4] (Approved in SOL#201) | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000106r5_SOL005ed431_ENH02_02_Flow_to_modify_NS_LCM_info_operation.zip NFVSOL(22)000106r5] (Approved in SOL#200) | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000553r7_SOL005ed431_ENH02_02_PATH_method_definition_to_modify_an_ind.docx NFVSOL(21)000553r7] (Approved in SOL#208) | |||
* SOL016 ongoing | |||
* | * | ||
|- | |- | ||
Line 4,254: | Line 5,780: | ||
|Release 4 | |Release 4 | ||
|Stage 2 complete | |Stage 2 complete | ||
Stage 3 | |||
complete without SOL14 | |||
|Chen Shaofan <chenshaofan@chinamobile.com>, | |Chen Shaofan <chenshaofan@chinamobile.com>, | ||
Line 4,262: | Line 5,792: | ||
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. | ||
| | |'''Stage2''': | ||
* NFVIFA(20)000401:Supporting_Material_for_NFV_MANO_New_Enhancement_Proposal_Data_Flow_Mirroring(Noted in IFA-197) | * NFVIFA(20)000401:Supporting_Material_for_NFV_MANO_New_Enhancement_Proposal_Data_Flow_Mirroring(Noted in IFA-197) | ||
* NFVIFA(20)000402r3: New enhancement proposal (accepted in IFA-202) | * NFVIFA(20)000402r3: New enhancement proposal (accepted in IFA-202) | ||
Line 4,289: | Line 5,819: | ||
*NFVIFA(21)000853r6_ENH02.03_IFA013_release_4_MegaCR | *NFVIFA(21)000853r6_ENH02.03_IFA013_release_4_MegaCR | ||
*NFVIFA(21)000854r1_ENH02.03_IFA014_release_4_MegaCR | *NFVIFA(21)000854r1_ENH02.03_IFA014_release_4_MegaCR | ||
'''Stage3:''' | |||
* SOL001 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000008r1_SOL001ed431_enh02_03_adding_policy_for_dataFlowMirroring.docx NFVSOL(22)000008r1] (approved at SOL#193) | |||
* SOL001 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000011r3_SOL001ed431_enh02_03_example_for_dataFlowMirroring.docx NFVSOL(22)000011r3] (approved at SOL#194) | |||
* SOL006 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000307r1_SOL006ed431_Implementation_of_ENH02_03_from_IFA014_release_4.docx NFVSOL(22)000307r1] (approved at SOL#211) | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000012r3_SOL005ed431_adding_dataFlowMirroringData_in_InstantiateNsReq.docx NFVSOL(22)000012r3] (approved at SOL#196) | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000013r2_SOL005ed431_adding_DataFlowMirroringJob_in_UpdateNsRequest.docx NFVSOL(22)000013r2] (approved at SOL#196) | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000014r2_SOL005ed431_adding_dataFlowMirroringJobInfo_in_NsInstance.docx NFVSOL(22)000014r2] (approved at SOL#196) | |||
* SOL014 ongoing | |||
|- | |- | ||
Line 4,295: | Line 5,834: | ||
|Release 4 | |Release 4 | ||
|Stage 2 completed | |Stage 2 completed | ||
Stage 3 completed | |||
|Arturo Martin de Nicolas <arturo.martin-de-nicolas@ericsson.com > | |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. | |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. | The enhancement will avoid having to change and create a new NSD when its components (VNFDs, PNFDs or nested NSDs) are replaced by another version and this replacement does not require changes in the rest of the NSD. | ||
| | |'''Stage2:''' | ||
* NFVIFA(20)000709r2: New enhancement proposal (accepted) | * NFVIFA(20)000709r2: New enhancement proposal (accepted) | ||
* NFVIFA(20)000710: New enhancement proposal - supporting material | * NFVIFA(20)000710: New enhancement proposal - supporting material | ||
Line 4,310: | Line 5,851: | ||
===== ============= Mega CRs for approval======== ===== | ===== ============= Mega CRs for approval======== ===== | ||
* '''NFVIFA(21)000190r1: ENH02.04 MegaCR Index (Noted at IFA#229)''' | * '''NFVIFA(21)000190r1: ENH02.04 MegaCR Index (Noted at IFA#229)''' | ||
* NFVIFA(20)000835r2: Enh02.04-IFA010ed421 | * NFVIFA(20)000835r2: Enh02.04-IFA010ed421 (approved at NFVIFA#229) | ||
* NFVIFA(21)000179: Enh02.04-IFA011ed421 MegaCR ( | * NFVIFA(21)000179: Enh02.04-IFA011ed421 MegaCR (approved at NFVIFA#229) | ||
* NFVIFA(21)000180: Enh02.04-IFA014ed421 MegaCR ( | * NFVIFA(21)000180: Enh02.04-IFA014ed421 MegaCR (approved at NFVIFA#229) | ||
* NFVIFA(20)000838r3: Enh02.04-IFA013ed421 | * NFVIFA(20)000838r3: Enh02.04-IFA013ed421 (approved at NFVIFA#229) | ||
'''Stage3:''' | |||
* SOL001 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000017r1_ENH02_04_SOL001ed431_Add_ExtInvariantId_to_VNF__NS_and_PNF.docx NFVSOL(22)000017r1] (approved at SOL#194) | |||
* SOL003 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000699r2_ENH02_04_SOL003ed431_Add_vnfdExtInvariantId_in_VnfPkgInfo.docx NFVSOL(21)000699r2] (approved at SOL#192) | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000590r1_ENH02_04_SOL005ed431_Add_DescriptorId_to_LCM_operations.docx NFVSOL(21)000590r1] (approved at SOL#187) | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000698r2_ENH02_04_SOL005ed431_Add_ExtInvariantId_to_PkgInfo_structure.docx NFVSOL(21)000698r2] (approved at SOL#192) | |||
* SOL006 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000304_SOL006ed431_Implementation_of_ENH02_04__from_IFA014_.docx NFVSOL(22)000304] (approved at SOL#209) | |||
|- | |- | ||
|ENH02.05 | |ENH02.05 | ||
|Flexibility with scalable VNF/NS instantiation | |Flexibility with scalable VNF/NS instantiation | ||
|Release 4 | |Release 4 | ||
|Stage 2 complete | |Stage 2 completed | ||
Stage 3 complete | |||
|Rajavarma Bhyrraju <rajavarma.bhyrraju@ericsson.com> | |Rajavarma Bhyrraju <rajavarma.bhyrraju@ericsson.com> | ||
|The enhancement feature proposes to add scaleLevels as input during instantiation to support flexibility with scalable VNF/NS instantiation. The VNFs/NSs supporting flexible instantiations are identified with VNFD/NSD level attribute(s). This enhancement provides flexibility for the service providers to adjust instantiation level when instantiating a VNF and supports instantiate a VNF with required size in one single operation. | |The enhancement feature proposes to add scaleLevels as input during instantiation to support flexibility with scalable VNF/NS instantiation. The VNFs/NSs supporting flexible instantiations are identified with VNFD/NSD level attribute(s). This enhancement provides flexibility for the service providers to adjust instantiation level when instantiating a VNF and supports instantiate a VNF with required size in one single operation. | ||
| | |'''Stage2:''' | ||
* NFVIFA(20)000820r2: New enhancement proposal (accepted - IFA#219-e) | * NFVIFA(20)000820r2: New enhancement proposal (accepted - IFA#219-e) | ||
* NFVIFA(20)000630r2: Discussion paper for flexible VNF/NS instantiations (Noted - IFA#216) | * NFVIFA(20)000630r2: Discussion paper for flexible VNF/NS instantiations (Noted - IFA#216) | ||
Line 4,332: | Line 5,882: | ||
===== ============= Mega CRs for approval======== ===== | ===== ============= Mega CRs for approval======== ===== | ||
* '''NFVIFA(21)000138: ENH02.05 MegaCR Index (Approved- IFA#227)''' | * '''NFVIFA(21)000138: ENH02.05 MegaCR Index (Approved- IFA#227)''' | ||
* NFVIFA(20)000841r1: ENH02.05 IFA011ed421 | * NFVIFA(20)000841r1: ENH02.05 IFA011ed421 (Approved- IFA#227) | ||
* NFVIFA(20)000842r3: ENH02.05 IFA014ed421 | * NFVIFA(20)000842r3: ENH02.05 IFA014ed421 (Approved- IFA#227) | ||
* NFVIFA(20)000843r3: ENH02.05 IFA007ed421 | * NFVIFA(20)000843r3: ENH02.05 IFA007ed421 (Approved- IFA#227) | ||
* NFVIFA(20)000844r3: ENH02.05 IFA008ed421 | * NFVIFA(20)000844r3: ENH02.05 IFA008ed421 (Approved- IFA#227) | ||
* NFVIFA(20)000845r3: ENH02.05 IFA013ed421 | * NFVIFA(20)000845r3: ENH02.05 IFA013ed421 (Approved- IFA#227) | ||
'''Stage3:''' | |||
* SOL001 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000289r2_ENH02_05_SOL001ed431_implementation.docx NFVSOL(22)000289r2] (approved at SOL#208) | |||
* SOL001 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000456_SOL001ed441_ENH02_05_NsScaleInfo_in_NsProfile.docx NFVSOL(22)000456] (approved at SOL#222) | |||
* SOL003 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000366_SOL003ed421_ENH02_05_Add_targetScaleLevelInfo_to_complement_.docx NFVSOL(21)000366] (approved at SOL#174) | |||
* SOL003 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000249_SOL003ed431_ENH02_05_Update_the_description_of_instantiation.docx NFVSOL(22)000249] (approved at SOL#207) | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2021//NFVSOL(21)000588_SOL005ed431_ENH02_05_Introduction_of_nsScaleInfo_complementi.docx NFVSOL(21)000588] (approved at SOL#187) | |||
* SOL005 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000453_SOL005ed441_ENH02_05_Add_targetScaleLevelInfo_to_ParamsForVn.docx NFVSOL(22)000453] (approved at SOL#223) | |||
* SOL006 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000306_SOL006ed431_Implementation_of_Enh02_05_from_IFA014ed421.docx NFVSOL(22)000306] (approved at SOL#210) | |||
* SOL006 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000323_SOL006ed431_Implementation_of_Enh02_05_from_IFA011ed421.docx NFVSOL(22)000323] (approved at SOL#210) | |||
* SOL016 [https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2022//NFVSOL(22)000379r1_SOL016ed441_ENH02_05_Add_targetScaleLevelInfo_to_complement_.docx NFVSOL(22)000379r1] (approved at SOL#218) | |||
|- | |- | ||
|ENH02.06 | |ENH02.06 | ||
Line 4,343: | Line 5,904: | ||
| | | | ||
|Arturo Martin de Nicolas <arturo.martin-de-nicolas@ericsson.com> | |Arturo Martin de Nicolas <arturo.martin-de-nicolas@ericsson.com> | ||
|The enhancement adds support for artifacts in the VNF package tha perform the mapping between NFV parameters obtained from the API and input parameters to the cloud native templates (e.g. Helm charts) | |The enhancement adds support for artifacts in the VNF package tha perform the mapping between NFV parameters obtained from the API and input parameters to the cloud native templates (e.g. Helm charts). | ||
| | | | ||
|} | |} |
Revision as of 15:26, 12 June 2023
Introduction
Current mirror date: 2023.06.12 | 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 | Stage 1 | Stage 2 | Stage 3 (note 6) |
---|---|---|---|
FEAT01: NFV-MANO Upgrades | completed (Rel 4) | not started | not started |
FEAT02: VNF software modification | completed (Rel 3) | completed (Rel 3) | completed (Rel 3) |
FEAT03: NFVI software modification | completed (Rel 3) | completed (Rel 3) | completed (Rel 3) |
FEAT04: Host Reservation | n/a | completed (Rel 3) | completed (Rel 3)
See note 1. |
FEAT05 Network Slicing | completed (Rel 3) | completed (Rel 3) | completed (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) | completed (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). | completed (Rel 3). |
FEAT13: Licensing | completed (Rel 4) | completed (Rel 4) | completed (Rel 4) |
FEAT15: VNF Snapshotting | completed (Rel 3) | completed (Rel 3) | completed (Rel 3).
|
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) | ongoing (Rel 4) |
FEAT18: Security | completed (Rel 3) | completed: architecture (Rel 3), interfaces (Rel 4).
|
not started |
FEAT19a: NFV-Connect - container networking | completed (Rel 4) | completed (Rel 4) | completed (Rel 4) |
FEAT19b: NFV-Connect - connectivity integration and operationalization | ongoing (Rel 5) | not started | not started |
FEAT20: Auto | completed (Rel 4) | ongoing (Rel 4) | not started |
FEAT21: 5GNFV | completed (Rel 4) | ongoing (Rel 4) | ongoing (Rel 4) |
FEAT22: M-Tenant | ongoing (Rel 5) | not started | not started |
FEAT23: MANO-SBA | ongoing (Rel 5) | not started | not started |
FEAT24: VNF-OAM | completed (Rel 4) | ongoing (Rel 4) | not started |
FEAT25: VNF-CI | ongoing (Rel 4) | not started | not started |
FEAT26: Policy-models | completed (Rel 4) | completed (Rel 4) | ongoing (Rel 4) |
FEAT27: NFV for vRAN | ongoing (Rel 5) | not started | not started |
FEAT28: Fault management models | ongoing (Rel 5) | ongoing (Rel 5) | not started |
FEAT29: Green NFV | ongoing (Rel 5) | not started | not started |
FEAT30: VNF configuration | ongoing (Rel 5) | not started | not started |
FEAT31: Flexible VNF deployment | ongoing (Rel 5) | not started | not started |
FEAT32: Reliability for cloud-native VNF | ongoing (Rel 5) | not started | not started |
FEAT19a (Rel. 5 extensions): Enhanced container networking | ongoing (Rel 5) | not started | not started |
FEAT24 (Rel. 5 extensions): VNF generic management functions | ongoing (Rel 5) | not started | not started |
ENH01: Security enhancements See note 5. |
ongoing (Rel 4) | ongoing (Rel 4) | not started |
ENH02: Special technical enhancements (Rel 4) See note 4. |
completed (Rel 4) | completed (Rel 4) | completed (Rel 4) |
ENH02: Special technical enhancements (Rel 5) See note 4. |
none applied yet (Rel 5) | not started | 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. Informative profiling of "protocol and data models" for the interfaces exposed by WIM is completed. Normative profiling of "protocol and data models" is ongoing. NOTE 3: void. NOTE 4: Concrete enhancement features and their status is available here. NOTE 5: Concrete security enhancement features and their status is available here NOTE 6: Detailed changes for SOL API are described in ETSI GS NFV-SOL 002 Annex E, ETSI GS NFV-SOL 003 Annex F and ETSI GS NFV-SOL 005. |
- Overview of each feature: Release Document
- Snapshot of Release 4 ed441/ed451 plan: NFVSOL(22)000520r1 and NFVIFA(22)000944r1
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.
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 | Stage2:
IFA007, IFA008, IFA011, IFA013, IFA010 Stage3: SOL001, SOL002, SOL003 |
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 | Stage 2: Completed
Stage 3: 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 | 2021-12-17 |
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(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 | Stage 2: IFA005, IFA006, IFA007, IFA008, IFA010, IFA011
Stage 3: SOL001, SOL002, SOL003, SOL005, SOL006, SOL014 |
MegaCRs | Stage 2:
IFA005: NFVIFA(19)000455 Baseline (Approved in IFA#159) IFA007: N/A (was IFA010: NFVIFA(19)000038r7 Baseline (Approved in IFA#159) Stage 3: |
Related/Dependent Features | N/A |
Status | Stage 2: Approved (IFA#159). MegaCR Index available in NFVIFA(19)000603r1
Stage 3: Completed |
Contributions | Stage 2:
All feature contributions Stage 3: SOL001 NfviMaintenanceInfo NFVSOL(21)000475 SOL006 NfviMaintenanceInfo issues#12(NFVSOL(20)000043) and issues#49(NFVSOL(21)000697) SOL002 VNF FM Alarm NFVSOL(21)000576r5 and NFVSOL(21)000678 SOL014 VR FM Notification NFVSOL(21)000453 and NFVSOL(21)000462 |
Feature team | Stage 2:
Maria Toeroe (Ericsson) Stage 3: |
Last Updated | 2021-12-10 |
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)000631r4 Status: Agreed
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 | Completed |
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 | Withdrawn |
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 | Withdrawn |
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 | Withdrawn |
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 | Withdrawn |
006 | Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vi reference point. CR Drafts:
|
IFA005 | June 2019 | Withdrawn |
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)0001054r4 Status: Agreed NFVIFA(19)000033 Status: Agreed
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 | Completed |
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(19)000102r8 Status: Agreed FEAT (IFA#144)
NFVIFA(19)000371r9 Status: Agreed FEAT (IFA#152) |
IFA008 | June 2019 | Completed |
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(19)000069 Status: Agreed FEAT (IFA#141)
NFVIFA(19)000515 Status: Candidate for Agreed FEAT in IFA#155 |
IFA007 | June 2019 | Completed |
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 | Completed |
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 | Specification of NfviMaintenanceInfo
- NFVSOL(21)000475. Status: approved |
SOL001 | November-2021 | Completed |
002 | Specification of NfviMaintenanceInfo
- issues#12(NFVSOL(20)000043). Status: approved - issues#49(NFVSOL(21)000697). Status: approved |
SOL006 | November-2021 | Completed |
003 | Extension FM interface
- NFVSOL(21)000576r5 and NFVSOL(21)000678. Status approved |
SOL002 | November-2021 | Completed |
004 | Specification of changeStatusNotification
- NFVSOL(21)000453 and NFVSOL(21)000462. Status approved |
SOL014 | November-2021 | Completed |
Issues
- Policy content is expected to fulfil FEAT03 usecase in Rel4.
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 | Stage2: Completed. MegaCR Index available in NFVIFA(18)000475r1
Stage3: Completed. See Issues. |
Contributions | Stage2:
All feature contributions Stage 3: SOL003 Grant operation: NFVSOL(19)000223 SOL005 NFVI capacity: NFVSOL(19)000359r2, NFVSOL(19)000358r3, NFVSOL(19)000373r1, NFVSOL(19)000372r1 and NFVSOL(20)000276r1 SOL014 Compute Resource Reservation: NFVSOL(22)000165 |
Feature team | Arturo Martin De Nicolas (Ericsson LM) Bertrand Souville (DOCOMO Communications Lab.) Joan Triay (DOCOMO Communications Lab.) |
Last Updated | 2023-01-01 |
Implementation Plan
NOTE: below contributions are marked as "OBSOLETE" as all content has been migrated to the MegaCRs (see above) and FEAT04 has been approved at IFA#101.
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Specify a requirement for the VIM to support the capability of handling reservation of resources at the host level. Specify a requirement for the NFVO to support requesting the reservation of resources at the host level. CR drafts: NFVIFA(17)0001086 (VIM) Status: Obsolete NFVIFA(18)000146 (NFVO) Status: Obsolete |
IFA010 | January-2018 | Completed |
002 | Specify requirements for an interface specialized on NFVI management on the Or-Vi to support the reservation of resources at the host level. CR draft NFVIFA(18)000053 Status: Obsolete |
IFA005 | January-2018 | Completed |
003 | Specify an interface and its operations to support the reservation of resources at the host level. CR draft NFVIFA(18)000145r2 Status: Obsolete |
IFA005 | February-2018 | Completed |
004 | Extend Annex A.2 to introduce physical compute host reservation. CR draft NFVIFA(18)000205 Status: Obsolete |
IFA010 | March-2018 | Completed |
005 | Extend clause 6.3.2 Grant VNF Lifecycle Operation operation. CR draft NFVIFA(18)000206r2 Status: Obsolete |
IFA007 | March-2018 | Completed |
006 | Enhancements of capacity management due to new functionality of host reservation: - Specify a requirement for the VIM to support NFVI capacity management. - Specify a requirement for the NFVO to support NFVI capacity management. CR drafts: NFVIFA(18)000207r2 (NFVO) Status: Obsolete NFVIFA(18)000208r1 (VIM) Status: Obsolete |
IFA010 | March-2018 | Completed |
007 | Specify an interface (IFA005, clause 7.X) and its operations to support Compute Hosts Capacity Management. CR draft NFVIFA(18)000364 Status: Obsolete |
IFA005 | March-2018 | Completed |
008 | A new interface and its operations may be needed in IFA013 for notifications from the NFVO related to resource capacity shortage. CR drafts: NFVIFA(18)000365r1 Status: Obsolete NFVIFA(18)000418 Status: Obsolete |
IFA013 | March-2018 | Completed |
Issues
Support host reservation when SOL014 supports reservation.-> resolved NFVSOL(22)000165- Capacity mgmt of SOL014 is missing as NFVSOL(22)000521r1
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 |
Related/Dependent Features | After analysis and LS exchange with 3GPP no dependencies for the time frame of this feature are seen anymore. |
Status | Stage2: Completed
Stage3: 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 | Stage2:
Latest status on Feature Dashboard Stage3: SOL001 NFVSOL(21)000159 and NFVSOL(19)000799r2 SOL005 NFVSOL(21)000109r8, NFVSOL(21)000110r3, NFVSOL(21)000111r4 and NFVSOL(21)000283r1 SOL006 NFVSOL(19)000854(Issue#11) and NFVSOL(21)000112(Issue#32) |
Feature team |
Anatoly Andrianov, Nokia |
Last Updated | 2023-01-01 |
Summary of decisions / agreed concepts
- Based on 3GPP's answer below, FEAT05 assumes that current NS LCM can be used by slicing to build slices and slice subnets.
- Based on 3GPP's answer below, FEAT05 can concentrate on analysing the use of NS priority only.
- 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.
- Based on 3GPP's answer below, FEAT05 closes the work on slice specific policies and multi-domain issues.
It is expected that Slice management functions can build the slices by using (instantiating) NS instances. NFV MANO is not aware of the network slices. Thus slice consumers / tenants are not known by MANO. Only the NS tenant is seen.
Depending on the use cases (contributed to an Annex for IFA010), it will be decided whether NS priorities need to be propagated to VNFM or VIM.
Overview Liaison Exchange
Specific Liaisons with 3GPP SA5 on Network Slicing
- LS to 3GPP SA5 on NFV support for Network Slicing: NFV(18)000065r2
- LS reply from 3GPP SA5 on NFV support for Network Slicing: NFV(18)000088
Summary of the answers:
- The definition of slice specific policies is not within the scope of ongoing Rel-15 work items
- Assurance data and Performance Management work item may have potential impacts on ETSI GS IFA027, but no detailed information
- 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).
- 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).
- According to the answer, 3GPP is not planning to share NS instance between two slices if isolation is needed.
- 3GPP expects that slicing management will use Os-Ma-nfvo and Ve-Vnfm-em reference points only.
A second set of questions has been sent to 3GPP SA5:
- LS to 3GPP SA5 on usage of NS priority in NFV MANO in support for Network Slicing: NFV(18)000264
- LS from 3GPP SA5 as first answer: NFV(18)000276
- LS Reply to SA5 with clarifications on questions: NFV(18)000288r1
- Preparation material for requested joint call: NFVIFA(18)000964_Prep_material_for_joint_session_3GPP_SA5.pptx
- LS Reply from 3GPP SA5 containing a set of answers: NFV(18)000299_Reply_LS_from_3GPP_SA5_on_clarifications_topics_for_NFV_NS_i.zip
- Main statements, see some questions in report from FEAT05 drafting call NFVIFA(18)000995_Report_of_FEAT05_Drafting_19_November_20.docx
Reply by SA5: NFV(18)000299_Reply_LS_from_3GPP_SA5_on_clarifications_topics_for_NFV_NS_i Main issues that could be clarified:
- Priorities are meant for LCM operations and resolution of resource conflicts in case of shortage
- MANO can act autonomously using the priority values
- If priority values are the same, MANO should act “first come first served”
- There should be a top priority, i.e. one that cannot be pre-empted.
- SA5 prefers the priority as attribute in NSD-DF.
Open questions collected:
- 2.1.1: “3GPP will expect to receive a notification” might be understood that the consumer will receive the notification.
- 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.
- What should MANO use instead if it shouldn’t use the priority?
- 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.
- 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.
- 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?
- Should MANO use priority during autohealing and “kill” a low priority NS instance to be able to heal a high priority NS instance in a resource shortage situation?
Other Liaisons with SA5
LS received in cc, but containing valuable inputs:
- Reply LS from 3GPP SA5 on draft Recommendation Y.3103: NFV(18)000277
- LS from SA5 to GSMA informing about documents: NFV(18)000282, referenced documents are 3GPP Rel-15 TS 28.530, 3GPP Rel-15 TS 28.531, 3GPP Rel-15 TS 28.541
Liaisons with other SDOs
Reply LS from ITU-T SG13 on consent of Recommendation Y.3103 (addressing network slicing) see NFV(18)000302_Reply_LS_from_ITU-T_SG13_on_consent_of_Recommendation_Y3103
Implementation Plan
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Add Functional requirements to support NFVSLICE in IFA010
|
IFA010 | Jan-2019 | Completed |
002 | Identify and add new parameters for NSD to allow support of the network slice and network slice subnet.
|
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
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:
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
|
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
|
IFA024 | Feb-2019 | Completed |
CRs abandoned
- NFVIFA(18)000876r1_FEAT05_IFA010_priority_support_in_software_image_distributio noted in IFA
- NFVIFA(18)000104r6_FEAT05_IFA010_priority-based_NS_resource_Mngmnt_by_NFVO replaced by 732
- NFVIFA(18)000102r2_FEAT05_IFA010_priority-based_NS_resource_Mngmnt_by_VIM not needed according to SA5 LS
- NFVIFA(18)000103r2_FEAT05_IFA010_priority-based_NS_resource_Mngmnt_by_VNFM not needed according to SA5 LS
- NFVIFA(18)000101r2_FEAT05-IFA010-Arch_Level_Req_to_Support_Additional_NS_Featur Noted in IFA#129
- NFVIFA(18)000108r2_FEAT05_IFA010_policy__priority__and_isolation_based_Multiple Noted in IFA#129
- NFVIFA(18)000109_FEAT05_IFA010_policy__priority__and_isolation_based_Multiple Noted in IFA#129
- NFVIFA(18)000110_FEAT05_IFA010_policy__priority__and_isolation_based_Multiple Noted in IFA#129
- NFVIFA(18)000866r3_FEAT05_IFA010__priority_support_in_NFP_management Noted in IFA#129
- NFVIFA(18)000877r1_FEAT05_IFA010_priority_support_in_NS_performance_management Noted in IFA#129
Other Contributions
- Presentation for Webinar "Network Slicing and ETSI NFV": NFV(17)000328
- Analyse NGMN Requirements on Slicing: NFVIFA(18)000017r1
- LS from 3GPP SA5 on transport network support of network slicing management: NFV(18)000026
- LS reply to 3GPP SA5 on transport network support of network slicing management: NFV(18)000057
- LS to 3GPP SA5 on NFV support for Network Slicing: NFV(18)000065r2
- LS reply from 3GPP SA5 on NFV support for Network Slicing: NFV(18)000088
- Presentation: "Towards NFV definition for Network Slicing" NFVIFA(18)000115r1
- Presentation at the Network Slicing World Summit held in Berlin, Germany on 23rd October 2018 NFV(18)000283
- Proposals to resolve editors notes NFVIFA(18)0001138_FEAT05_IFA010_Resolving_Editors_Notes.pptx
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 |
001b | Add priority to NS node type. NFVSOL(21)000159 | SOL001 | March-2021 | Completed |
002 | Add priority to NSD.NFVSOL(19)000854 | SOL006 | December-2019 | Completed |
002b | Add priority to NSD. NFVSOL(21)000112 | SOL006 | March-2021 | Completed |
003 | Introduce new NsLcmCapacityShortageNotification type. NFVSOL(21)000110r2 | SOL005 | April-2021 | Ongoing |
004 | Add priority in NS data type. NFVSOL(21)000111r4 | SOL005 | March-2021 | Completed |
005 | Add flow of NS LCM operation with pre-emption. NFVSOL(21)000109r2 | SOL005 | April-2021 | Ongoing |
006 | Warnings in LcmOpOcc. NFVSOL(21)000092 | SOL005 | March-2021 | Completed |
007 | NS LCM coordination interface - data model. NFVSOL(21)000104r4 | SOL005 | March-2021 | Completed |
008 | NS LCM coord interface – changes in other GS parts. NFVSOL(21)000106r3 | SOL005 | March-2021 | Completed |
009 | Mirror of 135 lcmcoord API addressing ENs. NFVSOL(21)000161 | SOL005 | March-2021 | Completed |
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 | Release 2
|
Impacted WIs | Stage2
IFA010, IFA012 (TBC), IFA013, and IFA014. Stage3 SOL005, SOL007 |
Mega-CRs | N/A |
Related/Dependent Features | |
New Specification | Stage2:
No new WI is expected in IFA WG. |
Status | Stage3: completed |
Contributions | Stage2:
All feature contributions Stage3: SOL005 NFVSOL(19)000567r5 new specfication SOL007 |
Feature team | Bhumip Khasnabish (ZTE) Haibin Chu (Ericsson) Yaoye Zhang (Huawei) Maopeng Zhang (ZTE) Lingli Deng (CMCC) |
Last Updated | 2023-01-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 | Stage2:
IFA010, IFA013, IFA007, IFA008, IFA005, IFA006 SOL012 |
Mega-CRs |
IFA013 MegaCR in NFVIFA(18)000429r1 (Approved) |
Related/Dependent Features | no dependency |
Status | Stage2: Completed. MegaCR Index available in NFVIFA(18)000492r1 Stage3: Completed. new specification SOL012 |
Contributions | All feature contributions Agreed content |
Feature team | Haitao Xia (Huawei) |
Last Updated | 2023-01-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 | Add functional requirements of policy management for the NFVO, VNFM and VIM IFA010 CRs (Status: Feature Agreed) |
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) |
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) |
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 | Stage2:
IFA010, IFA030 (new deliverable) Stage3: new specification SOL011 |
Mega-CRs | IFA010 MegaCR in NFVIFA(18)000425r1 (Approved) |
Related/Dependent Features | no dependency |
Status | Stage2: Completed. MegaCR Index available in NFVIFA(18)000515r2. New deliverable IFA030GS Approved Stage3: Completed. New specfication SOL011 |
Contributions | All feature contributions Agreed content |
Feature team | Haitao Xia (Huawei) Arturo Martin de Nicolas (Ericsson) Bhumip Khasnabish (ZTE) |
Last Updated | 2023-01-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: |
IFA030 | Jan-2018 | Completed |
002 | Add NFVO functional requirement description derived from Table 6.3-2 of IFA028 to IFA010 IFA010 CRs (Status: Obsolete) |
IFA010 | May-2018 | Completed |
003 | Add interface requirement description of Or-Or reference point derived from Table 6.3-1 of IFA028 Approved contributions: |
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: |
IFA030 | Apr-2018 | Completed |
005 | Define Or-Or interface functions of NS lifecycle granting and NS instance usage notification Approved contributions: |
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: |
IFA030 | Mar-2018 | Completed |
007 | New GS (IFA030) clean-up, EN resolution
Approved Contributions: |
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) |
Feature description | Following the recommendations written in IFA022, this feature is to specify management requirements, interfaces and information models to support connectivity for Multi-Site Services |
Target Release | Stage 2:
Release 3 drop 2 (2018-12) Release 3 (without SOL014 and SOL019) Release 4 |
Impacted WIs | Stage 2: IFA005, IFA007, IFA010, IFA011, IFA013, IFA014, IFA022, IFA032 Stage 3: SOL014, SOL003, SOL005, SOL001, SOL006, SOL017, SOL019 |
Mega-CRs | Stage 2: - IFA005 MegaCR in NFVIFA(18)0001111r2 - IFA007 MegaCR in NFVIFA(18)0001112r4 - IFA010 MegaCR in NFVIFA(18)0001107r2 - IFA013 MegaCR in NFVIFA(18)0001110r4 - IFA014 MegaCR in NFVIFA(18)0001113r2 |
Related/Dependent Features | N/A |
New Specification | Stage 2: IFA032 Stage 3: SOL017, SOL019 |
Status | Stage 2: Completed,
MegaCR Index available in NFVIFA(18)0001117r3 complated release 3(SOL001, SOL003, SOL005, SOL006, SOL009, SOL017) ongoing release 4 (SOL014, SOL019) |
Contributions | Stage2:
All feature contributions Stage3: SOL001 NFVSOL(19)000792r1 SOL003 NFVSOL(19)000732 and NFVSOL(21)000363 SOL005 NFVSOL(19)000734, NFVSOL(20)000080, NFVSOL(20)000081, NFVSOL(20)000082r2, NFVSOL(20)000235r1, NFVSOL(20)000252 and NFVSOL(19)000817 SOL006 NFVSOL(20)000115 SOL009 NFVSOL(21)000153 SOL014 (ongoing) new report SOL017 (completed) new specifcation SOL019 (ongoing) |
Feature team | Stage 2: - Hiroshi Dempo (NEC Europe Ltd.) - Zarrar Yousaf (NEC Europe Ltd.) - Lei Zhu (Huawei Tech (UK) Co., Ltd. - Ulrich Kleber (Huawei Tech (UK) Co., Ltd. - Marc Flauw (HPE) - Joan Triay (DOCOMO) Stage 3: - Zarrar Yousaf (NEC Europe Ltd.) - Joan Triay (DOCOMO) |
Last Updated | 2022-10-21 |
Stage 2 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | - Approve FEAT10 and new WI draft titled “Reference point between NFVO and WIM- Interface and Information Model Specification" | None | Oct-2017 | Done |
002 |
- Approve IFA022 as a stable draft
|
IFA022 | Dec-2017 | Done |
003 |
- Specify general and functional recommendations for Multi-Site Service
|
IFA010 | Jan/ 2018 | Completed |
004 |
- Specify Os-Ma-Nfvo reference point interface and information model specification for Multi-Site Service
|
IFA013 | Mar-2018 | Completed |
005 |
- Specify Or-Vi reference point interfaces and information model specification between NFVO and VIM for Multi-Site Service
|
IFA005 | Mar-2018 | Completed |
006 |
- Specify enhancements to Or-Vnfm ref. point interfaces and information model to address the case of VNF multi-site deployment. - Make relevant changes to the scope and overview sections to include the support for Multi-site Service on Or-Vnfm reference point
|
IFA007 | Mar-2018 | Completed |
007 | - Specify parameters for the VNFD file relevant for the support of Multi-Site Service
" No CRs received" |
IFA011 | May-2018 | Closed |
008 | - Specify parameters for the NSD file relevant for the support of Multi-Site Service
|
IFA014 | May-2018 | Completed |
009 |
- Specify Or-Vi reference point interfaces and information model specification between NFVO and WIM for Multi-Site Service
NOTE: As written in ID#2, naming of the ref. point is FFS. Purpose of the specification is to focus on virtualised network resource management subset of existing IFA005, and necessary extensions/enhancements particular to managing resources in the WAN |
IFA032 | May-2018 | Completed |
Issues
List of issues raised based on the feature implementation.
- All topics can start from the beginning but the progress needs to be managed on the action IDs (e.g. individual mega CRs and new deliverable basis)
- The target dates are set according to the requirement categories in IFA022 (CRs for general, functional, reference point and information element, descriptor, or new deliverable)
- Discussion for IFA032 may take more time than CRs but finalise before the 1st drop of Release 3.
Security Considerations
List of security considerations implied by the feature.
Stage 3 Implementation Plan
ID | Action | Impacted WI(s) | Target completion | Status |
---|---|---|---|---|
001 | Specification of multi-site connectivity support in SOL003: - Add specification for Multi-Site Connectivity Services: NFVSOL(19)000732. Status: approved - Bug fix: NFVSOL(21)000363. Status: approved at SOL#174 |
SOL003 | Dec. 2019 | Completed |
002 | Specification of multi-site connectivity support in SOL005: - Add specification for Multi-Site Connectivity Services: NFVSOL(19)000734, NFVSOL(20)000080, NFVSOL(20)000081. Status: approved at SOL#128 - Add Annex of multi-site connectivity: NFVSOL(20)000082r2, - Resolve EN: NFVSOL(20)000235r1, NFVSOL(20)000252, NFVSOL(19)000817 Status: approved |
SOL005 | Dec. 2019 | Completed |
003 | Specification of multi-site connectivity support in SOL descriptors: - SOL001ed331 FEAT10 Add specification for Multi-Site Connectivity Services: NFVSOL(19)000792r1. Status: approved at SOL#121 - SOL006ed331 FEAT10 Add specification for Multi-Site Connectivity Services: NFVSOL(20)000115. Status: approved at SOL#128 |
SOL001, SOL006 | Dec. 2019 | Completed |
004 | Specification of multi-site connectivity support in SOL014: - TBD |
SOL014 | TBD | Not started |
005 | Report and profiling of stage 3 solutions addressing IFA032 requirements. General structure of the report: - SOL017 skeleton: NFVSOL(19)000360r1. Status: approved at SOL#102. - SOL017 scope: NFVSOL(19)000361r1. Status: approved at SOL#102. - IFA032 Overview Clause 4.2: NFVSOL(19)000548r1. Status: approved at SOL#111 EA. - IFA032 Overview for Capacity, Performance and Fault Management interfaces for Clause 4.2: NFVSOL(19)000592. Status: approved at SOL#115. |
SOL017 | Dec. 2019 | Completed |
006 | Profiling of IETF ACTN stage 3 solutions addressing IFA032 requirements: - IETF ACTN Overview: NFVSOL(19)000506r3. Status: approved at SOL#115. - Clause 4.3.2.3 Mapping concepts with ACTN: NFVSOL(19)000573. Status: approved at SOL#115. - IETF ACTN profiling: NFVSOL(20)000501r5, NFVSOL(20)000464r7, NFVSOL(20)000535r6, NFVSOL(20)000629r1, NFVSOL(20)000632r1, NFVSOL(20)000634r1, NFVSOL(20)000633r2, NFVSOL(20)000654r1, NFVSOL(20)000656r1, NFVSOL(20)000666r2, NFVSOL(20)000657r1, NFVSOL(20)000658r2 Status: approved - IETF ACTN Analysis: - IETF ACTN Architecture: - IETF ACTN Annex: NFVSOL(20)000655, NFVSOL(21)000024 - IETF ACTN Recommendation: NFVSOL(20)000771r1 - Resolve EN and others: NFVSOL(20)000668, NFVSOL(20)000669, NFVSOL(21)000023, NFVSOL(21)000016r1, NFVSOL(21)000017r1 |
SOL017 | Feb. 2020 | Completed |
007 | Profiling of TAPI stage 3 solutions addressing IFA032 requirements: - TAPI Overview: NFVSOL(19)000605r2. Status: approved at SOL#115. - TAPI Analysis: NFVSOL(20)000321r3, NFVSOL(20)000325r1, NFVSOL(20)000572, NFVSOL(20)000672r1, NFVSOL(20)000683, NFVSOL(20)000677, NFVSOL(20)000589r1 |
SOL017 | Feb. 2020 | Completed |
008 | Stage3 of Profiling specification of solutions for Multi-site Connectivity Services based on Abstraction and Control of TE Networks (ACTN)
- Skeleton: NFVSOL(21)000651r3 Status: approved - next steps: NFVSOL(22)000369 Noted |
SOL019 | Ongoing | |
009 | Specification of WIM support in SOL009:
- NFVSOL(21)000153: Approved |
SOL009 | Completed |
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 | Stage2: ETSI GS NFV-IFA 031 ("NFV; Management and Orchestration; Requirements and interfaces for NFV-MANO management Specification") Work Item: DGS/NFV-IFA031 Stage3: ETSI GS NFV-SOL 009 ("Network Functions Virtualisation (NFV) Release 3; Protocols and Data Models; RESTful protocols specification for the management of NFV-MANO") |
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: Release 3 |
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: Completed |
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 | 2021-12-10 |
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 - Data types for CreateVnfSnapshotData: NFVSOL(20)000130r1. Status approved |
SOL005 | Dec. 2019 | Completed |
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 - Moving VNF snapshot pkg mgmt interface: NFVSOL(20)000273r1. Satus: approved |
SOL003 | Dec. 2019 | Completed |
005 | Specification of the VNFC snapshot package management interface in SOL002: - Withdrawn VNF snapshot package management interface from SOL002: NFVSOL(20)000287. Status approved |
SOL002 | Dec. 2019 | Completed |
006 | Specification of the VNF snapshot package management interface in SOL005: - Flows, resource, methods and data types for VNF snapshot pkg mgmt: NFVSOL(20)000234r2. Status: approved |
SOL005 | Dec. 2019 | Completed |
007 | Specification of the VNF snapshot related operations in the VNFD and NSD of SOL001: - Operation Configuration: NFVSOL(20)000320r6. Status: approved |
SOL001 | Dec. 2019 | Completed |
008 | Specification of the VNF snapshot related operations in the VNFD and NSD of SOL006: - Operation Configuration: NFVSOL(19)000830r1. Status: approved |
SOL006 | Dec. 2019 | Completed |
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)000056r4. Status: approved - Security aspects of VNF snapshot package: -- NFVSOL(21)000231r1 . Status: approved -- NFVSOL(21)000244r2 . Status: approved -- NFVSOL(21)000245 . Status: approved -- NFVSOL(21)000348r1. Status: approved |
SOL010 | Dec. 2019 | Completed |
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:
|
Target Release | Release 3 (2019) |
Impacted WIs | Stage2:
IFA013, IFA008, IFA011 Stag3: 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 | Completed (100% complete) |
Contributions | All feature contributions
Stage3: SOL002 NFVSOL(20)000128 SOL004 NFVSOL(17)000585r3 SOL005 NFVSOL(20)000053r1 Others: MEC API development platform: NFVSOL(17)000402 TOSCA model of AppD in MEC and: SOL NFVSOL(22)000078 NFV Registries of Non MANO artifact sets (no registry for MEC yet) |
Feature team | Uwe Rauschenbach, Nokia
Yang Xu, Huawei Pekka Kuure, Nokia Anatoly Andrianov, Nokia |
Last Updated | 2022-12-05 |
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 | June 2020 | Complete |
002 | Add needed MEC extensions to SOL005 (placement control). | SOL005 | June 2020 | Complete |
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 |
006 | Add needed MEC extensions to SOL002 (to allow standardizing graceful termination). | SOL002 | June 2021 | Complete |
Issues
MEC has confirmed in December 2022 that all open issues are closed, see NFV(22)000259.
MEC may or may not provide additional requirements in the future. These would need to go into a new feature.
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 | Stage2: IFA011
Stage3: SOL004 |
MegaCRs | N/A (only 1 CR for IFA011) |
Related/Dependent Features | NA |
Status | Stage2: completed
Stage3: completed |
Contributions | Stage2
IFA011 NFVIFA(22)000534r3 Stage3 SOL004 NFVSOL(22)000359r4 |
Feature team | Abinash Vishwakarma (Netcracker)
Janusz, Pieczerak, Orange Etienne, Steinert, Orange Oliver, Le Grand, Orange Anne-Marie Praden, Gemalto Martin, Liepert, Gemalto |
Last update | 2023-01-01 |
FEAT16: Service Availability Level
Overview
Feature Prime | Stefan Arntzen (Huawei) |
Feature description | This feature adds the functions needed to assign resources with defined reliability characteristics to NSs with special reliability requirements. It also allows to achieve an optimized assignment of resources with defined availability characteristics to multiple VNFs and NSs (belonging to the same slice) |
Target Release | Stage 2: Release 3 drop 3 (2019-06)
Stage 3: Release 3 (2019-12) |
Impacted WIs | Stage 2: IFA010, IFA014
Stage 3: SOL001, SOL006 |
MegaCRs | Stage 2:
IFA010: NFVIFA(19)000480r8 Approved by email on July 15
|
Related/Dependent Features | N/A |
Status | Stage 2: Approved in IFA#160; MegaCR Index available in NFVIFA(19)000746
Stage 3: Completed |
Contributions | Stage2
All feature contributions Stage3 SOL001 NFVSOL(20)000067r1 SOL006 NFVSOL(20)000026r2 |
Feature team | Shaoji Ni (Huawei) Maria Toeroe(Ericsson) Gerald Kunzmann (DOCOMO) Stefan Arntzen (Huawei) Janusz Pieczerak (Orange) Chidung Lac (Orange) |
Last Updated | 2023-01-01 |
Stage 2 Implementation Plan
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Add terminology of the “service availability level (SAL)” and explain difference between FEAT05 Slicing
NFVIFA(19)000402r3 Status: Agreed FEAT (IFA#159) |
IFA010 | June-2019 | Completed |
002 | Specify requirements for the VIM to support the capability for supporting SAL for the assignment/reservation of resources. Specify requirements for the NFVO/VNFM to support SAL for requesting the assignment/reservation of resources.
NFVIFA(19)000296r1 Status: Noted (IFA#145) NFVIFA(19)000306r5 Status: Agreed FEAT (IFA#150) NFVIFA(19)000307r7 Status: Agreed FEAT (IFA#149) NFVIFA(19)000309r2 Status: Agreed FEAT (IFA#148) NFVIFA(19)000310r5 Status: Agreed FEAT (IFA#148) NFVIFA(19)000311r2 Status: Agreed FEAT (IFA#148) NFVIFA(19)000482r1 Status: Agreed FEAT (IFA#154)
NFVIFA(19)000502r9 Status: Agreed FEAT (IFA#156) NFVIFA(19)000590r4 Status: Agreed FEAT (IFA#157) |
IFA010 | June-2019 | Completed |
003 | Specify requirements for an NFVI resource management on the Or-Vi/Vi-Vnfm to support SAL for the assignment/reservation of resources. | IFA005/006 | December-2018 | Stopped. Not part of release 3 |
004 | Add the parameter of SAL into “VnfDF”, “vdu profile”, “VirtualLinkDescFlavour” of VNFD
|
IFA011 | December-2018 | Stopped |
005 | Add a requirement and the parameter of SAL into “Network service deployment flavour” of NSD
NFVIFA(19)000355r4 Status: Agreed FEAT (IFA#152) NFVIFA(19)000397r2 Status: Agreed FEAT (IFA#152) NFVIFA(19)000547r5 Status: Agreed FEAT (IFA#155) |
IFA014 | June-2019 | Completed |
006 | Specify operations of the assignment/reservation of resources in Or-Vi/Vi-Vnfm/Or-Vnfm/Ve-Vnfm interfaces to support SAL by adding the parameter of “SAL” into the Virtual resource assignment/reservation requests
NFVIFA(19)000399r3 Status: Agreed FEAT (IFA#152) NFVIFA(19)000408r2 Status: Agreed FEAT (IFA#152) NFVIFA(19)000417r6 Status: Agreed FEAT (IFA#152) NFVIFA(19)000419r4 Status: Agreed FEAT (IFA#152) NFVIFA(19)000472 Status: Agreed FEAT (IFA#155) NFVIFA(19)000474 Status: Agreed FEAT (IFA#155) NFVIFA(19)000467r1 Status: Agreed FEAT (IFA#154) NFVIFA(19)000466r4 Status: Agreed FEAT (IFA#155) NFVIFA(19)000473r2 Status: Agreed FEAT (IFA#155) |
IFA005/006/007/008 | February-2019 | Stopped. Not part of release 3 |
Stage 3 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
SOL
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Add SAL(service_availability_level) in to NSD.
- NFVSOL(20)000067r1: Approved |
SOL001 | March-2018 | Completed |
002 | Add SAL(service_availability_level) in to NSD.
- NFVSOL(20)000026r2: Approved |
SOL006 | Completed |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature are described in: NFVSEC(19)000085r1 Status: agreed in SEC#151
FEAT17: Cloud-Native VNFs and Container Infrastructure management
Overview
Feature Prime | Jörg Aelken (Ericsson LM) Ulrich Kleber (Huawei Technologies Co.,Ltd) |
Feature description | The scope of the feature covers the following areas: - NFV Architecture support for VNFs which follow “cloud-native” design principles. |
Target Release | Stage 2
Stage 3
|
Impacted WIs | Stage 2: IFA007, IFA008, IFA010, IFA011, IFA013, IFA014, IFA036, IFA040, IFA052 Stage 3: SOL001, SOL002, SOL003, SOL006, SOL018, SOL020 |
MegaCRs | Stage 2
Stage 3
|
Related/Dependent Features | FEAT19 – NFV-Conn FEAT23 – MANO-SBA |
New Specification | Stage 2
Stage 3
|
Status |
Stage 2
Stage 3
|
Contributions | Stage 2:
All stage 2 feature contributions Stage 3: Step 1 introduce CISM/CIR and OsContainer SOL018 contributions, SOL001ed421 and SOL001ed431, SOL002ed431, SOL003ed431, SOL005ed431, SOL006ed431, SOL009ed431 SOL020 |
Feature team | Stage 2: Ulrich Kleber (Huawei Technologies Co.,Ltd) Jörg Aelken (Ericsson LM) Stage 3: Jörg Aelken (Ericsson LM) |
Last Updated | 2023-01-24 |
Stage 2 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
Stage 2 - Step 1 (ed411)
ID | Action | Impacted WI(s) | Target completion | Status |
---|---|---|---|---|
ST2-001 | Skeleton, scope, and term definitions for IFA040 (Clauses 1, 2, 3)
CR drafts: |
IFA040 | October - 2019 | Complete |
ST2-002 | Overview and framework for OS container management and orchestration (Clause 4)
CR drafts: |
IFA040 | November - 2019 | Complete |
ST2-003 | Skeleton and scope for IFA036 (Clause 1)
CR drafts: |
IFA036 | October - 2019 | Complete |
ST2-004 | Enhance the VNFD and its VDU information element with attributes/information elements for the OS container resource model
CR drafts: |
IFA011ed411 | February - 2020 | Complete |
ST2-005 | OS container NFV object model (Clause 5)
CR drafts: |
IFA040 | November - 2019 | Complete |
ST2-007 | Specify the functional requirements for the CISM function
CR drafts: |
IFA010ed411 | January - 2020 | Complete |
ST2-008 | Specify the functional requirements for the CIR function
CR drafts: |
IFA010ed411 | February - 2020 | Complete |
ST2-009 | General CISM service requirements (Clauses 6.1, 6.2)
CR drafts: |
IFA040 | January - 2020 | Complete |
ST2-010 | OS container management service interface requirements (Clauses 6.3, 6.4, 6.5, 6.6, 6.7)
CR drafts: |
IFA040 | January - 2020 | Complete |
ST2-011 | General CIR service requirements (Clauses 7.1, 7.2)
CR drafts: |
IFA040 | December - 2019 | Complete |
ST2-012 | OS container image management service interface requirements (Clause 7.3)
CR drafts: |
IFA040 | January - 2020 | Complete |
ST2-013 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CISM function
CR drafts: |
IFA010ed411 | March - 2020 | Complete |
ST2-014 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CIR function
CR drafts: |
IFA010ed411 | March - 2020 | Complete |
ST2-015 | Extend the VNFM functional requirements for consuming the management service interfaces exposed by the CISM function
CR drafts: |
IFA010ed411 | March - 2020 | Complete |
Stage 2 - Step 2 (ed421)
ID | Action | Impacted WI(s) | Target completion | Status |
---|---|---|---|---|
ST2-016 | Enhance the information models of the Or-Vnfm interfaces for OS container management and orchestration
CR drafts: |
IFA007ed421 | March - 2021 | Complete |
ST2-017 | Enhance the information models of the Ve-Vnfm interfaces for OS container management and orchestration
CR drafts: |
IFA008ed421 | March - 2021 | Complete |
ST2-018 | Extend the NFVO, VNFM, CISM functional requirements according to additional enhancements identified for FEAT17
CR drafts: |
IFA010ed421 | March - 2021 | Complete |
ST2-019 | Extend the VNFD information model according to additional enhancements identified for FEAT17
CR drafts: |
IFA011ed421 | March - 2021 | Complete |
ST2-020 | Enhance the information models of the Os-Ma-nfvo interfaces for OS container management and orchestration
CR drafts: |
IFA013ed421 | March - 2021 | Complete |
ST2-021 | Enhance the information models of the NSD for OS container management and orchestration
CR drafts: |
IFA014ed421 | March - 2021 | Complete |
ST2-022 | Extend the abstract NFV object model description and CISM/CIR service interface requirements according to additional enhancements identified for FEAT17
CR drafts: |
IFA040ed421 | March - 2021 | Complete |
Stage 2 - Step 3 (ed431)
ID | Action | Impacted WI(s) | Target completion | Status |
---|---|---|---|---|
ST2-006 | Terminology and overview of management and orchestration of CIS cluster nodes (Clauses 3 and 4, Annex)
Concept discussions: CR drafts: |
IFA036 | June - 2022 | Completed |
ST2-023 | Container cluster nodes management interface requirements (Clause 5)
CR drafts: |
IFA036 | June - 2022 | Completed |
ST2-024 | CIS Cluster NFV object model (Clause 6)
CR drafts: |
IFA036 | June - 2022 | Completed |
ST2-025 | CIS Cluster Node NFV object model (Clause 7)
CR drafts: |
IFA036 | June - 2022 | Completed |
ST2-026 | Analyse and if necessary enhance VNFD and its VDU information element with attributes/information elements related to cluster and node affinity No enhancements required from CCM |
IFA011ed431 | March - 2022 | Completed |
ST2-027 | Analyse and if necessary enhance NSD and constituent information elements with attributes/information elements related to cluster and node affinity No enhancements required from CCM |
IFA014ed431 | March - 2022 | Completed |
ST2-028 | Specify the functional requirements for the CCM function
CR drafts: |
IFA010ed431 | March - 2022 | Completed |
ST2-029 | Add requirements on CIS cluster node management for the CISM function
CR drafts: |
IFA010ed431 | March - 2022 | Completed |
ST2-030 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CCM function CR drafts: |
IFA010ed431 | March - 2022 | Moved to step 4 |
ST2-031 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CISM function related to CIS Cluster Node management CR drafts: |
IFA010ed431 | March - 2022 | Moved to step 4 |
ST2-032 | Analyse and if necessary enhance the information models of the Os-Ma-nfvo interfaces for CIS Cluster management and CIS Cluster Node management CR drafts: |
IFA013ed431 | March - 2022 | Moved to step 4 |
ST2-033 | Additional interface enhancements in step 3
CR drafts: NFVIFA(22)000127 (Agreed FEAT, IFA007) NFVIFA(22)000153 (Agreed FEAT, IFA007) NFVIFA(22)000155 (Agreed FEAT, IFA008) |
IFA007ed431, IFA008ed431, IFA011ed431, IFA013ed431 |
March - 2022 | Completed |
ST2-034 | Workgroup review
CR drafts: |
IFA036 | July - 2022 | Completed |
Stage 2 - Step 4 (ed441)
ID | Action | Impacted WI(s) | Target completion | Status |
---|---|---|---|---|
ST2-030 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CCM function CR drafts: |
IFA010ed441 | March - 2023 | Not started
(move to step 5) |
ST2-031 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CISM function related to CIS Cluster Node management CR drafts: |
IFA010ed441 | March - 2023 | Not started
(move to step 5) |
ST2-032 | Analyse and if necessary enhance the information models of the Os-Ma-nfvo interfaces for CIS Cluster management and CIS Cluster Node management CR drafts: |
IFA013ed441 | March - 2023 | Not started
(move to step 5) |
ST2-035 | Provide additional workflows and examples
CR drafts: NFVIFA(22)000854r1 (Approved) NFVIFA(22)000949r3 (Approved) NFVIFA(22)000976r1 (Approved) NFVIFA(23)000002r1 (Approved) |
IFA036ed441 | March - 2023 | Completed |
ST2-036 | Provide more details for some concepts in CCM, e.g. shared storage, clusters with multiple NFVI-Pops, clusters and
multiple domains, cluster-related measurements, etc. CR drafts: |
IFA036ed441,
IFA030ed441, IFA032ed441, IFA027ed441 |
Not started
(move to step 5) | |
ST2-037 | Reliability considerations for CCM | IFA036ed441 | Not started
(move to step 5) | |
ST2-038 | Security considerations for CCM | IFA036ed441 | Not started
(move to step 5) | |
ST2-039 | Describe management of CCM
CR drafts: NFVIFA(23)000011 (IFA010, Approved) NFVIFA(23)000012 (IFA031, Approved) NFVIFA(23)000013 (IFA031, Approved) |
IFA010ed441
IFA031ed441 |
March - 2023 | Completed |
ST2-040 | Additional enhancements in step 4
CR drafts: |
IFA011ed441 | March - 2023 | Completed |
Stage 2 - Step 5 (ed451)
ID | Action | Impacted WI(s) | Target completion | Status |
---|---|---|---|---|
ST2-030 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CCM function CR drafts: |
IFA010 | Not started | |
ST2-031 | Extend the NFVO functional requirements for consuming the management service interfaces exposed by the CISM function related to CIS Cluster Node management CR drafts: |
IFA010 | Not started | |
ST2-032 | Analyse and if necessary enhance the information models of the Os-Ma-nfvo interfaces for CIS Cluster management and CIS Cluster Node management CR drafts: |
IFA013 | Not started | |
ST2-036 | Provide more details for some concepts in CCM, e.g. shared storage, clusters with multiple NFVI-Pops, clusters and
multiple domains, cluster-related measurements, etc. CR drafts: |
IFA036,
IFA030, IFA032, IFA027 |
Not started | |
ST2-037 | Reliability considerations for CCM | IFA036 | Not started | |
ST2-038 | Security considerations for CCM | IFA036 | Not started | |
ST2-041 | CCM southbound interface | IFA052 | Ongoing |
Stage 3 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
SOL Stage3 Step1
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
ST3-001 | introduce OsContainer
- NFVSOL(21)000011r8 - NFVSOL(21)000018r6 - NFVSOL(21)000020r2 - NFVSOL(21)000223 - NFVSOL(21)000246r1 - NFVSOL(21)000374 - NFVSOL(21)000252r3 - NFVSOL(21)000436r2 - NFVSOL(21)000481r1 - NFVSOL(21)000097r9 - NFVSOL(21)000440r2 - NFVSOL(21)000622r1 introduce MCIOP - NFVSOL(21)000064r5 - NFVSOL(21)000246r1 - NFVSOL(21)000480 - NFVSOL(21)000487 - NFVSOL(21)000491r1 - NFVSOL(21)000617r1 - NFVSOL(21)000152r5 introduce MCIO - NFVSOL(21)000451r1 - NFVSOL(22)000096r1 - NFVSOL(22)000112r1 enhance container network - NFVSOL(21)000019r4 - NFVSOL(21)000021r4 - NFVSOL(21)000238r2 |
SOL001 | January-2022 | Completed |
ST3-002 | extends Grant and introduce CISM/CIR | SOL003 | July-2022 | Completed |
ST3-003 | introduces MCIO
enhance CP for container network |
SOL003 | July-2022 | Completed |
ST3-004 | introduces MCIO
- NFVSOL(22)000089 (684r1 mirror) - NFVSOL(22)000120r1 (053r4 mirror) enhance CP for container network - NFVSOL(22)000177 (482 mirror) - NFVSOL(22)000052 (040 mirror) - NFVSOL(22)000107 (092 mirror) - NFVSOL(22)000171r1 (139r2 mirror) - NFVSOL(22)000501r1 (500r1 mirror) |
SOL002 | July-2022 | Completed |
ST3-005 | introduce CISM/CIR
- NFVSOL(22)000037r1 (367r2 mirror) introduces MCIO - NFVSOL(22)000073 (684r1 mirror) - NFVSOL(22)000121r1 (053r4 mirror) enhance CP for container network - NFVSOL(22)000154r4 (482 mirror) - NFVSOL(22)000122 (040 and 092 mirror) - NFVSOL(22)000172 (139r2 mirror) - NFVSOL(22)000514r1 (500r1 mirror) |
SOL005 | July-2022 | Completed |
ST3-006 | DP: prestudy of stage3
DP: CISM API object map |
SOL018 | July-2022 | Completed |
ST3-007 | introduce CISM | SOL009 | July-2022 | Completed |
ST3-008 | introduce OsContainer
introduce MCIOP introduce MCIO |
SOL006 | Completed | |
ST3-009 | SOL016 | January-2023 | ongoing |
Issues
Feature implementation approach
This feature implementation plan proposes to implement the feature according to its scope from the latest NFV Release-4 “Strawman of Release 4 definition”.
Due to the complexity of the feature and its implementation, the feature will be implemented in a stepwise approach. The feature steps are bundling dependent solutions in different work items/specifications. The solutions for one feature step impacting existing specifications will be delivered by Mega-CR’s. There will be one Mega-CR per impacted specification per feature step and all Mega-CR’s for one feature step will be delivered together with dependent new specifications.
The current plan bundles the following solutions together:
- Stage 2 - Step 1: IFA040 and related Rel-4 Mega-CRs on existing specifications
- Stage 2 - Step 2: IFA036 and related Rel-4 Mega-CRs on existing specifications
Background Information
This feature was originally planned as ETSI NFV Release-3 delivery.
According to its definition, the ETSI NFV Release 3 includes objectives:
- To specify requirements and enhancements to NFV Architectural Framework to support PaaS features.
- To specify non-functional parameters to classify and characterize VNF cloud-native implementations.
They are reflected in the following two features and corresponding work items:
Feature ID | Title | Work Item |
---|---|---|
R03.F19 | NFV Architecture PaaS (NFVPAAS) | IFA029 |
R03.F20 | Cloud-Native VNF (VNFCLOUD) | EVE011 |
During the work on the two work items it was discovered that both features are very much related and the envisioned solutions and implementations might overlap and will target the same impacted work items.
During discussions in IFA#73 it was further identified that EVE011, even though it is normative, should be considered as stage 1 requirements on cloud-native on a high abstraction level without taking the actual implementation into consideration. It was further identified in this meeting that IFA029 as a GR looks at architectural aspects of both Cloud Native and PaaS.
Meanwhile, both work items, EVE011 and IFA029, have been concluded and approved by the ISG NFV plenary as NFV Release-3 deliveries. It was further decided by the ISG NFV plenary to carry over the normative specifications for stage 2 and 3 of this feature with a modified scope according to the “Strawman of Release 4 definition” into NFV Release-4.
Security Considerations
The work item DGS/NFV-SEC023 “Network Functions Virtualisation (NFV) Release 4; Security; Container Security Specification” was approved by the ISG NFV to investigate the security considerations for OS container technologies and provide a respective specification.
It is expected that applicable container security aspects will be handled by this work item.
FEAT18: Security
Overview
Feature Prime | Mark Shepherd (Tencastle) |
Feature description | To address security challenges arising in NFV, particularly in terms of isolation of sensitive functions and security management and monitoring |
Target Release | Release 3 drop X (2019-06-30) |
Impacted WIs | Stage 1: SEC009, SEC011, SEC012, SEC013
Stage 2: IFA026, IFA033, Future work items: consider whether SOL or TST items would be appropriate. |
MegaCRs | tbd |
Related/Dependent Features | Enh01.01 Certficate Management |
Status | Ongoing (25% complete) |
Contributions | All feature contributions Agreed content (direct links to search-URLs to be added later) |
Feature team | Alex Leadbeater (Rapporteur), BT
Leslie Willis (Rapporteur), BT Mark Shepherd, Tencastle |
Last Updated | 2023-01-01 |
Implementation Plan
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Complete requirements in IFA026 | IFA026 | November 2018 | Open |
002 | Map requirements from IFA026 into IFA033 and assign to each interface | IFA026
IFA033 |
November 2018 | Open |
003 | Complete all of IFA026 and identify all interfaces in IFA033 | IFA026
IFA033 |
December 2018 | Open |
004 | introduce ADMF
introduce NFV SC |
IFA010 | Not started | |
005 | new interface for NFV SC
new interface for LI controller and SM |
IFA033 | Not started | |
006 | Add ADMF and NFV SC
Add interface for NFV SC, LI controller and SM |
NFV006 | Not started | |
007 | IFA008 | Not started | ||
008 | IFA013 | Not started |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT19: NFV-Conn
Overview
Feature Prime | Manchang Ju (ZTE), ju.manchang@zte.com.cn
Hammad Zafar (NEC), Hammad.Zafar@neclab.eu |
Feature description | The scope of IFA038 (Release 4) covers the following areas:
a) investigating aspects of network connectivity for container-based VNF, b) determining the enhancement related to NFV descriptors and NFV-MANO functional aspects for the management of network connectivity of containerized VNFs, c) determining the enhancement related to NFV-MANO interfaces for the management of OS container multiple networks. The scope of IFA035 (Release 4) covers the following areas:
The scope of IFA043 (Release 5) covers the following areas:
|
Target Release | Stage 2 Step 1 : Release 4 drop 3 (2022-02)
Stage 2 Step 2 : Release 4 drop 5 (2023-07) Stage 3 Step 2: Release 4 ed431 (2022-07) |
Impacted WIs | Stage 2: IFA010, IFA007, IFA011, IFA013, IFA014
Stage 3: SOL001, SOL002, SOL003, SO005, SOL006 |
MegaCRs | Stage 2 Step 1 (drop3):
IFA010 MegaCR NFVIFA(22)000179 (Approved at IFA#276) IFA040 MegaCR NFVIFA(22)000180 (Approved at IFA#276) |
Related/Dependent Features | FEAT17 |
New Specifcations | Informative: ETSI GR NFV-IFA 038 , ETSI GR NFV-IFA 035 (ongoing), ETSI GR NFV-IFA 043 (ongoing)
Normative: not required |
Status | Stage 2 Step 1: Completed
Stage 2 Step 2: Ongoing Stage 3 Step 1: Completed |
Contributions | All feature contributions Agreed content |
Feature team | Stage 2: Manchang Ju (ZTE), Hammad Zafar (NEC), Baoguo Xie(ZTE)
Stage 3: Name (Company) |
Last Updated | 2023-01-01 |
Stage 1 Informative Work Plan
Informative work in ETSI GR NFV-IFA 035(October 2019 - June 2023)
IFA035
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Complete Clause 4 . CR draft [LINK] | IFA | March-2018 | Open |
IFA043
Informative work in ETSI GR NFV-IFA 043(July 2021 - July 2023)
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | First GR draft introducing the skeleton and the scope.
Accepted contributions: NFVIFA(21)000786r1, NFVIFA(21)000787r1 |
IFA | October-2021 | Done |
002 | Problem statement and introducion
Accepted contributions: NFVIFA(21)000961r2, NFVIFA(21)000962r2 |
IFA | December-2021 | Done |
003 | Use case for CCM preconfigures cluster network
Accepted contributions: NFVIFA(22)000159r4 |
IFA | April-2022 | Done |
004 | Network policy and use case for re-configuration of secondary container cluster network
Accepted contributions: NFVIFA(22)000897, NFVIFA(22)898r4 |
IFA | December-2022 | Done |
005 | Solutions for re-configuration of secondary container cluster networks and pre-configuration of secondary container cluster networks | IFA | June-2023 | ongoing |
006 | support of network policies, Potential architectural enhancements | IFA | June-2023 | Not started |
007 | Recommendations related to NFV descriptors and other artefacts if needed
Recommendations on architectural framework if needed Recommendations on functional aspects if needed |
IFA | July-2023 | Not started |
Stage 2 Implementation Plan
Informative work in ETSI GR NFV-IFA 038(October 2019 - November 2021)
IFA038
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Add interface X in to IFA007. CR draft [LINK] | IFA | March-2018 | Open |
Normative work plan (December 2021- February 2022)
ID | Action | Impacted WI(s) | Target completion | Status |
001 | Add general functional requirements for management of connectivity for multiple networks.
Add functional requirements for the NFVO, VNFM and CISM to support of the management of network connectivity of containerized VNFs. |
IFA010 | Dec-2021 | Completed |
002 | Add functional requirements for the VNFM, and interface and information model specification for the VNF LCM to support OS container multiple networks. | IFA007 | July-2023 | Not started |
003 | Add requirements and modelling for the VNFD and NSD to support describing the properties for one or more secondary container cluster internal/external networks.
Add requirements and modelling for the VNFD and NSD to support describing the information for associating the VLD with the declarative descriptors of secondary container cluster internal/external networks. Add resource requirements for the VNFD to support describing load balancers associated to network MCIOs. |
IFA011,
IFA014 |
July-2023 | Not started |
004 | Add functional requirements to the NFVO, and interface and information model specification to the VNF LM or NS LCM to support OS container multiple networks. | IFA013 | July-2023 | Not started |
005 | Add service interface requirements related to OS container multiple networks management to the CISM, to support the configuration and management of OS container multiple networks. | IFA040 | Jan-2022 | Completed |
NOTE : |
Stage 3 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
SOL
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | enhance CP for container network (FEAT17)
- SOL003 NFVSOL(21)000482r4 - SOL002 NFVSOL(22)000177 (482r4 mirror) |
SOL001, SOL002, SOL003, SOL005, SOL006 | July-2022 | Completed |
002 | introduce secondary container cluster network | SOL018 | July-2022 | Completed |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT20: Auto
Overview
Feature Prime | Haitao XIA (Huawei), xiahaitao@huawei.com |
Feature description | The scope of the feature covers the following areas:
- NFV-MANO support for managing autonomous networks. - Enabling higher level of automation for NFV-MANO. - Intent-based principles for external exposure network services management. |
Target Release | Stage 1: Release 4 informative work (2021-08-17) Published as ETSI GR NFV-IFA 041 v4.1.1.
Stage 2 Step 1: MDAF related specs (IFA047) target release v4.4.1, Stage 2 Step 2: Intent management related specs (IFA050) target release v4.5.1. Stage 3: Release 4 (202x-X-X) |
Impacted WIs | Stage 2: IFA010ed441 (for MDAF functional requirements), IFA010ed451 (for Intent Management functional requirements)
Stage 3: SOLzz |
MegaCRs | Stage 2:
IFA010 MegaCR NFVIFA(18)000xxx (CR Status, to be created) Stage 3: SOLzzz MegaCR NFVSOL(19)000zzz (CR Status) |
Related/Dependent Features | FEAT07 FEAT26 |
New Specifcations | Stage 2: IFA047 (MDAF service interfaces specification); IFA050 (Intent management service interface specification)
Stage 3: SOLaaa |
Status | Stage 1: Informative work completed (delivered in IFA041)
Stage 2 Step 1: Normative work is ongoing, targeted to be completed until 2023 Q2. Stage 2 Step 2: Stage 3: Not started |
Contributions | All feature contributions Agreed content |
Feature team | Stage 2: Haitao XIA (Huawei), Cristina BADULESCU (Ericsson), Joan TRIAY (Docomo),Rajavarma BHYRRAJU (Ericsson),
Jiachen ZHANG (China Mobile), Shen GAO (China Telecom), Shitao LI (Huawei) Stage 3: Name (Company) |
Last Updated | 2022-12-30 |
Stage 2 Implementation Plan
Informative work in ETSI GR NFV-IFA 041(October 2019 - May 2021)
IFA041
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | First GR (IFA041) draft introducing the skeleton and the scope.
Accepted contributions: NFVIFA(19)000859r2, NFVIFA(19)000860r1 |
IFA | October-2019 | Done |
002 | Overview of related work in NFV-MANO and other SDOs.
Accepted contributions: NFVIFA(19)000959, NFVIFA(19)000960r1, NFVIFA(19)000961r2, NFVIFA(19)000962r2, NFVIFA(19)000963r2, |
IFA | February-2020 | Done |
003 | Use cases related to NFV-MANO autonomous management, mainly include three categories:
- Intent based NS management - Management Data Analytics assisted management - Autonomous container infrastructure management Accepted contributions: NFVIFA(20)000017r1, NFVIFA(20)000021, NFVIFA(20)000051r2, NFVIFA(20)000134r1, NFVIFA(20)000230r1, NFVIFA(20)000245r1, NFVIFA(20)000246r1, NFVIFA(20)000247r2, NFVIFA(20)000248r1, NFVIFA(20)000279r1, NFVIFA(20)000280r1, NFVIFA(20)000319, NFVIFA(20)000281r3, NFVIFA(20)000472r2, NFVIFA(20)000591, NFVIFA(20)000592, NFVIFA(20)000622r1, NFVVIFA(20)000720r3, NFVIFA(20)000781r1, NFVIFA(20)000782r1 |
IFA | November-2020 | Done |
004 | Analysis of key issues related to use cases in Clause 6.
Accepted contributions: NFVIFA(20)000353r1, NFVIFA(20)000354r2, NFVIFA(20)000355r1, NFVIFA(20)000416r2, NFVIFA(20)000418r2, NFVIFA(20)000445r1, NFVIFA(20)000446r1, NFVIFA(20)000447r1, NFVIFA(20)000557, NFVIFA(20)000566r3, NFVIFA(20)000593, NFVIFA(20)000594r3, NFVIFA(20)000623r4, NFVIFA(20)000624r1, NFVIFA(20)000729r3, NFVIFA(20)000732r3, NFVIFA(21)000793r1, NFVIFA(20)000878r1, NFVIFA(20)000879r1, NFVIFA(21)000013 NFVIFA(21)000014r2, NFVIFA(21)000022r1, NFVIFA(21)000058r1 |
IFA | February-2021 | Done |
005 | Analysis of pontential architectural impacts on NFV-MANO in clause 7.
Accepted contributions: NFVIFA(20)000794r1, NFVIFA(20)000797r3, NFVIFA(21)000060, NFVIFA(21)000062r7, NFVIFA(21)000133r2, NFVIFA(21)000134r5, NFVIFA(21)000135r2, NFVIFA(21)000149r7 |
IFA | May-2021 | Done |
006 | Recommendations and conclusion in clause 8.
Accepted contributions: NFVIFA(21)000073, NFVIFA(21)000280r1, NFVIFA(21)000281r3, NFVIFA(21)000284r2, NFVIFA(21)000285r2, NFVIFA(21)000321r3, NFVIFA(21)000322r1, NFVIFA(21)000413 |
IFA | May-2021 | Done |
Normative work plan (October 2021- June 2022)
- Not urgent for ISG NFV to start the stage 2 normative work, need more close observation/analysis on 3GPP SA5 R17 related normative work (IDMS and MDAS) and FEAT23 output on MANO SBA.
- One or two new group specifications are expected to carry stage 2 normative work on intent management and MDA interfaces.
- MDA input information model improvement related normative work has been kicked off by FEAT28/IFA045 development.
IFA047/IFA050
(IFA047 development in March 2022 to January 2023, IFA050 development in July 2022 to June 2023)
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | IFA047 first draft including the skeleton and scope | IFA | March-2022 | Done |
002 | IFA047 interface requirements specification | IFA | May-2022 | Done |
003 | IFA047 interface operations specification | IFA | November-2022 | Done |
004 | IFA047 annex on use cases (stable draft) and IFA010ed441 megaCR | IFA | December-2022 | Done |
005 | IFA050 first draft including the skeleton and scope | IFA | July-2022 | Done |
006 | IFA050 use cases | IFA | January-2023 | Ongoing |
007 | IFA050 interface requirements specification | IFA | January-2023 | Planned |
008 | IFA050 interface operations specifications and IFA010ed451 megaCR | IFA | June-2023 | Planned |
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
N/A.
FEAT21: 5GNFV
Overview
Feature Prime | Joan Triay (DOCOMO) |
Feature description | The scope of the feature covers the following areas: a) investigating the NFV support for deploying 5G networks, capabilities and associated requirements. b) determine the 5G network capabilities and features interworking and their relationship with NFV, and c) determine and profile how NFV can support 5G deployments. |
Target Release | Stage 2: Release 4 (2023/07) Stage 3: TBD (Release 4 (2023/XX)) |
Impacted WIs | Stage 2: IFA010, IFA013, IFA014, IFA011, IFA007, IFA008, IFA049 Stage 3: TBD (SOLzz) |
MegaCRs | Stage 2: ed431: includes action 007 of stage 2 work, i.e. "Add enhancements related to NSD processing" - IFA010: NFVIFA(22)000186r1 IFA010ed431 FEAT21 MegaCR --> Approved at IFA#277 - IFA013: NFVIFA(22)000187r2 IFA013ed431 FEAT21 MegaCR --> Approved at IFA#277 - IFA014: NFVIFA(22)000188r1 IFA014ed431 FEAT21 MegaCR --> Approved at IFA#277 - MegaCR Index: NFVIFA(22)000248r2 FEAT21 stage 2 set #1 in ed431 MegaCR Index ed441: no updates ed451: - IFA010: NFVIFA(23)000010r3 IFA010ed451 FEAT21 MegaCR for PaaS Services aspects - IFA007: NFVIFA(23)000347r3 IFA007ed451 FEAT21 MegaCR for PaaS Services aspects - IFA008: NFVIFA(23)000419r1 IFA008ed451 FEAT21 MegaCR for PaaS Services aspects - IFA011: NFVIFA(23)000346r3 IFA011ed451 FEAT21 MegaCR for PaaS Services aspects - IFA013: NFVIFA(23)000418r2 IFA013ed451 FEAT21 MegaCR for PaaS Services aspects - IFA014: NFVIFA(23)000389r1 IFA014ed451 FEAT21 MegaCR for PaaS Services aspects |
Related/Dependent Features | FEAT17 on "Cloud-native VNF and container infrastructure management"
FEAT19 on "NFV connectivity" |
New Specifcations | Informative: DGR/NFV-IFA037 Stage 2: None (currently) Stage 3: TBD |
Status | Informative: completed Stage 2: ongoing (70%) Stage 3: ongoing (20%) |
Contributions | All feature contributions Agreed content |
Feature team | Informative: Joan Triay (DOCOMO) Stage 2: Joan Triay (DOCOMO) Stage 3: Name (Company) |
Last Updated | 2023-06-08 |
Informative work
IFA
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Skeleton and scope - NFVIFA(19)000900 IFA037 skeleton --> Approved - NFVIFA(19)000901 IFA037 Scope --> Approved |
IFA | Nov-2019 | Completed |
002 | Introduction and overview - NFVIFA(20)0001021 IFA037 Clause 4.1 Introduction to 5G network --> Approved - NFVIFA(20)0001022 IFA037 Clause 4.2 Characteristics of 5G network --> Approved - NFVIFA(20)000830 IFA037 Clause 5.1 Introduction to characteristics --> Approved |
IFA | Jan-2020 | Completed |
003 | Profiling and analysis of characteristic: Network function modularization - NFVIFA(20)000760r1 IFA037 Clause 5 Adding characteristic NF modularization --> Approved - NFVIFA(21)000573 FEAT21 IFA037 Clause 5.2 Gap analysis modularization --> Approved |
IFA | Dec-2020 | Completed |
004 | Characteristic: Service-based interfaces, communication and service mesh - NFVIFA(21)000100r1 FEAT21 IFA037 Clause 5 Adding characteristic SBI, communication and service mesh --> Approved - NFVIFA(21)000544 FEAT21 IFA037 Clause 5.3 Adding missing solutions on SBI, communication and mesh --> Approved - NFVIFA(21)000574 FEAT21 IFA037 Clause 5.3 Gap analysis SBI --> Approved |
IFA | Feb-2021 | Completed |
005 | Characteristic: Network slicing - NFVIFA(21)000099r3 FEAT21 IFA037 Clause 5 Adding characteristic network slicing --> Approved - NFVIFA(21)000545 FEAT21 IFA037 Clause 5.4 Completing solutions of network slicing --> Approved - NFVIFA(21)000575 FEAT21 IFA037 Clause 5.4 Gap analysis network slicing --> Approved |
IFA | Feb-2021 | Completed |
006 | Characteristic: Convergent (3GPP and non-3GPP) access - NFVIFA(21)000522r1 FEAT21 IFA037 Clause 5 Adding characteristic Convergent access --> Approved - NFVIFA(21)000594 FEAT21 IFA037 Clause 5.10 Gap analysis convergent access --> Approved |
IFA | Jun-2021 | Completed |
007 | Characteristic: Stateless NF, with separation of data processing from state - NFVIFA(21)000257 IFA037 Clause 5 Adding characteristic Stateless NF --> Approved - NFVIFA(21)000592r1 FEAT21 IFA037 Clause 5.7 Gap analysis stateless NF --> Approved |
IFA | Mar-2021 | Completed |
008 | Characteristic: Network capabilities exposure - NFVIFA(21)000502 FEAT21 IFA037 Clause 5 Adding characteristic Network capabilities exposure --> Approved - NFVIFA(21)000595r2 FEAT21 IFA037 Clause 5.8 Gap analysis Network capabilities exposure --> Approved - NFVIFA(21)000722r3 FEAT21 IFA037 Start cleaning up EN_nef_non3gpp --> Approved |
IFA | May-2021 | Completed |
009 | Characteristic: Distribution of services across the network (local and centralized) - NFVIFA(21)000293r1 FEAT21 IFA037 Clause 5 Adding characteristic distribution of services across the network --> Approved - NFVIFA(21)000576r1 FEAT21 IFA037 Clause 5.4 Gap analysis services distribution --> Approved |
IFA | Mar-2021 | Completed |
010 | Characteristic: Unified authentication framework - NFVIFA(21)000329r1 IFA037 Clause 5 Adding characteristic Unified authentication framework --> Approved - NFVIFA(21)000496r1 FEAT21 IFA037 5.6 Adding potential solutions for characteristic Unified authentication framework --> Approved |
IFA | May-2021 | Completed |
011 | Characteristic: Roaming capabilities - NFVIFA(21)000526 FEAT21 IFA037 Clause 5 Adding characteristic roaming --> Approved - NFVIFA(21)000593 FEAT21 IFA037 Clause 5.9 cleaning up editor notes --> Approved |
IFA | Jul-2021 | Completed |
012 | Derivation of recommendations and conclusion - NFVIFA(21)000639r1 FEAT21 IFA037 Clause 6.1 Adding recommendations overview --> Approved - NFVIFA(21)000659r2 FEAT21 IFA037 Clause 6 Adding recommendations related to all characteristics --> Approved - NFVIFA(21)000660 FEAT21 IFA037 Clause 7 Adding Conclusion --> Approved - NFVIFA(21)000660 FEAT21 IFA037 Clause 7 Adding Conclusion --> Approved - NFVIFA(21)000678r4 FEAT21 IFA037 Clause 6 Adding recommendations related to unified authentication --> Approved |
IFA | Jul-2021 | Completed |
013 | Address remaining major technical editor's notes - NFVIFA(21)000543 FEAT21 IFA037 Start cleaning up EN --> Approved - NFVIFA(21)000544 FEAT21 IFA037 Clause 5.3 Adding missing solutions on SBI, communication and mesh --> Approved - NFVIFA(21)000545 FEAT21 IFA037 Clause 5.4 Completing solutions of network slicing --> Approved - NFVIFA(21)000677r2 FEAT21 IFA037 Clause 5.6 addresses Editor’s Note about SEC005 and gap analysis of unified authentication framework --> Approved - NFVIFA(21)000698 FEAT21 IFA037 Clauses 5.4.2.2 and 6.5 addressing EN about L2 connectivity --> Approved - NFVIFA(21)000722r3 FEAT21 IFA037 Start cleaning up EN_nef_non3gpp --> Approved |
IFA | Jun/Jul-2021 | Completed |
014 | Final review - NFVIFA(21)000748r1 IFA037 Review clause 1,3,4 editorial clean-up --> Approved - NFVIFA(21)000749r1 IFA037 Review clause 5 editorial clean-up --> Approved - NFVIFA(21)000768r1 IFA037 Review clause 6 editorial clean-up --> Approved - NFVIFA(21)000777 IFA037 Review 6.3 refining recommendations 002 and 003 --> Noted - NFVIFA(21)000796r1 IFA037 review - editorial fixes and small technical wording improvements --> Approved - NFVIFA(21)000797 IFA037 review - comments and questions --> Noted - NFVIFA(21)000798r2 IFA037 review - miscellaneous technical improvements --> Approved - NFVIFA(21)000807 FEAT21 IFA037 Clause 5.1 Statement of 3GPP Release baseline and update of references --> Approved - NFVIFA(21)000809r1 FEAT21 IFA037 Clause 4 to 5.6.2.2 Minor miscellaneous changes --> Approved - NFVIFA(21)000820r1 FEAT21 IFA037 Clauses 5.7 to 5.10 Miscellaneous changes --> Approved - NFVIFA(21)000821r1 FEAT21 IFA037 Clauses 6 Miscellaneous changes to recommendations --> Approved - NFVIFA(21)000822 FEAT21 IFA037 Deleting unused clauses --> Approved - NFVIFA(21)000838 IFA037 review - removing misleading recommendations --> Noted - NFVIFA(21)000842r2 FEAT21 IFA037 Deleting unused clauses --> Approved - NFVIFA(21)000848r2 FEAT21_IFA037_Comments_missing_gap_associated_recommendations --> Approved - NFVIFA(21)000849 FEAT21 IFA037 Clause 5.6 Clarifying security aspects --> Approved - NFVIFA(21)000852 FEAT21 IFA037 Security comments in clause 5.6 --> Approved - NFVIFA(21)000872r1 FEAT21_IFA037_security_recommendations_gap 5.5 --> Agreed at IFA#256 |
IFA | Aug/Sep-2021 | Completed |
Stage 2 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
IFA
ID | Action | Impacted WI(s) | Target completion | Status |
---|---|---|---|---|
001 | Add functional requirements for the NFV architectural framework to include the support of inventory of VNF Common and Dedicated Services and platform/infrastructure capabilities (5gnfv.arch.001) Contributions: - NFVIFA(21)0001022r2 IFA010ed431 FEAT21 Adding PaaS Services management --> FEAT Agreed at IFA#266 - NFVIFA(22)000123 IFA010ed431 FEAT21 Adding PaaS Services management --> see action 005 Pending CRs: - None |
IFA010 | Jun-2023 | All CRs FEAT agreed |
002 | Add functional requirements for the NFV architectural framework to include the support of operator certificate management functions (5gnfv.arch.002), requirements on the operator certificate management functions to synchronize the LCM of the certificates with the LCM operations of the VNF/VNFC (5gnfv.func.008), and retrieval of VNF/VNFC runtime information from VNFM/NFVO (5gnfv.if.011). See note 2. | IFA010 | See ENH01.01 | See ENH01.01 |
003 | Add functional requirements to the VNFM, and interface and information model specification to the VNF LCM to support adding/removing VNF external CP that are not sub-ports of a trunk (5gnfv.func.001, 5gnfv.if.004). | IFA010, IFA007, IFA008 | Jun-2023 | Not started |
004 | Add requirements and modelling for the VNFD and NSD to support describing requirement to use VNF Common/Dedicated Services (5gnfv.desc.001). See note 3. Contributions: - NFVIFA(21)0001025 IFA011ed431 FEAT21 Adding requirements for PaaS Services --> FEAT Agreed at IFA#265 - NFVIFA(21)0001028r1 IFA014ed431 FEAT21 Adding requirements for PaaS Services --> FEAT Agreed at IFA#266 - NFVIFA(23)000276r1 FEAT21 IFA011 VNFD modeling to use PaaS Services: FEAT Agreed at IFA#332 - NFVIFA(23)000277r2 FEAT21 IFA014 NSD modeling to use PaaS Service: FEAT Agreed at IFA#335 - NFVIFA(23)000351 IFA011ed451 FEAT21 VNFD PaaS Servivce modeling refinements on top of 276r1: FEAT Agreed at IFA#335 Pending CRs: - None |
IFA011, IFA014 | Jun-2023 | All CRs FEAT agreed |
005 | Determining the mapping and requirements for the NFV architectural framework about the "PaaS service management function" (5gnfv.func.002). See note 3. Contributions: - NFVIFA(22)000123r5 IFA010ed431 FEAT21 Adding PaaS Services management --> FEAT Agreed at IFA#313 - Addressing editor's notes as shown in the interim MegaCR for IFA010 in contribution NFVIFA(23)000010 NFVIFA(23)000278r1 FEAT21 IFA010 Address EN about PSM framework: FEAT Agreed at IFA#332 Pending CRs: - None |
IFA010 | Jun-2023 | All CRs FEAT agreed |
006 | Add functional requirements to the VNFM and NFVO to support determining and triggering LCM for VNF Common/Dedicated Services (5gnfv.func.002, 5gnfv.func.003). See note 3. Contributions: - NFVIFA(22)000123r1 IFA010ed431 FEAT21 Adding PaaS Services management --> see action 005 - NFVIFA(23)000279 FEAT21 IFA007 Enhance granting to support PaaS Services requirements for a VNF: FEAT Agreed at IFA#332 - NFVIFA(23)000300 FEAT21 IFA007 Enhance VnfInfo to support PaaS Services information for a VNF: FEAT Agreed at IFA#332 - NFVIFA(23)000301 FEAT21 IFA013 Enhance NsInfo to support PaaS Services information for a VNF and NS: FEAT Agreed at IFA#332 - NFVIFA(23)000409 (Mirror of 300) FEAT21 IFA008 Enhance VnfInfo to support PaaS Services information for a VNF: Almost FEAT agreed at IFA#336 Pending CRs: - None |
IFA010, IFA007, IFA008, IFA013 | Jun-2023 | All CRs FEAT agreed |
007 | Add enhancements related to NSD processing: - requirements and modelling on the NSD management interface to allow onboarding of an NSD even if not all VNF packages, nested NSDs and PNFDs have been previously on-boarded (5gnfv.func.004a), - requirements and modelling on the NS LCM to handle the case of not all constituent elements being on-boarded (5gnfv.if.006), - functional requirement to the NFVO to support processing information related to version dependencies between constituent VNF (5gnfv.func.004b), - requirements for the NSD regarding whether NSD on-boarding can be performed even if not all referred VNF Packages, NSD and PNFDs are on-boarded (5gnfv.desc.007a), and - requirements for the NSD to support information related to constituent VNF version dependencies (5gnfv.desc.007b). Contributions: - NFVIFA(22)000086r1 FEAT21-IFA010ed431-Clause 6.3.1 NFVO support for version dependency information --> FEAT Agreed at IFA#273 - NFVIFA(22)000100r1 FEAT21 IFA014ed431 Adding version dependencies --> FEAT agreed at IFA#275 - NFVIFA(22)000101r1 FEAT21-IFA013ed431-Adding version dependencies to NS LCM operations --> FEAT agreed at IFA#275 - NFVIFA(22)000178 FEAT21 IFA013ed431 Exposure of version dependencies --> FEAT Agreed at IFA#276 - NFVIFA(22)000191r1 FEAT21-IFA014ed431-Clause 6.2.2 Add flag for strict NSD onboarding --> Agreed at IFA#276 - NFVIFA(22)000192r1 FEAT21-IFA010ed431-Clause 6.6.1 NFVO allow lenient NSD onboarding --> FEAT Agreed at IFA#276 - NFVIFA(22)000189r1 FEAT21 IFA013ed431 precondition about onboarded constituents --> FEAT Agreed at IFA#276 |
IFA013, IFA010, IFA011, IFA014 | Nov-2021 | Completed in IFAed431 |
008 | Add requirements to extend the capability support of NFVO and VNFM to handle the modification of security groups of a particular VNF instance based on LCM actions performed on the corresponding VNF instance (5gnfv.func.005, 5gnfv.if.007) and updates on the relevant descriptors to indicate the mapping of security groups to target CP (5gnfv.desc.008). | IFA010, IFA007, IFA014 | Jun-2023 | Not started |
009 | Add enhancements to the VL construct to support additional services such as name resolution, communication security, etc. (5gnfv.desc.002). Contributions: - CR for IFA014 to address 5gnfv.desc.002 NFIFA(23)000406r1 FEAT21 IFA014ed451 Enhancing VL with additional capabilities (action 009): FEAT Agreed at IFA#337 |
IFA014 | Jun-2023 | All CRs FEAT agreed |
010 | Add enhancements, requirements to address the capability to indicate, reuse and shared virtualised resources among VNF instances, including extensions to the granting LCM interface (5gnfv.desc.004, 5gnfv.desc.005, 5gnfv.if.005) and to the scaling of virtualised storage resources independently (5gnfv.desc.003). Contributions: - NFVIFA(23)000008r1 IFA007ed441 FEAT21 Granting for shared virtual resource --> Almost FEAT Agreed at IFA#316 |
IFA011, IFA014, IFA007 | Jun-2023 | Ongoing |
011 | Add requirements and modelling to the NS LCM interface to address various capabilities: - providing information about external L2 networks (5gnfv.if.001), - providing location constraints of constituents of a VNF to be deployed (5gnfv.if.002), - providing naming related information related to SAP or VNF external CP (5gnfv.if.003), and - relevant descriptor enhancements in the VNFD/NSD for additional network properties (5gnfv.desc.006). Contributions: - NFVIFA(23)000440 FEAT21 IFA013ed451 Providing naming related information for SAP or VnfExtCp (action 011): FEAT Agreed at IFA#337 - NFVIFA(23)000441 (mirror of 440) FEAT21 IFA007ed451 Providing naming relating information for VnfExtCp (action 011): FEAT Agreed at IFA#337 - NFVIFA(23)000442 (mirror of 440) FEAT21 IFA008ed451 Providing naming relating information for VnfExtCp (action 011): FEAT Agreed at IFA#337 - NFVIFA(23)000439 FEAT21 IFA013ed451 Providing location constraints of VNF constituents (action 011): FEAT Agreed at IFA#337 - NFVIFA(23)000438 FEAT21 IFA013ed451 Providing information about external L2 networks (action 011): FEAT Agreed at IFA#337 - NFVIFA(23)000437 FEAT21 IFA011ed451 Additional network properties for CPs (action 011): To be revised at IFA#337 |
IFA013, IFA011, IFA014, IFA007, IFA008 | Jun-2023 | Ongoing |
012 | Update the definition of VNF to clarify that a VNF can be used to deploy the implementation of a subset of an NF (5gnfv.func.007). | NFV003 | Jun-2023 | Not started |
013 | Enhancements to the VNFD to support describing requirements to use VNF Common/Dedicated Services related to authorization server (5gnfv.desc.009), CA (5gnfv.desc.010) and identify if VNF provides authorization server capabilities (5gnfv.desc.011). See notes 2 and 3. | IFA011 | Jun-2023 | Not started. Postponed to complete first ENH01.01 |
014 | Add functional requirements, interface requirements, interface modelling to cover the aspects of registering/unregistering client information in respective authorization server: - NFVO requirements (5gnfv.func.006) - VNF LCM interface (5gnfv.if.008) - VNF Configuration interface (5gnfv.if.009 and 5gnfv.if.010) See note 2. |
IFA010, IFA007, IFA008 | Jun-2023 | Not started. Postponed to complete first ENH01.01 |
015 | Document about the potential use of non-MANO artefacts describing the relationship of scaling aspects with the purposed services offered by the VNF (5gnfv.other.001). | IFA011 | Jun-2023 | Not started |
016 | Modeling of the PaaS Services descriptors for VNF Common/Dedicated services. Contributions: - NFVIFA(23)000280 FEAT21 IFA049 Scope and skeleton extension for future IFA049 version to include PaaS Services management: available |
IFA049 | Jan-2024 | Ongoing |
017 | Specification of interfaces and information modeling of management of PaaS Services. Contributions: - NFVIFA(23)000280 FEAT21 IFA049 Scope and skeleton extension for future IFA049 version to include PaaS Services management: available |
IFA049 | Jan-2024 | Ongoing |
NOTE 1: In the actions, references to relevant recommendations in ETSI GR NFV-IFA 037 v0.12.0 are provided for more information and details regarding the expected recommendation. NOTE 2: This action might be performed via a specific "security enhancement" feature. If so, proper cross-referencing will be highlighted on the feature plan. NOTE 3: Relationship with other features such as FEAT24 "Generic VNF OAM" and FEAT17 on aspects of "PaaS" will be evaluated to determine what feature work takes final responsibility to perform the specification in order to avoid overlapping specification. |
Stage 3 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
SOL
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Add version dependancy to VNFD and NSD
- NFVSOL(22)000189: Approved - NFVSOL(22)000225: Approved |
SOL001 | 2022-April | Completed |
002 | Add version dependancy to VNFD and NSD
- NFVSOL(22)000305: Approved |
SOL006 | 2022-April | Completed |
003 | Add version dependency to VNF LCM and NS LCM | SO005 | 2022-April | Completed |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT22: M-Tenant
Overview
Feature Prime | Ulrich Kleber, Huawei, Ulrich.kleber@huawei.com |
Feature description | Start with use cases where multiple users consume services from the same NFV-MANO environment and implement necessary enhancements in the NFV-MANO stack. |
Target Release | Stage 1: Release 5
Stage 2: Release 5 (2021-X-X) |
Impacted WIs | Stage 1: EVE018
Stage 2: tbd |
MegaCRs | Stage 2: IFAxxx MegaCR NFVIFA(18)000xxx (CR Status) IFAyyy MegaCR NFVIFA(18)000yyy (CR Status) |
Related/Dependent Features | |
New Specifcations | Stage 1: EVE018 Stage 2: none |
Status | Stage 1: Ongoing (60% completed)
Stage 2: Not started Stage 3: Not started |
Contributions | All feature contributions Agreed content |
Feature team | Stage 1: U.Kleber (Huawei) Stage 2: Name (Company) |
Last Updated | 2021-09-22 |
Stage 2 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
IFA
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Add interface X in to IFA0xx. CR draft [LINK] | IFA | xx | Open |
SOL
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Add interface X in to SOL0xx. CR draft [LINK] | SOL | xx | Open |
Stage 3 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
SOL
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Add interface X in to SOL0xx. CR draft [LINK] | SOL | xx | Open |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT23: M-SBA
Overview
Feature Prime | Janusz Pieczerak, Orange, janusz.pieczerak@orange.com |
Feature description | This feature studies the application of a Service-Based Architecture (SBA) design style to the NFV architectural framework and provides recommendations on the evolution of the ISG specifications structure to apply SBA design patterns to the NFV architectural framework. |
Target Release | Stage 2: Release 5 (2022-12)
Stage 3: Release 5 (2024-X-X) |
Impacted WIs | Stage 2: TBD
Stage 3: TBD |
MegaCRs | Stage 2:
IFAxxx Stage 3: SOLzzz MegaCR NFVSOL(19)000zzz (CR Status) |
Related/Dependent Features | None |
New Specifcations | Informative: DGR/NFV-IFA039 (published)
Stage 2: TBD Stage 3: TBD |
Status | Informative: Completed (100%)
Stage 2: TBD Stage 3: TBD |
Contributions | All feature contributions Agreed content |
Feature team | Stage 2: Janusz Pieczerak (Orange)
Stage 3: Name (Company) |
Last Updated | 2022-12-06 |
Stage 2 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
IFA
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Add interface X in to IFA007. CR draft [LINK] | IFA | 2023 | Open |
SOL
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Add interface X in to SOL001. CR draft [LINK] | SOL | 2024 | Open |
Stage 3 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
SOL
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Add interface X in to SOL001. CR draft [LINK] | SOL | March-2018 | Open |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT24: VNF-OAM
Overview
Feature Prime | Kostas Katsalis, DOCOMO, Katsalis@docomolab-euro.com & Yuhan Zhang, China Mobile, zhangyuhan@chinamobile.com |
Feature description | This feature will analyse and define the type of OAM functions for VNFs that can be generalized and be provided as a “generic function” supporting the provisioning, connectivity, configuration and monitoring of VNFs on a virtualized platform. The feature will also determine possible solutions to realize such generic OAM functions, e.g., by leveraging PaaS capabilities. The result report will include, if necessary, recommendations for requirements and architectural enhancements. |
Target Release | Stage 2: Release 4 (December 2022)
Stage 3: Release 4 (2020-X-X) |
Impacted WIs | Stage 2: IFAxx, IFAyy
Stage 3: SOLzz |
MegaCRs | Stage 2:
IFA0xx Stage 3: SOLzzz MegaCR NFVSOL(19)000zzz (CR Status) |
Related/Dependent Features | FEAT17: cloud-native VNF and NFV architecture PaaS
FEAT21: 5GNFV |
New Specifcations | Stage 2: IFA049
Stage 3: SOLaaa |
Status | Stage 2: Ongoing (10% completed)
Stage 3: Not started |
Contributions | All feature contributions Agreed content |
Feature team | Stage 2: Kostas Katsalis (DOCOMO), Yuhan Zhang (China Mobile)
Stage 3: Name (Company) |
Last Updated | 2022-10-02 |
Stage 2 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
IFA
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Skeleton, scope, and term definitions (Clauses 1, 2, 3)
CR drafts: NFVIFA(22)000283r2 (Approved) |
IFA049 | Ongoing | |
002 | Overview and framework for Generic OAM functions (Clause 4)
CR drafts: NFVIFA(22)000419r1 (Approved) NFVIFA(22)000493r1 (Approved) NFVIFA(22)000518 (Approved) |
IFA049 | Ongoing | |
003 | Specify the functional requirements for Generic OAM functions (Clause 5)
CR drafts: NFVIFA(22)000422r3 (Approved) NFVIFA(22)000435 (Approved) NFVIFA(22)000441r3 (Approved) NFVIFA(22)000443r3 (Approved) NFVIFA(22)000444r3 (Approved) NFVIFA(22)000445r2 (Approved) NFVIFA(22)000475r2 (Approved) NFVIFA(22)000540r2 (Approved) |
IFA049 | Ongoing | |
004 | Specify the interface requirements for Generic OAM functions (Clause 6)
CR drafts: |
IFA049 | Ongoing | |
005 | Specify information elements (Clause 7) | IFA049 | December-2022 | Open |
006 | Specify service interaction with VNF (Clause 8) | IFA049 | December-2022 | Open |
007 | Specify Descriptors for Generic OAM functions (Clause 9) | IFA049 | December-2022 | Open |
00x | 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
|
IFA011 | 2nd Half-2020 | Open |
002 | VNF should support to specify the test mode via configuration interface between VNFM and VNF | IFA | 2nd Half-2020 | Open |
003 | When a common test framework is used , it's recommended that VNF should support standardized test API | IFA | 1st Half-2021 | Open |
SOL
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Add interface X in to SOL001. CR draft [LINK] | SOL | March-2018 | Open |
Stage 3 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
SOL
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Under the '/tests' directory in VNF package, there should contain information about VNF test mode. | SOL | Need further focus | Open |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT26: Policy Management Models
Overview
Feature Prime | Lingli Deng, China Mobile, denglingli@chinamobile.com |
Feature description | This feature will analyse existing policy information and data models and identify solutions that potentially could be applied to NFV-MANO; clarify the main alternatives for policy management (between NFV-MANO and OSS/BSS); determine the objectives and management alternatives for policy management applicable to NFV-MANO; identify policy expression information model applicable to NFV-MANO; identify policy expression data model applicable to NFV-MANO. |
Target Release | Study: Release 4 (2021-04-15) Study to be completed
Stage 2: Release 4 (2022-12-15) Stage 3: Release 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 | Study: IFA042
Stage 2: IFA048 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 | 2023-05-30 |
Stage 2 Implementation Plan
0Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
IFA
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | First GR (IFA042) draft introducing the skeleton and the scope.
Accepted contributions: NFVIFA(20)000553r2 |
IFA042 | August-2020 | Done |
002 | Analysis of existing SDOs and Open Source Community policy models
Accepted contributions: NFVIFA(20)000615r2 NFVIFA(20)000616r6 NFVIFA(20)000617r1 NFVIFA(20)000618r2 NFVIFA(20)000619r2 NFVIFA(20)000620r1 |
IFA042 | November-2020 | Done |
003 | NFV-MANO policy model potential requirements analysis
Analysis of existing SDOs and Open Source Community policy models NFVIFA(21)000304 NFVIFA(21)000305r2 NFVIFA(21)000306r3 NFVIFA(21)000307r2 NFVIFA(21)000308r3 NFVIFA(21)000309r4 NFVIFA(21)000310r3 NFVIFA(21)000313r2_IFA042_5_4_1_Examples__Potential_Attributes_of_the_VNF_Auto- NFVIFA(21)000314r2_IFA042_5_4_2_Examples__Potential_Attributes_of_the_NS_Self-h NFVIFA(21)000315r3_IFA042_5_4_3_Examples__Potential_Attributes_of_the_Virtualiz NFVIFA(21)000316r2_IFA042_6_3_2_3_A_YANG_Data_Model_for_ECA_Policy_Management |
IFA042 | January-2021 | Done |
004 | Analysis and Recommendations
NFVIFA(21)000310r3_IFA042_5_3_1_General_Recommendations NFVIFA(21)000311r2_IFA042_5_3_2_Recommendations_for_Policy_Model_Information_El NFVIFA(21)000312r2_IFA042_5_3_3_Recommendations_for_Policy_Model_Attributes NFVIFA(21)000407r1 NFVIFA(21)000408 NFVIFA(21)000409r1 NFVIFA(21)000410r2 NFVIFA(21)000411r2 NFVIFA(21)000424r2 NFVIFA(21)000439r1 NFVIFA(21)000440r1 NFVIFA(21)000441r1 NFVIFA(21)000443r1 NFVIFA(21)000444r1 NFVIFA(21)000454r1 NFVIFA(21)000442r1 NFVIFA(21)000445r1 NFVIFA(21)000446r1 NFVIFA(21)000487r1 NFVIFA(21)000488r1 NFVIFA(21)000489r1 NFVIFA(21)000503r1 NFVIFA(21)000520r1 NFVIFA(21)000530r1 NFVIFA(21)000558r1 NFVIFA(21)000559r1 NFVIFA(21)000560r1 NFVIFA(21)000561r1 NFVIFA(21)000562 NFVIFA(21)000563r1 NFVIFA(21)000617r2 NFVIFA(21)000618r2 |
IFA042 | Feburary-2021 | Done |
005 | Review
NFVIFA(21)000674r1 NFVIFA(21)000675r1 NFVIFA(21)000699 NFVIFA(21)000701r2 NFVIFA(21)000700r1 NFVIFA(21)000727 NFVIFA(21)000728 NFVIFA(21)000729r1 NFVIFA(21)000730r1 |
IFA042 | September-2021 | Done |
006 | Policy information model | IFA048 | Done | |
007 | General
Example of policy model Review |
IFA048 | Done | |
008 | Policy management alignment with IFA048 | IFA005
IFA006 IFA007 IFA008 IFA013 |
Done |
Stage 3 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
SOL
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Study of solution
- NFVSOL(23)000084r1 |
NWI | ||
002 | Policy management alignment with IFA048
- NFVSOL(23)000014 |
SOL012 | Done | |
003 | Policy information model | Not started | ||
004 | Policy data model | Not started |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT27: NFV for vRAN
Overview
Feature Prime | Kostas Katsalis (DOCOMO EUL) |
Feature description | The scope of this feature covers the following areas: a) study the advances concerning the virtualization of the RAN and profile the NFV framework to determine how it can support virtualized RAN (vRAN) use cases, b) identify key technical challenges relevant to architectural, operational and management aspects, in case the NFV architectural framework is leveraged to support virtualization of the RAN, and c) provide recommendations for enhancements to the NFV architectural framework and its functionality, aiming to provide further support for vRAN use cases. |
Target Release | Stage 2: TBD (Release 5 (2023-X-X))
Stage 3: TBD (Release 5 (2023-X-X)) |
Impacted WIs | Stage 2: TBD (IFAxx, IFAyy, SOLzz)
Stage 3: TBD (SOLzz) |
MegaCRs | Stage 2:
TBD: IFAxxx MegaCR NFVIFA(21)000xxx (CR Status) IFAyyy MegaCR NFVIFA(21)000yyy (CR Status) Stage 3: TBD: SOLzzz MegaCR NFVSOL(21)000zzz (CR Status) |
Related/Dependent Features | FEAT17 on "Cloud-native VNF and container infrastructure management"
FEAT19 on "NFV connectivity" FEAT21 on "5GNFV" |
New Specifcations | Informative: DGR/NFV-IFA046
Stage 2: TBD Stage 3: TBD |
Status | Informative: ongoing (0%)
Stage 2: TBD Stage 3: TBD |
Contributions | All feature contributions Agreed content |
Feature team | Informative: Kostas Katsalis (DOCOMO EUL)
Stage 2: Name (Company) Stage 3: Name (Company) |
Last Updated | 2023-02-06 |
Informative work
IFA
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Skeleton and scope - NFVIFA(21)000751 IFA046 skeleton - NFVIFA(21)000806 IFA037 Scope - NFVIFA(22)000749 scope update - NFVIFA(22)000865 review abbreviations |
IFA | Dec-2022 | Completed |
002 | Overview and Introduction - NFVIFA(21)0001032r2 introduction - NFVIFA(21)0001033r2 state of the art - NFVIFA(21)0001034r3 Clause adding vRAN characteristics - NFVIFA(21)0001035r2 problem statement - NFVIFA(22)000752r1 addressing ENs_sec 4 - NFVIFA(22)000784 editorial cleanup - NFVIFA(22)000851 additional editorial cleanup - NFVIFA(22)000927r1 updating section1_section2_section3 - NFVIFA(22)000928r1 updating section 4 |
IFA | Dec-2022 | Completed |
003 | Identification and description of Key technical challenges
- NFVIFA(22)000141r1 introduction - NFVIFA(22)000142r1 intro and challenges for architectural mappings - NFVIFA(22)000143r1 solutions and gaps for architectural mappings - NFVIFA(22)000144r2 evaluation to key issue architectural mappings - NFVIFA(22)000251 O-RAN arch figure update - NFVIFA(22)000260r1 acceleration abstraction intro - NFVIFA(22)000261r3 packaging and descriptors introduction - NFVIFA(22)000306r1 challenges for acceleration abstraction - NFVIFA(22)000307r1 challenges for descriptors and packaging - NFVIFA(22)000318 Numbering challenges - NFVIFA(22)000319r2 introduction for ransport network management - NFVIFA(22)000325r3 solutions to key issue VNF descriptors and packaging - NFVIFA(22)000326r4 solutions for key issue acceleration abstraction - NFVIFA(22)000329 challenges for key issue transport network management - NFVIFA(22)000356 solutions to transport network management - NFVIFA(22)000364 updates to the structure of transport network management solutions - NFVIFA(22)000365r1background information about functional splits in Annex B - NFVIFA(22)000368 gap analysis for key issue transport network management - NFVIFA(22)000369r4 physical infrastructure management - NFVIFA(22)000416r1 gap analysis for key issue acceleration abstraction - NFVIFA(22)000417r1 gap analysis for key issue descriptors and packaging - NFVIFA(22)000420r3 additional solutions to key issue transport network management - NFVIFA(22)000436 evaluation to key issue transport network management - NFVIFA(22)000417r2 gap analysis for key issue descriptors and packaging - NFVIFA(22)000470 evaluation to key issue acceleration abstraction - NFVIFA(22)000490r2 gap analysis for CRDs in NFV - NFVIFA(22)000491r1 evaluation of PIM solutions - NFVIFA(22)000574 evaluation to key issue descriptors and packaging - NFVIFA(22)000678r1 MANO figures update based on NFV006 rel4 - NFVIFA(22)000679r3 additional clarification points for architectural mappings - NFVIFA(22)000680 CCDs in vRAN - NFVIFA(22)000683r3 solution for VNF Packaging - Different LCM-VNF Bundle - NFVIFA(22)000750 CRDs for CIS cluster - NFVIFA(22)000751 architectural mappings evaluation updates - NFVIFA(22)000753r1 addressing an EN in clause 5.1.2 - NFVIFA(22)000754 addressing ENs_sec 5.2.1 - NFVIFA(22)000764r2 Gap Analysis and Evaluation for SOL-C3-3 (VNF Bundle) - NFVIFA(22)000787 revision of AAL-part A - NFVIFA(22)000788 revision of AAL-part B - NFVIFA(22)000789 revision of AAL-part C - NFVIFA(22)000800 handling ENs for descriptors - NFVIFA(22)000806 transport network analysis ENs handling - NFVIFA(22)000809 Recommendations for solution SOL-C3-3 - NFVIFA(22)000823r2 solution for VNF LCM dependencies - NFVIFA(22)000929r1 updating section 5.1 - NFVIFA(22)000930r1 updating section 5.2.1 - NFVIFA(22)000931 updating section 5.2.2 - NFVIFA(22)000932 updating section 5.2.3 - NFVIFA(22)000933 updating section 5.2.4 - NFVIFA(22)000941 Notation for the VIM-CCM interactions in figures - NFVIFA(22)000960 updates on the virtual accelerator |
IFA | Dec-2022 | Completed |
004 | Analysis of Use Cases (from other SDOs)
- NFVIFA(21)0001069r1 use case analysis in Annex A - NFVIFA(22)000037r1 use case analysis in Annex A.3 (UC1-11) - NFVIFA(22)000038r1 use case analysis in Annex A.3(UC12-19) - NFVIFA(22)000140 analysis in Annex about Near RT RIC - NFVIFA(22)000935 updating Annexes |
IFA | Dec-2022 | Completed |
005 | Recommendations
- NFVIFA(22)000549 recommendations overview - NFVIFA(22)000581r1 recommendations for solutions - NFVIFA(22)000681r2 recommendations framework - NFVIFA(22)000682r1 recommendations functional aspects - NFVIFA(22)000684r2 recommendations descriptors - NFVIFA(22)000685r1 recommendations interfaces - NFVIFA(22)000686r3 recommendations collaboration - NFVIFA(22)000767 recommendation for CCM functionality - NFVIFA(22)000934 updating section 6 |
IFA | Dec-2022 | Completed |
006 | Conclusion
NFVIFA(22)000695r1 conclusions |
IFA | Dec-2022 | Completed |
Stage 2 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
IFA
ID | Action | Impacted WG(s) | 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.
FEAT28: Fault management models
Overview
Feature Prime | WANG Chen (China Mobile) & TRIAY Joan (DOCOMO) |
Feature description | The proposed feature aims to extend the defined data model of alarms and values of attributes (e.g., fault type) to enhance the processing of failure information. In addition, the proposal will analyse, determine and enrich the fault management interfaces to provide and acquire information to/from fault management closed loops in between different NFV-MANO, platform and OSS layers.
Thus, the objectives of the feature comprise: - Define the necessary vendor agnostic information and data models for alarms and event notifications. - Expose and relate the type, cause, and additional information of the faults with appropriate levels of severity of the violation, like critical, major, minor, warning as defined in the current Alarm information elements. - Enable automated fault detection and performance degradation analysis over complex and correlated metrics. NOTE: Alarms related to security violations are out of scope of this activity. |
Target Release | Stage 2: TBD (Release 5 (2023-X-X))
Stage 3: TBD (Release 5 (2023-X-X)) |
Impacted WIs | Stage 2: EVE019, IFA005/006/007/008/013
Stage 3: TBD (SOLzz) |
MegaCRs | Stage 2:
TBD: IFAxxx MegaCR NFVIFA(21)000xxx (CR Status) IFAyyy MegaCR NFVIFA(21)000yyy (CR Status) Stage 3: TBD: SOLzzz MegaCR NFVSOL(21)000zzz (CR Status) |
Related/Dependent Features | FEAT24 on "Generic VNF OAM" |
New Specifcations | Stage 2: DGS/NFV-IFA045
Stage 3: TBD |
Status | Stage 2: ongoing (80%)
Stage 3: TBD |
Contributions | All feature contributions Agreed content |
Feature team | Normative: WANG Chen (China Mobile) & Joan TRIAY (DOCOMO)
Stage 2: Name (Company) Stage 3: Name (Company) |
Last Updated | 2023-06-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.
IFA
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Skeleton and scope for the IFA045. Contributions: - NFVIFA(21)000810 Proposed ETSI GS skeleton IFA045 FM Models: approved - NFVIFA(23)000463 FEAT28 IFA045 Adding scope: approved |
IFA045 | Sept-2021 | Completed |
002 | Overview and introduction of IFA045 content (clause 4). Contributions: - NFVIFA(21)000914 FEAT28 IFA045 Clause 4 Adding introduction: approved |
IFA045 | Oct-2021 | Completed |
003 | Define the “alarm definition template” (clause 6). See note 1. Contributions: - NFVIFA(21)0001067r2 FEAT28 IFA045 clause 6 Alarm definition template: approved - NFVIFA(22)000506 FEAT28 IFA045 Add Alarm Definition Template: available |
IFA045 | Nov-2021 | Completed |
004 | Development of use cases related to FM alarms (annex A.1). Contributions: - NFVIFA(21)000915 FEAT28 IFA045 Annex A.1.2 Use cases VR and NFVI alarms: approved - NFVIFA(21)0001068r2 FEAT28 IFA045 A1.2.m Use case about packet loss alarm: approved - NFVIFA(22)000045r1 FEAT28 IFA045 A1.2.m Use case about unavailable storage service alarm: approved - NFVIFA(22)000151 IFA045 A1.2.m Use case about network link anomaly alarm: approved - NFVIFA(23)000152 FEAT28 IFA045 Annex A.1 Use cases about VNF and NS alarms: approved - NFVIFA(23)000443r1 FEAT28 IFA045 Clause A.1.2.3 adding annex about container and cluster alarms: approved |
IFA045 | May-2023 | Completed |
005 | Development of use cases related to use of Alarms information (annex A.2). Contributions: - NFVIFA(21)0001043r1 IFA045 A.2.1.1 Use case about generic procedure of using alarm information produced by the VIM: approved - NFVIFA(21)0001044r1 IFA045 A.2.1.2 Use case about generic procedure of using alarm information produced by the VNFM: approved - NFVIFA(21)0001045r1 IFA045 A.2.1.3 Use case about generic procedure of using alarm information produced by the NFVO: approved |
IFA045 | Mar-2021 | Completed |
006 | Definition of object types that can be fault monitored (clause 5). See note 1 and note 2. Contributions: - NFVIFA(22)000911 FEAT28 IFA045 virtualised resource object types: approved - NFVIFA(23)000140r1 FEAT28 IFA045 VNF/NS object types: approved - NFVIFA(23)000153 FEAT28 FM and alarms for containerized workloads: noted - NFVIFA(23)000271 FEAT28 IFA045 MSCS object types: approved - NFVIFA(23)000275 FEAT28 IFA045 Discussion about CIS cluster management object types: noted - NFVIFA(23)000391 FEAT28 IFA045 CIS cluster object types: approved - NFVIFA(23)000444 FEAT28 IFA045 additional CIS cluster object types: approved - NFVIFA(23)000445 FEAT28 IFA045 containerized workload object types: approved - NFVIFA(23)000398r1 FEAT28 IFA045 Clause 5.1 Introduction: approved |
IFA045 | Jun-2023 | Completed |
007 | Alarm definitions (clause 7). See note 1 and note 2. Contributions: - NFVIFA(22)000912r2 FEAT28 IFA045 VIM alarms baseline: common definitions: approved - NFVIFA(22)000913r1 FEAT28 IFA045 VIM alarms baseline: compute and CPU: approved - NFVIFA(22)000914 FEAT28 IFA045 VIM alarms baseline: memory: approved - NFVIFA(22)000915 FEAT28 IFA045 VIM alarms baseline: storage: approved - NFVIFA(22)000916r1 FEAT28 IFA045 VIM alarms baseline: network interface: approved - NFVIFA(23)000917 FEAT28 IFA045 VIM alarms baseline: network: approved - NFVIFA(23)000141r1 FEAT28 IFA045 VNFM alarms baseline: common definitions: approved - NFVIFA(23)000143 FEAT28 IFA045 NFVO alarms baseline: common definitions: approved - NFVIFA(23)000144 FEAT28 IFA045 VNFM alarms baseline: VNF: approved - NFVIFA(23)000145 FEAT28 IFA045 VNFM alarms baseline: VNFC: approved - NFVIFA(23)000146 FEAT28 IFA045 VNFM alarms baseline: VNF virtual link: approved - NFVIFA(23)000147r1 FEAT28 IFA045 VNFM alarms baseline: VNF internal CP: approved - NFVIFA(23)000148r1 FEAT28 IFA045 VNFM alarms baseline: VNF external CP: approved - NFVIFA(23)000149 FEAT28 IFA045 NFVO alarms baseline: NS: approved - NFVIFA(23)000150r1 FEAT28 IFA045 NFVO alarms baseline: NS virtual link: approved - NFVIFA(23)000151 FEAT28 IFA045 NFVO alarms baseline: NS service access point: approved - NFVIFA(23)000272 FEAT28 IFA045 WIM alarms baseline: common definitions: approved - NFVIFA(23)000273 FEAT28 IFA045 WIM alarms baseline: MSCS: approved - NFVIFA(23)000274 FEAT28 IFA045 WIM alarms baseline: MSNC: approved - NFVIFA(23)000318r2 FEAT28 IFA045 VNFM alarms: clarification of virtual compute and MCIO based VNFC caused alarms: approved - NFVIFA(23)000413r1 FEAT28 IFA045 Clause 7.1 Introduction: approved - NFVIFA(23)000392r2 FEAT28 IFA045 CIS cluster alarms baseline: common definitions: approved - NFVIFA(23)000393r1 FEAT28 IFA045 CCM alarms baseline: CIS cluster: approved - NFVIFA(23)000394r2 FEAT28 IFA045 CCM alarms baseline: CIS cluster node: approved - NFVIFA(23)000395r1 FEAT28 IFA045 CCM alarms baseline: CIS cluster storage: approved - NFVIFA(23)000396r1 FEAT28 IFA045 CCM alarms baseline: CIS cluster network: approved - NFVIFA(23)000397r1 FEAT28 IFA045 CCM alarms baseline: MCCO: approved - NFVIFA(23)000446 FEAT28 IFA045 CISM alarms baseline: common definitions: approved - NFVIFA(23)000447 FEAT28 IFA045 CISM alarms baseline: CISI: approved - NFVIFA(23)000448 FEAT28 IFA045 CISM alarms baseline: MCIO: approved - NFVIFA(23)000400r1 FEAT28 IFA045 Updating event types of alarms produced by VIM: approved - NFVIFA(23)000415 FEAT28 IFA045 Updating event types of alarms produced by VNFM: approved - NFVIFA(23)000416 FEAT28 IFA045 Updating event types of alarms produced by NFVO: approved - NFVIFA(23)000417 FEAT28 IFA045 Updating event types of alarms produced by WIM: approved |
IFA045 | Jun-2023 | Completed |
008 | Final review of IFA045 and addressing open editor's notes. Contributions: - NFVIFA(23)000401 FEAT28 IFA045 addressing editorial and guideline editor's note: approved - NFVIFA(23)000399 FEAT28 IFA045 Clause A.1.1 and A.2.1 overview: approved |
IFA045 | Jun-Jul 2023 | Ongoing |
009 | Alignment CRs to other NFV-IFA specifications. Contributions: |
IFA | Dec-2023 | Not started |
NOTE 1: It can run in parallel with the development of use cases, in particular if there are diverse object types and some of them are clarified with use cases at early stages.
NOTE 2: Additional sub-task details could be defined to sequence or parallelize the work on different object types and associated alarm definitions, e.g., split by “NFV managed objects such as VR, MSCS, VNF, NS” or by “resource related domain, such as compute, storage, network”. |
Stage 3 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
SOL
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | TBD | TBD | TBD | TBD |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT29: Green NFV
Overview
Feature Prime | Joan Triay (DOCOMO) |
Feature description | The scope of the feature covers the following areas: - Analyse aspects of NFV (VNF design, NFV-MANO and VNF operation, deployment configuration of NFV-MANO, NFVI, etc.) that have impact on energy consumption and those that can enable smart energy NFV and power saving features. - Identify design guidelines needed for optimizing energy consumption. - Specify enhancements to specifications on interfaces and information model, augment exposed KPIs and metrics to enable resources orchestration and VNF/NS LCM to operate following power saving policies. |
Target Release | Stage 2: TBD (Release 5 (2021-X-X)) Stage 3: TBD (Release 5 (2021-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 | FEAT20 on "Autonomous management" (Release 4) FEAT07 on "Policy management framework" (Release 4) FEAT26 on "Policy models" (Release 4) |
New Specifications | Informative: DGR/NFV-EVE021 Stage 2: TBD Stage 3: TBD |
Status | Informative: ongoing (65%) 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 | 2023-06-08 |
Informative work
EVE
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Skeleton and scope. Contributions: - NFVEVE(21)000080 FEAT29 EVE021 Skeleton: Approved - NFVEVE(21)000081 FEAT29 EVE021 Scope: Approved |
EVE (EVE021) | Oct-2021 | Completed |
002 | Introduction and overview - Introduction to energy efficiency and global initiatives - NFV and energy efficiency - Other organizations work Contributions: - NFVEVE(21)000107r1 FEAT29 EVE021 Clause 4.1 Introduction to energy efficiency: Approved - NFVEVE(21)000133r1 FEAT29 EVE021 Clause 4.2 NFV and energy efficiency: Approved - NFVEVE(21)000134r1 FEAT29 EVE021 Clause 4.3.1 Energy efficiency in 3GPP: Approved - NFVEVE(22)000017r1 EVE021 Energy Efficiency - clause 4.3: Approved - NFVEVE(22)000027r1 FEAT29 - EVE021 - Proposed update to clause 4.3: Approved - NFVEVE(22)000043 FEAT29 EVE021 Clause 2.2 correct reference of DMTF Redfish: Approved - NFVEVE(22)000051 FEAT29 EVE021 Clause 2.2 additional references for DMTF Redfish: Approved |
EVE (EVE021) | Mar-2022 | Completed |
003 | Development of use cases. See note 1 and note 2. - Network-wide and NFV-MANO aspects. - Energy related measurements and runtime aspects. - Energy-driven design - Enabling smart energy usage and decision making. Contributions: - NFVEVE(22)000037r1 FEAT29 EVE021 Clause 5 UC resources sleep resume: Approved - NFVEVE(22)000052r2 FEAT29 EVE021 Clause 5 UC Power saving management function under limited power supply: Approved - NFVEVE(22)000075r2 FEAT29 EVE021 Clause 5 UC acquiring infrastructure power consumption data: Approved - NFVEVE(22)000076r2 FEAT29 EVE021 Clause 5 UC acquiring NFV power consumption data: Approved - NFVEVE(22)000077r1 FEAT29 EVE021 Clause 5 UC processing power state driven deployment: Approved - NFVEVE(22)000116r1 FEAT29 EVE021 Clause 5 UC power consumption and resources placement optimization: Approved - NFVEVE(22)000115r2 FEAT29 EVE021 Clause 5 UC Restoration management from resource reservation in power saving situations: Approved - NFVEVE(22)000162 FEAT29 EVE021 Clause 5 UC on dynamic power state management: Approved - NFVEVE(22)000175 FEAT29 EVE021 Clause 5 UC on dynamic power state management - actors, conditions and flow description: Approved - NFVEVE(23)000101 FEAT29 EVE021 Clause 5.1 Overview of use cases: Agreed |
EVE (EVE021) | Oct-2022 | Completed |
004 | Documentation of key issues. See note 1 and note 2. - Energy consumption - Energy efficiency management - Energy efficient design - Energy related metrics and KPI Contributions: - NFVEVE(22)000096r1 FEAT29 EVE021 Clause 6 Key issues: Approved - NFVEVE(22)000161r1 FEAT29 EVE021 Clause 6 Update key issues: Approved - NFVEVE(22)000204 FEAT29 EVE021 Clause 6 Re-organize questions between key issues: Approved - NFVEVE(22)000209 FEAT29 EVE021 Clause 6 Key issues related to CPU power state management: Approved |
EVE (EVE021) | Sep-2022 | Completed |
005 | Framework and potential solutions. Contributions: - NFVEVE(22)000205 FEAT29 EVE021 Clause 7.1 Solutions introduction: Approved - NFVEVE(22)000199r2 FEAT29 EVE021 Clause 7 Solutions key issues #1.1 and #1.2: Approved - NFVEVE(22)000206 FEAT29 EVE021 Clause 7 Solutions key issues #1.2: Approved - NFVEVE(22)000219 FEAT29 EVE021 Clause 7 Solutions key issues #2.2 resources: Approved - NFVEVE(22)000220r1 FEAT29 EVE021 Clause 7 Solutions key issues #2.2 state and config: Approved - NFVEVE(22)000221r1 FEAT29 EVE021 Clause 7 Solutions key issues #3.1 VNF power profiles: Approved - NFVEVE(22)000222 FEAT29 EVE021 Clause 7 Solutions key issues #3.1 VNF power management: Approved - NFVEVE(23)000041 FEAT29 EVE021 Clause 7 Solutions key issues #3.3 Power state based zones in NFVI: Approved - NFVEVE(23)000042 FEAT29 EVE021 Clause 7 Solutions key issue #2.1 Power state aware allocation of compute resources: Approved - NFVEVE(23)000043r1 FEAT29 EVE021 Clause 7 Solutions key issues #2.1 energy policies: Approved - NFVEVE(23)000044r1 FEAT29 EVE021 Clause 7 Solutions key issue #3.2 NFV-MANO power consumption: Approved - NFVEVE(23)000045 FEAT29 EVE021 Clause 7 Updating key issues by existing solutions: Approved - NFVEVE(23)000046r1 FEAT29 EVE021 Clause 7 Solutions key issue #2.1 NFV-MANO capabilities: Approved - NFVEVE(23)000047 FEAT29 EVE021 Clause 7.1 Update summary of solutions and related key issues: Approved - NFVEVE(23)000051 FEAT29 EVE021 Clause 7.1 Update summary of solutions and related key issues (2nd round): Approved - NFVEVE(23)000065 FEAT29 EVE021 Clause 7.1 Further update summary of solutions and related key issues (3nd round): Approved - NFVEVE(23)000066 FEAT29 EVE021 Clause 7 Solutions key issue #4.2 VIM for acquiring VR power consumption: Approved - NFVEVE(23)000067 FEAT29 EVE021 Clause 7 Solutions key issue #4.2 CISM for acquiring containerized power consumption: Approved - NFVEVE(23)000068 FEAT29 EVE021 Clause 7.2.6 Update solution to address key issue #4.3 of acquiring VNF power consumption: Approved - NFVEVE(23)000069 FEAT29 EVE021 Clause 7 Solutions key issue #4.4 NFVO for acquiring NS power consumption: Approved - NFVEVE(23)000070 FEAT29 EVE021 Clause 7 Solutions key issue #4.2, #4.3 and #4.4 NFV power manager for acquiring power consumption: Approved - NFVEVE(23)000074 FEAT29 EVE021 Clause 7.1 Further update summary of solutions (4th round): Approved - NFVEVE(23)000078 FEAT29 EVE021 Clause 7 Solutions key issue #4.1 energy efficiency of NFVI physical resources: Approved - NFVEVE(21)000081 FEAT29 EVE021 Clause 7 Solutions key issue #4.2 energy efficiency and metrics of virtualised resources and containerized workloads: Approved - NFVEVE(23)000082 FEAT29 EVE021 Clause 7 Solutions key issue #4.3 energy efficiency and metrics of VNF: Approved - NFVEVE(23)000083 FEAT29 EVE021 Clause 7 Solutions key issue #4.4 energy efficiency and metrics of NS: Approved - NFVEVE(23)000090 FEAT29 EVE021 Clause 7.1 Further update summary of solutions (5th round): Approved - NFVEVE(23)000098r1 FEAT29 EVE021 Clause 7 Solutions key issue #4.1 PIM for acquiring PR power consumption: Agreed - NFVEVE(23)000103 FEAT29 EVE021 Clause 7.3 Evaluation of solutions: Available |
EVE (EVE021) | May-2023 | Ongoing |
006 | Documentation of recommendations. Contributions: - NFVEVE(23)000104 FEAT29 EVE021 Clause 8 Recommendations: Available |
EVE (EVE021) | Jun-2023 | Ongoing |
007 | Documentation of the conclusion. Contributions: - NFVEVE(23)000105 FEAT29 EVE021 Clause 9 Conclusions: Agreed |
EVE (EVE021) | Jun-2023 | Completed |
008 | Final review of EVE021. See note 3. Contributions: - NFVEVE(23)000052 FEAT29 EVE021 Clause 2.2 and 7.2.9.2 Fix missing reference: Approved - NFVEVE(23)000102r1 FEAT29 EVE021 Clean-up of various editor's notes and empty template clauses: Agreed |
EVE (EVE021) | Jul-2023 | Ongoing |
NOTE 1: Minimum set of items to consider are listed. NOTE 2: These tasks can run in parallel, since as we develop use cases, we can start documenting findings about related key issues. NOTE 3: It may include addressing “minor” editor’s notes that do not require substantial new content. |
Stage 2 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
IFA
ID | Action | Impacted WG(s) | 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.
FEAT30: VNF configuration
Overview
Feature Prime | Bruno Chatras (Orange) |
Feature description | The scope of this feature covers the following areas:
1) Provide guidelines on the use of the configuration options available in the NFV framework and the types of configuration data applicable to each of these options. 2) Specify related enhancements to the set of ETSI NFV specifications needed to improve interoperability between VNFs and independently-developed VNF configuration management functions and further facilitate automation of VNF configuration. |
Target Release | Stage 2: TBD (Release 5 (2022-X-X))
Stage 3: TBD (Release 5 (2023-X-X)) |
Impacted WIs | Stage 2: TBD (IFAxx, IFAyy, SOLzz)
Stage 3: TBD (SOLzz) |
MegaCRs | Stage 2:
TBD: IFAxxx MegaCR NFVIFA(21)000xxx (CR Status) IFAyyy MegaCR NFVIFA(21)000yyy (CR Status) Stage 3: TBD: SOLzzz MegaCR NFVSOL(21)000zzz (CR Status) |
Related/Dependent Features | FEAT24 on "VNF generic OAM" |
New Specifcations | Informative: DGR/NFV-EVE022
Stage 2: TBD Stage 3: TBD |
Status | Informative: Completed
Stage 2: TBD Stage 3: TBD |
Contributions | All feature contributions Agreed content |
Feature team | Informative: Bruno Chatras (Orange)
Stage 2: Name (Company) Stage 3: Name (Company) |
Last Updated | 2022-12-06 |
EVE
ID | Action | Impacted WG(s) | Target completion | Status |
---|---|---|---|---|
001 | Skeleton and scope - NFVIFA(21)000751 EVE022 skeleton and scope |
EVE | Sept-2021 | Completed |
002 | Overview and and use cases |
EVE | Oct-2021 | Completed |
003 | Analysis of Use Cases and Identification of Key Issues |
EVE | Nov-2021 | Completed |
004 | Solutions identification |
EVE | March-2022 | Completed |
005 | Solutions comparison |
EVE | June-2022 | Completed |
006 | Recommendations |
EVE | Sep-2022 | Completed |
Stage 2 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
IFA
ID | Action | Impacted WG(s) | 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.
FEAT31: Flexible VNF deployment
Overview
Feature Prime | Arturo Martin de Nicolas (Ericsson) |
Feature description | This feature enhances the flexibility of the VNF deployment by introducing parametrization of VNF deployment flavours. It covers the following areas
1) Ability to specify in the VNFD which VDUs or groups of VDUs are optional for a particular deployment flavour 2) Ability to specify in the VNFD which VDU attributes related to resource capacity are configurable 3) Ability to specify in the NSD the selected optional VDUs or group of VDUs of a constituent VNF that are to be deployed 4) Ability to specify in the NS LCM and VNF LCM interfaces the selected optional VDUs or group of VDUs to be deployed 5) Ability to specify in the NS LCM and VNF LCM interfaces the selected values for VDU attributes related to resource capacity |
Target Release | Stage 2: TBD (Release 5 (2023-X-X))
Stage 3: TBD (Release 5 (2023-X-X)) |
Impacted WIs | Stage 2:
IFA010 IFA011 IFA007 IFA008 IFA013 IFA014 Stage 3: SOL001 SOL002 SOL003 SOL005 SOL016? SOL018? |
MegaCRs | Stage 2:
TBD: IFAxxx MegaCR NFVIFA(21)000xxx (CR Status) IFAyyy MegaCR NFVIFA(21)000yyy (CR Status) Stage 3: TBD: SOLzzz MegaCR NFVSOL(21)000zzz (CR Status) |
Related/Dependent Features | None |
New Specifcations | Informative: IFA044 |
Status | Informative: Completed
Stage 2: Not started Stage 3: Not started |
Contributions | All feature contributions Agreed content |
Feature team | Stage 2: Arturo Martin de Nicolas (Ericsson)
Stage 3: Arturo Martin de Nicolas (Ericsson) |
Last Updated | 2023-01-10 |
Stage 2 Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
IFA
ID | Action | Impacted WG(s) | Target
completion |
Status |
---|---|---|---|---|
001 | Add requirements on functional behaviour as per recommendations
Vnfm.DepMod.001, Vnfm.ConfAttr.001 and Nfvo.DepMod.001 IFA044 clause 8.1. CRs: NFV(23)000126r2 Status: Feat agreed in NFVIFA#325 |
IFA010 | TBD | All CRs Feat agreed |
002 | Introduce deployableModules in the VNFD as per recommendations VNFD.DepMod.001,
VNFD.DepMod.002 and VNFD.DepMod.003 in IFA044 clause 8.2. CRs: NFV(23)000127r1 Status: Feat agreed in NFVIFA#325 NFV(23)000206 Status: Feat agreed in NFVIFA#329 NFV(23)000128 Status: Feat agreed in NFVIFA#325 |
IFA011 | TBD | All CRs Feat agreed |
002a | Add a provision in ScalingAspect IE to exclude combining VDUs that don't belong to the same deployable modules
CRs: NFV(23)000264r2 Status: Feat agreed in NFVIFA#334 |
IFA011 | TBD | All CRs Feat agreed |
002b | Add a provision in MciopProfile IE to exclude combining VDUs that don't belong to the same deployable modules
CRs: NFVIFA(23)000270r2 Status: Feat agreed in NFVIFA#334 |
IFA011 | All CRs Feat agreed | |
003 | Introduce support for indication that a VDU resource capacity related attribute is configurable
and in which operations the value is modifiable as per recommendations VNFD.ConfAttr.001 and VNFD.ConfAttr.002 in IFA044 clause 8.2. CRs: NFV(23)000281r1 Status: Feat agreed in NFVIFA#333 |
IFA011 | TBD | Started |
004 | Introduce new attributes in VnfProfile and NsProfile for the support of the selection of deployableModules
of the constituent VNFs as per recommendations NSD.DepMod.001, NSD.DepMod.002, NSD.DepMod.003, NSD.DepMod.004 in IFA044 clause 8.2. CRs: NFV(23)000131r2 Status: Feat agreed in NFVIFA#327 |
IFA014 | TBD | All CRs Feat agreed |
005 | Introduce a new attribute in the VnfProfile to indicate whether it is allowed or not to modify values of VDU
attributes related to resource capacity by means of NS LCM interface as per recommendation NSD.ConfAttr.001 in IFA044 clause 8.2. |
IFA014 | TBD | Not started |
006 | Introduce new parameters in VNF LCM operations Instantiate VNF, Change VNF flavour, Change current
VNF package operation to convey the selection of deployableModules. as per recommendations Vnflcm.DepMod.001, Vnflcm.DepMod.003 and Vnflcm.DepMod.004 in IFA044 clause 8.3. CRs: NFVIFA(23)000181r1 Status: Feat agreed in NFVIFA#327 NFVIFA(23)000243 Status: Feat agreed in NFVIFA#332 |
IFA007
IFA008 |
TBD | All CRs Feat agreed |
006a | Introduce provisions for how to handle instantiation or scale level information related to VNFCs that are not part of the selected deployable modules.
CRs: NFVIFA(23)000223r1 Status: Feat agreed in NFVIFA#332 NFVIFA(23)000359 Status: Feat agreed in NFVIFA#337 NFVIFA(23)000360r1 Status: Feat agreed in NFVIFA#337 |
IFA007
IFA008 |
All CRs Feat agreed | |
007 | Introduce new VNF LCM operation to support the modification of the selection (addition or removal) of
deployableModules as per recommendation Vnflcm.DepMod.002 in IFA044 clause 8.3. CRs: NFVIFA(23)000185r3 Status: Feat agreed in NFVIFA#329 NFVIFA(23)000244 Status: Feat agreed in NFVIFA#332 |
IFA007
IFA008 |
TBD | All CRs Feat agreed |
007a | Introduce a new attribute in the VnfInfo or InstantiatedVnfInfo to indicate the deployable modules currently selected
CRs: NFVIFA(23)000199r1 Status: Feat agreed in NFVIFA#330 NFVIFA(23)000246 Status: Feat agreed in NFVIFA#332 NFVIFA(23)000269 Status: Feat agreed in NFVIFA#332 |
IFA007
IFA008 IFA013 |
TBD | All CRs Feat agreed |
007b | Add SelectVnfDeployableModules configuration parameters to VnfLcmOperationsConfiguration IE
CRs: NFVIFA(23)000226 Status: Feat agreed in NFVIFA#331 |
IFA011 | All CRs Feat agreed | |
008 | Introduce new parameters in VNF LCM operations Instantiate VNF, Change VNF flavour, Change current
VNF package to convey selected values for VDU attributes related to resource capacity as per recommendations Vnflcm.ConfAttr.001, Vnflcm.ConfAttr.003 and Vnflcm.ConfAttr.004 in IFA044 clause 8.3. CRs: |
IFA007
IFA008 |
TBD | Not started |
009 | Decide whether to use scale VNF operation or add a new VNF LCM operation to support the modification of
selected values for VDU attributes related to resource capacity and add new parameters to the scale VNF operation or add new operation based on the decision, as per recommendation Vnflcm.ConfAttr.002 in IFA044 clause 8.3. |
IFA007
IFA008 |
TBD | Not started |
010 | Add attributes to IEs used in the update NS operation to support conveying the selection of
deployableModules as per recommendations Nslcm.DepMod.001, Nslcm.DepMod.002, Nslcm.DepMod.003, Nslcm.DepMod.004, Nslcm.DepMod.005, Nslcm.DepMod.006, Nslcm.DepMod.007 in IFA044 clause 8.3. CRs: NFVIFA(23)000222 Status: Feat agreed in NFVIFA#331 |
IFA013 | TBD | All CRs Feat agreed |
011 | Add new NS update type to the update NS operation and corresponding new IE to support the modification
of the selection of deployableModules as per recommendations Nslcm.DepMod.008 in IFA044 clause 8.3. CRs: NFVIFA(23)000245r1 Status: Feat agreed in NFVIFA#332 |
IFA013 | TBD | All CRs Feat agreed |
012 | Add attributes to IEs used in the update NS operation to support conveying selected values for VDU
attributes related to resource capacity as per recommendations Nslcm.ConfAttr.001, Nslcm.ConfAttr.002, Nslcm.ConfAttr.003, Nslcm.ConfAttr.004, Nslcm.ConfAttr.005, Nslcm.ConfAttr.006, Nslcm.ConfAttr.007 in IFA044 clause 8.3. |
IFA013 | TBD | Not started |
013 | Decide whether to use scale NS operation or introduce new NS update type or use the new NS update
type introduced in activity 011 to support the modification of selected values for VDU attributes related to resource capacity and add attributes to the new or existing IEs, depending on the decision, as per recommendation Nslcm.ConfAttr.008 in IFA044 clause 8.3. |
IFA013 | TBD | Not started |
014 | Add new parameters in the grant VNF lifecycle operation to convey the selected deployableModules as per
recommendation VnfGrant.DepMod.001 in IFA044 clause 8.3. CRs: NFVIFA(23)000200r2 Status: Feat agreed in NFVIFA#330 |
IFA007 | TBD | All CRs Feat agreed |
015 | Add new parameters in the grant VNF lifecycle operation to convey values for VDU attributes related
to resource capacity as per recommendation VnfGrant.ConfAttr.001 in IFA044 clause 8.3. |
IFA007 | TBD | Not started |
016 | Add SAP to deployable modules mapping information in the NSD
CRs: NFVIFA(23)000388r1 |
IFA014 | 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 | Introduce deployableModules in the VNFD as per recommendations VNFD.DepMod.001,
VNFD.DepMod.002 and VNFD.DepMod.003 in IFA044 clause 8.2. |
SOL001 | TBD | Not started |
002 | Introduce support for indication that a VDU resource capacity related attribute is configurable
and in which operations the value is modifiable as per recommendations VNFD.ConfAttr.001 and VNFD.ConfAttr.002 in IFA044 clause 8.2 |
SOL001 | TBD | Not started |
003 | Introduce new attributes in VnfProfile and NsProfile for the support of the selection of deployableModules
of the constituent VNFs as per recommendations NSD.DepMod.001, NSD.DepMod.002, NSD.DepMod.003, NSD.DepMod.004 in IFA044 clause 8.2. |
SOL001 | TBD | Not started |
004 | Introduce a new attribute in the VnfProfile to indicate whether it is allowed or not to modify values of VDU
attributes related to resource capacity by means of NS LCM interface as per recommendation NSD.ConfAttr.001 in IFA044 clause 8.2. |
SOL001 | TBD | Not started |
005 | Introduce new parameters in VNF LCM operations Instantiate VNF, Change VNF flavour, Change current
VNF package operation to convey the selection of deployableModules. as per recommendations Vnflcm.DepMod.001, Vnflcm.DepMod.003 and Vnflcm.DepMod.004 in IFA044 clause 8.3. |
SOL003
SOL002 |
TBD | Not started |
006 | Introduce new VNF LCM operation to support the modification of the selection (addition or removal) of
deployableModules as per recommendation Vnflcm.DepMod.002 in IFA044 clause 8.3. |
SOL002
SOL003 |
TBD | Not started |
007 | Introduce new parameters in VNF LCM operations Instantiate VNF, Change VNF flavour, Change current
VNF package to convey selected values for VDU attributes related to resource capacity as per recommendations Vnflcm.ConfAttr.001, Vnflcm.ConfAttr.003 and Vnflcm.ConfAttr.004 in IFA044 clause 8.3. |
SOL002
SOL003 |
TBD | Not started |
008 | Introduce new parameters in the scale VNF operation or add new VNF LCM operation based on the
decision taken in IFA (action 009 in the stage 2 implementation plan), as per recommendation Vnflcm.ConfAttr.002 in IFA044 clause 8.3. |
SOL002
SOL003 |
TBD | Not started |
009 | Add attributes to datatypes used in the update NS operation to support conveying the selection of
deployableModules as per recommendations Nslcm.DepMod.001, Nslcm.DepMod.002, Nslcm.DepMod.003, Nslcm.DepMod.004, Nslcm.DepMod.005, Nslcm.DepMod.006, Nslcm.DepMod.007 in IFA044 clause 8.3.. |
SOL005 | TBD | Not started |
010 | Add new NS update type to the update NS operation and corresponding datatype to support the modification
of the selection of deployableModules as per recommendations Nslcm.DepMod.008 in IFA044 clause 8.3. |
SOL005 | TBD | Not started |
011 | Add attributes to datatypes used in the update NS operation to support conveying selected values for VDU
attributes related to resource capacity as per recommendations Nslcm.ConfAttr.001, Nslcm.ConfAttr.002, Nslcm.ConfAttr.003, Nslcm.ConfAttr.004, Nslcm.ConfAttr.005, Nslcm.ConfAttr.006, Nslcm.ConfAttr.007 in IFA044 clause 8.3. |
SOL005 | TBD | Not started |
012 | Add attributes to the datatype used in scale NS operation, or in the new datatype introduced in
SOL activity 010 or in a new datatype for a new update NS operation depending on the decision taken in IFA (action 013 in the stage 2 implementation plan) to support the modification of selected values for VDU attributes related to resource capacity as per recommendations Nslcm.ConfAttr.008 in IFA044 clause 8.3. |
SOL005 | TBD | Not started |
013 | Add new parameters in the grant VNF lifecycle operation to convey the selected deployableModules as per
recommendation VnfGrant.DepMod.001 in IFA044 clause 8.3. |
SOL003 | TBD | Not started |
014 | Add new parameters in the grant VNF lifecycle operation to convey values for VDU attributes related
to resource capacity as per recommendation VnfGrant.ConfAttr.001 in IFA044 clause 8.3. |
SOL003 | TBD | Not started |
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.
Ways of Working for this security enhancement feature. Latest update made by NFVSEC(22)000032r2 at NFV#38/SEC#210
Resolve open comments on the contribution in IFA;IFA almost feature agrees (first step) the contribution;Seek feedback from SEC;After resolving open comments on the contribution in SEC, SEC endorse the contribution and back to step 1.IFA feature agrees (second step) the contribution with confirmation from SEC.- SEC approval, then will be sent to IFA for feat agreed/approval
- IFA026 on Basic use case / Basic concept and architectural aspects including IFA010 existing featagreedCRs
- IFA033
- update SEC021/022/023/025, if necessary
- IFA feat agreed/approval, will be sent back to SEC for endorsement
- IFA006/008
- (Potential) IFA013/007/011/014
ID | Name | Release | Status | Contact | Descirption | Contributions |
---|---|---|---|---|---|---|
ENH01.xx | New security enhancement | {Proposal,Under development, Completed, Closed} | Foo Bar (ACME) <foo.bar@acme.org> | A short description of the feaure |
| |
ENH01.01 | Certificate management | Release 4 | Under development | Yuya Kuno (DOCOMO) | The security enhancement aims to specify the capability to support certificate management by introducing OCMF (Operator Certificate Management Function) within the NFV MANO architecture and is enhancing the NFV-MANO reference points and functional blocks. OCMF enhances "Operator Certificate Enrolment Server" as defined in ETSI GR NFV-SEC 005. | Information about the planned schedule and potential specification impacts is available in contribution NFVIFA(21)000843r2/NFVSEC(21)000071r2:Enhancement Proposal on Certificate Management Security Enhancement (Noted - IFA#258)
Discussion paper of direction for Stage 2 in IFA & SEC joint session: NFVIFA(21)001053r1/NFVSEC(21)000094r6:Enh01.01 DP for IFA and SEC joint session (IFA#264 check open issues -> SEC review -> IFA#274 Noted - agreed Suggestion#1 (NFV specifies both option) and Suggestion#2(registration usecase is starting points))) Discussion paper for the stage2 level working specs on Certificate Management: NFVSEC(22)000024:Enh01.01 DP for proposing to work on IFA026/IFA033 as for SEC related architecture and RPs/IFs (SEC#207 - agreed to work on IFA026/IFA033 for Certificate Management and noted clear separation between SM and Certificate Management needed. And also asuumed that the contirbutions on IFA026/033 worked in SEC WG first) Discussion paper NFVSEC(22)000032r2 "Enh01.01 Discussion on Certificate Management IFA specs impacts and work plan": Enh01.01 DP for identifying the impacted specs and work role/step between IFA and SEC in IFA/SEC joint session on NFV#38 (SEC#210/IFA#287).
Discussion paper NFVSEC(22)000059r5 "Enh01.01 Supporting material for Use Cases " in NFV#39/SEC#215:
Discussion paper NFVSEC(23)0000008 "ENH0101 documentation overview" in SEC#221.
|
Enh01.01: Certificate Management
Stage1/2
ID | Action | impacted WI(s) | Status |
---|---|---|---|
001 | develop usecase for direct mode of VNFCI certficate and VNF OAM certificate.
|
IFA026 | |
002 | develop usecase for delegation mode of VNFCI certificate and VNF OAM certificate.
|
IF026 | |
003 | develop usecase for VNF Package certificate. | IFA026 | Not started |
004 | develop usecase for NFV-MANO certificate.
|
IFA026 | |
005 | develop usecase for Virtualised computation environment control plane certificate. | IFA026 | Not started |
006 | Add functional requirements for the certirficate mgmt.
- functional requirements
- Architecture
- General
|
IFA026
IFA010 |
|
007 | Add interface for certificate management to CMF.
|
IFA033 | |
008 | Add Register Operation
|
IFA033 | |
009 | Add CSR Operation
|
IFA033 | |
010 | Add Vnfm-Cm reference point
|
IFA033 | |
011 | Add Vnf-Cm reference point | IFA033 | Not started |
012 | Enhance VNFD to support certificate mgmt.
|
IFA011 | |
013 | Enhance VNF LCM to support certificate mgmt.
|
IFA006
IFA007 IFA008 |
|
014 | Enhance NS LCM to support certificate mgmt.
|
IFA013 | |
015 | Enhance MANO mgmt to support certificate mgmt.
|
IFA031 |
Stage3
ID | Action | Impacted WI(s) | Status |
---|---|---|---|
001 | Enhance VNFD to support certificate mgmt. | SOL001
SOL006 |
|
002 | Enhance VNF LCM to support certificate mgmt. | SOL002
SOL003 |
|
003 | Enhancde NS LCM to support certificate mgmt. | SOL005 |
ENH02: Special technical enhancements
This section contains an overview of small and generic technical enhancements to the ETSI NFV framework and their current status.
ID | Name | Release | Status | Contact | Description | Contributions | ||
---|---|---|---|---|---|---|---|---|
ENH02.01 | NFV-MANO enhancement with SDN-based networking | Release 4 | Stage 2 complete
Stage 3 SOL001 completed |
|
This new enhancement proposes to enhance the NFV-MANO functionality related to virtualised network management, lifecycle management and template information model to support the integration of SDN-based network in the framework of NFV-MANO during the timeframe of Release 4.
This work suggests to specify the SDN-based network resources in the NSD and VNFD model in order to use the different type of network to provision the network connection requirements at the design time. This work also suggests to enhance Os-Ma-nfvo, Or-Vi and Or-Vnfm reference points in order to manage the lifecycle of the different type of network. |
Stage 2:
============= Mega CRs Approved ========
Stage 3:
| ||
ENH02.02 | NFV-MANO enhancement for NS feasibility check | Release 4 | Stage 2 complete
Stage 3 completed without SOL016 |
Junichi Kawasaki <ju-kawasaki@kddi.com>, Kenichi Ogaki <ke-oogaki@kddi.com>, Rajavarma Bhyrraju <rajavarma.bhyrraju@ericsson.com>, Cristina Badulescu <cristina.badulescu@ericsson.com>, Anatoly Andrianov <anatoly.andrianov@nokia.com>, Kleber Ulrich <Ulrich.Kleber@huawei.com> | This new enhancement proposes to add the capability of feasibility check of Network Service to the lifecycle management during the timeframe of Release 4.
This is required to support the requirements specified in step-3 of clause 5.1.21 in 3GPP TS28.531 (Management and provisioning of 5G network slicing), to check the feasibility of Network slice subnet by sending enquiry requests to MANO to determine availability of network constituents. This work suggests to enhance the Os-Ma-nfvo reference point to supporting the feasibility check of Network Service. |
Stage2:
============= Mega CRs Approved ========
Stage3:
| ||
ENH02.03 | NFV-MANO enhancement with Data flow mirroring | Release 4 | Stage 2 complete
Stage 3 complete without SOL14 |
Chen Shaofan <chenshaofan@chinamobile.com>,
Li Shitao <lishitao@huawei.com> |
This new enhancement proposes to enhance the NFV-MANO functionality to enable data flow mirroring management during the timeframe of Release 4.
This work suggests to specify the intra NFVI-PoP data flow mirroring requirements in the NSD model in order to provide the flow information need to be mirrored at the design time. This work also suggests to enhance Or-Vi reference point in order to manage the intra NFVI-PoP data flow mirroring during the lifecycle of a NS. |
Stage2:
============= Mega CRs Approved ========
Stage3:
| ||
ENH02.04 | Invariant identification of NSD constituents | Release 4 | Stage 2 completed
Stage 3 completed |
Arturo Martin de Nicolas <arturo.martin-de-nicolas@ericsson.com > | This enhancement proposes to add the capability to identify the VNFDs, nested NSDs and PNFDs of an NSD by invariant identities, as an alternative option to the descriptor Ids.
The enhancement will avoid having to change and create a new NSD when its components (VNFDs, PNFDs or nested NSDs) are replaced by another version and this replacement does not require changes in the rest of the NSD. |
Stage2:
============= Mega CRs for approval========
Stage3:
| ||
ENH02.05 | Flexibility with scalable VNF/NS instantiation | Release 4 | Stage 2 completed
Stage 3 complete |
Rajavarma Bhyrraju <rajavarma.bhyrraju@ericsson.com> | The enhancement feature proposes to add scaleLevels as input during instantiation to support flexibility with scalable VNF/NS instantiation. The VNFs/NSs supporting flexible instantiations are identified with VNFD/NSD level attribute(s). This enhancement provides flexibility for the service providers to adjust instantiation level when instantiating a VNF and supports instantiate a VNF with required size in one single operation. | Stage2:
============= Mega CRs for approval========
Stage3:
| ||
ENH02.06 | Support for parameter mapping artifacts for MCIOP input | Release 5 | Arturo Martin de Nicolas <arturo.martin-de-nicolas@ericsson.com> | The enhancement adds support for artifacts in the VNF package tha perform the mapping between NFV parameters obtained from the API and input parameters to the cloud native templates (e.g. Helm charts). |