IRATI First phase report on use cases, requirements analysis, updated RINA specifications and high-level software architecture available

IRATI’s deliverable D2.1, informing about the first phase use cases, requirements analysis, updated RINA specifications and high-level software architecture, is now available in the Deliverables area.

The components of the high-level software architecture for the IRATI implementation of RINA

Executive summary.

This report explains the project environment for phase 1, including the use cases, the updated RINA specifications and the high-level software architecture for the first project prototype. The document is structured into four differentiated parts: i) Overview of the RINA architectural model; ii) Use cases and requirements analysis; iii) Updated RINA specifications and iv) High-level software architecture of the prototype implementation.

Section 4 provides a brief introduction to the RINA architecture model and its components, intended to provide the minimum background required to the reader in order to be able to understand the document. For a more complete description the reader should refer to the “RINA specification handbook” booklet, which contains the draft RINA reference model and specifications as of January 2013. This booklet will be delivered as a companion document of D2.1.

Section 5 describes the use cases that will shape the research, development and experimentation activities that will be carried out by IRATI partners during the first phase of the project. High-level requirements are extracted from the use cases analysis, defining the overall service characteristics that the DIFs developed by the project should have. The uses cases have been divided into three categories:

  • Integration-test use cases. Specify the basic scenarios that the prototype has to fulfil before being able to be deployed in the experimentation environment.
  • Interoute scenario use cases. The project focuses on the operation of the “Unified Connectivity” and “Virtual Data Center” services offered by Interoute; describing how these services are provided today and what advantages would RINA bring into the table.
  • Cloud bursting use case. An advanced scenario that showcases the dynamicity provided by the Inter DIF Directory, enabling the creation of DIFs that support a particular set of applications on the fly.

Based on the use cases report and the current draft RINA specifications available to the IRATI consortium, T2.2 has identified the more interesting specifications to be updated and/or added to the RINA specification set during the first phase of the project. These specifications are provided in Section 6 and briefly introduced in the following paragraphs.

  • Shim IPC Process over 802.1q layer (new specification). This specification wraps a 802.1q layer (a VLAN) with the DIF interface, enabling RINA to be overlaid on top of 802.1q layers. The goal is not to enhance 802.1q layers with enough functionality to make them a DIF, but to add the minimal functionality that enables an IPC Process to use a 802.1q layer as an underlying transport.
  • PDU Forwarding table generator (routing, new specification). This specification will define a strategy to compute the PDU forwarding tables of IPC Processes in a DIF, based on link-state routing. The developed routing scheme is targeted to small and medium-sized DIFs (first phase scenario).
  • Inter DIF Directory (update to current specification). An updated version of the IDD specification, identifying further commonality with the Flow Allocator application discovery mechanisms, as well as with the PDU Forwarding Table generator component.
  • Policies for the search phase of the Inter-DIF Directory (New policies for an existing specification). This specification will provide policies to implement a strategy for the application-search phase of the IDD. This strategy is based on exhaustive search, targeted to a simple scenario with a reduced number of DIFs and applications (first phase scenario).

Finally section 7 describes the high-level software architecture guidelines that will be used for the implementation of the RINA model in the IRATI project. The architecture described spans the Operating System as a whole, from the user space to the kernel space, and identifies software components, their interactions and delineates their interfaces. The IRATI project targets both Linux/OS and FreeBSD systems for the prototypes implementation and the approach described in this document provides generic concepts that allow implementing the model in both targets.

Section 7 refers to RINA architectural and functional concepts without explaining them in depth. While the specification of the RINA model is not the core focus of section 7, key concepts are presented to better frame the components communications. The focus of this section is on optimally partitioning the components residing in both the user and kernel spaces, defining their interfaces as well.

The description presented introduces modular additions that allows flexible integration and incremental development. All the functional modules and components will converge into a set of software packages, which will implement a complete RINA model in the final architecture.

Details that go beyond the provided specifications will derive from the completion of the development activities and the release of the implementation prototypes. Section 7 is intended as a basic general reference for the prototypes implementation that will be delivered by WP3, further details will be provided by the planned deliverables that will be released by WP2 (D2.3 and D2.4) and WP3 (D3.1, D3.2, D3.3 and D3.4). The RINA software architecture will be developed in the next months and integration or testing activities might introduce upgrades. In that case a new version of this document might be produced, in case significant evolutions of the specification would need to be incorporated.

Post Tagged with

Comments are closed.