PARD: Hybrid Proactive and Reactive Method Eliminating Flow Setup Latency in SDN
- PDF / 1,074,839 Bytes
- 28 Pages / 439.37 x 666.142 pts Page_size
- 9 Downloads / 177 Views
PARD: Hybrid Proactive and Reactive Method Eliminating Flow Setup Latency in SDN Michal Rzepka1 · Piotr Borylo1 · Artur Lason1 · Andrzej Szymanski1 Received: 4 March 2019 / Revised: 18 June 2020 / Accepted: 23 June 2020 © The Author(s) 2020
Abstract Advantages of Software Defined Networking are unquestionable and are widely described in numerous scientific papers, business white papers and press articles. However, to achieve full maturity, crucial impediments to this concept and its shortcomings must be overcame. One of the most important issues regards significant setup latency of a new flow. To address this issue we propose PARD: a hybrid proactive and reactive method to manage flow table entries. Additional advantages of the proposed solution are, among the others, its ability to preserve all capabilities of Software Defined Networking, utilization of multiple flow tables, a possibility to employ fine-grained traffic engineering and, finally, compatibility with existing protocol and hardware design. It is shown that the proposed solution is able to significantly reduce latency of first packets of a new flow, which directly impacts packet loss and perceived throughput. Thus, our solution is expected to enable a wide deployment of Software Defined Networking concept without any need for protocol changes or, what is extremely important, hardware modifications. Keywords SDN · Network management · Flow setup · Control plane · OpenFlow · Network performance
* Michal Rzepka [email protected] Piotr Borylo [email protected] Artur Lason [email protected] Andrzej Szymanski [email protected] 1
Department of Telecommunications, AGH University of Science and Technology, Krakow, Poland
13
Vol.:(0123456789)
Journal of Network and Systems Management
1 Introduction The main paradigm of Software Defined Networking (SDN) is to separate a control plane from a data plane. The control plane is implemented in a form of a logically centralized entity called an SDN controller while the data plane is composed of simplified forwarding devices, called SDN switches. Hence, a communication channel between the planes and an appropriate protocol is required. The OpenFlow Protocol (OFP) is designed for this purpose. Through the OFP the SDN controller sends, among the others, entries to be placed in switches’ flow tables in order to implement globally scoped routing policies, which is in contrast to the suboptimal hop-by-hop approach. Thanks to centralized nature of the SDN, the policies may easily be managed by a network administrator or automatically programmed by external applications integrated with the controller [1]. Programmability, combined with controller’s global knowledge about network state, together with an abstraction of network layer exposed to the external applications, becomes the main advantage of the SDN concept which follows the network softwareization process. The aforementioned architecture is illustrated in Fig. 1. Despite opening attractive perspectives for network operators, SDN also raises numero
Data Loading...
