RINA Distributed Mobility Management over WiFi
- 1. Large scale RINA Experimentation on FIRE + Distributed Mobility Management demo
- 2. Trends in future converged networks • MEC: Local storage, local compute and networking processing of “edge” services in the mobile network, enabling cloud capabilities at closer proximities to the mobile user • Slicing / Virtualisation: Security and performance-isolated network slices, sharing the same network infrastructure and optimized for the delivery of different applications (“verticals”) • Distributed mobility management: avoid centralized mobility anchors to provide efficient routing and traffic management. Get rid of tunnels if possible. Large-scale RINA Experimentation on FIRE+ 2
- 3. RINA in one slide Large-scale RINA Experimentation on FIRE+ 33 Host Border router Interior Router DIF DIF DIF Border router DIF DIF DIF (Distributed IPC Facility) Host App A App B Consistent API through layers IPC API Data Transfer Data Transfer Control Layer Management SDU Delimiting Data Transfer Relaying and Multiplexing SDU Protection Retransmission Control Flow Control RIB Daemon RIB CDAP Parser/Generator CACEP Enrollment Flow Allocation Resource Allocation Routing Authentication StateVector StateVector StateVector Data TransferData Transfer Retransmission Control Retransmission Control Flow Control Flow Control Increasing timescale (functions performed less often) and complexity Namespace Management Security Management
- 4. What RINA can do for you • Place compute/storage resources where needed. RINA discover distributed applications, locating processes and allocating flows to them independent of their network location. • Native support for scope, virtualization and slicing: DIFs are securable layers whose policies can be tailored to the needs of each tenant/application. • Support for mobility without the need of tunnels or dedicated protocols. Scoped routing, topological addressing and architectural support for seamless renumbering allow RINA to efficiently support any type of mobility. Large-scale RINA Experimentation on FIRE+ 4
- 5. Physical systems May 2017 OMEC Workshop demo Large-scale RINA Experimentation on FIRE+ 5 Access 1 Access 2 Access 3 UE VLAN 10 Wifi (ssid pristine) Wifi (ssid irati) Core 1 Core 2 Gateway ISP1 ISP2 Server1 Server2 VLANs 20,21 VLAN 30 VLAN 40 VLAN 50 Wifi (ssid arcfire) VLAN 60 VLAN 70 VLAN 80 VLAN 90 VLAN 100 VLAN 20 VLAN 30 VLANs 10,21 Laptop running Demonstrator (Blue boxes are QEMU/KVM VMs) Raspberry Pi 3B Laptop VLAN-Aware Eth. Switch
- 6. DIFs Large-scale RINA Experimentation on FIRE+ 6 UE Access 1 Core 1 Gateway ISP1 Server1 Mobile network DIF Internet DIF DAF (rina-tgen or rina-echo-time) Shim DIF Eth Shim DIF Eth Shim DIF Eth Shim DIF Eth Shim DIF Eth UE A1 A3 A2 C1 GW C2 Mobile Network DIF I1 UE GW S1 S2I2 Internet DIF
- 7. Storyboard: Initial state • Initial setup: All nodes except UE already up & running and configured • Server 1 and 2 run rina-echo-time server Large-scale RINA Experimentation on FIRE+ 7 Access 1 Core 1 Gateway ISP1 Server1 Mobile network DIF Internet DIF Shim DIF Eth Shim DIF Eth Shim DIF Eth Shim DIF Eth ET
- 8. Storyboard: UE enrollment • UE enrolls to mobile network DIF • UE enrolls to Internet DIF • UE allocates 2 flows to rina-echo-time servers Large-scale RINA Experimentation on FIRE+ 8 UE Access 1 Core 1 Gateway ISP1 Server1 Mobile network DIF Internet DIF DAF (rina-tgen or rina-echo-time) Shim DIF Eth Shim DIF Eth Shim DIF Eth Shim DIF Eth Shim DIF Eth
- 9. Storyboard: Handover • UE starts moving towards Access2, at some point it allocates a flow to Access2 (UE is multihomed) • UE continues moving further away from Access 1, flow to it is deallocated. When UE is closer to A3, it allocates a flow to it. • All of this happens in the mobile network DIF without impacting higher DIF flows. Large-scale RINA Experimentation on FIRE+ 9 UE A1 A3 A2 C1 GW C2 Mobile Network DIF UE A1 A3 C1 GW C2 Mobile Network DIF A2 UE A1 C1 GW C2 Mobile Network DIF A2 A3
- 10. Current status of demo Things that are yet to be improved • All flows unreliable (no rtx. control) – Packet loss reported by the rina-echo-time app from time to time due to losses on the WiFi link – Rtx. Control implementation has a bug that prevents its use on the current demo -> working on it • Integration with WPASuplicant – Optimize scan time (too long scans may also cause packet loss) • Routing policy in mobile DIF not optimized for mobility yet – Uses default link state routing policy with flat addressing – From time to time a packet is lost during handover – Next step: work on better routing policies for handling mobility in different scenarios (leverage topological addressing and seamless IPC Process renumbering) Large-scale RINA Experimentation on FIRE+ 10
- 11. FUTURE DEMO: OMEC Access to different applications in different nets Secure layers Distributed mobility management Large-scale RINA Experimentation on FIRE+ 11
- 12. Large-scale RINA Experimentation on FIRE+ 12 Physical systems UE 1 UE 2 AR 1 AR 2 AR 3 AR 4 AR 5 AR 6 CR 1 CR 2 GW 1 ISP 1 ISP 2 SRV 5 SRV 6 SRV 1 SRV 2 SRV 3 SRV 4 ToR 2 ToR 1 DC GW Small DC Service Provider net Data Center Gateway User Equipment Provider Access Router Core Router Provider 1 Border Router ISP Router Server Top of Rack Router
- 13. DIFs (I) Large-scale RINA Experimentation on FIRE+ 13 UE Access 1 Core 1 Gateway ISP1 Server6 Mobile network DIF Internet DIF DAF (rina-tgen or rina-echo-time) Shim DIF WiFi Shim DIF Eth Shim DIF Eth Shim DIF Eth Shim DIF Eth UE A1 A4 A2 C1 GW C2 Mobile Network DIF I1 UE GW S1 S2I2 Internet DIF A3 A5 A6 DC
- 14. DIFs (II) Large-scale RINA Experimentation on FIRE+ 14 UE Access 2 Core 1 DC Gateway ToR 1 Server 1 Mobile network DIF Enterprise 1 VPN DIF DAF (Any demo app) Shim DIF WiFi Shim DIF Eth Shim DIF Eth Shim DIF Eth Shim DIF Eth S2 GW S4Enterprise 2 VPN DIF DC Fabric DIF S1 UE 1 GW S3Enterprise 1 VPN DIF UE 2 S2 S1 S3 S4 GW ToR 1 ToR 2
- 15. Storyboard • 2 UEs belonging to users of two different enterprises • Each enterprise has applications hosted in the DC owned by the operator – Each enterprise has its own private slice (DIF) of the DC hosting their apps • Owner of first UE (enterprise A), accesses some app in the Internet (e.g. Web browsing), and also accesses enterprise App (e.g. rina-tgen for example) – DIF Allocator chooses right DIF to use (locating the app by name), and creates IPCPs in the UE required to join enterprise VPN DIF (requires authentication) or public Internet DIF – User can move while accessing his/her application • Owner of second UE (enterprise B) can do the same, but accessing the app via its enterprise VPN DIF Large-scale RINA Experimentation on FIRE+ 15