SRv6 Net etwork Programming FD.io VPP and Linux Pablo Camarillo - - - PowerPoint PPT Presentation

Pablo Camarillo - Software Engineer @ Cisco Systems Ahmed Abdelsalam – PhD student @ Gran Sasso Science Institute

FD.io VPP and Linux

SRv6 Net etwork Programming

(CC) FOSDEM 2018 (CC) FOSDEM 2018

Pablo lo Ca Camarillo illo Software Engineer @ Cisco Systems pcamaril@cisco.com

Who are we?

Ah Ahmed Ab Abdelsalam PhD student @ Gran Sasso Science Institute ahmed.abdelsalam@gssi.it

(CC) FOSDEM 2018 (CC) FOSDEM 2018

Agenda

1

SRv6 101

2

Deployment use-cases

3

SRv6 on FD.io VPP

4

SRv6 on Linux

5

SERA

(CC) FOSDEM 2018

• Source Routing
• the topological and service (NFV) path is encoded in packet header
• Scalability
• the network fabric does not hold any per-flow state for TE or NFV
• Simplicity
• automation: TILFA sub-50msec FRR
• protocol elimination: LDP, RSVP-TE, NSH…
• End-to-End
• DC, Metro, WAN

Segment Routing

(CC) FOSDEM 2018

IPv6

• leverages RFC8200 provision for source routing extension header
• 1 segment = 1 address
• a segment list = an address list in the SRH

Two dataplane instantiations

MPLS

• leverage the mature MPLS HW with only SW upgrade
• 1 segment = 1 label
• a segment list = a label stack

Segment Routing

(CC) FOSDEM 2018

IPv6 adoption is a reality

% Web pages available over IPv6

Sources: 6lab.cisco.com – Web content Cisco VNI Global IP Traffic Forecast, 2016-2021

Global IPv6 traffic gr grew ew 241% in 2016 Globally IPv6 traffic wi will grow w 16 16-fo fold from 2016 to 2021 IPv6 wi will be 37% of total Internet traffic in 2021

(CC) FOSDEM 2018

IPv6 provides reachability

(CC) FOSDEM 2018

• Simplicity
• Protocol elimination
• SLA
• FRR and TE
• Overlay
• NFV
• SDN
• SR is de-facto SDN architecture
• 5G

SR SRv6 – Segment Routing & IPv6

IP IPv6 for reacha hability SR SR for r anything else

(CC) FOSDEM 2018

IP IPv6 for reacha hability

SR SRv6 for underlay

RS RSVP for FRR/T FRR/TE Horrendous states scaling in k*N^2 SR SRv6 for r Un Underl rlay Simplification through protocol reduction SLA through automated FRR and TE De-facto SDN architecture

(CC) FOSDEM 2018

IP IPv6 for reacha hability

Multiplicity of protocols and states hinder network economics

SR SRv6 for underlay and overlay

SR SRv6 for r Un Underl rlay Simplification, FRR, TE, SDN UDP+VxLAN Overlay Additional Protocol just for tenant ID NSH for NFV Additional Protocol and State

(CC) FOSDEM 2018

SR for anything: Ne Netwo work as a Computer

(CC) FOSDEM 2018

• 128-bit SRv6 SID
• Locator: routed to the node performing the function
• Function: any possible function

either local to NPU or app in VM/Container

• Flexible bit-length selection

Network instruction

Function Locator

(CC) FOSDEM 2018

• 128-bit SRv6 SID
• Locator: routed to the node performing the function
• Function: any possible function

either local to NPU or app in VM/Container

• Ar

Argumen ents: o

• ptional

al ar argumen ent b bits t to b be u e used ed o

• nly b

by t that at S SID

• Flexible bit-length selection

Network instruction

Function Locator Args*

(CC) FOSDEM 2018

Network Program

Next Segment

Locator 1 Function 1 Locator 1 Function 1 Locator 2 Function 2 Locator 3 Function 3 Locator 2 Function 2 Locator 3 Function 3

(CC) FOSDEM 2018

Network Program

Next Segment

Locator 2 Function 2 Locator 1 Function 1 Locator 2 Function 2 Locator 3 Function 3 Locator 1 Function 1 Locator 3 Function 3

(CC) FOSDEM 2018

Network Program

Next Segment

Locator 3 Function 3 Locator 1 Function 1 Locator 2 Function 2 Locator 3 Function 3 Locator 1 Function 1 Locator 2 Function 2

