When Open Source Meets Network Control Planes

Rothenberg, Christian Esteve; Chua, Roy Y. J.; Bailey, Josh; Winter, Martin; Corrêa, Carlos N. A.; Lucena, Sidney C. de; Salvador, M.R.; Nadeau, Thomas D.

doi:10.1109/mc.2014.340

Cited by 26 publications

(17 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…RouteFlow [525] implements an IP level control plane on top of an OpenFlow network, allowing the underlying devices to act as IP routers under different possible arrangements. The Cardigan project [526], [50] has deployed RouteFlow at a live Internet eXchange now for over a year. LegacyFlow [527] extends the OpenFlowbased controlled network to embrace non-OpenFlow nodes.…”

Section: G Migration and Hybrid Deploymentsmentioning

confidence: 99%

“…While some of the activities are being carried out in Standard Development Organizations (SDOs), other related efforts are ongoing at industrial or community consortia (e.g., OpenDaylight, OpenStack, OPNFV), delivering results often considered candidates for de facto standards. These results often come in the form of open source implementations that have become the common strategy towards accelerating SDN and related cloud and networking technologies [50]. The reason for this fragmentation is due to SDN concepts spanning different areas of IT and networking, both from a network segmentation point of view (from access to core) and from a technology perspective (from optical to wireless).…”

Section: Standardization Activitiesmentioning

confidence: 99%

“…APIs for security applications are likely to be different from those for routing or financial applications. One possible path of evolution for northbound APIs are vertically-oriented proposals, before any type of standardization occurs, a challenge the ONF has started to undertake in the NBI WG in parallel to open-source SDN developments [50]. The ONF architectural work [218] includes the possibility of northbound APIs providing resources to enable dynamic and granular control of the network resources from customer applications, eventually across different business and organizational boundaries.…”

Section: E Layer V: Northbound Interfacesmentioning

confidence: 99%

See 2 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: Standardization Activitiesmentioning

confidence: 99%

Section: E Layer V: Northbound Interfacesmentioning

confidence: 99%

See 1 more Smart Citation

Software-Defined Networking: A Comprehensive Survey

et al. 2015

View full text Add to dashboard Cite

show abstract

“…Shall we talk about different types of SDN applications and originally present Northbound API as a collection of problem-oriented APIs? We see that some like this is mentioned in open-source SDN development [9], but have not seen practical results in direction.…”

Section: ) Call Control Apis It Is How To Setup and Control Of Connmentioning

confidence: 96%

On Standards for Application Level Interfaces in SDN

Daradkeh¹,

Al‐Dhaifallah²,

Namiot³

et al. 2016

ijacsa

View full text Add to dashboard Cite

Abstract-In this paper, authors discuss application level interfaces for Software Defined Networks. While the Application Programming Interfaces for the interaction with the hardware are widely described in Software Defined Networks, the software interfaces for applications received far less attention. However, it is obvious that interfaces to software applications are very important. Actually, application level interfaces should be one of the main elements in Software Defined Networks. It is a core feature. In this article, we want to discuss the issues of standardization of software interfaces for applications in Software Defined Networks area. Nowadays, there are several examples of unified Application Program Interfaces in the telecommunications area. Is it possible to reuse this experience for Software Defined Networks or Software Defined Networks standards are radically different? This is the main question discussed in this paper.

show abstract

“…OpenFlow) and opensource controller platforms (e.g., OpenDaylight) allows running the same code in experiments using real networking environments. The vast amount of open source components in all layers of SDN [6] are to me among the most disruptive aspects of SDN, a term that is used today to encompass diverse modern networking approaches beyond the original OpenFlow split control model. Second, in operational environments, SDN abstractions through programmatic interfaces allow extensively testing the same code in a shadow environment prior to moving it to production.…”

Section: Christian Esteve Rothenbergmentioning

confidence: 99%