investigating the recursive internetwork architecture … · investigating the recursive...

Investigating the Recursive InterNetwork Architecture as the next generation GÉANT and NREN network architecture

1

Sander Vrijders, Dimitri Staessens, Didier Colle Ghent University - iMinds GN3plus JRA1 and TERENA 3rd Network Architects Workshop

2 Connect | Communicate | Collaborate

Challenges faced by network engineers

Explosion in the complexity of the overall system (hundreds of protocols and thousands of standards documents) Weak security Scalability issues with the routing system

(IPv6/BGP multihoming) Mobile end-users

No QoS support

High OPEX


The Internet is a live environment

Ever growing customer base Ever growing number of devices New and more demanding services RAD of services Fast deployment “whac-a-mole” approach to solving problems


RINA A brief introduction to the Recursive InterNetwork Architecture


Mgt. Tasks

Application Process

Components Application specific tasks Management tasks

Application Specific Tasks Renderi

ng Game engine

Task schedul

ing

Memory mgt

Mechanism Static, invariant parts

Policy Dynamic, variant parts Occurs in pairs

Sender Receiver

IPC RIB


Distributed Application

X

Y

X X

Y X X X

Processing system: hardware and software capable of executing programs as Application Processes that can coordinate via shared memory (“test and set”) Computing system: a collection of processing systems under the same management domain with no restrictions on connectivity


Mgt. Tasks

Application Process

Components Application specific tasks Management tasks IPC Management tasks

DIF Allocator: Finds remote application processes IRM: manages DA requests Multiplexing: SDUs from different tasks SDU protection: Integrity and security

IPC Resource Manager

DIF Allocator SDU Protection

Multiplexing

IPC Mgt. Tasks

Application Specific Tasks Renderi

ng Game engine

Task schedul

ing

Memory mgt IPC RIB


Distributed Applications

host host Edge router Edge router Internal AS router

X Y Common Distributed Application Protocol


Common Distributed Application Protocol (CDAP)

Perform operations on RIB objects Create/Delete Read/Write Start/Stop

But what about different applications? The objects they manipulate Control and sequencing of operations …


Distributed Applications Provide IPC services


X Y

A1 A2 B1 B2

C2 C1 E1 E2

F1 F2 F3 F4

D1 D3 D2


Effectively extending the IPC model


IPC API

APs communicate using a port, identified by 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, …


The IPC process

IPC Process

IPC API

Data Transfer Data Transfer Control Layer Management

SDU Delimiting

Data Transfer

Relaying and Multiplexing

SDU Protection

Transmission Control

Retransmission Control

Flow Control

RIB Daemon

RIB CDAP Parser/Generator

CACEP

Enrollment

Flow Allocation

Resource Allocation

Forwarding Table Generator

Authentication

State Vector State Vector State Vector

Data Transfer Data Transfer





Flow Control Flow Control

Appl. Process

IPC Resource

Mgt.

DIF Allocator

SDU Protec

tion

Multiplexing

IPC Mgt. Tasks

Other Mgt. Tasks

Application Specific Tasks • Authentication of all processes

• RIB Daemon manages state objects • EFCP protocol performs SDU transport


Error and Flow Control Protocol

DTP Fragmentation Reassembly Sequencing Concatenation Separation

DTCP Retransmission control Flow control Transmission control

Loosely coupled by a state vector Based on Delta-t


Delta-t (Watson, 1981)

Developed at L.Livermore labs, unique approach. Assumes all connections exist all the time. keep caches of state on ones with recent activity

Watson proves that the conditions for distributed synchronization are met if and only if 3 timers are bounded:

Maximum Packet Lifetime: MPL Maximum number of Retries: R Maximum time before Ack: A

That no explicit state synchronization, i.e. hard state, is necessary. SYNs, FINs are unnecessary

1981:Watson shows that TCP has all three timers and more.


RMT


Shims

Wrap a technology with the IPC API Physical medium Legacy technology – Ethernet – IP

Hypervisors Not required to add functionality So it’s an “incomplete” DIF


Basic concept of RINA

IP (L3)

Ethernet (L2)

Physical Media (L1)

Applications

TCP/UDP (L4)

IEEE 802.1Q (L2)

IEEE 802.1ah (L2)

10GBASE-ER (L1)

Applications

MPLS (L2.5)

IP (L3)

IP (L3)

UDP (L4)

VXLAN(L2)

IP (L3)

UDP (L4)

Physical Media

Applications

DIF

DIF

DIF

DIF

IEEE 802.3 (L2)

Theory

Everyday practice

RINA


Bootstrapping a RINA network


X Y

A1 A2 B1 B2

C2 C1 D2 D1 D3 E1 E2

