REN SDN Use Cases With OpenFlow and P4 status TNC2016 Curt Beckmann Chair of Open Datapath Working Group, ONF Chief Technology Architect for EMEA

Agenda SDN Perspective from 50 km SDN Deployments for REN OpenFlow Challenges and Progress “Next Generation” SDN activity: P4 2 © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY:

Agenda SDN Perspective from 50 km SDN Deployments for REN OpenFlow Challenges and Progress “Next Generation” SDN activity: P4 3 © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY:

SDN: Perspective from 50km Customer driven movement ONF “technical” definition of SDN ‒ “Control physically separated from Data Plane” Real customer desire ‒ “Control and Data are VENDOR separated”  “Ecosystem”-ouch! ‒ Oh, and key customers (SPs) also want NFV- yikes! How to “bootstrap” an ecosystem? ‒ Add OpenFlow to legacy boxes (done) ‒ Converge on small # of controllers (done) ‒ Common NB APIs (In process) ‒ Build what early ecosystem buyers want (in process) ‒ Sell “open vertical” solutions (in process) 4 SDN / OpenFlow Router Control Plane (software) Data Plane (hardware) Router Data Plane (hardware) Control Plane (software) Traditional Controller Control Plane (software) APIs © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY Hybrid

SDN: Perspective from 50km Customer driven movement ONF “technical” definition of SDN ‒ “Control physically separated from Data Plane” Real customer desire ‒ “Control and Data are VENDOR separated”  “Ecosystem”-ouch! ‒ Oh, and key customers (SPs) also want NFV- yikes! How to “bootstrap” an ecosystem? ‒ Add OpenFlow to legacy boxes (done) ‒ Converge on small # of controllers (done) ‒ Common NB APIs (In process) ‒ Build what early ecosystem buyers want (in process) ‒ Sell “open vertical” solutions (in process) 5 SDN / OpenFlow Router Control Plane (software) Data Plane (hardware) Router Data Plane (hardware) Control Plane (software) Traditional Controller Control Plane (software) APIs © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY Hybrid

Agenda SDN Perspective from 50 km SDN Deployments for REN OpenFlow Challenges and Progress “Next Generation” SDN activity: P4 6 © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY:

SDN Use Cases 7 Volumetric Attack Mitigation Elephant Flow Management Firewall Bypass Policy Based Flow Forwarding Botnet Attack Mitigation Campus Access Management SDN Based MPLS Traffic Engineering Bandwidth Scheduler Packet-Optical Integration WAN Network Virtualization Flow Metering SDN Based Wiretap VXLAN Monitoring CONTROL AUTOMATIONVISIBILITY © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY:

SDN Use Cases… popular in REN context 8 Volumetric Attack Mitigation Elephant Flow Management Firewall Bypass Policy Based Flow Forwarding Botnet Attack Mitigation Campus Access Management SDN Based MPLS Traffic Engineering Bandwidth Scheduler Packet-Optical Integration WAN Network Virtualization Flow Metering SDN Based Wiretap VXLAN Monitoring CONTROL AUTOMATIONVISIBILITY © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.

SDN for Policy-Based Firewall Insertion / Bypass REN DC X One-armed Firewall Trusted Traffic Flow WAN Inline Firewall REN DC Y Default Traffic Flow SDN Controller SDN App Internet Operator or sFlow driven policy enforcement for large trusted flows © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. : Evaluating: Indiana U, CERN

Path Explorer MLXe SDN-based Education Campus Access Dynamic policy for flexible network access control and security Access based on MAC / IP addresses Redirect to IPsec, GRE or MPLS tunnel Suitable for consultants, mobile workers for short-term network access © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. OF rule OF 1.3 Matching Shipping Campus / DC Visual Engine Flow Policy Normal Forward GRE Tunnel to Guest Network Re-direct Drop Programmable Access Control via Northbound API I’m consultant for project Y. Can I access the RED network? IPsec Tunnel to Secure Resources Guest Policy In Planning for v1.1 Developing: ASU Evaluating: Cornell

SDWAN 11 © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. : SDN Backbone Long term deployment: Internet2 Evaluating: AARNET

Agenda SDN Perspective from 50 km SDN Deployments for REN OpenFlow Challenges and Progress “Next Generation” SDN activity: P4 12 © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY:

OpenFlow Deployment: Challenges (1 of 2) The point: ONF and ODWG are aware of these Two main platform categories ‒ Well-deployed “fixed function” ASIC-based ‒ Flexible, NPUs & “programmable ASICs” OpenFlow Applicability Challenge ‒ OF1.x too flexible for ASICs, not enough for NPUs ‒ Not all boxes do all things: Need a “config phase” API / Interoperability Challenges ‒ Hardware independence means common stable NB APIs ‒ Apps coded for specific devices, extensions often required © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. Image credit:

OpenFlow Deployment: Challenges (2 of 2) Conformance testing challenges ‒ OF1.3 basic test defined ‒ No long term support (LTS) for OF1.4 & OF1.5 OF Pipeline config solution: “Table Type Patterns” (TTP) v1.0 ‒ Upside: Designed to address most OpenFlow challenges ‒ Challenges: limited examples, “machine consumability”, YANG issues © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.

OpenFlow standards progress OF1.6 coming late 2016, ‒ Long term support (LTS) and modularity ‒ Optical / wireless expanding OF down OSI stack More adoption of TTPs: China Mobile SPTN, etc ‒ Growing interest in TTP-based conformance testing TTP v1.1 syntax is ready, English language spec in process ‒ “machine”/YANG friendly, better Extension support, 1.0  1.1 converter ‒ More examples, TTP 1.1 tools planned or underway ‒ Stage set for Jsonnet or similar on top of TTP This abstract language will include Library support for even more re-use 15 © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.

Agenda SDN Perspective from 50 km SDN Deployments for REN OpenFlow Challenges and Progress “Next Generation” SDN activity: P4 16 © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY:

“Next Generation” SDN activity: P4 OF and P4 communities overlap ‒ P4 “defines pipelines”, has a “config phase” ‒ P4 leaves control protocol open, so complements OF OpenFlow will need some adjustments; ODWG plans to take that up OF Lesson: Do more “prelaunch” validation ‒ Despite high interest and strong demos, be conservative ‒ One thorn: platform independent “Intermediate Representation” is tricky P4 is packet-centric, needs augmentation for L0 and L1 devices OpenFlow transport extensions will offer that augmentation 17 © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.

In 2014, P4 & ONF agreed on a path P4 to work IR & flex pipeline via open source ODWG subgroup to look at “P4 ecosystem” Progress on both… ODWG “TR” is approved for pub ‒ Key OF lessons: Address the “meta technical” issues too ‒ Vital: hybrid OF/P4 deployment models Greenfield is too risky… A “P4 for ASICs” option would be very helpful ASICs support legacy protocols… P4 devices will interact with legacy… so create std libs ‒ P4 / OpenFlow co-existence eases adoption, and both need stable NB APIs P4 (and OpenFlow) need to work w controller projects, unify control protocol ‒ Smart conformance test approach needed… address it NOW 18 © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC

Conclusions Low level control protocol is important to SDN ‒ OpenFlow is still the only open control protocol OpenFlow is facing its challenges, and making progress solving them P4 is making progress as well ‒ More tools and examples and “ecosystem readiness” will be needed ‒ OpenFlow compatibility likely ‒ P4’s Value will be easier to establish as SDN traction grows 19 © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.