Software-Defined Networking – Literature review Example

Download full paperFile format: .doc, available for editing

The paper “ Software-Defined Networking” is a thoughtful example of a literature review on information technology. Nowadays, networked computer systems demands have dramatically taken a complete turn from the basic hosting of applications on a server to more sophisticated computing environments such as remote data storage devices, and cloud-based networks. Meanwhile, such advanced computing environments demand more advanced planning methods, more computing resources as well as more labor. In a bid to quickly reconfigure and design the way resources or data is handled within a network, developers, and network programmers have come up with Software-Defined Networking (SDN) which is one of the latest networking architecture using standardized application programming interfaces (API) [1].

With the use of API, it is possible to quickly interface and reconfigure the network, its components such as switches and pull data as instructed via network applications the likes of email systems. Apparently, SDN has brought significant changes and improvements in computer networking, which makes it imperative to understand its unique benefits through a review of literature as well as some of the security issues facing SDN.

Furthermore, owing to the security issues that will be identified, it becomes crucial to propose a theoretical security framework. Literature ReviewGladish & Kellerer conducted a study with the aim of understanding the relationship between SND and Network Function Virtualization, especially in their application [2]. Over the past decade, Gladisch & Kellerer claims that there have been complaints regarding the complexity of the internet, limited mobility, limited security integration in the Internet architecture as well as laxity in innovation [2]. To curb these problems in the usage of the internet, a Clean Slate Program was started at Stanford University aims to enhance Open Flow and SDN, improving data center networks, mobile internet, and social networking.

The initial proposal towards Software Defined Networking was separating control and forwarding in networks as well as develop a program that would enable the control plane to adopt an open software architecture. The result of the initiative was that serve performance and computing became more powerful. Apparently, for the first time, open stack 3 enabled server virtualization and data centers to realize multiple vendor-driven initiatives [2]. Furthermore, since mobile networks require run virtualized network functions such as packet inspections and gateways in a simplified manner, the adoption of SDN and network function virtualization offers the plausible concepts that are integral in realizing this aspect.   Kirkpatrick conducted research to determine the effectiveness of software-defined networking in enabling programmers to quickly reconfigure network resource usage [3].

Kirkpatrick claims that regarding the way mobile applications are built, it is possible to think the idea of SDN as somehow analogous. The truth is, using SDN, it is possible to reach via network switches through an application programming interface reconfiguring the network’ s resources to suits the needs of the programmer [3].

Depending on the manner in which switches are deployed, it becomes quicker to reprogram. This I contrary to the traditional ways where dedicated switches dominated the process through which data was transmitted, in a bid to direct various packets between the connected devices. Apparently, the switches come in two planes the first one being the forwarding plane also known as the data plane. The task of the data plane is the routing of data packets to the network destination.

Secondly, there is the control plane. The control plane plays the role of creating the routing tables, responsible for determining how various packets reach or are sent to their respective destinations. Furthermore, the control plane manages connections between switches and as well is responsible for defining the quality of service and handling exceptions and errors from a variety of packets.      

References

List of References

[1]M. Dabbagh, B. Hamdaoui, M. Guizani, and A. Rayes, "Software-defined networking security: pros and cons", IEEE Commun. Mag., vol. 53, no. 6, pp. 73-79, 2015.

[2]A. Gladish and W. Kellerer, "Software-defined networking and network function virtualization", it - Information Technology, vol. 57, no. 5, 2015.

[3]K. Kirkpatrick, "Software-defined networking", Communications of the ACM, vol. 56, no. 9, p. 16, 2013.

[4]M. Klepac, T. Her and L. Bohac, "Enhancing Availability of Services Using Software-Defined Networking", AEEE, vol. 13, no. 5, 2015.

[5]Z. Shu, J. Wan, D. Li, J. Lin, A. Vasilakos and M. Imran, "Security in Software-Defined Networking: Threats and Countermeasures", Mobile Networks and Applications, 2016.

Download full paperFile format: .doc, available for editing
Contact Us