Future Internet Design Principles
From FutureInternetWiki
This is the current Design Principles document.
There is an open workshop on 23 September 2011 in Brussels and it is expected to present a pre-final version of the Design Principles during the Future Internet Assembly in Poznan , while the final version is scheduled for end of November 2011.
See the SOFI design principles input below. Are the descriptions incomplete, or what can be argued further in favour of this being considered a design principle? Are there missing design principles from this list?
Contents |
[edit] What is a Design Principle (according to the FI Arch working group)?
"Design principles suggest normative rules on how a designer/an architect can best structure the various architectural components and describe the fundamental and time invariant laws underlying the working of an engineered artifact.
- Normative rules: refer to the set of rules serving to guide, control, or regulate a proper and acceptable structure of a system at design time and a proper and acceptable behaviour of a system at running time;
- Time invariance: refers to a system whose output does not depend explicitly on time (this time invariance is to be seen as within a given set of initial conditions due to the technological change and paradigms shifts, the economical constraints, etc.). Robustness and longevity over time is a consequence of this time invariance.
- Engineered artifact: object formed/produced by engineering.
Note that the canonical definition of architecture includes the principles and guidelines governing their design and evolution over time.
Design principles play a central role in the architecture of the Internet as driving most engineering decisions at communication system conception level but also operational level. Often cited as the corner stone of the Internet design compared to architectures that rely exclusively on modelling, they are not formally defined (using a closed mathematical formulation). Indeed, when it comes to the design of the Internet, the formulation of design principles is a fundamental characteristic of the Internet design process that guides the specification of the design model."
(These definitions have been discussed and shared in the FIAarch WG and reported in the FIArch Design Principles (DRAFT) document
(Contribution from Matteo Melideo - SOFI)
[edit] How services & virtualisation are reflected in the current document
The document is focused mainly on the network level and only considers services as one of many types of resource which exist in the network.
[edit] Foreseen Design Principles for the Internet of Services and Cloud
(This part has been re-edited completely by Matteo Melideo - SOFI)
SOFI delivered a first document to the WG and the contents of this document were presented at the workshop on the 23rd of May 2011 ( SOFI Design Principles - 23rd May 2011.ppt). As a follow up of the comments received, a couple of new documents on two design principles for the Future Internet have been provided by our invited experts.
The initial experts that took part to the editing were\are:
- Luciano Baresi (Politecnico di Milano, Italy)
- Reto Krummenacher (STI International, Austria)
- Marco Pistore (CEO of the SAYSERVICE -SME, Italy)
- Andrew Edmonds (Intel ltd)
- From SOFI:
- Vito Morreale (ENGINEERING Ingegneria Informatica S.p.A.)
- Matteo Melideo (ENGINEERING Ingegneria Informatica S.p.A.)
On 2nd October 2011 several experts left the group. The current composition is the following:
- Coordinator:
- Francesco Torelli (ENGINEERING Ingegneria Informatica S.p.A., Italy)
- Experts:
- Andrew Edmonds (Intel, Ireland)
- Massimo Villari (University of Messina, Italy)
- Dimosthenis Kyriazis (National Technical University of Athens, Greece)
[edit] The new proposed Design Principles
See Internet Design Principles contribution by SOFI (current draft)
[edit] Comments
Any additional comment from your side on this Design Principle will be extremely valuable and will be recognised when the document will be finalized.
[edit] Contribution provided to the existing Design Principles
[edit] Naming of services
To manage identities and names for all these entities at a global level
- assignment of unique identities for these entities at the different levels of abstraction (e.g., service, service machine, service instance);
- identification of different names corresponding to the same entity;
- possibility to define virtual names and hide the real identity;
- manage changes in names and identities.
[edit] Comments
Any additional comment from your side on this Design Principle will be extremely valuable and will be recognised when the document will be finalized.
[edit] Addressing services
- Future Internet needs service addressing mechanisms that are independent of the physical location (and if possible, technology) of the services and things
- Detachment of service addressing from the URIs is especially important if the other computational entities in the FI (things, objects, sensors, resources) are going to be described as services
- It also requires a proper layer that is able to mask locations and technologies and provide the right abstraction level
[edit] Comments
Any additional comment from your side on this Design Principle will be extremely valuable and will be recognised when the document will be finalized.
[edit] Shared access to distributed resources and services
- IoS and IoT requires to incorporate sophisticated notions of content delivery networks, which optimize the access to resources, both static and dynamic – such as services or sensor data aggregators
- The Future Internet architecture must be designed on the basis of a convergent data routing, data delivery and data management infrastructure
[edit] Comments
[edit] Space for new suggestions
- Name of the principle:
- Justification:
- Contributor:
- on behalf of Project:
