Experimental evaluation of a Recursive InterNetwork Architecture prototype Sander Vrijders, Dimitri Staessens, Didier Colle (Ghent University iminds) Francesco Salvestrini, Vincenzo Maffione (Nextworks s.r.l.) Leonardo Bergesio, Miquel Tarzan-Lorente, Bernat Gaston, Eduard Grasa (i2cat Foundation) 1/7/15 1
Basic concept of the Recursive InterNetwork Architecture Everyday practice Applications Theory Applications TCP/UDP (L4) IP (L3) Ethernet (L2) Physical Media (L1) UDP (L4) IP (L3) VXLAN(L2) UDP (L4) IP (L3) IP (L3) IEEE 802.3 (L2) MPLS (L2.5) IEEE 802.1Q (L2) IEEE 802.1ah (L2) 10GBASE-ER (L1) RINA Applications DIF DIF DIF DIF Physical Media
IPC API APs communicate using a portid 6 operations: int _registerapp(appname, List<difName>) portid _allocateflow(destappname, List<QoSParams>) int _write(portid, sdu) sdu _read(portid) int _deallocate(portid) int _unregisterapp(appname, List<difName>) QoSParams are defined in a technology-agnostic way Bandwidth-related, delay, jitter, in-order-delivery, loss rates,
Architectural Model Application Specific Tasks Other Mgt. Tasks Appl. System (Host) System (Router) Mgmt Agemt Appl. System (Host) IPC Mgt. Tasks Multipl exing SDU Protec tion IPC Resource Mgt. DIF Allocator Mgmt Agemt IPC Shim DIF over TCP/UDP IPC DIF Shim DIF over Ethernet IPC Mgmt Agemt IPC API Data Transfer Data Transfer Control Layer Management SDU Delimiting Data Data Transfer Transfer Data Transfer Relaying and Multiplexing SDU Protection State Vector State Vector State Vector Transmission Transmission Control Control Control Retransmission Retransmission Control Control Control Flow Control Flow Control Flow Control RIB Daemon RIB CACEP Authentication CDAP Parser/ Generator Enrollment Flow Allocation Resource Allocation Forwarding Table Generator Increasing timescale (functions performed less often) and complexity
Host A Host B Application Application Flow IPC E F C P E F C P IPC Connection
PROTOTYPE
OS/Linux implementation Source: S. Vrijders, F. Salvestrini, E.Grasa, M. Tarzan, L. Bergesio, D. Staessens, D. Colle Prototyping [RINA], the project approach, IEEE Network, March 2014
Host A Host B Host R VLAN 300 VLAN 400 8
Host A Host R Host B test1. test3. VLAN 300 VLAN 400 1/7/15 9
Host A Host B Host R test1. test2. test3. VLAN 300 VLAN 400 1/7/15 10
Host A Host B Host R test1. Normal DIF A test2. test3. VLAN 300 VLAN 400 1/7/15 11
Host A Host B Host R test1. Normal DIF A test2. test3. VLAN 300 VLAN 400 1/7/15 12
Host A Host B Host R rina-echo time server test1. Normal DIF A test2. test3. VLAN 300 VLAN 400 1/7/15 13
Host A Host B Host R rina-echo time server rina-echo time client test1. Normal DIF A test2. test3. VLAN 300 VLAN 400 1/7/15 14
Bootstrapping a RINA network host Edge router Internal AS router Edge router host X Y F3 F1 F2 F4 C2 C1 D2 D1 D3 E1 E2 A1 A2 B1 B2
Data center (DC) network Example scenario: Customer access DC via the Internet DAP DAP Customer DIF (VPN) P2P DIF DataCentre (DC) Fabric DIF Public Internet DIF Customer Site DIF VM P2P DIF P2P DIF P2P DIF Provider 1 Metro DIF Provider 2 Metro DIF P2P DIF P2P DIF Border Router (Server) Interior Router (Top of Rack) Interior Router (Aggregation) Border Router (DataCentre) P2P DIF P2P DIF Access DIF Border Router (Customer Site) Interior Router Host BR (NSP 1) BR (NSP 1) BR (NSP2) BR (NSP 2) DC Network Provider 1 Network Provider 2 Network Customer Network
Experimental evaluation of a Recursive InterNetwork Architecture prototype
Extra information RINA workshop 28 January 2015, Ghent Belgium Register at http://ict-pristine.eu/?p=350 prototype can be found at https://irati.github.io/stack/