(CC) FOSDEM 2018

Network Program in the Packet Header

Lo Locator 1 Fu Func nction n 1 Lo Locator 2 Fu Func nction n 2 Lo Locator 3 Fu Func nction n 3

TC TCP, UDP DP, QUIC

Lo Locator 1 Fu Func nction n 1 Sou Source Address

Active Segment

IPv6 header Segment Routing Header IPv6 payload

(CC) FOSDEM 2018

Argument shared between functions

“Global” Argument Metadata TLV

Se Segments ts Left Lo Locator 1 Fu Func nction n 1 Lo Locator 2 Fu Func nction n 2 Lo Locator 3 Fu Func nction n 3 TA TAG

(CC) FOSDEM 2018

Group-Based Policy

Metadata TLV

Se Segments ts Left Lo Locator 1 Fu Func nction n 1 Lo Locator 2 Fu Func nction n 2 Lo Locator 3 Fu Func nction n 3 TA TAG

(CC) FOSDEM 2018

SR SRv6 Header

Metadata TLV

Se Segments ts Left Lo Locator 1 Fu Func nction n 1 Lo Locator 2 Fu Func nction n 2 Lo Locator 3 Fu Func nction n 3 TA TAG

(CC) FOSDEM 2018

SRv6 LocalSIDs

(CC) FOSDEM 2018

• For simplicity function 1 denotes the most basic function
• Shortest-path to the Node

Endpoint function

A1 A1 A1:: A3 A3 A3:: A2 A2 A2:: A5 A5 A5:: A4 A4 A4::

50 50

A6 A6 A6:: A7 A7 A7:: A8 A8 A8::

Default metric 10 SR SR: A4 A4::1, A6 A6::1, A8 A8::

>VPP: show sr localsid LocalSID Behavior A6::1 End Total SR LocalSIDs: 1 >VPP: show sr localsid LocalSID Behavior A4::1 End Total SR LocalSIDs: 1

(CC) FOSDEM 2018

Endpoint then xconnect to neighbor function

A1 A1 A1:: A3 A3 A3:: A2 A2 A2:: A5 A5 A5:: A4 A4 A4::

50 50

A6 A6 A6:: A7 A7 A7:: A8 A8 A8::

Default metric 10 SR SR: A4 A4::C5, A6 A6::1, A8 A8::

>VPP: show sr localsid LocalSID Behavior A6::1 End Total SR LocalSIDs: 1 >VPP: show sr localsid LocalSID Behavior A4::C5 End.X {TenGE0/1/0 A5::} Total SR LocalSIDs: 1

• For simplicity Ak::Cj denotes:
• Shortest-path to the Node K and then x-connect (function C) to the neighbor J

(CC) FOSDEM 2018

Deployment use-cases

(CC) FOSDEM 2018

• 50msec Protection upon

local link, node or SRLG failure

• Simple to operate and understand
• automatically computed by the router’s IGP process
• 100% coverage across any topology
• predictable (backup = postconvergence)
• Optimum backup path
• leverages the post-convergence path, planned to carry the traffic
• avoid any intermediate flap via alternate path
• Incremental deployment
• Distributed and Automated Intelligence

TILFA

2 4 6 5 1

A5 A5::0 A5 A5::/64 Pr Pri → vi via 5 A2 A2::C4 C4 A5 A5::0 FR FRR → i insert A A2::C4 A5 A5::0 <50m <50mec FRR

100

(CC) FOSDEM 2018

Input Acquisition

• BGP-LS
• Telemetry

Policy Instantiation

• PCEP
• BGP-TE
• Netconf / Yang

Algorithm

• SR native

Centralized TE

DC (BGP-SR)

10 10 11 11 12 12 13 13 14 14 2 4 6 5 7

WAN (IGP-SR)

3 1

PEER

Low Low La Lat, L Low B BW

50 50

Default ISIS cost metric: 10

<A1::1, A2::C4, A4::C7>

Low Low-La Latency to 7 7 fo for a application … …

(CC) FOSDEM 2018

• Automated
• No tunnel to configure
• Simple
• Protocol elimination
• Efficient
• SRv6 for everything

Overlay

1 2 4 V/ V/64 3 T/ T/64

IPv6 Hdr SA = A1 A1::0, DA = A2 A2::C4 Payload IPv6 Hdr SA = T::1, DA = V: V::2

