P4: Programming protocol-independent packet processors

Pat Bosshart; Dan Daly; Glen Gibb; Martin Izzard; Nick McKeown; Jennifer L. Rexford; Cole Schlesinger; Dan Talayco; Amin Vahdat; George Varghese; David P. Walker

doi:10.1145/2656877.2656890

P4: Programming protocol-independent packet processors

Pat Bosshart, Dan Daly, Glen Gibb, Martin Izzard, Nick McKeown, Jennifer L. Rexford, Cole Schlesinger, Dan Talayco, Amin Vahdat, George Varghese, David P. Walker

Research output: Contribution to journal › Article › peer-review

2318 Scopus citations

Abstract

P4 is a high-level language for programming protocol-inde-pendent packet processors. P4 works in conjunction with SDN control protocols like OpenFlow. In its current form, OpenFlow explicitly specifies protocol headers on which it operates. This set has grown from 12 to 41 fields in a few years, increasing the complexity of the specification while still not providing the exibility to add new headers. In this paper we propose P4 as a strawman proposal for how Open-Flow should evolve in the future. We have three goals: (1) Reconfigurability in the field: Programmers should be able to change the way switches process packets once they are deployed. (2) Protocol independence: Switches should not be tied to any specific network protocols. (3) Target inde- pendence: Programmers should be able to describe packet-processing functionality independently of the specifics of the underlying hardware. As an example, we describe how to use P4 to configure a switch to add a new hierarchical label.

Original language	English (US)
Pages (from-to)	87-95
Number of pages	9
Journal	Computer Communication Review
Volume	44
Issue number	3
DOIs	https://doi.org/10.1145/2656877.2656890
State	Published - Jul 2014

All Science Journal Classification (ASJC) codes

Software
Computer Networks and Communications

Access to Document

10.1145/2656877.2656890

Cite this

@article{be6e56b685134770bd165fc4d71bd998,

title = "P4: Programming protocol-independent packet processors",

abstract = "P4 is a high-level language for programming protocol-inde-pendent packet processors. P4 works in conjunction with SDN control protocols like OpenFlow. In its current form, OpenFlow explicitly specifies protocol headers on which it operates. This set has grown from 12 to 41 fields in a few years, increasing the complexity of the specification while still not providing the exibility to add new headers. In this paper we propose P4 as a strawman proposal for how Open-Flow should evolve in the future. We have three goals: (1) Reconfigurability in the field: Programmers should be able to change the way switches process packets once they are deployed. (2) Protocol independence: Switches should not be tied to any specific network protocols. (3) Target inde- pendence: Programmers should be able to describe packet-processing functionality independently of the specifics of the underlying hardware. As an example, we describe how to use P4 to configure a switch to add a new hierarchical label.",

author = "Pat Bosshart and Dan Daly and Glen Gibb and Martin Izzard and Nick McKeown and Rexford, {Jennifer L.} and Cole Schlesinger and Dan Talayco and Amin Vahdat and George Varghese and Walker, {David P.}",

year = "2014",

month = jul,

doi = "10.1145/2656877.2656890",

language = "English (US)",

volume = "44",

pages = "87--95",

journal = "Computer Communication Review",

issn = "0146-4833",

publisher = "Association for Computing Machinery (ACM)",

number = "3",

}

TY - JOUR

T1 - P4

T2 - Programming protocol-independent packet processors

AU - Bosshart, Pat

AU - Daly, Dan

AU - Gibb, Glen

AU - Izzard, Martin

AU - McKeown, Nick

AU - Rexford, Jennifer L.

AU - Schlesinger, Cole

AU - Talayco, Dan

AU - Vahdat, Amin

AU - Varghese, George

AU - Walker, David P.

PY - 2014/7

Y1 - 2014/7

N2 - P4 is a high-level language for programming protocol-inde-pendent packet processors. P4 works in conjunction with SDN control protocols like OpenFlow. In its current form, OpenFlow explicitly specifies protocol headers on which it operates. This set has grown from 12 to 41 fields in a few years, increasing the complexity of the specification while still not providing the exibility to add new headers. In this paper we propose P4 as a strawman proposal for how Open-Flow should evolve in the future. We have three goals: (1) Reconfigurability in the field: Programmers should be able to change the way switches process packets once they are deployed. (2) Protocol independence: Switches should not be tied to any specific network protocols. (3) Target inde- pendence: Programmers should be able to describe packet-processing functionality independently of the specifics of the underlying hardware. As an example, we describe how to use P4 to configure a switch to add a new hierarchical label.

AB - P4 is a high-level language for programming protocol-inde-pendent packet processors. P4 works in conjunction with SDN control protocols like OpenFlow. In its current form, OpenFlow explicitly specifies protocol headers on which it operates. This set has grown from 12 to 41 fields in a few years, increasing the complexity of the specification while still not providing the exibility to add new headers. In this paper we propose P4 as a strawman proposal for how Open-Flow should evolve in the future. We have three goals: (1) Reconfigurability in the field: Programmers should be able to change the way switches process packets once they are deployed. (2) Protocol independence: Switches should not be tied to any specific network protocols. (3) Target inde- pendence: Programmers should be able to describe packet-processing functionality independently of the specifics of the underlying hardware. As an example, we describe how to use P4 to configure a switch to add a new hierarchical label.

UR - http://www.scopus.com/inward/record.url?scp=84905861611&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84905861611&partnerID=8YFLogxK

U2 - 10.1145/2656877.2656890

DO - 10.1145/2656877.2656890

M3 - Article

AN - SCOPUS:84905861611

SN - 0146-4833

VL - 44

SP - 87

EP - 95

JO - Computer Communication Review

JF - Computer Communication Review

IS - 3

ER -

P4: Programming protocol-independent packet processors

Abstract

All Science Journal Classification (ASJC) codes

Access to Document

Other files and links

Fingerprint

Cite this