8.1 Northbound API concepts and protocols

The Northbound API is a crucial component in Software-Defined Networking, enabling communication between controllers and applications. This section dives into REST and RPC-based protocols, exploring how they facilitate network management and programmability in SDN environments.

We'll examine REST architecture principles, intent-based networking concepts, and specific implementations like NETCONF and gRPC. These protocols form the backbone of SDN controller interactions, allowing for dynamic configuration and efficient network control.

REST-based Protocols

RESTful API Architecture and Principles

Top images from around the web for RESTful API Architecture and Principles

• 

  rest - Restful API Design Document - Stack Overflow View original

  Is this image relevant?

• 

  rest - One web application using multiple RESTful APIs? - Stack Overflow View original

  Is this image relevant?

• 

  Rest API design, storing access tokens - Stack Overflow View original

  Is this image relevant?

• 

  rest - Restful API Design Document - Stack Overflow View original

  Is this image relevant?

• 

  rest - One web application using multiple RESTful APIs? - Stack Overflow View original

  Is this image relevant?

1 of 3

Top images from around the web for RESTful API Architecture and Principles

• 

  rest - Restful API Design Document - Stack Overflow View original

  Is this image relevant?

• 

  rest - One web application using multiple RESTful APIs? - Stack Overflow View original

  Is this image relevant?

• 

  Rest API design, storing access tokens - Stack Overflow View original

  Is this image relevant?

• 

  rest - Restful API Design Document - Stack Overflow View original

  Is this image relevant?

• 

  rest - One web application using multiple RESTful APIs? - Stack Overflow View original

  Is this image relevant?

1 of 3

• Northbound API enables communication between SDN controllers and applications
• REST API utilizes HTTP methods (GET, POST, PUT, DELETE) for resource manipulation
• Stateless communication characterizes REST, enhancing scalability and performance
• RESTCONF protocol extends NETCONF capabilities using HTTP-based RESTful APIs
• Resources in REST are identified by URIs, facilitating easy access and manipulation
• REST APIs typically use JSON or XML for data representation and exchange
• Idempotent operations in REST ensure consistent results regardless of multiple executions

Intent-based Networking and Abstraction

• Intent-based networking focuses on desired outcomes rather than specific configurations
• Network administrators define high-level policies translated into low-level configurations
• Application layer abstraction simplifies network management by hiding underlying complexities
• Intent-based systems use AI and machine learning to interpret and implement network policies
• Abstraction layers in SDN separate network functions from hardware implementations
• Intent-based networking improves network agility, reducing manual configuration errors
• Closed-loop systems in intent-based networking continuously monitor and adjust network state

REST API Implementation in SDN

• REST APIs in SDN controllers expose network resources and functionalities
• CRUD operations (Create, Read, Update, Delete) map to HTTP methods in REST APIs
• API versioning ensures backward compatibility and smooth transitions
• Authentication and authorization mechanisms secure REST API access in SDN environments
• Rate limiting and throttling prevent API abuse and ensure fair resource allocation
• Pagination and filtering optimize large dataset retrieval in REST-based SDN APIs
• Hypermedia As The Engine Of Application State (HATEOAS) enhances API discoverability

RPC-based Protocols

NETCONF Protocol and Operations

• NETCONF uses XML-encoded data for configuration management
• RPC (Remote Procedure Call) model underlies NETCONF operations
• NETCONF supports multiple data stores (running, candidate, startup configurations)
• Operations include get-config, edit-config, copy-config, and delete-config
• Subtree filtering in NETCONF allows precise data retrieval and manipulation
• NETCONF uses SSH or TLS for secure communication between client and server
• Capabilities negotiation in NETCONF ensures compatibility between devices

gRPC Framework and Benefits

• gRPC developed by Google uses Protocol Buffers for efficient data serialization
• Bidirectional streaming supports real-time communication in gRPC
• Code generation tools in gRPC simplify client and server implementation
• gRPC supports multiple programming languages, enhancing interoperability
• Low-latency and high-performance characterize gRPC communications
• Load balancing and service discovery integrate well with gRPC architecture
• gRPC leverages HTTP/2 for multiplexing and header compression

OpenFlow Protocol in SDN

• OpenFlow enables communication between SDN controllers and network devices
• Flow tables in OpenFlow define packet handling rules and actions
• OpenFlow supports both proactive and reactive flow installation
• Match fields in OpenFlow allow fine-grained packet classification
• Actions in OpenFlow include forwarding, dropping, and modifying packets
• Multiple table pipeline processing enhances OpenFlow's flexibility
• OpenFlow enables centralized control and programmability of network behavior

SDN Controller Interaction

Network Programmability Concepts

• Network programmability allows dynamic configuration and management of network devices
• APIs expose network functionalities for programmatic access and control
• Software-defined networking separates control plane from data plane
• Automation scripts and tools leverage network programmability for efficient management
• Network as Code paradigm applies software development practices to network management
• Programmability enables rapid service deployment and network optimization
• Event-driven network management reacts to real-time network conditions and triggers

SDN Controller Interfaces and Communication

• Northbound interfaces connect SDN controllers to applications and orchestration systems
• Southbound interfaces facilitate communication between SDN controllers and network devices
• East-west interfaces enable communication between multiple SDN controllers
• Application-layer protocols (REST, gRPC) used for northbound communication
• Device-layer protocols (OpenFlow, NETCONF) used for southbound communication
• Controller clustering and synchronization ensure high availability and scalability
• Policy enforcement and network-wide visibility achieved through centralized control