The following paragraphs provide a summary of the work that will be carried out in each of the five work packages of the IRATI project:
WP1 – Project Management
The aim of WP1 is to provide the internal project management and the overall co-ordination of activities, financial- and technical- planning and control. It ensures that the project objectives are met and represents the contact point of the project to the Commission, the FP7 community and the external world. It provides guidance for the process of registering IPR, especially in cases where joint ownership is involved. It also addresses any issues concerning access rights, including cases where partners join or leave the project during its duration. It is assisted in its tasks by other bodies established as part of the management structure.
WP2 – Architecture, Use Cases and Requirements
WP2 is the overarching work package that will define the scope of the use cases to be validated, propose a set of refinements and enhancements to the RINA architecture reference model and specifications, and elaborate a high level software architecture for the implementation. For each phase of the project, WP2 will:
- Elaborate the use cases to be showcased during the experimentation phases, analyze them and extract requirements. Use cases will try to focus at first on the availability/integration of core RINA functionalities in basic experimental setups; then, more complex scenarios that are challenging with the current Internet will be targeted to explore the full RINA functionalities and thus meet the expectations/take-up strategies of network operators and cloud service providers (like Interoute). The use cases will drive the experiment design and provide requirements for the completion/validation of the RINA architecture reference model and specifications.
- Analyse the RINA architecture reference model and specifications, identify holes in the mechanisms or missing policies, and propose enhancements/refinements.
- Based on the RINA architecture reference model and specifications on one side and the phase scenario and targeted platform on the other side, provide a high-level software architecture for the design and implementation of the prototype. This high-level software architecture will be the unifying document for the WP3 implementation tasks.
Last but not least, this WP will provide technical supervision of the work in the other technical work packages by hosting the technical board and performing audits of the project technical progress.
WP3 – Software Design and Implementation
WP3 is the development workpackage of the project. Its overall objective is to translate the WP2 specifications and high-level software design into a set of prototypes that will be used by WP4 for its test-bed activities and experimentation. The main objectives of this WP are:
- to provide a common development environment
- to implement a RINA prototype over Ethernet for two platforms: a UNIX-like OS and JunOS
- to integrate the various functionalities and components into a demonstrable system (at node -level)
The architecture releases at the various project phases and the related functional decompositions delivered by WP2 are the starting point of work for WP3. Software prototypes are the major WP3 outcomes to be delivered to WP4. Moreover, it is expected that WP3 will produce a number of feedbacks on previous or concurrent activities, both internally (i.e. among tasks) and externally (i.e. towards other WPs). The feedbacks produced by WP3 to either internal or external tasks will have eventually an impact on the work produced by the target task, i.e. its deliverable. As a general rule, it is expected that major feedbacks on a task could lead to fix and reissue the deliverable(s) produced by that task previously.
WP4 – Deployment into OFELIA testbed, Experimentation and Validation
WP4 is the experimentation and validation work package, responsible of the following goals:
- Design the experiments required to validate the use cases and deploy WP3 prototypes into the OFELIA facility for experimentation.
- Validate the correctness of the prototype with respect to its compliance with the use cases through experimentation.
- Compare and document RINA benefits against TCP/IP in different areas: application interface, multi-homing, use of CPU resources and memory (directly related to energy efficiency), support of heterogeneous applications, security and others identified by WP2.
- Based on the experiments result analysis, provide feedback to the RINA specifications enhancement and high-level software architecture design activities in WP2.
WP5 – Dissemination, Standardization and Exploitation
The goals of WP5 are:
- Dissemination of project results, already starting in the early stages of the project, culminating in the organisation of a final workshop, in which project results, prototypes and discussions around further RINA directions will take place.
- Preparation of publications, brochures, press handouts, project posters and other material.
- Presentation of IRATI at several types of events, including conferences, seminars and user group meetings.
- Collaboration with ICT projects.
- Launch of an open-source community around the RINA prototype for the UNIX-like OS and the IP-RINA gateway.
- Participate at the RINA standardization efforts carried out within the Pouzin Society and make established standard bodies more aware about RINA.
- Produce an exploitation plan comprising the exploitation plans of each partner and the joint marketing plans, which will mainly target the project’s key industrial partners. Wherever possible, potential users of the project results will be contacted and exploitation activities will be initiated early in the project.