Multi-operator "IPC" VPN Slices: Applying RINA to Overlay Networking

1. CIENA BT I2CAT TSSG

3. PoC: Multi-Operator
“IPC” VPN Slice
Enterprise Application Service Provider
“IPC” VPN Slice - Intent API
E2E Slice Automation
Service Monthly Fees
Slice Subnet Automation
IPC = InterProcess Communication
Slice Subnet AutomationSlice Subnet Automation

5. Context-Aware
“IPC” VPN Slices
Scenario – Enterprise Application Server
Provider uses RINA
• RINA Slice between Host & App Service
• ‘On Demand’, i.e., Slice not nailed up
• User Device & Application specific Context
RINA: Recursive Internet Network Architecture
DIF: Distributed IPC Facility; IPC: Inter-Process Communication
Inter-Galactic SP
Host
1
SRV
2
SRV
1
RINA DIF Core DC
(Slice Dashed)
RINA DIF Edge DC
(Slice Solid)
Hosted APP
(Core DC)
User
Hosted APP
(Edge DC)
DIF Edge DC
DIF Core DC
QoS Cube: Reliable/Unreliable
Overlay: RINA DIFs
Multi—Domain L2 VPN “Fabric”
Underlay: Fabric
Control
https://xkcd.com/1810/
DIF DC

6. “IPC” VPN Slices
Single Operator Single Domain
Host 1
SxRV
2
SRV 1
(P4 LTE)
P4 Service
Provider
Hosted APP
(Edge DC)
Hosted APP
(Core DC)
CE
CE
Customer Edge
CE
(P4 Data
Centre)
(P4 LTE)
P4 =Service Provider as a Single Operator across a
Single Domain

7. “IPC” VPN Slices
Single Operator Multi-Domain
Host 1
SxRV
2
SRV 1
(P4 Wifi)
P4 Service
Provider
Hosted APP
(Edge DC)
Hosted APP
(Core DC)
CE
CE
Customer Edge
CE
(P4 Data
Centre)
(P4 LTE)
P4 =Service Provider across a Multiple Domains

8. “IPC” VPN Slices
Multi-Operator Multi-Domain
Host 1
SxRV
2
SRV 1
(P1 Wifi)
P4 Service
Provider
Hosted APP
(Edge DC)
Hosted APP
(Core DC)
CE
CE
Customer Edge
CE
(P3 Data
Centre)
(P2 LTE)
P4 =Service Provider as a Multi Operator across
Multiple Domains

10. “IPC” VPN Slices
Objective
Inter-Galactic SP
Host
1
SRV 2
SRV
1
RINA DIF D
(Slice Dashed)
RINA DIF S1
(Slice Solid)
Hosted APP
(Edge DC)
Host
1
SRV 2
SRV
1
(P1)
P4=“SP”
User
Hosted APP
(Edge DC)
CE
CE
(P3)
(P2)
RINA Overlay – “IPC” VPN for VM Networking
üDistributed Inter-Process Communication Facility (DIF)
üETH Shim to map to C-VLAN Tagged Ethernet Frame
ü“IPC” VPN Slice flow à L2 VPN Underlay
• “IPC” VPN QoS Cube à L2 VPN Class of Service
Orchestrated Slice on Demand
üAutonomous “IPC” VPN Overlay
• L2 VPN Underlay
Separation of Concerns
üIPC VPN Name Space for DC Provider vs SP
• Service Demarcation
Service Continuity
• Path independent Application association
üMobile CE/Host attachment to Application
CE
Customer
Edge
P1, P2 & P3=“Last Mile”
Partners

11. Overlay/ “IPC VPN”
(VM Network)
Concept –
“IPC” VPN Slices
Core NodeMetro NodeAccess NodeCPE Node
L S S S
“WAN” Leaf/Spine
Fabric
Underlay
(L2 VPN)
Create as many DIFs as needed depending on density of devices and speed of mobility in the network
Each application can use the DIF that provides enough scope and QoS for its communication needs
RINA = layers have the same structure and protocols, implementations can be highly optimized
Server
Endpoint
User ApplicationServer
Endpoint

12. Slice Orchestration
Recursive Abstraction
User /DC
Application
P4/SP Slice Orchestration
P1 Slice Subnet
Orchestration
P4 Slice Subnet
Orchestration
P3 Slice Subnet
Orchestration
FD-(EVP-LAN C-Tag Flows)
LTP
FD– Core DIF
FD– Edge DIF
FD-P1 FD-P4 FD-P3
LTP1 LTP2
LTP4LTP3
LTP
LTP
LTP
LTP
LTP
Underlay
(L2 VPN)
LTP LTP LTP LTP
Metro Core Metro
E2E
Create Core/Edge Slices
Create DIF EPs & FD Create DIF EPs & FD Create DIF EPs & FD
LTP1
LTP3 LTP4
LTP2
Partner Partner
P1, P2 & P3=“Last Mile”
Partners
FD– DC DIFLTP5 LTP6
LTP5 LTP6

13. ICIN Workshop Demo
Dynamic Slice Instantiation and Mobility Support

14. ICIN Workshop Demo
Dynamic Slice Instantiation and Mobility Support

15. miguelpdl@tssg.org
rraghu@ciena.com dbainbri@ciena.com kramanar@ciena.com
andy.petrie@bt.com
egrasa@i2cat.net