Miguel PdL

This D2.1 is one of the 1st public deliverables of 4WARD [pdf] and it describes the technical requirements for a family of future global communication networks, with the potential to supersede current telecommunication networks as well as the current “internet” in the long run, as identified in the first phase of the FP7 project “4WARD”.
I’ve given a more general overview of the document on on the main TSSG 4WARD page. Just to say most of my contribution in this document was towards the consolidation of the WP2 new architecture requirements and the WP4 in-netwrk management requirements.
In WP2 we are developing an architecture framework that is flexible enough for specifying and realising a new family of interoperable network architectures with varying degrees of desired properties according to the needs of the targeted networking scenario (e.g., in a backbone network, a sensor network, or a mobile ad hoc network) while ensuring certain common principles and properties (e.g. interoperability, security, mobility, quality of service). Hence this framework has to take into account a multitude of network variants in order to facilitate the design of the “best” network for each task, each device, each customer, and each technology.
I also had a part to play in pulling together the requirements for WP4 for In-Network Management in which we are devising an embedded “default-on” management capability which is an inseparable part of the network itself. This capability will generate extra value in terms of guaranteed performance in a cost effective way, and will enable the networks to adjust themselves to different sizes, configurations and external conditions”. The guiding principles to achieve this goal are decentralisation and self-organisation.
The realisation of the In-Network Management paradigm includes developing a network management plane that self-configures and dynamically adapts to changes in networking conditions. The plane provides communication and coordination primitives for a range of distributed management functions.
4WARD In-Network Management addresses these challenges by introducing a thin, pervasive layer which performs core management functionalities already inside the network, but which can be complemented by additional management functionality outside the network where necessary.
For more information in relation to this 4WARD In-Network Management there is an public deliverable available D4.1 Definition of scenarios and use cases [pdf]
I must admit it is still early in the project and there are a number of significant advances being made, however at times it feels as though there are some many things happening in parallel its hard to keep up with everthing going on.