F1 F2 F3 F4


Architectural Model

DIF

System (Host)

IPC Process

Shim IPC Process

Mgmt Agemt

System (Router)

Shim IPC Process

Shim IPC Process

IPC Process

Mgmt Agemt

System (Host)

IPC Process

Shim IPC Process

Mgmt Agemt

Appl. Process

Shim DIF

over TCP/UDP

Shim DIF

over Ethernet

Appl. Process

IPC API

Data Transfer Data Transfer Control Layer Management

SDU Delimiting

Data Transfer

Relaying and Multiplexing

SDU Protection



Flow Control

RIB Daemon

RIB CDAP Parser/Generator

CACEP

Enrollment

Flow Allocation

Resource Allocation

Forwarding Table Generator

Authentication

State Vector State Vector State Vector

Data Transfer Data Transfer





Flow Control Flow Control

IPC Resource

Mgt.

DIF Allocator

SDU Protec

tion

Multiplexing

IPC Mgt. Tasks

Other Mgt. Tasks

Application Specific Tasks

Increasing timescale (functions performed less often) and complexity


IRATI PROTOTYPE


IRATI OS/Linux implementation

Source: S. Vrijders, F. Salvestrini, E.Grasa, M. Tarzan, L. Bergesio, D. Staessens, D. Colle “ Prototyping [RINA], the IRATI project approach”, IEEE Network, March 2014


Prototype performances


GEANT3+ IRINA


IRINA - Intro

Investigating RINA as the next generation GEANT and NREN network architecture (IRINA) GEANT3+ project

Started Oct 2013, ends March 2015 (18 months) 4 Partners:

[Research] iMinds VZW(Belgium) [Research] Fundació Privada i2CAT (Spain) [Research] Waterford Institute of Technology – Telecommunications Software & Systems Group (Ireland) [SME] Nextworks s.r.l. (Italy)


IRINA – Overview/Objectives


30

GEANT Border Router

IPC Process

IPC Process

IPC Process

IPC Process

IPC Process

P2P DIF P2P DIF

P2P DIF

IPC Process

P2P DIF

IPC Process

IPC Process

P2P DIF

IPC Process

IPC Process

Client Border Router

NREN Border Router

NREN Border Router

NREN Border Router

NREN Border Router

NREN Interior Router

NREN Interior Router

Top-Level DIF

Aggregation DIF

Backbone DIF

Aggregation DIFs

DIF 1 DIF 2

DIF 3

DIF 4

Backbone DIF

GEANT DIF

DIF 1 DIF 2

DIF 4 DIF 5

DIF 3

DIF 6 Top Level DIFs

GEANT DIF

IPC Process

P2P DIF P2P DIF

IPC Process

Client DIF

Multi DIFs (e.g. Public Internet DIF, application-specific DIF, etc)

P2P DIF

Client DIF

Internal NREN network design


Lab trials of RINA

rina-echo-time application of IRATI basic ping functionality rudimentary bandwidth testing capabilities

Traffic generation tool is needed

Netperf Distributed Internet Traffic Generator Ostinato


Traffic modelling

IEEE 802.16 Interrupted Poisson Processes (IPP) Interrupted Renewal Processes (IRP) Interrupted Discrete Processes (IDP)

4IPP IDP, 2IDP, 4IDP 2IRP


IRATI DEMO


Demo setup

Application Process

Application Process

IPC Process

IPC Process

Shim IPC Process

Shim IPC Process

Host A Host B

Shim DIF

Normal DIF A


RINA TIMELINE Where does the IRINA project fit in the big picture?

35


An optimistic timeline

2012 2013 2014 2015 2016 2017 2018 2019 2020 2011

PRISTINE 01/2014-06/2016

National and Individual projects

(US/EU)

Inter-university RINA / IPSec tunnels

Small lab prototypes Linux kernel prototype

Mature Linux kernel prototype

IRATI 01/2013-12/2014

ALL-RINA networks

Initial specification (PSOC)

Standardisation (ISO/SC6)

NREN lab prototypes

IRINA 10/13-03/14

RINA DIFs supported by NRENs

DIFs being adopted by

Carriers

Future research projects

COTS Commercial products

Niche Commercial products


Upcoming workshops

Globecom Workshop “Alternatives to TCP/IP” 8-12 December, Austin TX US

RINA workshop

28-29 January 2015, Ghent Belgium

TERENA TNC 2015 June, Porto, Portugal

Summer school 2015 (?)


www.geant.net

www.twitter.com/GEANTnews | www.facebook.com/GEANTnetwork | www.youtube.com/GEANTtv

Connect | Communicate | Collaborate

Thank you!

investigating the recursive internetwork architecture … · investigating the recursive...

Documents