The Impact on Security due to the Vulnerabilities Existing in the network a Strategic Approach towards Security

Software Defined Networking, the emerging technology is taking the network sector to a new variant. Networking sector completely focused on hardware infrastructure is now moving towards software programming. Due to an exponential growth in the number of user and the amount of information over wires, there arises a great risk with the existing IP Network architecture. Software Defined Networking paves a platform identifying a feasible solution to the problem by virtualization. Software Defined Networking provides a viable path in virtualization and managing the network resources in an “On Demand Manner”. This study is focused on the drawbacks of the existing technology and a fine grained introduction to Software Defined Networking. Further adding to the above topic, this study also passes over the current steps taken in the industrial sector in implementing Software Defined Networking. This study makes a walkthrough about the security features of Software Defined Networking, its advantages, limitations and further scope in identifying the loopholes in the security

Comparison of TCP/IP routing versus openflow table and implementation of intelligent computational model to provide autonomous behavior

© Springer International Publishing Switzerland 2015 Software-Defined Networking (SDN) is an emerging programmable network architecture, where network control plane is decoupled from forwarding plane. The first standardize communication interface defined between the controls and forwarding layers of the SDN architecture is known as OpenFlow. OpenFlow is a key enabler for SDN that allows direct manipulation on the forwarding plane of network devices. SDN forwarding methods are based on flows, through a protocol like OpenFlow, which operates in contrast to conventional networking device methods, such as TCP/IP routing table and MAC learning table. In more details, OpenFlow protocol has the same forwardingmethods to push L2-L4 functions which are simplified into a Flow-Table(s). This paper discusses the relationship between the processes of forwarding packets in conventional IP routing table versus OpenFlow-table. Then, the paper proposes the three phases of implementing aDistributed Active Information Model (DAIM) within OpenFlow to support an autonomic network management