In OpenFlow, data and control plane are decoupled from switches or routers. While the data plane resides in the switches or routers, the control plane might be moved into one or more external servers (controllers). In this article, we propose verification mechanisms for the data plane functionality of switches. The latter consists of two parts: (1) Flow-Match Header part (to match a flow of incoming packets) and (2) action part (e.g., to forward incoming packets to an outgoing port). We propose a mechanism to verify the Flow-Match Header part of the data plane. The mechanism can be executed at the controller, or on an additional device or server (or virtual machines) attached to the network. Deploying a virtual machine (VM) or server for verification may decrease the load of the controller and/or consumed bandwidth between the controller and a switch. We propose a heuristic to place external verification devices or VMs in a network such that the verification time can be minimized. Verification time with respect to consumed resources are evaluated through emulation experiments. Results confirm that the verification time using the proposed heuristic is indeed shortened significantly, while requiring low bandwidth resources.
Sachin SHARMA
Ghent University
Wouter TAVERNIER
Ghent University
Sahel SAHHAF
Ghent University
Didier COLLE
Ghent University
Mario PICKAVET
Ghent University
Piet DEMEESTER
Ghent University
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Copy
Sachin SHARMA, Wouter TAVERNIER, Sahel SAHHAF, Didier COLLE, Mario PICKAVET, Piet DEMEESTER, "Verification of Flow Matching Functionality in the Forwarding Plane of OpenFlow Networks" in IEICE TRANSACTIONS on Communications,
vol. E98-B, no. 11, pp. 2190-2201, November 2015, doi: 10.1587/transcom.E98.B.2190.
Abstract: In OpenFlow, data and control plane are decoupled from switches or routers. While the data plane resides in the switches or routers, the control plane might be moved into one or more external servers (controllers). In this article, we propose verification mechanisms for the data plane functionality of switches. The latter consists of two parts: (1) Flow-Match Header part (to match a flow of incoming packets) and (2) action part (e.g., to forward incoming packets to an outgoing port). We propose a mechanism to verify the Flow-Match Header part of the data plane. The mechanism can be executed at the controller, or on an additional device or server (or virtual machines) attached to the network. Deploying a virtual machine (VM) or server for verification may decrease the load of the controller and/or consumed bandwidth between the controller and a switch. We propose a heuristic to place external verification devices or VMs in a network such that the verification time can be minimized. Verification time with respect to consumed resources are evaluated through emulation experiments. Results confirm that the verification time using the proposed heuristic is indeed shortened significantly, while requiring low bandwidth resources.
URL: https://global.ieice.org/en_transactions/communications/10.1587/transcom.E98.B.2190/_p
Copy
@ARTICLE{e98-b_11_2190,
author={Sachin SHARMA, Wouter TAVERNIER, Sahel SAHHAF, Didier COLLE, Mario PICKAVET, Piet DEMEESTER, },
journal={IEICE TRANSACTIONS on Communications},
title={Verification of Flow Matching Functionality in the Forwarding Plane of OpenFlow Networks},
year={2015},
volume={E98-B},
number={11},
pages={2190-2201},
abstract={In OpenFlow, data and control plane are decoupled from switches or routers. While the data plane resides in the switches or routers, the control plane might be moved into one or more external servers (controllers). In this article, we propose verification mechanisms for the data plane functionality of switches. The latter consists of two parts: (1) Flow-Match Header part (to match a flow of incoming packets) and (2) action part (e.g., to forward incoming packets to an outgoing port). We propose a mechanism to verify the Flow-Match Header part of the data plane. The mechanism can be executed at the controller, or on an additional device or server (or virtual machines) attached to the network. Deploying a virtual machine (VM) or server for verification may decrease the load of the controller and/or consumed bandwidth between the controller and a switch. We propose a heuristic to place external verification devices or VMs in a network such that the verification time can be minimized. Verification time with respect to consumed resources are evaluated through emulation experiments. Results confirm that the verification time using the proposed heuristic is indeed shortened significantly, while requiring low bandwidth resources.},
keywords={},
doi={10.1587/transcom.E98.B.2190},
ISSN={1745-1345},
month={November},}
Copy
TY - JOUR
TI - Verification of Flow Matching Functionality in the Forwarding Plane of OpenFlow Networks
T2 - IEICE TRANSACTIONS on Communications
SP - 2190
EP - 2201
AU - Sachin SHARMA
AU - Wouter TAVERNIER
AU - Sahel SAHHAF
AU - Didier COLLE
AU - Mario PICKAVET
AU - Piet DEMEESTER
PY - 2015
DO - 10.1587/transcom.E98.B.2190
JO - IEICE TRANSACTIONS on Communications
SN - 1745-1345
VL - E98-B
IS - 11
JA - IEICE TRANSACTIONS on Communications
Y1 - November 2015
AB - In OpenFlow, data and control plane are decoupled from switches or routers. While the data plane resides in the switches or routers, the control plane might be moved into one or more external servers (controllers). In this article, we propose verification mechanisms for the data plane functionality of switches. The latter consists of two parts: (1) Flow-Match Header part (to match a flow of incoming packets) and (2) action part (e.g., to forward incoming packets to an outgoing port). We propose a mechanism to verify the Flow-Match Header part of the data plane. The mechanism can be executed at the controller, or on an additional device or server (or virtual machines) attached to the network. Deploying a virtual machine (VM) or server for verification may decrease the load of the controller and/or consumed bandwidth between the controller and a switch. We propose a heuristic to place external verification devices or VMs in a network such that the verification time can be minimized. Verification time with respect to consumed resources are evaluated through emulation experiments. Results confirm that the verification time using the proposed heuristic is indeed shortened significantly, while requiring low bandwidth resources.
ER -