Green Overlay V/64 via A2::C4

IPv6 Hdr SA = T::1, DA = V: V::2 Payload IPv6 Hdr SA = T::1, DA = V: V::2 Payload

(CC) FOSDEM 2018

• SRv6 does not only eliminate

unneeded overlay protocols

• SRv6 solves problems that

these protocols cannot solve

Overlay with Underlay Control

1 2 4 V/ V/64 3 T/ T/64

Green Overlay V/64 via A2::C4 with Latency

IPv6 Hdr SA = T::1, DA = V: V::2 Payload IPv6 Hdr SA = T::1, DA = V: V::2 Payload

3

IPv6 Hdr SA = A1 A1::0, DA = A3 A3::1 Payload IPv6 Hdr SA = T::1, DA = V: V::2 SR Hdr < A3 A3::1, A2::C4 > IPv6 Hdr SA = A1 A1::0, DA = A2 A2::C4 Payload IPv6 Hdr SA = T::1, DA = V: V::2 SR Hdr < A3::1, A2 A2::C4 >

(CC) FOSDEM 2018

Endpoint behaviors specs summary

Cod Codename Be Behavior End Endpoint [PSP/USP flavors] End.X Endpoint with Layer-3 cross-connect [PSP/USP flavors] End.B6 Endpoint bound to an SRv6 policy End.B6.Encaps Endpoint bound to an SRv6 Encapsulation policy End.DX6 Endpoint with decapsulation and IPv6 cross-connect (per-CE VPN label) End.DX4 Endpoint with decapsulation and IPv4 cross-connect (per-CE VPN label) End.DT6 Endpoint with decapsulation and specific IPv6 table lookup (per-VRF VPN label) End.DT4 Endpoint with decapsulation and specific IPv4 table lookup (per-VRF VPN label) End.DX2 Endpoint with decapsulation and Layer-2 cross-connect Cod Codename Be Behavior End Endpoint [PSP/USP flavors] End.X Endpoint with Layer-3 cross-connect [PSP/USP flavors] End.B6 Endpoint bound to an SRv6 policy End.B6.Encaps Endpoint bound to an SRv6 Encapsulation policy End.DX6 Endpoint with decapsulation and IPv6 cross-connect (per-CE VPN label) End.DX4 Endpoint with decapsulation and IPv4 cross-connect (per-CE VPN label) End.DT6 Endpoint with decapsulation and specific IPv6 table lookup (per-VRF VPN label) End.DT4 Endpoint with decapsulation and specific IPv4 table lookup (per-VRF VPN label) Cod Codename Be Behavior End Endpoint [PSP/USP flavors] End.X Endpoint with Layer-3 cross-connect [PSP/USP flavors] End.B6 Endpoint bound to an SRv6 policy End.B6.Encaps Endpoint bound to an SRv6 Encapsulation policy Cod Codename Be Behavior End Endpoint [PSP/USP flavors] End.X Endpoint with Layer-3 cross-connect [PSP/USP flavors]

(CC) FOSDEM 2018

Service chaining

(CC) FOSDEM 2018

• Se

Serv rvices are expressed with se segm gment nts

• Flexible
• Scalable
• Stateless

Packets from are steered through a sequence of services on their way to the server

Service Chaining with SR SRv6

S1 S1 S2 S2 S3 S3 D SR SR: S1 S1, C1 C1, S2 S2, S3 S3, D C1 C1

(CC) FOSDEM 2018

• Stateless
• NSH creates per-chain state

in the fabric

• SR does not
• App is SR aware or not
• App can work on IPv4, IPv6
• r L2

Integrated NFV

1 2 4 V/ V/64 3 T/ T/64 4

Ap App 76 VM VM

Se Server 5

5 3

Ap App 32 Co Container

Se Server 3

IPv6 HdrSA = A1 A1::0, DA = A3 A3::A3 A32 Payload IPv6 Hdr SA = T::1, DA = V: V::2 SR Hdr < A3 A3::A3 A32, A4::1, A5::A76, A2::C4 > IPv6 Hdr SA = T::1, DA = V: V::2 Payload

(CC) FOSDEM 2018

• Integrated with underlay SLA

Integrated NFV

1 2 4 V/ V/64 3 T/ T/64 4

Ap App 76 VM VM

Se Server 5

5 3

Ap App 32 Co Container

Se Server 3

