Flávio de Oliveira Silva, J. H. S. Pereira, P. F. Rosa, S. Kofuji
Internet core protocols were designed in the seventies and after four decades and a huge success, most of that initial design is still in place. As stated by Moore's law, current digital devices offer a huge processing capacity when compared to the computational resources of the early Internet. Moreover, physical links, wired or not, offer great connectivity and high throughput capacity. New applications bring a new set of requirements that the Internet is not able to satisfy in a proper way. The Internet architecture must be reviewed and several research groups are engaged in this design. Software Defined Networking (SDN), currently materialized in OpenFlow, represents an extraordinary opportunity to rethink computer networks, enabling the design and deployment of a future Internet. This paper presents SDN based technologies available, describes some research initiatives and discusses how the research community can use them to shape future Internet architecture.
{"title":"Enabling Future Internet Architecture Research and Experimentation by Using Software Defined Networking","authors":"Flávio de Oliveira Silva, J. H. S. Pereira, P. F. Rosa, S. Kofuji","doi":"10.1109/EWSDN.2012.24","DOIUrl":"https://doi.org/10.1109/EWSDN.2012.24","url":null,"abstract":"Internet core protocols were designed in the seventies and after four decades and a huge success, most of that initial design is still in place. As stated by Moore's law, current digital devices offer a huge processing capacity when compared to the computational resources of the early Internet. Moreover, physical links, wired or not, offer great connectivity and high throughput capacity. New applications bring a new set of requirements that the Internet is not able to satisfy in a proper way. The Internet architecture must be reviewed and several research groups are engaged in this design. Software Defined Networking (SDN), currently materialized in OpenFlow, represents an extraordinary opportunity to rethink computer networks, enabling the design and deployment of a future Internet. This paper presents SDN based technologies available, describes some research initiatives and discusses how the research community can use them to shape future Internet architecture.","PeriodicalId":127229,"journal":{"name":"2012 European Workshop on Software Defined Networking","volume":"2015 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125714499","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
C. Argyropoulos, D. Kalogeras, G. Androulidakis, B. Maglaris
The Passive Flow Monitoring (PaFloMon) framework aims at enriching OpenFlow (OF) platforms with user-aware passive monitoring tools. It thus complements user-oriented network programming of OF controllers with measurement capabilities offered to advanced users (slice owners), e.g. Future Internet researchers. PaFloMon provides per-slice monitoring plane isolation, extending control-plane slice isolation features of OF infrastructures, while it empowers users with monitoring toolsets, e.g. sFlow, Net Flow, widely employed in legacy networking systems. It is based on slice-centric statistics unilaterally described through an XML based Resource Specification schema (RSpec) and collected across Future Internet experimental facilities. The feasibility of slice-based monitoring is verified via sFlow trials in OpenFlow S/W (Open vSwitch) and H/W (NEC IP8800) platforms. PaFoMon can be easily integrated within OF control frameworks, notably the OFELIA framework being developed by the Future Internet Research & Experimentation program of the European Union.
被动流量监控(PaFloMon)框架旨在通过用户感知的被动监控工具丰富OpenFlow (OF)平台。因此，它补充了面向用户的网络编程的控制器与测量能力提供给高级用户(片所有者)，如未来的互联网研究人员。PaFloMon提供了每片监控平面隔离，扩展了of基础设施的控制平面切片隔离功能，同时它还为用户提供了监控工具集，例如sFlow, Net Flow，这些工具集广泛应用于传统网络系统。它基于通过基于XML的资源规范模式(RSpec)单方面描述的以片为中心的统计数据，并在Future Internet实验设施中收集。通过sFlow在OpenFlow S/W (Open vSwitch)和H/W (NEC IP8800)平台上的试验，验证了基于切片监测的可行性。PaFoMon可以很容易地集成到控制框架中，特别是由欧盟未来互联网研究与实验计划开发的OFELIA框架。
{"title":"PaFloMon -- A Slice Aware Passive Flow Monitoring Framework for OpenFlow Enabled Experimental Facilities","authors":"C. Argyropoulos, D. Kalogeras, G. Androulidakis, B. Maglaris","doi":"10.1109/EWSDN.2012.13","DOIUrl":"https://doi.org/10.1109/EWSDN.2012.13","url":null,"abstract":"The Passive Flow Monitoring (PaFloMon) framework aims at enriching OpenFlow (OF) platforms with user-aware passive monitoring tools. It thus complements user-oriented network programming of OF controllers with measurement capabilities offered to advanced users (slice owners), e.g. Future Internet researchers. PaFloMon provides per-slice monitoring plane isolation, extending control-plane slice isolation features of OF infrastructures, while it empowers users with monitoring toolsets, e.g. sFlow, Net Flow, widely employed in legacy networking systems. It is based on slice-centric statistics unilaterally described through an XML based Resource Specification schema (RSpec) and collected across Future Internet experimental facilities. The feasibility of slice-based monitoring is verified via sFlow trials in OpenFlow S/W (Open vSwitch) and H/W (NEC IP8800) platforms. PaFoMon can be easily integrated within OF control frameworks, notably the OFELIA framework being developed by the Future Internet Research & Experimentation program of the European Union.","PeriodicalId":127229,"journal":{"name":"2012 European Workshop on Software Defined Networking","volume":"60 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125797468","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
R. D. Corin, M. Gerola, R. Riggio, F. Pellegrini, E. Salvadori
In this paper we present Vertigo (Virtual Topologies Generalization in OpenFlow networks), a Software-defined networking platform designed for network virtualization. Based on the OpenFlow original network slicing system Flow Visor, the Vertigo platform aims at covering all flavors of network virtualization: in particular, it is able to expose a simple abstract node on one extreme, and to deliver a logically fully connected network at the very opposite end. In this work, we first introduce the Vertigo system architecture and its design choices, then we report on a prototypical implementation deployed over an OpenFlow-enabled test bed. Experimental results show that Vertigo can deliver flexible and reliable network virtualization services to a wide range of use cases in spite of failure and/or congestion at the underlying physical network.
在本文中，我们提出了Vertigo (Virtual topology Generalization In OpenFlow networks)，一个为网络虚拟化而设计的软件定义网络平台。Vertigo平台基于OpenFlow原始的网络切片系统Flow Visor，旨在覆盖所有类型的网络虚拟化:特别是，它能够在一个极端上暴露一个简单的抽象节点，并在相反的一端提供一个逻辑上完全连接的网络。在这项工作中，我们首先介绍了Vertigo系统架构及其设计选择，然后报告了在启用openflow的测试平台上部署的原型实现。实验结果表明，尽管底层物理网络出现故障和/或拥塞，Vertigo仍然可以为广泛的用例提供灵活可靠的网络虚拟化服务。
{"title":"VeRTIGO: Network Virtualization and Beyond","authors":"R. D. Corin, M. Gerola, R. Riggio, F. Pellegrini, E. Salvadori","doi":"10.1109/EWSDN.2012.19","DOIUrl":"https://doi.org/10.1109/EWSDN.2012.19","url":null,"abstract":"In this paper we present Vertigo (Virtual Topologies Generalization in OpenFlow networks), a Software-defined networking platform designed for network virtualization. Based on the OpenFlow original network slicing system Flow Visor, the Vertigo platform aims at covering all flavors of network virtualization: in particular, it is able to expose a simple abstract node on one extreme, and to deliver a logically fully connected network at the very opposite end. In this work, we first introduce the Vertigo system architecture and its design choices, then we report on a prototypical implementation deployed over an OpenFlow-enabled test bed. Experimental results show that Vertigo can deliver flexible and reliable network virtualization services to a wide range of use cases in spite of failure and/or congestion at the underlying physical network.","PeriodicalId":127229,"journal":{"name":"2012 European Workshop on Software Defined Networking","volume":"100 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125978668","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Bram Naudts, M. Kind, F. Westphal, S. Verbrugge, D. Colle, M. Pickavet
Worldwide mobile network operators have to spend billions to upgrade their own network to the latest standards for wireless communication of high-speed data for mobile phones (e.g. Long Term Evolution, LTE). This is in contrast with the decline in average revenue per user and threatens: (1) their profitability and (2) the fast adaptation of new standards. Investigating new mechanisms that can decrease the capital expenditures (capex) and operational expenditures (opex) of a mobile network is therefore essential. Enabling multiple mobile network operators on a common infrastructure is one such mechanism. Software defined networks can overcome this problem and a solution based on exploring OpenFlow (OF) as architecture for mobile network virtualization has been proposed. We investigate two network scenarios based on this OF solution in a techno-economic analysis: (scenario 1) software-defined, non-shared networks and (scenario 2) virtualized, shared networks and compare it against the current situation. By doing so, this paper provides insights on the relative cost savings that a mobile network operator can reach through Software Defined Networking (SDN) and network sharing. The techno-economic analysis indicates that SDN and virtualization of the first aggregation stage and second aggregation stage network infrastructure leads to substantial capex cost reductions for the mobile network operator. As a consequence, mobile network infrastructure virtualization through the use of OpenFlow could be one of the problem solvers to tackle the issue of rising costs and decreasing profitability. Still, we did not take into account the direct effect on operational expenditures and the indirect effect that network sharing can adversely affect the ability of the operators to differentiate themselves.
{"title":"Techno-economic Analysis of Software Defined Networking as Architecture for the Virtualization of a Mobile Network","authors":"Bram Naudts, M. Kind, F. Westphal, S. Verbrugge, D. Colle, M. Pickavet","doi":"10.1109/EWSDN.2012.27","DOIUrl":"https://doi.org/10.1109/EWSDN.2012.27","url":null,"abstract":"Worldwide mobile network operators have to spend billions to upgrade their own network to the latest standards for wireless communication of high-speed data for mobile phones (e.g. Long Term Evolution, LTE). This is in contrast with the decline in average revenue per user and threatens: (1) their profitability and (2) the fast adaptation of new standards. Investigating new mechanisms that can decrease the capital expenditures (capex) and operational expenditures (opex) of a mobile network is therefore essential. Enabling multiple mobile network operators on a common infrastructure is one such mechanism. Software defined networks can overcome this problem and a solution based on exploring OpenFlow (OF) as architecture for mobile network virtualization has been proposed. We investigate two network scenarios based on this OF solution in a techno-economic analysis: (scenario 1) software-defined, non-shared networks and (scenario 2) virtualized, shared networks and compare it against the current situation. By doing so, this paper provides insights on the relative cost savings that a mobile network operator can reach through Software Defined Networking (SDN) and network sharing. The techno-economic analysis indicates that SDN and virtualization of the first aggregation stage and second aggregation stage network infrastructure leads to substantial capex cost reductions for the mobile network operator. As a consequence, mobile network infrastructure virtualization through the use of OpenFlow could be one of the problem solvers to tackle the issue of rising costs and decreasing profitability. Still, we did not take into account the direct effect on operational expenditures and the indirect effect that network sharing can adversely affect the ability of the operators to differentiate themselves.","PeriodicalId":127229,"journal":{"name":"2012 European Workshop on Software Defined Networking","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124925713","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Software-defined networking and OpenFlow in particular enable independent development of network devices and software that controls them. Such separation of concerns eases the introduction of new network functionality, however, it leads to distributed responsibility for bugs. Despite the common interface, separate development entails the need to test an integrated network before deployment. In this work-in-progress paper, we identify the challenges of creating an environment that simplifies and systematically conducts such tests. We discuss optimizations required for efficient and reliable OpenFlow switch black-box testing and present a possible approach to address other challenges. In our preliminary prototype, we combine systematic state-space exploration techniques with real switches execution to explore an integrated network behavior. Our initial results show that such methods help detect previously unrevealed inconsistencies in the network.
{"title":"OFTEN Testing OpenFlow Networks","authors":"Maciej Kuźniar, M. Canini, Dejan Kostic","doi":"10.1109/EWSDN.2012.21","DOIUrl":"https://doi.org/10.1109/EWSDN.2012.21","url":null,"abstract":"Software-defined networking and OpenFlow in particular enable independent development of network devices and software that controls them. Such separation of concerns eases the introduction of new network functionality, however, it leads to distributed responsibility for bugs. Despite the common interface, separate development entails the need to test an integrated network before deployment. In this work-in-progress paper, we identify the challenges of creating an environment that simplifies and systematically conducts such tests. We discuss optimizations required for efficient and reliable OpenFlow switch black-box testing and present a possible approach to address other challenges. In our preliminary prototype, we combine systematic state-space exploration techniques with real switches execution to explore an integrated network behavior. Our initial results show that such methods help detect previously unrevealed inconsistencies in the network.","PeriodicalId":127229,"journal":{"name":"2012 European Workshop on Software Defined Networking","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122414276","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
J. Matías, Borja Tornero, A. Mendiola, E. Jacob, N. Toledo
Novel approaches for network virtualization at Layer 2 which are not based on VLAN have became a real possibility since the appearance of Software Defined Networking and OpenFlow in particular. We have deployed our own network virtualization facility based on Layer 2 prefixes using OpenFlow: the EHU OpenFlow Enabled Facility (EHU-OEF). We have implemented a solution that allows research and production traffic to share the same infrastructure without interfering with each other. It requires minimum configuration in the case of researchers and none in the case of non-technical users. In our deployment we found several challenges with Layer 2 protocols that use broadcast/multicast addresses due to the use of OpenFlow. In order to solve those challenges, we developed several custom modules for the OpenFlow controller and made some changes in the Flow Visor. Finally, the design of the EHU-OEF facility as well as some configuration details are described.
{"title":"Implementing Layer 2 Network Virtualization Using OpenFlow: Challenges and Solutions","authors":"J. Matías, Borja Tornero, A. Mendiola, E. Jacob, N. Toledo","doi":"10.1109/EWSDN.2012.18","DOIUrl":"https://doi.org/10.1109/EWSDN.2012.18","url":null,"abstract":"Novel approaches for network virtualization at Layer 2 which are not based on VLAN have became a real possibility since the appearance of Software Defined Networking and OpenFlow in particular. We have deployed our own network virtualization facility based on Layer 2 prefixes using OpenFlow: the EHU OpenFlow Enabled Facility (EHU-OEF). We have implemented a solution that allows research and production traffic to share the same infrastructure without interfering with each other. It requires minimum configuration in the case of researchers and none in the case of non-technical users. In our deployment we found several challenges with Layer 2 protocols that use broadcast/multicast addresses due to the use of OpenFlow. In order to solve those challenges, we developed several custom modules for the OpenFlow controller and made some changes in the Flow Visor. Finally, the design of the EHU-OEF facility as well as some configuration details are described.","PeriodicalId":127229,"journal":{"name":"2012 European Workshop on Software Defined Networking","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121503582","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
While OpenFlow enables the customization of the control plane of a router, currently no solutions are available for the customization of the data plane. This paper presents a prototype that offers to third parties (even end-users) the possibility to install their own applications on the data plane of a router, particularly the ones operating at the edge of the network. This paper presents the motivation of the idea, the reason why we use OpenFlow even if it does not seem appropriate for the data plane, the architecture and the implementation of our prototype, and a first characterization of the system running in our lab.
{"title":"Customizing Data-Plane Processing in Edge Routers","authors":"Fulvio Risso, Ivano Cerrato","doi":"10.1109/EWSDN.2012.14","DOIUrl":"https://doi.org/10.1109/EWSDN.2012.14","url":null,"abstract":"While OpenFlow enables the customization of the control plane of a router, currently no solutions are available for the customization of the data plane. This paper presents a prototype that offers to third parties (even end-users) the possibility to install their own applications on the data plane of a router, particularly the ones operating at the edge of the network. This paper presents the motivation of the idea, the reason why we use OpenFlow even if it does not seem appropriate for the data plane, the architecture and the implementation of our prototype, and a first characterization of the system running in our lab.","PeriodicalId":127229,"journal":{"name":"2012 European Workshop on Software Defined Networking","volume":"2013 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128949856","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
We propose a method to control Packet-In messages in OpenFlow switches for reducing CPU and network utilization of switches and controllers. In OpenFlow network, controllers setup flow entries to switches in response to Packet-In messages from switches. When a host suddenly starts to send many packets of a flow without any negotiation in advance, like a video stream on UDP, the control traffic and CPU utilization of switches and controllers become high until the flow entries are inserted into switches, and this high utilization would make network control unstable. In this paper, we propose a method to filter out unimportant Packet-In messages to reduce CPU utilization and the control traffic in OpenFlow switches and controllers. We categorize Packet-In messages into three groups, State Change, Flow Setup and Forward. Controllers process these messages to change the internal state of controllers, to trigger inserting flow entries, and to forward packets to other switches, respectively. Forward type of messages are less important than State Change and Flow Setup messages in terms of network control, because State Change and Flow Setup messages change states of network such as flow entries but Forward messages do not. We propose a method to identify Forward messages in switches by recording the header of Flow Setup packets and by matching packets with recorded flows. We have implemented our method into Open vSwitch to limit the bandwidth of Forward type of messages, and our evaluation shows that our method can control Packet-In messages with little CPU utilization overhead in the switch.
{"title":"Packet-In Message Control for Reducing CPU Load and Control Traffic in OpenFlow Switches","authors":"Daisuke Kotani, Y. Okabe","doi":"10.1109/EWSDN.2012.23","DOIUrl":"https://doi.org/10.1109/EWSDN.2012.23","url":null,"abstract":"We propose a method to control Packet-In messages in OpenFlow switches for reducing CPU and network utilization of switches and controllers. In OpenFlow network, controllers setup flow entries to switches in response to Packet-In messages from switches. When a host suddenly starts to send many packets of a flow without any negotiation in advance, like a video stream on UDP, the control traffic and CPU utilization of switches and controllers become high until the flow entries are inserted into switches, and this high utilization would make network control unstable. In this paper, we propose a method to filter out unimportant Packet-In messages to reduce CPU utilization and the control traffic in OpenFlow switches and controllers. We categorize Packet-In messages into three groups, State Change, Flow Setup and Forward. Controllers process these messages to change the internal state of controllers, to trigger inserting flow entries, and to forward packets to other switches, respectively. Forward type of messages are less important than State Change and Flow Setup messages in terms of network control, because State Change and Flow Setup messages change states of network such as flow entries but Forward messages do not. We propose a method to identify Forward messages in switches by recording the header of Flow Setup packets and by matching packets with recorded flows. We have implemented our method into Open vSwitch to limit the bandwidth of Forward type of messages, and our evaluation shows that our method can control Packet-In messages with little CPU utilization overhead in the switch.","PeriodicalId":127229,"journal":{"name":"2012 European Workshop on Software Defined Networking","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122225516","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Balázs Sonkoly, A. Gulyás, F. Németh, János Czentye, Krisztian Kurucz, Barnabas Novak, Gabor Vaszkun
OpenFlow is the most promising architecture for future Software Defined Networks (SDNs). However, from the aspects of large-scale or carrier-grade networks, it still lacks some key components. For example, QoS (Quality of Service) provisioning is an indispensable part of such production networks. During the evolution of the OpenFlow standard, some QoS capabilities have been added to the protocol, however, even the latest version has only a limited and not well-defined QoS framework. Hence, integrated QoS support is missing in current OpenFlow experimental test beds including Ofelia. This paper describes a possible architectural extension to Ofelia in order to make it capable of running QoS related experiments. We summarize the initial tasks regarding the survey of QoS features and limitations of OpenFlow switches deployed in Ofelia islands and the performance tests needed to characterize these devices. For extending the feature palette of Ofelia, we propose a QoS management platform with full integration into the existing management framework. By means of this envisioned extension, QoS settings of the whole Ofelia test bed can be adjusted easily, in a user friendly fashion. Moreover, we walk through the main steps needed not only towards an integrated OpenFlow test bed with QoS support but towards a QoS architecture to OpenFlow.
{"title":"On QoS Support to Ofelia and OpenFlow","authors":"Balázs Sonkoly, A. Gulyás, F. Németh, János Czentye, Krisztian Kurucz, Barnabas Novak, Gabor Vaszkun","doi":"10.1109/EWSDN.2012.26","DOIUrl":"https://doi.org/10.1109/EWSDN.2012.26","url":null,"abstract":"OpenFlow is the most promising architecture for future Software Defined Networks (SDNs). However, from the aspects of large-scale or carrier-grade networks, it still lacks some key components. For example, QoS (Quality of Service) provisioning is an indispensable part of such production networks. During the evolution of the OpenFlow standard, some QoS capabilities have been added to the protocol, however, even the latest version has only a limited and not well-defined QoS framework. Hence, integrated QoS support is missing in current OpenFlow experimental test beds including Ofelia. This paper describes a possible architectural extension to Ofelia in order to make it capable of running QoS related experiments. We summarize the initial tasks regarding the survey of QoS features and limitations of OpenFlow switches deployed in Ofelia islands and the performance tests needed to characterize these devices. For extending the feature palette of Ofelia, we propose a QoS management platform with full integration into the existing management framework. By means of this envisioned extension, QoS settings of the whole Ofelia test bed can be adjusted easily, in a user friendly fashion. Moreover, we walk through the main steps needed not only towards an integrated OpenFlow test bed with QoS support but towards a QoS architecture to OpenFlow.","PeriodicalId":127229,"journal":{"name":"2012 European Workshop on Software Defined Networking","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127408956","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Meral Shirazipour, Ying Zhang, N. Beheshti, Geoffrey Lefebvre, M. Tatipamula
Even though software-defined networking (SDN) and the OpenFlow protocol have demonstrated great practicality in the packet domain, there has been some hesitance in extending the OpenFlow specification to circuit and optical switched domains that constitute wide area multi-layer transport networks. This paper presents an overview of various proposals with regards to extending OpenFlow to support circuit switched multi-layer networks. The goal is to shed light on these ideas and propose a way forward. This paper favors a top-down approach, which relies on transport network's main SDN use case: packet-optical integration, to help identify the sufficient extensions for OpenFlow to support circuit/optical switching.
{"title":"OpenFlow and Multi-layer Extensions: Overview and Next Steps","authors":"Meral Shirazipour, Ying Zhang, N. Beheshti, Geoffrey Lefebvre, M. Tatipamula","doi":"10.1109/EWSDN.2012.22","DOIUrl":"https://doi.org/10.1109/EWSDN.2012.22","url":null,"abstract":"Even though software-defined networking (SDN) and the OpenFlow protocol have demonstrated great practicality in the packet domain, there has been some hesitance in extending the OpenFlow specification to circuit and optical switched domains that constitute wide area multi-layer transport networks. This paper presents an overview of various proposals with regards to extending OpenFlow to support circuit switched multi-layer networks. The goal is to shed light on these ideas and propose a way forward. This paper favors a top-down approach, which relies on transport network's main SDN use case: packet-optical integration, to help identify the sufficient extensions for OpenFlow to support circuit/optical switching.","PeriodicalId":127229,"journal":{"name":"2012 European Workshop on Software Defined Networking","volume":"66 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114711239","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：