Hardware Abstraction Layer as an SDN-enabler for Non-OpenFlow Network Equipment

Belter, Bartosz; Parniewicz, Damian; Ogrodowczyk, Łukasz; Binczewski, Artur; Stroiński, Maciej; Fuentes, Victor; Matias, Jon; Huarte, Maider; Jacob, Eduardo

doi:10.1109/ewsdn.2014.16

Cited by 10 publications

(10 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…LegacyFlow [527] extends the OpenFlowbased controlled network to embrace non-OpenFlow nodes. There are also some other early use cases on integrating complex legacy system such as DOCSIS [161], Gigabit Ethernet passive optical network and DWDM ROADM (Reconfigurable Optical Add/Drop Multiplexer) [157], [158]. The common grounds of these pieces of work are (1) considering hybrid as the coexistence of traditional environments of closed vendor's routers and switches with new OpenFlow-enabled devices; (2) targeting the interconnection of both control and data planes of legacy and new network elements; and (3) taking a controllercentric approach, drawing the hybrid line outside of any device itself, but into the controller application space.…”

Section: G Migration and Hybrid Deploymentsmentioning

confidence: 99%

“…Some of these efforts include new architectures for a smooth migration from the current mobile core infrastructure to SDN [222], and techno-economic models for virtualization of these networks [549], [550]; carrier-grade OpenFlow virtualization schemes [551], [112], including virtualized broadband access infrastructures [552], techniques that are allowing the offer of network-as-a-service [553]; programmable GE-PON and DWDM ROADM [157], [158], [159], [160]; largescale inter-autonomous systems (ASs) SDN-enabled deployments [554]; flexible control of network resources [555], including offering MPLS services using an SDN approach [556]; and the investigation of novel network architectures, from proposals to separate the network edge from the core [557], [558], with the latter forming the fabric that transports packets as defined by an intelligent edge, to software-defined Internet exchange points [559], [526].…”

Section: H Meeting Carrier-grade and Cloud Requirementsmentioning

confidence: 99%

“…There are other API proposals such as ForCES [30], OVSDB [153], POF [31], [120], OpFlex [154], OpenState [155], Revised OpenFlow Library (ROFL) [156], Hardware Abstraction Layer (HAL) [157], [158], and Programmable Abstraction of Datapath (PAD) [159]. ForCES proposes a more flexible approach to traditional network management without changing the current architecture of the network, i.e., without the need of a logically-centralized external controller.…”

Section: B Layer Ii: Southbound Interfacesmentioning

confidence: 99%

“…HAL [157], [158] is not exactly a southbound API, but is closely related. Differently from the aforementioned approaches, HAL is rather a translator that enables a southbound API such as OpenFlow to control heterogeneous hardware devices.…”

Section: B Layer Ii: Southbound Interfacesmentioning

confidence: 99%

See 3 more Smart Citations

Software-Defined Networking: A Comprehensive Survey

et al. 2015

View full text Add to dashboard Cite

Abstract-The Internet has led to the creation of a digital society, where (almost) everything is connected and is accessible from anywhere. However, despite their widespread adoption, traditional IP networks are complex and very hard to manage. It is both difficult to configure the network according to predefined policies, and to reconfigure it to respond to faults, load and changes. To make matters even more difficult, current networks are also vertically integrated: the control and data planes are bundled together. Software-Defined Networking (SDN) is an emerging paradigm that promises to change this state of affairs, by breaking vertical integration, separating the network's control logic from the underlying routers and switches, promoting (logical) centralization of network control, and introducing the ability to program the network. The separation of concerns introduced between the definition of network policies, their implementation in switching hardware, and the forwarding of traffic, is key to the desired flexibility: by breaking the network control problem into tractable pieces, SDN makes it easier to create and introduce new abstractions in networking, simplifying network management and facilitating network evolution.In this paper we present a comprehensive survey on SDN. We start by introducing the motivation for SDN, explain its main concepts and how it differs from traditional networking, its roots, and the standardization activities regarding this novel paradigm. Next, we present the key building blocks of an SDN infrastructure using a bottom-up, layered approach. We provide an in-depth analysis of the hardware infrastructure, southbound and northbound APIs, network virtualization layers, network operating systems (SDN controllers), network programming languages, and network applications. We also look at cross-layer problems such as debugging and troubleshooting. In an effort to anticipate the future evolution of this new paradigm, we discuss the main ongoing research efforts and challenges of SDN. In particular, we address the design of switches and control platforms -with a focus on aspects such as resiliency, scalability, performance, security and dependability -as well as new opportunities for carrier transport networks and cloud providers. Last but not least, we analyze the position of SDN as a key enabler of a software-defined environment.

show abstract

Section: G Migration and Hybrid Deploymentsmentioning

confidence: 99%

Section: H Meeting Carrier-grade and Cloud Requirementsmentioning

confidence: 99%

Section: B Layer Ii: Southbound Interfacesmentioning

confidence: 99%

Section: B Layer Ii: Southbound Interfacesmentioning

confidence: 99%

See 2 more Smart Citations

Software-Defined Networking: A Comprehensive Survey

et al. 2015

View full text Add to dashboard Cite

show abstract

“…Although SDN and OpenFlow started as an academic experiment [12], they gained significant traction in the industry over the past few years. Most vendors of commercial switches now include support of the OpenFlow API in their equipment [13].…”

Section: Related Workmentioning

confidence: 99%