Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Rina IRATI GLIF Singapore 2013

1,425 views

Published on

Overview of European RINA research and development activities, with a main focus in the work of the IRATI project. Presented at the 13th GLIF annual meeting, Singapore.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Rina IRATI GLIF Singapore 2013

  1. 1. Early RINA prototyping and deployment in the IRATI project, and future research in the PRISTINE and IRINA projects Sergi Figuerola, Innovation and Technology Director (sergi.Figuerola@i2cat.net) 13th annual Global LambdaGrid Workshop October 4th, 2013 13th Annual Global LambdaGrid Workshop © Fundació i2CAT 2013
  2. 2. Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations) 13th Annual Global LambdaGrid Workshop 2 © Fundació i2CAT 2013
  3. 3. RINA is an.. Innovative approach to computer networking using inter-process communications (IPC), a set of techniques for the exchange of data among multiple threads in processes running on one or more computers connected to a network. Ref. : J. Day: “Patterns in Network Architecture: A Return to Fundamentals, Prentice Hall, 2008. The RINA principle: Networking is not a layered set of different functions but rather a single layer (DIF) of distributed IPC’s that repeats over different scopes. 13th Annual Global LambdaGrid Workshop 3 © Fundació i2CAT 2013
  4. 4. RINA Architecture • • • Separation of mechanism from policy All layers have the same functions, with different scope and range. – • There’s a single type of layer that repeats as many times as required by the network designer • • A structure of recursive layers that provide IPC (Inter Process Communication) services to applications on top Not all instances of layers may need all functions, but don’t need more. A Layer is a Distributed Application that performs and manages IPC (a Distributed IPC Facility –DIF-) This yields a theory and an architecture that scales indefinitely, – i.e. any bounds imposed are not a property of the architecture itself . 13th Annual Global LambdaGrid Workshop © John Day, All Rights Reserved, 2011 4 © Fundació i2CAT 2013
  5. 5. Naming and addressing in RINA • • 1 1 DIF A 2 DIF B 2 2 DIF C 3 1 2 DIF D 1 DIF E 2 1 DIF F 2 In order to facilitate its operation within a DIF, each IPC process within a DIF gets a synonym that may be structured to facilitate its use within the DIF (i.e. an address). 4 3 1 All application processes (including IPC processes) have a name that uniquely identifies them within the application process namespace.  The scope of an address is the DIF, addresses are not visible outside of the DIF.  The Flow Allocator function of the DIF finds the DIF IPC Process through which a destination Application process can be accessed.  Because the architecture is recursive, applications, nodes and PoAs are relative  For a given DIF of rank N, the IPC Process is a node, the process at the layer N+1 is an application and the process at the layer N-1 is a Point of Attachment . 13th Annual Global LambdaGrid Workshop 5 © Fundació i2CAT 2013
  6. 6. Architectural model System (Host) System (Router) Appl. Process IPC Process Appl. Process Mgmt Agemt IPC Process DIF IPC Process Mgmt Agemt Shim DIF over TCP/UDP Shim IPC Process Shim IPC Process Shim IPC Process System (Host) Shim DIF over Ethernet Mgmt Agemt Shim IPC Process IPC API Data Transfer Data Transfer Data Transfer Data Transfer Relaying and Multiplexing SDU Protection State Vector State Vector State Vector SDU Delimiting Layer Management Data Transfer Control Transmission Control Transmission Control Transmission Control Retransmission Retransmission Retransmission Control Control Control Flow Control Flow Control Flow Control CACEP RIB Daemon RIB RIB Enrollment Authentication Flow Allocation CDAP Parser/Generator Resource Allocation Forwarding Table Generator Increasing timescale (functions performed less often) and complexity 13th Annual Global LambdaGrid Workshop 6 © Fundació i2CAT 2013
  7. 7. Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations) 13th Annual Global LambdaGrid Workshop 7 © Fundació i2CAT 2013
  8. 8. Why researching RINA (I) • Architecture: – Today: 5 layers, layers “2.5”, layer violations, “overlays”, “virtual networks”, Today “middleboxes” (NATs, firewalls, application-layer gateways) Getting complex! – RINA: Repeating structure, DIF (one type of layer, repeat as needed) RINA • Naming, addressing and routing: – Today: No independent application names, no node names, just PoA names, Today routing on PoAs (multi-homing and mobility is hard to support) – RINA: Complete naming & addressing, routing on the node; support for multiRINA homing and mobility without special protocols. No need for global address space. • Congestion control: – Today: Put in TCP, not in the best place it could be, since it maximizes the delay Today and variance of the control loop (makes the system chaotic: self-similar traffic) – RINA: Each layer can perform congestion control, confining the effects of RINA congestion to that layer. The delay and variance of control loops can be bound. 13th Annual Global LambdaGrid Workshop 8 © Fundació i2CAT 2013
  9. 9. Why researching RINA (II) • Scalability: – Today: Limited due to the fixed number of layers in the architecture Today – RINA: Recursion provides a divide and conquer approach, the way to scalability RINA • Security: – Today: No systematic approach to security, secure each protocol or add boxes in Today between to improve security (firewalls). – RINA: Strong design dictates where security functions go in the architecture RINA (encryption, authenticaiton, access control). DIFs are securable containers. • Quality of Service: – Today: Best effort is the dogma, applications cannot express desired outcomes Today – RINA: Each DIF is free to provide different QoS classes, using different policies for RINA resource allocation, routing and data transfer. Applications can request the desired characteristics for a flow (delay, loss, ordering, etc) • Management: – Today: Complex, reflecting the complexity in the architecture and the high Today number of protocols. – RINA: The commonality in the structure simplifies management by orders of RINA magnitude 13th Annual Global LambdaGrid Workshop 9 © Fundació i2CAT 2013
  10. 10. Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations) 13th Annual Global LambdaGrid Workshop 10 © Fundació i2CAT 2013
  11. 11. Flow of RINA R&D activities (feedback between activities not shown for clarity reasons) Data transfer DIF creation Multiplexing Research on Application policies for discovery different Enrollment Security areas Manage ment Routing Policy specs Resource allocation Design and development of simulators Study different use cases and deployment options Research on RINA reference model Core RINA specs Simul ators Use case analy sis Proto types Prototyping Java VM Linux OS Data and conclu sions Experiment ation and validation Different Platforms Android OS NetFP GA 13th Annual Global LambdaGrid Workshop TCP/UDP /IP Coexisting VLANs with different technolog WiFi ies MPLS LTE 11 © Fundació i2CAT 2013
  12. 12. Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations) 13th Annual Global LambdaGrid Workshop 12 © Fundació i2CAT 2013
  13. 13. IRATI @ a Glance • http://irati.eu What? Main goals – To advance the state of the art of RINA towards an architecture reference model and specifications that are closer to enable implementations deployable in production scenarios. – The design and implementation of a RINA prototype on top of Ethernet will enable the experimentation and evaluation of RINA in comparison to TCP/IP. Who? 4 partners 5 activities:  WP1: Project management  WP2: Arch., Use cases and Req.  WP3: SW Design and Implementation  WP4: Deployment into OFELIA  WP5: Dissemination, Standardisation and Exploitation Budget Total Cost 1.126.660 € EC Contribution 870.000 € Duration 2 years Start Date 1st January 2013 External Advisory Board Juniper Networks, ATOS, Cisco Systems, Telecom Italia, BU 13th Annual Global LambdaGrid Workshop 13 © Fundació i2CAT 2013
  14. 14. IRATI contributions to RINA roadmap • Reference model and core specifications – Detect inconsistencies and errors • Research on policies for different areas – Routing (link-state), Shim DIF over Ethernet VLANs (802.1q) • Use cases – Corporate VPNs and cloud networking • Prototyping – Initial implementation for Linux OS (user-space and kernel) – Porting of RINA implementation to Juniper platforms • Experimentation – First experimental analysis of RINA against TCP/IP in similar conditions (focusing in LAN environments) 13th Annual Global LambdaGrid Workshop 14 © Fundació i2CAT 2013
  15. 15. Cloud/Network provider use case (Introduction) • RINA applied to a hybrid cloud/network provider – Mixed offering of connectivity (Ethernet VPN, MPLS IP VPN, Ethernet Private Line, Internet Access) + computing (Virtual Data Center) Datacenter Design Access Network Wide Area Network 13th Annual Global LambdaGrid Workshop 15 © Fundació i2CAT 2013
  16. 16. Cloud/Network provider use case (Modeling) PE CE Customer 1 Site A CE Customer 1 Site B PE MPLS backbone CE Customer 2 Site A CE PE Customer 1 Site C CE PE Customer 2 Site B PE Internet GW CE CE TOR TOR TOR TOR HV VM VM VM HV VM VM VM HV VM VM VM HV VM HV VM VM VM HV VM VM VM Public Internet HV VM VM VM HV VM VM VM VM VM HV VM VM VM HV VM VM VM HV VM VM VM HV VM VM VM HV VM VM VM HV VM VM VM HV VM VM VM HV VM VM VM Customer 2 Site C End user Data Center 1 13th Annual Global LambdaGrid Workshop Data Center 2 16 © Fundació i2CAT 2013
  17. 17. Cloud/Network provider use case (Applying RINA) Scenario 1: Inter-DC Customer A DIF Inter-datacenter DIF Datacenter-wide DIF VM HV Provider top-level DIF CE TOR P CE TOR PE Backbone Provider Access network VM HV Backbone DIF PE Datacenter 1 network Datacenter-wide DIF Network Service Provider Core Network Provider Access network Datacenter 2 network Scenario 2: DC-Customer Customer A DIF Datacenter-wide DIF VM HV TOR Provider top-level DIF CE Backbone DIF PE Datacenter 1 network Access network P Interoute core network CE PE Access network 13th Annual Global LambdaGrid Workshop Customer 1 site A network 17 © Fundació i2CAT 2013
  18. 18. Shim DIF over Ethernet General requirements • The task of a shim DIF is to put a small as possible veneer over a legacy protocol to allow a RINA DIF to use it unchanged. – Not a RINA-conformant application.  We are not trying to make legacy protocols provide full support for RINA.   – Anything more should be provided by the first full DIF. • The shim DIF should provide no more service or capability than the legacy protocol provides.   System (Host) System (Router) Appl. Process IPC Process Appl. Process Mgmt Agemt IPC Process DIF IPC Process Mgmt Agemt Shim IPC Process Shim DIF over TCP/UDP Shim IPC Process Shim IPC Process Shim DIF over Ethernet 13th Annual Global LambdaGrid Workshop System (Host) Mgmt Agemt Shim IPC Process 19 © Fundació i2CAT 2013
  19. 19. High-level software architecture General requirements and choices • Linux has been the chosen target platform for IRATI, due to – It is widely used in different contexts – Open source OS with a great community and documentation • However the implementation aims to be as reusable as possible in similar environments – other UNIX-based Operating Systems • The implementation targets both the user-space and the kernel-space, since – Low performance penalties have to be achieved for highly-frequent tasks (such as reading and writing data) -> Some components must be placed in the kernel – There is the need to access device driver functionalities in order to be able to overlay RINA on top of Ethernet (or other networking technologies in the future) -> Some components must be placed in the kernel 13th Annual Global LambdaGrid Workshop 20 © Fundació i2CAT 2013
  20. 20. Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations) 13th Annual Global LambdaGrid Workshop 23 © Fundació i2CAT 2013
  21. 21. PRISTINE @ a Glance • What? Main goals – – – To design and develop an SDK for the IRATI RINA prototype, to unleash the programmability provided by RINA. To use the SDK to design, implement and trial a set of a policies to create optimized DIFs for each of the project use cases: distributed cloud, datacenter networking and network service provider. To design and implement the first RINA multi-layer management system. Who? 15 partners 7 activities:  WP1: Project management  WP2: Use cases, req. analysis and programmable reference architecture  WP3: Programmable performanceenhancing functions and protocols  WP4: Innovative security and reliability enablers  WP5: Multi-layer management plane  WP6: System-level integration, validation, trials and assessment WIT-TSSG, i2CAT, TID, Ericsson, NXW, Thales,  Nexedi, Atos, BISDN, Juniper, Telecom SudParis, U Brno, UiO, CREATE-NET, iMinds WP7: Dissemination, standardisation and exploitation 13th Annual Global LambdaGrid Workshop Budget Total Cost 5.034.961 € EC Contribution 3.337.000 € Duration 2.5 years Start Date 1st January 2014 External Advisory Board Cisco Systems, Telecom Italia, Deutsche Telekom, Colt Telecom, BU, Interoute 24 © Fundació i2CAT 2013
  22. 22. PRISTINE contributions to RINA roadmap • Reference model and core specifications – Detect inconsistencies and errors • Research on policies for different areas – Congestion control, distributed resource allocation, addressing, routing, authentication, access control, encryption, DIF management • Use cases – Decentralized cloud, datacentre networking, network service provider • Prototyping – Build on IRATI implementation for Linux OS. Develop SDK to allow easier customization, develop sophisticated policies with SDK. Prototype first DIF Management System • Experimentation – More realistic experimentation, with more complex deployments, coexisting with several technologies at once (IPv4, IPv6, Ethernet), usage of business applications 13th Annual Global LambdaGrid Workshop 25 © Fundació i2CAT 2013
  23. 23. Use cases • Distributed cloud – Decentralized cloud technology; customer’s applications run in datacenters but also in servers from offices and home users. – Infrastructure interconnected through multiple ISPs, overall connectivity provided through overlay on top -> Use RINA to provide this overlay • Datacentre networking – Evaluate RINA as a technology that allows more dynamicity and tighter integration with applications (dynamic instantiation of application-optimized VPNs) • Network Service Provider – Investigate benefits of RINA for NSP: better network design, simpler management, DIFs that support different levels of QoS with stronger flow isolation, better security, programmability, etc. 13th Annual Global LambdaGrid Workshop 26 © Fundació i2CAT 2013
  24. 24. PRISTINE Infrastructure for trials Virtual Wall EXPERIMENTA Trentino Testbed 13th Annual Global LambdaGrid Workshop 27 © Fundació i2CAT 2013
  25. 25. Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations) 13th Annual Global LambdaGrid Workshop 28 © Fundació i2CAT 2013
  26. 26. IRINA @ a glance • What? Main goals – To make a study of RINA against the current networking state of the art and the most relevant clean-slate architectures under research. – To perform a use-case study of how RINA could be better used in the NREN scenario, and showcase a lab-trial of the use case – To involve the NREN and GEANT community in the different steps of the project, in order to to get valuable feedback Who? 4 partners 5 activities:  WP1: Technical coordination and interaction with GEANT3+  WP2: Comparative analysis of network architectures  WP3: Use case study and lab trials  WP4: Dissemination and workshop organization Budget Total Cost 199.940 € EC Contribution 149.955 € Duration 18 months Start Date 1st November 2013 13th Annual Global LambdaGrid Workshop 29 © Fundació i2CAT 2013
  27. 27. IRINA contributions to RINA roadmap • Reference model and core specifications – Compare with other clean-slate architectures • Use cases – Research network operators (NRENs and GEANT environment) • Prototyping – Little adaptations to the IRATI prototype (Linux OS), to be able to trial the use case in the lab • Experimentation – Focus on the requirements of NRENs 13th Annual Global LambdaGrid Workshop 30 © Fundació i2CAT 2013
  28. 28. GEANT and NRENs use case 13th Annual Global LambdaGrid Workshop 31 © Fundació i2CAT 2013
  29. 29. Many Thanks ! Moltes gràcies ! Sergi Figuerola, Innovation and Technology Director (sergi.Figuerola@i2cat.net) Eduard Grasa, RINA research line leader (eduard.grasa@i2cat.net) 13th annual Global LambdaGrid Workshop October 4th, 2013 13th Annual Global LambdaGrid Workshop http://www.i2cat.cat http://dana.i2cat.net http://irati.eu © Fundació i2CAT 2013

×