IPv6 Hdr SA = A1 A1::0, DA = A4 A4::1 Payload IPv6 Hdr SA = T::1, DA = V: V::2 SR Hdr < A3::A32, A4 A4::1, A5::A76, A2::C4 >

(CC) FOSDEM 2018

• Stateless
• NSH creates per-chain state

in the fabric

• SR does not
• App is SR aware or not
• App can work on IPv4, IPv6
• r L2

Integrated NFV

1 2 4 V/ V/64 3 T/ T/64 4

Ap App 76 VM VM

Se Server 5

5 3

Ap App 32 Co Container

Se Server 3

IPv6 HdrSA = A1 A1::0, DA = A5 A5::A7 A76 Payload IPv6 Hdr SA = T::1, DA = V: V::2 SR Hdr < A3::A32, A4::1, A5 A5::A7 A76, A2::C4 >

(CC) FOSDEM 2018

• Integrated with Overlay

Integrated NFV

1 2 4 V/ V/64 3 T/ T/64 4

Ap App 76 VM VM

Se Server 5

5 3

Ap App 32 Co Container

Se Server 3

IPv6 Hdr SA = A1 A1::0, DA = A2 A2::C4 Payload IPv6 Hdr SA = T::1, DA = V: V::2 SR Hdr < A3::A32, A4::1, A5::A76, A2 A2::C4 > IPv6 Hdr SA = T::1, DA = V: V::2 Payload

(CC) FOSDEM 2018

SR-UnAware VNFs:

• Application is not aware of SR at all
• Leverage VPP as a vm/container vSwitch to do SRv6 processing

Service Chaining with SR SRv6

SR-Aware VNFs:

• Leverage SRv6 Kernel support to create smarter applications
• SERA: SR-Aware Firewall (extension to iptables)

Types of VNFs

(CC) FOSDEM 2018

SRv6 support in VPP

(CC) FOSDEM 2018

• Extensible framework that provides out-of-the-box production quality

switch/router functionality (dataplane only)

• We’ve implemented the entire SRv6 Network Programming on it

Vector Packet Processing

Extremely fast Packet processing stack Open Source Runs on commodity CPU

(CC) FOSDEM 2018

• End.AM – Endpoint to SR-unaware app via masquerading
• End.AD – Endpoint to SR-unaware app via dynamic proxy
• End.ASM – Endpoint to SR-unaware app via shared memory

SR-UnAware VNFs

S1 S1 D SR SR: S1 S1, C1 C1, S2 S2, S3 S3, D C1 C1 S2 S2 S3 S3

(CC) FOSDEM 2018

RFC2460: “A Routing header is not examined or processed until it reaches the node identified in the Destination Address field of the IPv6 header.”

End.AM – Endpoint to SR-unaware app via masquerading

Te TenGE GE0/1/0 Te TenGE GE0/2/0

VN VNF VP VPP E1 E1::

IPv6 Hdr SA = A: A::, DA = E1 E1::A Payload SR Hdr ( B::, C3::, E1 E1::A ) SL=2 IPv6 Hdr SA = A: A::, DA = B: B:: Payload SR Hdr ( B::, C3 C3::, E1::A ) SL=1 IPv6 Hdr SA = A: A::, DA = C3 C3:: Payload SR Hdr ( B::, C3 C3::, E1::A ) SL=1

>VPP: show sr localsid LocalSID Behavior E1::A End.AM {OIF: TenGE0/1/0, NH: 2001::a, IIF: TenGE0/2/0} Total SR LocalSIDs: 1

• Ingress:
• Active SID is E1::A where function 0xA is

associated with End.AM

• Replace DA with the last segment B:

B::

• Forward to VNF (OIF, NH)
• Egress:
• Inspect SRH and update DA with active

segment C3 C3::

(CC) FOSDEM 2018

End.AD – Endpoint to SR-unaware app via dynamic proxy

Te TenGE GE0/1/0 Te TenGE GE0/2/0

VN VNF VP VPP E1 E1::

IPv6 Hdr SA = A: A::, DA = B: B:: Payload

>VPP: show sr localsid LocalSID Behavior E1::B End.AD {OIF: TenGE0/1/0, NH: 2001::a, IIF: TenGE0/2/0} Total SR LocalSIDs: 1

• Ingress:
• Active SID is E1::B where function 0xB is

associated with End.AD

• Pop and stor

tore outer IP and SR headers

• Forward to VNF (OIF, NH)
• Egress:
• Push the IP and SR headers
• Forward based on next segment
• Valid

