Biblio

Software Defined Networking (SDN) is a programmable network technology which aims to move an existing controller role in hardware equipment into an area of software. The control layer employs an application programming interface (API) to communicate with the application and infrastructure layers as it is centered between two layers. As the Southbound API used in communication with the infrastructure layer, the OpenFlow is defined as the current de factor standard in most SDN controllers. In contrast, the Northbound API used in communication with the application layer had no standard. Only REST API is used in Floodlight or OpenDaylight. Thus, the development in application area where SDN's true value lies to achieve network intelligence is not promoted well enough. In this paper, a gRPC protocol is proposed as useable Northbound API rather than REST API used in some controllers, and applicability of new standard as Northbound API is investigated.

SDN (Software Defined Network) separates control plane from data plane (forwarding plane) which leads programmability of network and scalability, flexibility of existed network. nevertheless, the reason that security requirements had never considered during the initial design of SDN brought various security issues. And this security issues includes vulnerabilities (such as unauthorized access, data modification and leakage) and attacks (for example, DoS (Denial of Service) and MIITM (Main-in-the-Middle attack)). In this paper, we proposed SEaaS (Security as a Service) which can provide security within SDN environment. Also, we suggest authentication mechanism between application and controller among the various services of SEaaS.

In infrastructure wireless network technology, communication between users is provided within a certain area supported by access points (APs) or base station communication networks, but in ad-hoc networks, communication between users is provided only through direct connections between nodes. Ad-hoc network technology supports mobility directly through routing algorithms. However, when a connected node is lost owing to the node's movement, the routing protocol transfers this traffic to another node. The routing table in the node that is receiving the traffic detects any changes that occur and manages them. This paper proposes a routing protocol method that sets up multi-hops in the ad-hoc network and verifies the performance, which provides more effective connection persistence than existing methods.