RINA IRATI Korea-EU Workshop 2013
Download as PPT, PDF1 like1,717 views
The document discusses the Recursive InterNetwork Architecture (RINA) and its potential benefits over current networking paradigms, such as improved scalability, security, and quality of service. It outlines ongoing research projects, including IRATI, PRISTINE, and IRINA, that aim to develop and implement RINA prototypes and evaluate them against traditional TCP/IP approaches. The text emphasizes the need for a simplified architecture that addresses contemporary networking challenges through recursive structures and innovative policies.
RINA IRATI Korea-EU Workshop 2013
- 1. Early RINA prototyping and deployment under the IRATI project, and the future research in PRISTINE and IRINA projects Sergi Figuerola, Technology and Innovation Director Korea-EU Workshop, September 30th, 2013 RINA Research, Korea-EU Workshop © Fundació i2CAT 2013
- 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) RINA Research, Korea-EU Workshop 2 © Fundació i2CAT 2013
- 3. RINA Architecture • • 1 DIF A 2 1 DIF B 2 • 1 • Separation of mechanism from policy 2 DIF E 2 1 DIF F 2 All layers have the same functions, with different scope and range. – • 3 DIF D 1 • 2 DIF C There’s a single type of layer that repeats as many times as required by the network designer 4 3 1 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 . RINA Research, Korea-EU Workshop © John Day, All Rights Reserved, 2011 3 © Fundació i2CAT 2013
- 4. Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations) RINA Research, Korea-EU Workshop 5 © Fundació i2CAT 2013
- 5. Why researching RINA (I) • Architecture: – Today: 5 layers, layers “2.5”, layer violations, “overlays”, “virtual networks”, “middleboxes” (NATs, firewalls, application-layer gateways) Getting complex! – RINA: Repeating structure, DIF (one type of layer, repeat as needed) • Naming, addressing and routing: – Today: No independent application names, no node names, just PoA names, routing on PoAs (multi-homing and mobility is hard to support) – RINA: Complete naming & addressing, routing on the node; support for multihoming and mobility without special protocols. No need for global address space. • Congestion control: – Today: Put in TCP, not the best place it could be, since it maximizes the delay and variance of the control loop (makes the system chaotic: self-similar traffic) – RINA: Each layer can perform congestion control, confining the effects of congestion to that layer. The delay and variance of control loops can be bound. RINA Research, Korea-EU Workshop 6 © Fundació i2CAT 2013
- 6. Why researching RINA (II) • Scalability: – Today: Limited due to the fixed number of layers in the architecture – RINA: Recursion provides a divide and conquer approach, the way to scalability • Security: – Today: No systematic approach to security, secure each protocol or add boxes in between to improve security (firewalls). – RINA: Strong design dictates where security functions go in the architecture (encryption, authenticaiton, access control). DIFs are securable containers. • Quality of Service: – Today: Best effort is the dogma, applications cannot express desired outcomes – RINA: Each DIF is free to provide different QoS classes, using different policies for 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 number of protocols. – RINA: The commonality in the structure simplifies management by orders of magnitude RINA Research, Korea-EU Workshop 7 © Fundació i2CAT 2013
- 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) RINA Research, Korea-EU Workshop 8 © Fundació i2CAT 2013
- 8. 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 RINA Research, Korea-EU Workshop NetFP GA TCP/UDP /IP Coexisting VLANs with different technolog WiFi ies MPLS WiFi 9 © Fundació i2CAT 2013
- 9. Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations) RINA Research, Korea-EU Workshop 10 © Fundació i2CAT 2013
- 10. 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 RINA Research, Korea-EU Workshop 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 11 © Fundació i2CAT 2013
- 11. 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) RINA Research, Korea-EU Workshop 12 © Fundació i2CAT 2013
- 12. 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 different 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 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 RINA Research, Korea-EU Workshop © Fundació i2CAT 2013
- 13. 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, DC 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 RINA Research, Korea-EU Workshop 14 © Fundació i2CAT 2013
- 14. IRINA @ a glance (as a GN3+ project) • 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 RINA Research, Korea-EU Workshop Budget Total Cost 199.940 € EC Contribution 149.955 € Duration 18 months Start Date 1st November 2013 15 © Fundació i2CAT 2013
- 15. 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 RINA Research, Korea-EU Workshop 16 © Fundació i2CAT 2013
- 16. Agenda • What is RINA • Why researching RINA • Flow of research and development activities • EC-funded RINA research – IRATI – PRISTINE (in negotiations) – IRINA (in negotiations) RINA Research, Korea-EU Workshop 17 © Fundació i2CAT 2013
- 17. Thanks for your attention! Sergi Figuerola, Innovation and Technology Director ([email protected]) Eduard Grasa, RINA research line leader ([email protected]) Korea-EU Workshop, September 30th, 2013 RINA Research, Korea-EU Workshop http://www.i2cat.cat http://dana.i2cat.net http://irati.eu © Fundació i2CAT 2013
Editor's Notes
- #2: En general: * Recordar que el punt de RINA es que es proporciona un building block (el DIF) adaptable a diferents requeriments (a través de policies diferents). Aquesta és la eina fonamental que es pot utilitzar tants cops com sigui necessari, anant construint estructures de DIFs. El building block serveix per separar diferents scopes (per exemple, diferents xarxes de diferents proveïdors, diferents regions de la xarxa dins un proveidor (metro, regional, backbone), diverses VPNs d’usuari, etc.) * El DIF ha de proporcionar servei a les aplicacions que te a sobre, recolzant-se en les característiques dels DIFs que té a sota (rollo casteller )
- #4: One of the design goals of RINA is to provide the minimum number of elements that can enable the full range of Inter Process Communication services. RINA separates mechanism from policy, specifying a common template for all DIFs that can be customized through the insertion of policies (for data transfer, resource allocation, authentication, access control, routing, etc. A DIF is a Distributed IPC Facility, a distributed application that provides and manages IPC over a certain scope. It can be viewed as a layer. All DIFs do the same functions but can be customized. What defines the characteristics of a DIF is the join behaviour of all the DIF policies working in conjunction
- #5: * Els numeros son les adreces, A1, A2, B1, B2, etc son application names * PoAs -> Point of attachment (el punt en el qual un procés està conectat a la xarxa). Mirant el dibuix, el PoA de A1 és B1, els PoAs de A3 son C3 I D1, etc. Application name spaces are not tied to any layer or DIF. Recognizing that they may all be members of other DIFs.
- #7: Layer violations -> capes que miren informació d’altres capes per fer la seva feina (e.g. TCP pseudo-header) Overlays / “Virtual Networks” -> capes que estan per sobre de transport (TCP/UDP). Per exemple protocols de tuneling com VXLAN, STP, NVGRE, … Naming addressing and routing. -------------------------------------------- IP només assigna nom a les interfícies, no als nodes (de manera que un node amb 2 o més interfícies es lo mateix que 2 o + nodes per la xarxa) -> problemes de multi-homing I mobilitat Els noms d’aplicació avui en dia es mapegen a una adreça IP i un port TCP o UDP a través de DNS, que es un sistema extern a la xarxa (La xarxa només entén d’adreces IP) -> complica la mobilitat Congestion control ------------------------------ 2 problemes: * Detecció implicita (es creu que es detecta la congestó perquè es perden paquets, però no se’n pot estar segur que realment hi hagi congestio) * El control I la detecció es fa a TCP, que es on més lluny s’està del problema (enlloc de detectar-se I arreglar-se a la xarxa on hi hagi la congestió) RINA arregla els 2: * Detecció explicita (en cada DIF) * Cada DIF controla la congestió que hi ha en el seu DIF, no en la dels DIFs dels atlres
- #10: With feedback between all the different activities
- #13: Shim DIF is =
- #15: Taronja, espais més petits
- #19: Logo irati, Web irati, Blog DANA