d for IPv4 and d IPv6 traffic

• Per

er-ch chain dynamic c co configuration

IPv6 Hdr SA = C1 C1::, DA = E1 E1::C SR Hdr ( E2::, C2::, E1 E1::C ) SL=2 IPv6 Hdr SA = A::, DA = B: B:: Payload IPv6 Hdr SA = C1 C1::, DA = C2 C2:: SR Hdr ( E2::, C2 C2::, E1::C ) SL=1 IPv6 Hdr SA = A::, DA = B: B:: Payload

(CC) FOSDEM 2018

End.ASM – Endpoint to SR-unaware app via shared mem.

1.

Put the received packet in a shared memory region

2.

Perform SR processing on the host Pass a po point nter er of the inner packet to S2

3.

Perform SR processing on the host Pass a po point nter er of the inner packet to S3

4.

Move the packet from the shared memory into the output iface buffer ring

• Valid

d for IPv4 and d IPv6 traffic

• Ma
• Max. theoretic

ical l achie ievable le performance S2 S2 S3 S3

(CC) FOSDEM 2018

• Users can write their own SRv6 LocalSIDs functions as VPP plugins
• There is a SR LocalSID plugin template
• Starting point for your own developments
• We do the ‘SRH’ processing for you

SRv6 LocalSID development kit

(CC) FOSDEM 2018

SRv6 support in Linux

(CC) FOSDEM 2018

• The first support of SRv6 in Linux kernel, released in February 2017.
• End, T.Insert6, and T.Encaps6 behaviors were supported
• The SRv6 support is enabled on interface basis.

All IPv6 addresses assigned to an SRv6-enabled interface are treated as local SID

• Iproute2 was extended to support creating an SR policy.

Kernel 4.10

sysctl –w net.ipv6.conf.all.seg6_enabled=1 sysctl –w net.ipv6.conf.<device>.seg6_enabled=1 ip -6 route add <prefix> encap seg6 mode <encapmode> segs <segments> dev <device>

(CC) FOSDEM 2018

• Another milestone in SRv6 support in Linux, released in November 2017
• More

SRv6 behaviors were supported: T.Encaps.L2, T.Insert4, T.Encaps4, End.X, End.T, End.DX2, End.DX4, End.DX6, End.DT6, End.B6, End.B6.Encaps.

• IProute2 extended to associate one of the new behaviors to a local SID

Kernel 4.14

ip -6 route add <segment> encap seg6local action <action> <params> \ dev <device> table localsid

(CC) FOSDEM 2018

• An

external kernel module provides advanced Segment Routing functions.

• Complements the existing SRv6 kernel

implementation.

• Supports several proxy behaviors that

enable SR-unaware service functions to be included in an SRv6 service chain.

SREXT

Netfilter Framework Pkt_in PRE_ROUTING POST_ROUTING FORWARD LOCAL_OUT LOCAL_IN Routing Local Process Local Process Routing Pkt_out SREXT Localsid table

(CC) FOSDEM 2018

• No more state information is required per a VNF .
• Leverage SID arguments for local parameters
• Leverage TLVs to pass metadata between services
• Have a vison of the whole packet path for better protection

SR-aware Service Functions

(CC) FOSDEM 2018

SERA

(CC) FOSDEM 2018

• SEgment Routing Aware firewall
• The first-ever SRv6-aware Network function
• An advanced SR aware firewall, with extended matching and actions

capabilities.

• It allows matching information from original packet, SRH, and the outer

packet.

• It’s capable of performing SR-specific actions.

SERA

(CC) FOSDEM 2018

SERA

F/ F/W

IPv6 Hdr SA = DA = Payload IPv6 Hdr SA=.., DA = … SR Hdr SID list TLV

F/ F/W + SR proxy xy

IPv6 Hdr SA = DA = Payload IPv6 Hdr SA=.., DA = … SR Hdr SID list TLV SR SR Pr Proxy

SE SERA

IPv6 Hdr SA = DA = Payload IPv6 Hdr SA=.., DA = … SR Hdr SID list TLV

SERA has a full view of SR Encapsulated packets

We can match all headers of a received packets

It has no way to analyze inner packet - matching capabilities limited to outer packet

SR Information is hidden from the firewall

(CC) FOSDEM 2018

