Hot Topics: Difference between revisions
| Line 28: | Line 28: | ||
| Q2 2015 | | Q2 2015 | ||
| [[CloudNFV Open NFV Framework Project|PoC#1]] [[Service Chaining for NW Function Selection in Carrier Networks|PoC#2]] [[Automated Network Orchestration|PoC#8]] [[SteerFlow: Multi-Layered Traffic Steering for Gi-LAN|PoC#13]] [[ForCES Applicability for NFV and integrated SDN|PoC#14]] | | [[CloudNFV Open NFV Framework Project|PoC#1]] [[Service Chaining for NW Function Selection in Carrier Networks|PoC#2]] [[Automated Network Orchestration|PoC#8]] [[SteerFlow: Multi-Layered Traffic Steering for Gi-LAN|PoC#13]] [[ForCES Applicability for NFV and integrated SDN|PoC#14]] | ||
[[Subscriber Aware SGi/Gi-LAN Virtualization|PoC#15]] [[NFVIaaS with Secure, SDN-controlled WAN Gateway|PoC#16]] [[Service Acceleration of NW Functions in Carrier Networks|PoC#19]] [[Network Intensive and Compute Intensive Hardware Acceleration|PoC#21]] [[E2E orchestration of virtualized LTE core-network functions and SDN-based dynamic service chaining of VNFs using VNF FG|PoC#23]] [[Virtual EPC with SDN Function in Mobile Backhaul Networks|PoC#26]] | [[Subscriber Aware SGi/Gi-LAN Virtualization|PoC#15]] [[NFVIaaS with Secure, SDN-controlled WAN Gateway|PoC#16]] [[Service Acceleration of NW Functions in Carrier Networks|PoC#19]] [[Network Intensive and Compute Intensive Hardware Acceleration|PoC#21]] [[E2E orchestration of virtualized LTE core-network functions and SDN-based dynamic service chaining of VNFs using VNF FG|PoC#23]] | ||
[[Virtual EPC with SDN Function in Mobile Backhaul Networks|PoC#26]] | |||
[[VoLTE Service based on vEPC and vIMS Architecture|PoC#27]] [[SDN Controlled VNF Forwarding Graph|PoC#28]] [[Full_ISO_7-layer_stack_fulfilment,_activation_and_orchestration_of_VNFs_in_carrier_networks|PoC#38]] | [[VoLTE Service based on vEPC and vIMS Architecture|PoC#27]] [[SDN Controlled VNF Forwarding Graph|PoC#28]] [[Full_ISO_7-layer_stack_fulfilment,_activation_and_orchestration_of_VNFs_in_carrier_networks|PoC#38]] | ||
|- | |- | ||
Revision as of 15:10, 7 July 2015
Rationale
The NFV HoT Topics concept has been created to complement the NFV PoC Framework with the following aspects:
• Improve the connection of NFV ISG specs with practical implementations in general and proofs of concept (PoCs) in particular.
• Enhance the relevance of PoC contributions to ISG NFV objectives and deliverables.
• Identify common concerns of different NFV ISG Working groups and focus on insights that might be useful to move forward.
NFV Hot Topics are identified, documented and consolidated by the ISG NFV Working Groups. Learn more about NFV Hot Topics
Current Hot Topics
| ID | Hot Topic | Status | WI(s) | PoC Feedback Template(s) | Deadline | Addressed by PoC(s) |
|---|---|---|---|---|---|---|
| HT#1 | HT#1 (EVE) Use of SDN in NFV architecture | Active | EVE005 | HT#1 FB Template | Q2 2015 | PoC#1 PoC#2 PoC#8 PoC#13 PoC#14
PoC#15 PoC#16 PoC#19 PoC#21 PoC#23 PoC#26 PoC#27 PoC#28 PoC#38 |
| HT#2 | HT#2 (TST) Test Methodology for NFV | Active | TST001, TST002 | HT#2 FB-TST001, HT#2 FB-TST002 | Q3 2015 | PoC#38 |
| HT#3 | HT#3 (REL) End-to-End Fault Correlation | Active | REL004 | HT#3 FB Template | Q2 2016 | PoC#38 |
| HT#4 | HT#4 (SEC) Lawful Interception | Active | SEC004, SEC009 | HT#4 FB Template | Q2 2016 |
Addressing a Hot Topic in a PoC
1. PoC teams interested in addressing a given hot topic will explicitly reflect it in their PoC Proposal (Section 2.5 – Expected PoC Contribution) by:
• Mentioning the Hot Topic that they want to address
• Committing in the PoC proposal to provide the information requested in the Hot Topic description
• Committing in the PoC proposal to notify the concerned WIs once the expected results are available in the form of a contribution (no need to wait until the final PoC Report is available). Some Hot Topics may provide a template to be filled in as part of this contribution.
• In case a PoC addresses more than one Hot Topic, the above procedure will apply for each of them.
2. The PoC Proposal will follow the regular procedure described in the PoC Framework for its acceptance. During the formal review of the PoC Proposal it will also be checked whether the information requested by the Hot Topic is effectively committed in the PoC Proposal. Once accepted, the PoC will be marked in the wiki as “WORKING on Hot Topic”.
3. On-going PoC Projects can also commit to address a Hot Topic and provide the requested information by submitting a revision of their PoC Proposal according to the above.
Feeding back the results
1. Once experimental results relevant for a given Hot Topic are available, the PoC Team will be in charge of creating a contribution and informing the affected WI (or WIs) and their WGs (if the Hot Topic had a specific template for feedback contributions, it should be used).
2. The WI/WG might require further clarifications to the PoC team until the PoC feedback is considered formally complete and useful for the targeted WI GS.
2. Once the PoC feedback has been completed by the concerned WG/WI, the PoC will be marked in the wiki as “CONTRIBUTOR to Hot Topic”.