54
edits
Seminar on Internet Technologies (Winter 2017/2018): Difference between revisions
Seminar on Internet Technologies (Winter 2017/2018) (view source)
Revision as of 11:32, 26 October 2017
, 26 October 2017→Topics
(→Topics) |
(→Topics) |
||
| Line 107: | Line 107: | ||
|[http://ieeexplore.ieee.org/abstract/document/7547948/] | |[http://ieeexplore.ieee.org/abstract/document/7547948/] | ||
|- | |- | ||
| '''Towards SDN and NFV Fault Management and High Availability''' | | '''Towards SDN and NFV Fault Management and High Availability (assigned to Hesham Hosney) ''' | ||
Network Function Virtualisation (NFV), is gaining rapid momentum, but are they reliable? can they conform with the Telecom operators latency and availability requirements of Fine Nines or Six Nines? The focus of this work is to first study and understand the concerns with NFV in terms of their failures, what amount of availability can they support. Second, study the state-of-the-art in terms of techniques that have been provided in the Cloud and Data Center networks for the traditional Virtual Machine based approaches and make the clear distinction of what aspects can and cannot be adapted? and what are the characteristics of NFV that make them differ from traditional VM based solutions? and aspects and solutions that can be adapted to achieve scalability, efficiency, and reliability in the NFV environments. | Network Function Virtualisation (NFV), is gaining rapid momentum, but are they reliable? can they conform with the Telecom operators latency and availability requirements of Fine Nines or Six Nines? The focus of this work is to first study and understand the concerns with NFV in terms of their failures, what amount of availability can they support. Second, study the state-of-the-art in terms of techniques that have been provided in the Cloud and Data Center networks for the traditional Virtual Machine based approaches and make the clear distinction of what aspects can and cannot be adapted? and what are the characteristics of NFV that make them differ from traditional VM based solutions? and aspects and solutions that can be adapted to achieve scalability, efficiency, and reliability in the NFV environments. | ||
| Line 113: | Line 113: | ||
| [http://www.etsi.org/deliver/etsi_gs/NFV-REL/001_099/002/01.01.01_60/gs_NFV-REL002v010101p.pdf] [https://portal.etsi.org/Portals/0/TBpages/NFV/Docs/NFV_White_Paper3.pdf] [https://datatracker.ietf.org/rg/nfvrg/documents/] [https://www.opnfv.org] | | [http://www.etsi.org/deliver/etsi_gs/NFV-REL/001_099/002/01.01.01_60/gs_NFV-REL002v010101p.pdf] [https://portal.etsi.org/Portals/0/TBpages/NFV/Docs/NFV_White_Paper3.pdf] [https://datatracker.ietf.org/rg/nfvrg/documents/] [https://www.opnfv.org] | ||
|- | |- | ||
|'''Service Plane for Network Functions: Network Service Headers and Other alternatives''' | |'''Service Plane for Network Functions: Network Service Headers and Other alternatives (assigned to Gulzaib Amjad)''' | ||
Focus of this topic is to understand 'Service Function Chaining of Network Functions', the state-of-the-art proposals like Network Service Headers and related academic works. Reason and justify the need for service plane and then try to propose new mechanisms and design of the data plane to support network services, and the control plane functions necessary to manage these data plane functions. | Focus of this topic is to understand 'Service Function Chaining of Network Functions', the state-of-the-art proposals like Network Service Headers and related academic works. Reason and justify the need for service plane and then try to propose new mechanisms and design of the data plane to support network services, and the control plane functions necessary to manage these data plane functions. | ||