What is the P4 Programming Language? - Northbound Networks

It seems there may be some confusion as to what P4 is, in particular how it relates to OpenFlow. So let's get one thing out of the way first, P4 is NOT a replacement for OpenFlow. They serve two different functions and as a matter of fact, complement each other. Both have a simple set of goals, to increase extensibility and reduce time to market. OpenFlow is a protocol, one that allows the separation of the control and data planes in a network device. By moving the control plane away from the network device onto commodity hardware, it allows the user to develop their own custom logic to centralise and enhance overall network manageability. Then OpenFlow allows these two components to communicate with each other.P4, on the other hand, is a programming language designed explicitly for programming the data plane

Software Defined Networking (Part 2) - OMSCS Notes

Intent-Based Networking with Programmable Data Planes

NDG NETLAB+ - Introduction to P4 Programmable Data Planes

4MIDable: Flexible Network Offloading For Security VNFs

PDF) Flexible IoT Datapath Programming using P4

Comparison of Software Defined Networking (SDN) Controllers. Part 2: Open Network Operating System (ONOS) - Aptira

Architecture and Design — SD-Fabric Docs 1.0.3-dev documentation

P4 Network Programming Language—what is it all about? - CodiLime

The Southbound and Northbound SDN interfaces.

Software Defined Networking (Part 2) - OMSCS Notes

Blog - RARE - GÉANT federated confluence

Chapter 1: Introduction — Software-Defined Networks: A Systems Approach Version 2.1-dev documentation

Software Defined Networking (Part 2) - OMSCS Notes

The Open Networking Cheat Sheet