Changes between Version 80 and Version 81 of nfvrg


Ignore:
Timestamp:
Jul 8, 2016, 12:52:27 AM (3 years ago)
Author:
diego@…
Comment:

Move descriptions of the near-term work items from the charter

Legend:

Unmodified
Added
Removed
Modified
  • nfvrg

    v80 v81  
    1818https://datatracker.ietf.org/rg/nfvrg/documents/
    1919
    20 == Near-Term Work Item Progress ==
     20== Near-Term Work Items ==
     21
     22The group shall focus on a concrete list of near-term work items. For each of the items mentioned below, the goal is to explore system architecture, optimization, and open interfaces across components, through experimental results, simulations, and/or real-world implementations.
     23
     24* '''Policy-based resource management'''. NFV Points of Presence (!PoPs) will be likely constrained in compute and storage capacity. Since practically all NFV !PoPs are foreseen to be distributed, inter-datacenter network capacity is an additional constraint as well. Additionally, energy consumption needs to be bounded, both as a general concern for NFV operators, and in particular for specific-purpose NFV !PoPs such as those in mobile base stations. Given these constraints and the highly complex and dynamic nature of the NFV environment, optimized resource management based on policy is a key factor for NFV deployments. Document editors for this work item are Róbert Szabó and Norival Figueira.
     25 
     26* '''Analytics for visibility and orchestration'''. In the spirit of NFV, network functions should be supportable on general purpose commodity hardware. Real-time monitoring providing insight into various components such as compute, storage, network, energy, and issues related to the cross-interactions among the deployed VNFs are key to not only providing visibility into the NFV infrastructure but also optimizing resource usage for the purposes of orchestration, by means of techniques applying real-time analytics
     27 
     28* '''Security and service verification'''. Driven by on-demand service offerings, NFV configuration is expected to be dynamic especially in the edge NFV PoP where capacity is limited. While autonomic networking techniques could be used to automate the configuration process including modular updates, it must be taken into account that incomplete and/or inconsistent configuration may lead to security and reliability issues. In the event of network and/or service degradation or failure, there must be suitable coordination, fail-over, and recovery. These reliable NFV mechanisms will also need tools and mechanisms to deploy and manage capability, and close coordination with NFV resource management and performance analytics is also expected. Elasticity of VNFs entails dynamic scale up/down/out/in that must be aware of general resiliency considerations. Finally, the envisaged deployment of arbitrary third-party VNF applications on the network infrastructure of service providers raises significant security concerns and poses challenges for VNF verification in terms of functionality, security and stability under well-defined procedures.
     29 
     30* '''Reliability and fault detection'''. Fault detection and isolation is a complex problem in the well-known non-NFV network deployments, and it becomes of at least an additional order of magnitude by the introduction of additional root causes for possible faults (hypervisors, containers, underlying infrastructure network, multi-vendor hardware etc.) and the dynamic nature of the NFV environment. In addition to addressing these challenges, a re-interpretation of the current practices in existing infrastructures is necessary, so fault detection becomes effective in mixed NFV and non-NFV networks, that will be the most common deployment in the foreseeable future.
     31 
     32* '''Service orchestration and lifecycle aspects'''. E2E service is the ultimate goal of any network technology, and NFV deployments must address these aspects to become part of the common practice of network programmers, designers and operators, leveraging commonalities with current cloud infrastructures. All aspects related to service operation and management must be considered, and in particular those that constitute the differentiation of NFV technologies  with respect to current non-NFV network deployments: descriptors and description artifacts, the integration with SDN design patterns, the applicability of DevOps and continuous integration, and the new FCAPS aspects induced by virtualization. Finally, the impact and advantages of new proposals around network management and operation, such as autonomic approaches and intent-based networking must be addressed as well.
     33 
     34* '''Real-time properties'''. While there is sufficient evidence that VNFs can provide an acceptable performance in practically all environments in which their application has been considered, there are still significative challenges regarding the monitoring, enforcement and management of real-time services based on NFV (a couple of examples could be VoLTE or augmented reality), and how the orchestration of these services has to be performed in order to guarantee those properties,not only at the initial deployment, but during the whole lifetime of the service. While there is sufficient evidence that VNFs can provide an acceptable performance in practically all environments in which their application has been considered, there are still significant challenges regarding the monitoring, enforcement and management of real-time services based on NFV (a couple of examples could be VoLTE or augmented reality), and how the orchestration of these services has to be performed in order to guarantee those properties, not only at the initial deployment, but during the whole lifetime of the service.
     35
     36== Appendix - Accomplishments of the team in the area of NFV ==
     37
     38=== White papers ===
     39
     40“ETSI NFV White Paper,” http://portal.etsi.org/NFV/NFV_White_Paper.pdf
     41
     42“ETSI NFV White Paper Update,” http://portal.etsi.org/NFV/NFV_White_Paper2.pdf
     43
     44=== Research papers ===
     45
     46“Behavioral Security Threat Detection Strategies for Data Center Switches and Routers,” IEEE International Workshop on Data Center Performance (DCPerf'14) – Published - http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6888844
     47
     48"Analysis of Data Center SDN Controller Architectures: Technology and Business Impacts," IEEE International Conference on Computing, Networking and Communications (ICNC) 2015 - Accepted
     49
     50"SDN Multi-Domain Orchestration and Control: Challenges and Innovative Future Directions," IEEE International Conference on Computing, Networking and Communications (ICNC) 2015 Workshop - Accepted
     51
     52"An Open NFV and Cloud Architectural Framework for Managing Application Virality Behaviour," IEEE Consumer Communications and Networking Conference (CCNC) 2015 - Published
     53
     54=== Conference & Journal Activities ===
     55
     56“Editor for special issue on Network and Service Virtualization,” IEEE Communications Magazine, http://www.comsoc.org/files/Publications/Magazines/ci/cfp/cfpcommag0215.html
     57
     58“Chairing special areas in communications track symposium on NFV,” IEEE Global Communications Conference (Globecom) 2015 in San Diego.
     59
     60“Resource Management Considerations for NFV and Cloud Systems," IEEE Communications Magazine NFV symposium – Submitted
     61
     62“Increasing Network and Energy Efficiency via Optimized NFV Placement in Openstack Clouds,” OpenStack Summit Atlanta 2014, http://www.slideshare.net/ybudupi/optimized-nfv-placement-in-openstack-clouds, https://www.youtube.com/watch?v=7QzDbhkk-BI
     63
     64"NFV Data Center Research – A Call for Participation," DCPerf 2014 Workshop Keynote @ ICDCS, Madrid, Spain, http://www.zurich.ibm.com/pdf/dcperf14/DCPerf14-Krishnaswamy.pdf
     65
     66=== Internet Drafts ===
     67
     68"An Open NFV Architectural Framework for Virality Based Content Caching," http://datatracker.ietf.org/doc/draft-krishnan-nfvrg-open-nfv-virality/
     69
     70=== ETSI NFV Proof of Concept Demonstrations ===
     71
     72“VNF Router Performance with DDoS Functionality,” http://nfvwiki.etsi.org/index.php?title=VNF_Router_Performance_with_DDoS_Functionality
     73
     74“VNF Router Performance with Hierarchical Quality of Service Functionality,” http://nfvwiki.etsi.org/index.php?title=VNF_Router_Performance_with_Hierarchical_Quality_of_Service_Functionality
     75
     76"Virality based content caching in NFV Framework,"
     77http://nfvwiki.etsi.org/index.php?title=Virality_based_content_caching_in_NFV_framework
     78
     79“ForCES Applicability for NFV and integrated SDN,” http://nfvwiki.etsi.org/index.php?title=ForCES_Applicability_for_NFV_and_integrated_SDN
     80
     81“Virtualized Mobile Network with Integrated DPI,” http://nfvwiki.etsi.org/index.php?title=Virtualised_Mobile_Network_with_Integrated_DPI
    2182
    2283'''''Policy based Resource Management'''''[[BR]]