SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the...
Transcript of SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the...
![Page 1: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/1.jpg)
NANOG, San Jose, Oct 2017
SRv6: Network as a Computer and Deployment use-cases
Gaurav Dawra, Technical Leader, Cisco Systems ([email protected]) John Brzozowski, Fellow and Chief Architect, Comcast John Leddy, Network Engineering, Comcast Clarence Filsfil, Fellow, Cisco Systems ([email protected])
![Page 2: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/2.jpg)
Agenda
1 SRv6 101
2 SRv6 LocalSID & Use-Cases
3 VPN Overlay
4 Service Chaining
VPP 5
SD-WAN 6
7 Spray
8 Mobile Network
![Page 3: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/3.jpg)
Segment Routing
• Source Routing – the topological and service (NFV) path is encoded in the packet header
• Scalability – the network fabric does not hold any per-flow state for TE or NFV
• Simplicity – automation: TILFA – protocol elimination: LDP, RSVP-TE, NSH…
• End-to-End – DC, Metro, WAN
![Page 4: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/4.jpg)
Our commitment to Lead Operators
Standardization
IETF
Multi-vendor Consensus
Seamless deployment
Bell COMCAST Proximus T-Mobile Orange
Strong customer adoption
WEB, SP, Enterprise
De-facto SDN Architecture
![Page 5: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/5.jpg)
Objectives of SRv6
![Page 6: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/6.jpg)
IPv6 provides reachability
Supports 5G growth IPv6 addresses summarization
5G
5G
5G
IoT services
Source Address
Destination Address
IPv6
Metro/Core Network
IP
4G
xDSLFTTH
Cable
Legacy DC
Supports container adoption for micro-services
Next-Gen Data Center
Micro-services
![Page 7: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/7.jpg)
IPv6 for reachability
SRv6 for underlay
RSVP for FRR/TE Scaling issue with k*N^2
SRv6 for Underlay
Simplification through protocol reduction
SLA through automated FRR and TE
De-facto SDN architecture
![Page 8: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/8.jpg)
IPv6 for reachability
Multiplicity of protocols and states hinder network economics
SRv6 for underlay and overlay
SRv6 for Underlay Simplification, FRR, TE, SDN
UDP+VxLAN Overlay Additional Protocol just for tenant ID
NSH for NFV Additional Protocol and State
![Page 9: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/9.jpg)
SR for anything: Network as a Computer
![Page 10: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/10.jpg)
• 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
![Page 11: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/11.jpg)
• 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 • Arguments: optional argument bits to be used only by that SID • Flexible bit-length selection
Network instruction
Function Locator Args*
![Page 12: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/12.jpg)
12 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
Network Program in the Packet Header
Next Segment Locator 1 Function 1
Locator 2 Function 2
Locator 3 Function 3
Segment Routing Header
Destination Address Source Address IPv6
Header
IPv6 Payload TCP, UDP, QUIC…
Locator 1 Function 1
![Page 13: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/13.jpg)
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
![Page 14: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/14.jpg)
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
![Page 15: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/15.jpg)
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
![Page 16: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/16.jpg)
Argument shared between functions
“Global” Argument
Metadata TLV
Segments Left
Locator 1 Function 1
Locator 2 Function 2
Locator 3 Function 3
TAG
![Page 17: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/17.jpg)
Group-Based Policy
Metadata TLV
Segments Left
Locator 1 Function 1
Locator 2 Function 2
Locator 3 Function 3
TAG
![Page 18: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/18.jpg)
SR Header
Metadata TLV
Segments Left
Locator 1 Function 1
Locator 2 Function 2
Locator 3 Function 3
TAG
![Page 19: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/19.jpg)
SRv6 for anything
Optimized for HW processing e.g. Underlay & Tenant use-cases
Optimized for SW processing e.g. NFV, Container, Micro-Service
Metadata TLV
Segments Left
Locator 1 Function 1
Locator 2 Function 2
Locator 3 Function 3
TAG
![Page 20: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/20.jpg)
Lead Operators
• Standardization • Multi-Vendor Consensus
Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved.
![Page 21: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/21.jpg)
Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved.
![Page 22: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/22.jpg)
SRv6 for Next-generation Mobile
Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved.
![Page 23: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/23.jpg)
Use-Cases
![Page 24: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/24.jpg)
24 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
SID allocation for illustration purpose
• For simplicity
• Node K advertises prefix AK::/64
• The function is encoded in the last 64 bits
DC
10
11
12
13
14
2 4
6 5
7
WAN
3
1
PEER
A5::/64
A1::/64
![Page 25: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/25.jpg)
25 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
Endpoint
• For simplicity
• Function 0 denotes the most basic function
• Shortest-path to the Node
2 4
6 5 3
1
PEER
A5::0
A1::0 10
11
12
13
14
7
DC WAN
![Page 26: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/26.jpg)
26 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
A1::0 and then A5::0
PEER
2 4
6 5 3
1
A5::0
A1::0 10
11
12
13
14
7
DC WAN
![Page 27: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/27.jpg)
27 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
Endpoint then xconnect to neighbor
• For simplicity • AK::CJ denotes Shortest-path to the Node K and then x-connect (function C) to the neighbor J
2 4
6 5 3
1
PEER
A5::C7
A1::C2 10
11
12
13
14
7
DC WAN
![Page 28: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/28.jpg)
28 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
A1::0 and then A5::C7
2 4
6 5 3
1
PEER
A5::C7
A1::0 10
11
12
13
14
7
DC WAN
![Page 29: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/29.jpg)
• 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 = post convergence)
• 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
100
1
A5::0
A5::/64 Pri → via 5
INSERT A2::C4
A5::0
FRR → insert A2::C4
A5::0
<50mec FRR
![Page 30: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/30.jpg)
30 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
Overlay
• Simple – Protocol elimination
• Automated – No tunnel to configure
• Efficient – SRv6 for everything – Reuse BGP/VPN
signaling
1
2
Green Overlay V/64 via A2::C4
4
V/64
3
T/64
IPv6 ( A1::0, A2::C4 )
payload IPv6 ( T::1, V::1 )
IPv6 ( T::1, V::1 ) payload
IPv6 ( T::1, V::1 ) payload
![Page 31: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/31.jpg)
31 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
Overlay with Underlay SLA
• SRv6 does not only eliminate unneeded overlay protocols
• SRv6 solves problems that these protocols cannot solve
• Also support IPv4 and Ethernet VPN’s
1
2
Green Overlay V/64 via A2::C4 with Latency
4
V/64
3
T/64
3
IPv6 ( T1::0, V::1 ) payload
IPv6 ( A1::0, A3::0 )
payload IPv6 ( T1::0, V::1 ) SRH {A2::C4, A3::0}
IPv6 ( A1::0, A2::C4 )
payload IPv6 ( T1::0, V::1 ) SRH {A2::C4, A3::0}
IPv6 ( T1::0, V::1 ) payload
![Page 32: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/32.jpg)
32 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
IPv6 ( A1::0, A3::A32 )
payload IPv6 ( T1::0, V2::0 )
SRH { A2::C4, A5::A76, A4::0, A3::A32 }
Integrated NFV
• Stateless Service Chaining – NSH creates per-chain state
in the fabric – SR does not
• App is SR aware or not • App can work on
IPv6 or IPv4 inner packets
1
2
4
V/64
3
T/64
4
3 App 32 Container
Server 3
5 App 76 VM
Server 5
IPv6 ( T1::0, V2::0 ) payload
Inner header could be IPv4 or IPv6 or Ethernet
![Page 33: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/33.jpg)
33 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
Integrated NFV
• Integrated SLA 1
2
4
V/64
3
T/64
4
5 App 76 VM
Server 5
3 App 32 Container
Server 3 IPv6 ( A1::0, A4::0 )
payload IPv6 ( T1::0, V2::0 )
SRH
Inner header could be IPv4 or IPv6 or Ethernet
{ A2::C4, A5::A76, A4::0, A3::A32 }
![Page 34: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/34.jpg)
34 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
Integrated NFV 1
2
4
V/64
3
T/64
4
5 App 76 VM
Server 5
3 App 32 Container
Server 3
• Stateless Service Chaining – NSH creates per-chain state
in the fabric – SR does not
• App is SR aware or not • App can work on
IPv6 or IPv4 inner packets
IPv6 ( A1::0, A5::A76 )
payload IPv6 ( T1::0, V2::0 )
SRH
Inner header could be IPv4 or IPv6 or Ethernet
{ A2::C4, A5::A76, A4::0, A3::A32 }
![Page 35: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/35.jpg)
35 © 2014 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
Integrated NFV
• Integrated with Overlay
1
2
4
V/64
3
T/64
4
5 App 76 VM
Server 5
3 App 32 Container
Server 3 IPv6 ( A1::0, A2::C4 )
payload IPv6 ( T1::0, V2::0 )
SRH
IPv6 ( T1::0, V2::0 ) payload
Inner header could be IPv4 or IPv6 or Ethernet
{ A2::C4, A5::A76, A4::0, A3::A32 }
![Page 36: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/36.jpg)
The VPP library
• FD.io project is a collection of several project/libraries to support flexible, programmable and composable services on generic hardware platforms
• VPP is the ‘core’ component of the project
Performance
Packet processing
stack
Mature
Commodity CPU
![Page 37: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/37.jpg)
GW1 C::1
GW2 C::2
GW3 C::3
GW4 C::4
GW5 C::5
Content Provider
Replicate traffic to every CMTS through TE-Engineered core
path then to access mcast tree then to anycast TV
2
3
SRv6 domain (Unicast)
SRv6 node Non SRv6 node
Peering to Content Provider Multicast domain
Subscribed to M1 channel
Flexible, SLA-enabled and efficient content injection without multicast core
Spray
CMTS4 4
CMTS5 5
Spray Policy 2: <B3::, B5::, M1> Spray Policy 1: <B2::, B4::, M1>
Unicasted VPP1 B::1
![Page 38: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/38.jpg)
• Lisbon (1) to Athens (7)
• Default • <16007>
• BW: Guaranteed 50Mbps • <16010, 16011, 16007> • BSID: 24002
• Low-Latency • <16009, 16007> • BSID: 24003
1 2
3
4
5 6
7 8 9
Default
Latency
SD-WAN: Default versus BW versus Latency
24003
10 11
24002 BW
![Page 39: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/39.jpg)
• E1 encrypts the inner packet and encapsulate in outer packet to E2 • E1 does not push any BSID
SD-WAN: App needs best-effort
E1 E2
App 1 needs default Site 2 push no BSID
![Page 40: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/40.jpg)
• E1 encrypts the inner packet and encapsulate in outer packet to E2 • E1 pushes 24002
• The network provides the guaranteed BW service to App2
SD-WAN: App needs guaranteed BW
E1 E2 App 2 needs 10Mbps
Site 2 push 24002
![Page 41: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/41.jpg)
• E1 encrypts the inner packet and encapsulate in outer packet to E2 • E1 pushes 24003
• The network provides the low-latency service to App3
SD-WAN: App needs low-latency
E1 E2 App 3 needs low-latency
Site 2
push 24003
![Page 42: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/42.jpg)
• Identifier for a customized SLA per application per Enterprise • Secured • Per-BSID counters for usage-based billing • Delegates the application recognition and policy decision to the
Enterprise who knows better when an application needs a non-default path and which non-default path is needed
Binding SID is crucial for Enterprise
![Page 43: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/43.jpg)
• Enterprise can easily monitors each individual service • Simply sends the probes with the related BSID
Performance Monitoring – Enterprise-based
![Page 44: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/44.jpg)
• The SP can enable per-SR-policy perf monitoring • latency • loss
• These metrics can be leveraged by SDWAN controller and provided to the Enterprise • Simply reporting • Additional data to select which application to steer on which BSID
Performance Monitoring – SP-based
![Page 45: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/45.jpg)
Current Mobile Network Example
SGi EPC RAN
Access Node (eNode-B)
GTP-U Tunnel GTP-U Tunnel
L2 Anchor Node (Serving Gateway)
L3 Anchor Node (Packet Data
Network Gateway)Service
Functions
IPv4 IPv4
VLAN, etc.,
IPv4/IPv6
Data-plane Role
Internet, Service network
• Well fragmented to RAN, EPC and SGi. • Per-session tunnel creation and handling. • Non-optimum data-path.
![Page 46: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/46.jpg)
5G: SID Functions* for Mobile Data-Plane Roles
SRv6 Network
Access Node (eNode-B)
SRv6 SIDs
L2 Anchor Node (Serving Gateway)
L3 Anchor Node (Packet Data Network Gateway)
Uplink
Downlink
Uplink Downlink
Access Node T.Insert, or T.Encaps END.X/END.DX {6 | 4}
L2 Anchor Node END or END.B6 END or END.B6
L3 Anchor Node END.T/END.DT {6 | 4} T.Insert, or T.Encaps
* SRv6 Network Programming
Internet, Service network
![Page 47: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/47.jpg)
• 6CN: enhancing IP to search for Content • 6LB: enhancing load-balancers
• Better flow stickiness and load distribution
• Service Pipeline
• Micro-Services
More use-cases
![Page 48: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/48.jpg)
Conclusion
![Page 49: SRv6: Network as a Computer and Deployment use-cases · Segment Routing • Source Routing – the topological and service (NFV) path is encoded in the packet header • Scalability](https://reader036.fdocuments.us/reader036/viewer/2022070801/5f02683e7e708231d404201c/html5/thumbnails/49.jpg)
• Go on www.segment-routing.net and check the latest demo • Read the IETF draft: draft-filsfils-spring-srv6-network-
programming • Read the IETF BGP draft:draft-dawra-bgp-srv6-vpn-00 • Read the IETF ISIS draft:draft-bashandy-isis-srv6-extensions-00
Homework time!