• Implemented as an extension to the existing Linux ip6tables firewall
• Three new extensions have been to the netfilter implementation as follows:
• ip6t_srh: matches information of SRH
• ip6t_inner6: matches information of inner packet
• ip6t_SEG6: performs SR- Specific actions

SERA – Netfilter extensions

(CC) FOSDEM 2018

• Three new shared libraries have been added to the iptables user-space

utility implementation to support the new features:

• libip6t_srh:

to add rules that match based on SRH

• libip6t_inner6: to add rules that match based on inner packet
• libip6t_SEG6: to add rules that perform SR-specific actions

SERA – Iptables extensions

(CC) FOSDEM 2018

SERA – CLI

$ ip6tables -m srh -h ........ srh match options: [!] --srh-next-hdr [!] --srh-hdr-len-eq [!] --srh-hdr-len-gt [!] --srh-hdr-len-lt [!] --srh-segs-left-eq [!] --srh-segs-left-gt [!] --srh-segs-left-lt [!] --srh-last-entry-eq [!] --srh-last-entry-gt [!] --srh-last-entry-lt [!] --srh-tag $ ip6tables -m srh -h ............. srh match options: [!] --inner6-src ip6_addr[/mask] [!] --inner6-dst ip6_addr[/mask] $ ip6tables -j SEG6 -h ............. SEG6 target options:

• -seg6-action ACTION

ACTION: go-next | skip-next | go-last

(CC) FOSDEM 2018

ip6tables -I INPUT -m inner6 --inner6-src fc00:a::/64 \

• -inner6-dst fc00:b::/64 -m srh --srh-next-hdr 6 \
• -srh-segs-left-gt 5 --srh-tag 0 -j DROP

ip6tables -I INPUT -m inner6 --inner6-src fc00:a::/64 \

• -inner6-dst fc00:b::/64 -m srh --srh-next-hdr 6 \
• -srh-segs-left-gt 5 --srh-tag 0 -j SEG6 --seg6-action go-last

SERA – Examples

(CC) FOSDEM 2018

Conclusion

(CC) FOSDEM 2018

Ma Mar 2017 Ap Apr 2017 Ju Jun 2017 Au Aug 2017 2017 2018 2018 Ap Apr 2016 Ma May 2017

SRv6 timeline

First SRv6 demo: Spray use-case

VPP ASR9k ASR1k

Fretta

First SRv6 HW demo in merchant sillicon VPN DP use-case

Cisco Live US SRv6 VPN

ASR1k ASR9k Fretta VPP+NFV BGP Control Plane

SD-WAN summit SRv6 for the SD-WAN

ASR1k

SRv6 VPN+NFV: MPLS World Con.

VPP Linux (sr srext)

Barefoot

SRv6 VPN HW demo

SR VPN InterOp

Fretta ASR9k ASR1k VPP Linux (srext) Ba Barefoot

More to come…

5G + Network slicing

Se Sep 2017 2017

(CC) FOSDEM 2018

IPv6 provides reachability

(CC) FOSDEM 2018

SRv6 unleashes IPv6 potential

Scalability Single protocol

NFV VPN FRR TE

Automation

(CC) FOSDEM 2018

• Go on www.

www.segment-ro routing.n .net and check the latest demos

• Read the IETF draft: draft

ft-fi filsfi fils-sp spri ring ng-srv6 srv6-ne network-pr progr gramming

• Play with VPP and srext
• Create y

your o

• wn S

SRv6 a 6 aware a

• apps. Th

There i is b

• business. I

It’s e easy. Contact u us!

Homework time!

Thank you!

www.segment-routing.net

(CC) FOSDEM 2018

Ma Mar 2017 Ap Apr 2017 Ju Jun 2017 Au Aug 2017 2017 2018 2018 Ap Apr 2016 Ma May 2017

SRv6 timeline

First SRv6 demo: Spray use-case

VPP ASR9k ASR1k

Fretta

First SRv6 HW demo in merchant sillicon VPN DP use-case

Cisco Live US SRv6 VPN

ASR1k ASR9k Fretta VPP+NFV BGP Control Plane

SD-WAN summit SRv6 for the SD-WAN

ASR1k

SRv6 VPN+NFV: MPLS World Con.

VPP Linux (sr srext)

Barefoot

SRv6 VPN HW demo

SR VPN InterOp

Fretta ASR9k ASR1k VPP Linux (srext) Ba Barefoot

More to come…

5G + Network slicing

Se Sep 2017 2017