Existing methods for traffic resilience at the network and transport layers typically work in isolation, often resorting to inference in fault detection and recovery respectively. This both duplicates functionality across layers, eroding efficiency, and leads to protracted recovery cycles, affecting responsiveness. Such misalignment is particularly at odds with the unprecedented concentration of traffic in data-centers, in which network and hosts are managed in unison. This paper advocates instead a cross-layer approach to traffic resilience. The proposed architecture, INFLEX, builds on the abstractions provided by software-defined networking (SDN) to maintain multiple virtual forwarding planes which the network assigns to flows. In case of path failure, transport protocols proactively request to switch plane in a manner which is unilaterally deployable by an edge domain, providing scalable end-to-end forwarding path resilience.
Year
2014
URL
Abstract
Summary
Proposes INFLEX, a cross-layer architecture that uses software-defined networking to maintain multiple virtual forwarding planes for traffic flows so that, on a path failure, transport protocols can proactively request a plane switch, avoiding the duplicated fault-detection and slow recovery that result from network and transport layers working in isolation — especially relevant to data-centre traffic where hosts and network are jointly managed.
bibtex
@inproceedings{araujo2014inflex,
author = {Jo\~ao Taveira Ara\'ujo and Raul Landa and Richard G. Clegg and George Pavlou},
title = {Software-defined network support for transport resilience},
booktitle = {2014 IEEE Network Operations and Management Symposium (NOMS)},
year = {2014},
pages = {1--8},
doi = {10.1109/noms.2014.6838243}
}
author = {Jo\~ao Taveira Ara\'ujo and Raul Landa and Richard G. Clegg and George Pavlou},
title = {Software-defined network support for transport resilience},
booktitle = {2014 IEEE Network Operations and Management Symposium (NOMS)},
year = {2014},
pages = {1--8},
doi = {10.1109/noms.2014.6838243}
}
Venue
2014 IEEE Network Operations and Management Symposium (NOMS), pp. 1-8