Architecture for a distributed openflow controller

Yazici, Volkan; Sunay, M.O.; Ercan, Ali

doi:10.1109/siu.2012.6204831

Cited by 6 publications

(9 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In addition, network devices in an NFVI require collaboration to be able to provide services, which cannot currently be provided by SDN. There is therefore still a need to improve SDN by considering distributed architectures [68], [69]. It may also be important for TSPs, InPs and ETSI to consider other possible solutions such as NETCONF [70].…”

Section: B Software Defined Networking (Sdn)mentioning

confidence: 99%

Network Function Virtualization: State-of-the-Art and Research Challenges

Mijumbi

Serrat

Gorricho

et al. 2016

IEEE Commun. Surv. Tutorials

1,583

773

View full text Add to dashboard Cite

Abstract-Network Function Virtualization (NFV) has drawn significant attention from both industry and academia as an important shift in telecommunication service provisioning. By decoupling Network Functions (NFs) from the physical devices on which they run, NFV has the potential to lead to significant reductions in Operating Expenses (OPEX) and Capital Expenses (CAPEX) and facilitate the deployment of new services with increased agility and faster time-to-value. The NFV paradigm is still in its infancy and there is a large spectrum of opportunities for the research community to develop new architectures, systems and applications, and to evaluate alternatives and trade-offs in developing technologies for its successful deployment. In this paper, after discussing NFV and its relationship with complementary fields of Software Defined Networking (SDN) and cloud computing, we survey the state-of-the-art in NFV, and identify promising research directions in this area. We also overview key NFV projects, standardization efforts, early implementations, use cases and commercial products.

show abstract

Section: B Software Defined Networking (Sdn)mentioning

confidence: 99%

Network Function Virtualization: State-of-the-Art and Research Challenges

Mijumbi

Serrat

Gorricho

et al. 2016

IEEE Commun. Surv. Tutorials

1,583

773

View full text Add to dashboard Cite

show abstract

“…Yazici et al 69 suggest a cluster‐based distributed paradigm in which a master controller is chosen based on the network load such that, in the event of an increase in demand, the master node can be moved to a less burdened one.…”

Section: Controller Placement Problemmentioning

confidence: 99%

Controller placement problem during SDN deployment in the ISP/Telco networks: A survey

Sapkota,

Dawadi,

Joshi

2023

Engineering Reports

View full text Add to dashboard Cite

With the successful implementation of Software‐Defined Networking (SDN) in data center networking, the way forward for its deployment in the ISP/Telco network is becoming prominent. Small and medium‐sized networks may easily adopt SDN. The research on SDN deployment and implementation for a large‐scale network is continuing. This paper properly presents the current research status of Controller Placement Problem (CPP) and Multi‐CPP (MCPP) over SDN with their specific challenges and provides a comprehensive review of the major performance metrics, that is, latency, and controller load balancing techniques. This survey highlights the use of network partitioning‐based CPP and clustering approaches and their benefits in the context of SDN deployment. Moreover, this paper highlights the importance of implementing SDN and SDN security issues into ISP/Telco networks. Finally, we provide some key areas of ongoing research and discuss the future research direction regarding the various SDN‐based Controller Placement (CP) issues in the next‐generation IP and advanced networking technologies.

show abstract

“…In Reference , the authors propose a coordination framework on top of the control plane to allow controllers working as controller clusters by supporting the communication among controllers via the communication library JGroups . In this framework, the controllers elect a master node in the controller cluster, which conducts and maintains the global controller‐switch mapping in the network.…”

Section: Securing Sdn Controllermentioning

confidence: 99%

A comprehensive 3‐dimensional security analysis of a controller in software‐defined networking

Tseng

Naït‐Abdesselam

Khokhar

2018

Security and Privacy

View full text Add to dashboard Cite

Software-defined networking (SDN) has recently emerged as a novel networking paradigm that enables network administrators to manage network services through high-level abstraction of networking functions. This is achieved by mainly decoupling the control plane from the data plane. The control plane, namely the SDN controller, makes dynamic decisions on where traffic is sent in the underlying systems that forward data to the selected destinations. The SDN controller, seen as a networking operating system, acts, therefore, as the brain in SDN. Consequently, its importance makes it a privileged new target for future attackers. In order to have a comprehensive security assessment of the SDN controller, we conducted a 3-dimensional analysis to study the security of OpenFlow-based SDN controllers. This study includes: (1) the essential components of a controller, (2) the characteristics provided by a controller, and (3) the STRIDE model. At the end, we also summarized 9 principles that are necessary to secure an SDN controller from the reported attacks and analyzed the security of 5 active open-source controllers following those principles. KEYWORDSOpenFlow, SDN, SDN controller, security INTRODUCTIONSoftware-defined networking (SDN) is as susceptible to attacks as traditionally managed networks. A long and continuous series of attacks have revealed many areas of network vulnerability. The SDN controller is a key to any software-defined network and offers attackers a target not present in earlier network technologies. Clearly, any successful attack on the controller will halt or disrupt network operations. 1 To address this problem, some researchers have proposed to harden the SDN control plane. For example, FortNOX 2 hardens the kernel of the SDN controller (NOX) to avoid malicious rule injection from the application plane. Extending FortNOX, SE-Floodlight 3 enhances the security of the overall control plane through authentication, role authorization, and network application operation auditing. Rosemary 4 isolates the net-app from the control plane via interprocess communication (IPC), which enables the SDN controller to be immune from resource exhaustion attacks. Moreover, the distributed controllers have also been proposed for providing a more scalable control plane, such as ONOS, 5 Onix, 6 Kandoo, 7 and the 3-level controller architecture for IoT (Internet of things). 8 Moreover, a distributed architecture brings new challenges for data consistency between controllers. 9 However, the SDN controller remains vulnerable to many threats, such as data inconsistency, OpenFlow messages flooding, topology spoofing, malicious scanning, etc. Hence, the motivation of this work is to provide a clear view in order to evaluate the security of the control plane. A number of surveys on SDN/OpenFlow security also precede this analysis such as References 10-16. Reference 13 adopts STRIDE to evaluate the security of SDN. Conversely, Reference 17 uses STRIDE to evaluate the security of the Security Privacy. 2018;1:e21.wileyonlinelibrar...

show abstract

Architecture for a distributed openflow controller

Cited by 6 publications

References 3 publications

Network Function Virtualization: State-of-the-Art and Research Challenges

Network Function Virtualization: State-of-the-Art and Research Challenges

Controller placement problem during SDN deployment in the ISP/Telco networks: A survey

A comprehensive 3‐dimensional security analysis of a controller in software‐defined networking

Contact Info

Product

Resources

About