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.
Highlights
Software-Defined Networking (SDN) is a paradigm that separates network‟s control logic from the underlying hardware
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
RESTCONF is a model describes a Representational State Transfer (REST)-like protocol that provides a programmatic interface over HTTP for accessing data defined in YANG, using the datastores defined in NETCONF [19]
Summary
Software-Defined Networking (SDN) is a paradigm that separates network‟s control logic from the underlying hardware (e.g., routers, switches etc.). This open entity enables the network application ecosystem. The goal is to explore what applications do, describe their data model, and what they require from SDN controller; 3) to provide recommendations to industry on required actions At this moment, there is no “standard” document that will describe the common requirements to Northbound (application level) API. The whole idea of this paper is to discuss the need for application level API for SDN, as well as the possible model for such standard. There are several attempts to create a unified application level program interfaces for telecommunication services Because this area is very close to SDN, it would be interesting to discuss re-usage of the telecom experience (in the terms of APIs) for SDN. The key question is: what should be included in basic requirements for application level API and how can we reuse existing unified APIs?
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Advanced Computer Science and Applications
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
