D7.4 Final dissemination, standardisation and exploitation activities report

PRISTINE’s deliverable D7.4 Final dissemination, standardisation and exploitation activities report is newly available from the website’s deliverables section.

Executive summary

This deliverable describes the activities performed in Work Package WP7 during the final phase of the PRISTINE project. It contains detailed reports and updates on the activities related to dissemination (task T7.1), standardisation (task T7.2) and exploitation (task T7.3).... read more

Posted by Miguel Ponce de Leon 2017-01-03 Labels: D74

D6.3 Consolidated software for the use cases and final report on the use cases trials and business impact

PRISTINE’s deliverable D6.3 Consolidated software for the use cases and final report on the use cases trials and business impact is newly available from the website’s deliverables section.

Executive summary

The second and last round of experiments carried out as part of the validation work of the PRISTINE SDK has shown promising results. The activities performed during this phase followed two parallel axes. On one hand, we carried out experiments aimed at validating the usefulness of the PRISTINE SDK as far as RINA benefits are concerned. On the other hand, we combined several research directions, designing and executing more complex scenarios that help validate the SDK and RINA at a larger scale. In particular we defined several experiments converging the requirements of the three PRISTINE use cases, making sure that the simultaneous use of policies belonging to different research (such as routing, congestion control, security, scheduling, etc.) areas do not interfere with one another, but rather show at least the same level of performance they did when they were tested individually. These experiments helped in identifying development and integration issues that have been promptly corrected.... read more

Posted by Miguel Ponce de Leon 2017-01-03

D3.3 on congestion control, resource allocation, routing and forwarding available!

PRISTINE’s deliverable D3.3 is available from the website’s deliverables section.

Executive summary

In this document, the “final specification and consolidated implementation” of the techniques proposed in the previous document (D3.2), “initial specification”, are presented. The goal is to show how the proposed techniques in the previous document have been implemented in RINA, what their performance improvement is over other similar methods (if applicable), and what future directions are. The activities performed in D3.3 are centered around three main areas: i) programmable congestion control; ii) resource allocation and iii) topological addressing to bound routing table sizes. This document also specifies the investigation results of these techniques as policies in RINA.... read more

Posted by Miguel Ponce de Leon 2017-01-03 Labels: d33

D5.4 Consolidated Management System ready!

This document describes the results and major contributions to the Network Management System for RINA networks that the PRISTINE project has been researching and developing. RIB design, NMS System Proof of Concept implementation and validation, configuration management, performance management and security management have been the major areas of work.

RIB design :The work performed in D5.4 enables the specification and validation of RIB objects using a formal language. RIB object model compilers and code generation tools enable developers to seamlessly incorporate the RIB model into their RINA management applications.... read more

Posted by Miguel Ponce de Leon 2016-09-06 Labels: RINA DMS Management

D2.6 Advanced RINA Simulator ready!

Simulation is widely accepted validation and verification tool to test and prove new technologies. Simulation runs can reveal design flaws, performance drawbacks and other weak points. Simulation results are able to enhance development process of researchers and programmers. Hence, the implementation of the Recursive Internet Architecture Simulator (RINASim) is a natural step to support the design and development of the RINA SDK.... read more

Posted by Miguel Ponce de Leon 2016-09-06 Labels: RINASim

D2.5 Consolidated SDK

This deliverable describes the consolidated version of the PRISTINE Software Development Kit (SDK). Task T2.3 has collected the feedbacks received from WP3, WP4, WP5 and WP6 during the PRISTINE first iteration, and has designed and implemented the SDK features required for the second iteration.

The RINA Plugin Interface (RPI) provides a set ot Application Programming Interfaces (APIs) that allow the SDK user to plug an unplug custom policies, and deploy them at run time. The RPI model defined during the first SDK release has proven to be effective in supporting the programmability needs of the technical work packages: a number of policies have been successfully integrated and deployed in the WP6 testbeds. As a consequence, no major model changes were required for the second iteration SDK.... read more

Posted by Miguel Ponce de Leon 2016-09-06 Labels: SDK RINA

D6.2 Proof of concept software for the use cases and draft report on the use cases trials and business impact

The first round of experiments carried out as part of the validation work of the PRISTINE SDK has shown promising results. Moreover, it also helped in identifying development issues that have been either corrected during this first development phase or that have been included in the development roadmap of RINA and the PRISTINE SDK for the second phase. Each experiment has covered different research areas (from resilient routing or aggregate congestion control to management aspects) and several RINA policies within each area.... read more

Posted by Miguel Ponce de Leon 2016-09-06 Labels: Trials RINA

D7.3 Second stage dissemination standardisation and exploitation activities report and updated plans

This deliverable describes the project' second-stage activities performed by Work Package WP7. It provides detailed reports and updates on the dissemination (task T7.1), standardisation (task T7.2) and exploitation (task T7.3) activities. The document is structured into three main sections: section 1 contains the dissemination plans and reports, section 2 presents the standardisation plans, while section 3 illustrates the exploitation plans.... read more

Posted by Miguel Ponce de Leon 2016-09-06 Labels: Dissemination PRISTINE

D4.2 Innovative security and reliability enablers

The security objective is set to reduce the security risks as much as possible by defining security functions and enablers. This document, D4.2, builds upon the security functions, mechanisms, and techniques that are described in D4.1 [D4.1] and provides their further developments within WP4 to meet the requirements enabling more secure and reliable networks than those that we have today. These functions, mechanisms and techniques include the Authentication, Access Controls (Capability-Based Access Control and Multi-Level Security) Cryptographic function, Key Management and Resiliency aspects of security. The deliverable overall provides the relevant specifications and analysis, the design aspects, Proof of Concept implementations (PoC), and related PoC tests.... read more

Posted by Miguel Ponce de Leon 2016-09-06 Labels: Security RINA

D5.3 Proof of concept DIF Management System

This deliverable describes the proof of concept of DIF Management System for the first iteration of PRISTINE DIF Management System (DMS). Specifically, it contains the design of the DMS manager and documents its current implementation. It begins with a general introduction to OSI management, the DMS and some realistic deployment options and migration strategies.

The next section describes the DMS Manager in greater detail. It outlines best practices for modular software design and presents a layered design that allows deployment (and technology) flexibility. This is followed by a detailed description of the components that form each layer in the DMS. This is followed by a worked example of writing a “management strategy”. This details the java interfaces to use, and how implementations of these interfaces may be combined to provide desired results.... read more

Posted by Miguel Ponce de Leon 2016-09-06 Labels: DIF Management System RINA