Software Defined Networking (SDN)

5.

Southbound Protocols and Interfaces

5.1.

Southbound Interface Purpose

5.1.1.

Controller-Device Communication

5.1.2.

Device Capability Abstraction

5.1.3.

Configuration Management

5.1.4.

Status Monitoring

5.2.

OpenFlow Protocol

5.2.1.

Protocol Evolution

5.2.1.1.

Version History

5.2.1.2.

Feature Development

5.2.1.3.

Standardization Process

5.2.1.4.

Industry Adoption

5.2.2.

OpenFlow Switch Specification

5.2.2.1.

Logical Switch Architecture

5.2.2.2.

Port Definitions

5.2.2.3.

Flow Table Structure

5.2.2.4.

Group Table Functionality

5.2.3.

OpenFlow Message Types

5.2.3.1.

Controller-to-Switch Messages

5.2.3.2.

Asynchronous Messages

5.2.3.3.

Symmetric Messages

5.2.3.4.

5.2.4.

Flow Table Management

5.2.4.1.

Flow Entry Structure

5.2.4.2.

Match Field Definitions

5.2.4.3.

Instruction Types

5.2.4.4.

Action Specifications

5.2.5.

Advanced OpenFlow Features

5.2.5.1.

Multiple Flow Tables

5.2.5.2.

5.2.5.3.

5.2.5.4.

Bundle Operations

5.3.

Alternative Southbound Protocols

5.3.1.

NETCONF Protocol

5.3.1.1.

Configuration Management

5.3.1.2.

Transaction Support

5.3.1.3.

5.3.1.4.

Security Features

5.3.2.

YANG Data Models

5.3.2.1.

Data Modeling Language

5.3.2.2.

Configuration Schemas

5.3.2.3.

Operational Data

5.3.2.4.

Notification Definitions

5.3.3.

P4Runtime Protocol

5.3.3.1.

Protocol-Independent Control

5.3.3.2.

Runtime Table Programming

5.3.3.3.

Packet I/O Operations

5.3.3.4.

Device Configuration

5.3.4.

gRPC and Protocol Buffers

5.3.4.1.

High-Performance RPC

5.3.4.2.

Schema Evolution

5.3.4.3.

Streaming Support

5.3.4.4.

Language Bindings

5.3.5.

5.3.5.1.

Database Management

5.3.5.2.

Virtual Switch Configuration

5.3.5.3.

Monitoring Capabilities

5.3.5.4.

Event Notifications

Previous

4. Data Plane and Forwarding Infrastructure

Go to top

Next

6. Northbound Interfaces and APIs