<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">stef</b> <span dir="ltr"><<a href="mailto:stefan.marsiske@gmail.com">stefan.marsiske@gmail.com</a>></span><br>
Date: Thu, Apr 28, 2011 at 5:29 AM<br>Subject: [fcf_discussion] FWD: Call for Position Papers on Internet Design Principles<br>To: fcforum_discussion <<a href="mailto:fcforum_discussion@list.fcforum.net">fcforum_discussion@list.fcforum.net</a>><br>
<br><br>anyone has any idea what's this about?<br>
<br>
> EUROPEAN COMMISSION<br>
><br>
> Information Society and Media Directorate-General<br>
><br>
><br>
><br>
> Converged Networks and Services<br>
><br>
> *Networked Media Systems*<br>
><br>
><br>
><br>
> Brussels, 27 April 2011<br>
><br>
> INFSO/D2 ILB/vdp D(2011)<br>
><br>
> This is a reminder for the Internet Design Principles Call for contributions<br>
> with deadline 10 May 2011.<br>
><br>
> The Call for position papers is also published at the following link:<br>
> <a href="http://ec.europa.eu/information_society/activities/foi/research/fiarch/index_en.htm" target="_blank">http://ec.europa.eu/information_society/activities/foi/research/fiarch/index_en.htm</a><br>
><br>
> Encl: call for position papers.<br>
><br>
> *Call for Position Papers on Internet Design Principles*<br>
><br>
> Design principles play a central role in the architecture of the Internet as<br>
> driving most engineering decisions at conception level but also operational<br>
> level. Often cited as the corner stone of the Internet design compared to<br>
> architectures that rely exclusively on design model (derived directly from<br>
> requirements), they are for most of them not formally defined by means of a<br>
> closed mathematical formulation.<br>
><br>
><br>
><br>
> Design principles suggest normative rules on how a designer/an architect can<br>
> best structure the various architectural components and describe the<br>
> fundamental and time invariant laws underlying the working of an engineered<br>
> artifact. Note that the canonical definition of architecture (as specified<br>
> in<br>
> <a href="http://ec.europa.eu/information_society/activities/foi/docs/current_internet_limitations_v9.pdf" target="_blank">http://ec.europa.eu/information_society/activities/foi/docs/current_internet_limitations_v9.pdf</a>)<br>
> includes the principles and guidelines governing their design and evolution<br>
> over time.<br>
><br>
><br>
><br>
> For what concerns the Internet (as engineered artifact), its architecture is<br>
> governed by the following design principles (this list is not exhaustive and<br>
> represents the common baseline in terms of principles currently applied to<br>
> the Internet architecture and its operation):<br>
><br>
> · Modularization by relaxed layering<br>
><br>
> · Connectionless datagram forwarding<br>
><br>
> · Network of collaborating networks (Interconnection via gateways)<br>
><br>
> · End‐to‐end principle/fate sharing principle combined with<br>
><br>
> · intelligent end systems (user stateless network)<br>
><br>
> · Simplicity principle<br>
><br>
> · Loose coupling principle<br>
><br>
> · Locality principle (local cause(s) shall result in local effects)<br>
><br>
> The present call for contributions aims to address the issue of design<br>
> principle applicability by identifying the necessary addition/possible<br>
> improvement to the current principles. It is to be emphasized that a large<br>
> part of the underlying research activity consists of identifying hidden<br>
> relationships and effects between them.<br>
><br>
><br>
><br>
> For this purpose, clear understanding about what individual projects<br>
> actually do and how they position against these design principles is to be<br>
> better identified. Position statements from various projects and research<br>
> activities are expected to provide better insight on associated<br>
> architectural challenges. For this purpose contributions shall be centered<br>
><br>
> on the following questions:<br>
><br>
> *Which design principles your project is currently addressing /*<br>
><br>
> *relying on?*<br>
><br>
> *Which design principles does your project challenge and for which*<br>
><br>
> *reasons?*<br>
><br>
> *Which design objectives can't be achieved by application of current*<br>
><br>
> *design principles?*<br>
><br>
> *Do you plan investigation on new principles or modification of*<br>
><br>
> *existing principles ?*<br>
><br>
> *Which design principles (or adaptation of existing principles) would*<br>
><br>
> *be required to address your design objectives ?*<br>
><br>
> * *<br>
><br>
> * *<br>
><br>
> *Please provide your input to the **fiarch@future**‐**<a href="http://internet.eu" target="_blank">internet.eu</a> **by **10<br>
> May** 2011.*<br>
><br>
> * *<br>
><br>
> * *<br>
><br>
> *References and Reading Material:*<br>
><br>
> ‐ R.Bush and D. Meyer, Some Internet Architectural Guidelines and<br>
><br>
> Philosophy, IETF, RFC 3439 (updates RFC 1958), December 2002.<br>
><br>
> ‐ R.Callon, The Twelve Networking Truths, IETF, RFC 1925, April 1996.<br>
><br>
> ‐ B.Carpenter, Ed., Architectural Principles of the Internet, IETF, RFC<br>
><br>
> 1958, June 1996.<br>
><br>
> ‐ B.Carpenter, Internet Transparency, IETF, RFC 2775, February 2000.<br>
><br>
> ‐ B.Carpenter and S.Brim, Middleboxes: Taxonomy and Issues, IETF, RFC 3234,<br>
><br>
> February 2002.<br>
><br>
> ‐ D.Clark, The design philosophy of the DARPA internet protocols, ACM<br>
><br>
> SIGCOMM Computer Communication Review, Vol.18, No.4, pp.106‐114, August<br>
><br>
> 1988.<br>
><br>
> ‐ J.Kempf, Ed., R.Austein, Ed., The Rise of the Middle and the Future of<br>
><br>
> End‐to‐End: Reflections on the Evolution of the Internet Architecture,<br>
><br>
> IETF, RFC 3724, March 2004.<br>
><br>
> ‐ T.Moors, A critical review of "End‐to‐end arguments in system design,<br>
><br>
> Proceedings of IEEE International Conference on Communications (ICC)<br>
><br>
> 2002, New York City (New Jersey), USA, April/May 2002.<br>
><br>
> ‐ J.Saltzer, D.Reed, and D.Clark, End‐to‐end arguments in system design,<br>
><br>
> ACM Transactions on Computer Systems, November 1984.<br>
><br>
> ‐ FIArch document: FIArch Group, “Fundamental Limitations of Current<br>
> Internet and the path to Future Internet,” December 2010 URL:<br>
> <a href="http://ec.europa.eu/information_society/activities/foi/docs/current_internet_limitations_v9.pdf" target="_blank">http://ec.europa.eu/information_society/activities/foi/docs/current_internet_limitations_v9.pdf</a><br>
<font color="#888888"><br>
--<br>
gpg: <a href="https://www.ctrlc.hu/%7Estef/stef.gpg" target="_blank">https://www.ctrlc.hu/~stef/stef.gpg</a><br>
gpg fp: F617 AC77 6E86 5830 08B8 BB96 E7A4 C6CF A84A 7140<br>
</font><br>-----<br>
+info <a href="http://list.fcforum.net/wws/info/fcforum_discussion" target="_blank">http://list.fcforum.net/wws/info/fcforum_discussion</a><br>
----<br>
<br></div><br><br clear="all"><br>-- <br>P2P Foundation: <a href="http://p2pfoundation.net" target="_blank">http://p2pfoundation.net</a> - <a href="http://blog.p2pfoundation.net" target="_blank">http://blog.p2pfoundation.net</a> <br>
<br>Connect: <a href="http://p2pfoundation.ning.com" target="_blank">http://p2pfoundation.ning.com</a>; Discuss: <a href="http://lists.ourproject.org/cgi-bin/mailman/listinfo/p2p-foundation" target="_blank">http://lists.ourproject.org/cgi-bin/mailman/listinfo/p2p-foundation</a><br>
<br>Updates: <a href="http://del.icio.us/mbauwens" target="_blank">http://del.icio.us/mbauwens</a>; <a href="http://friendfeed.com/mbauwens" target="_blank">http://friendfeed.com/mbauwens</a>; <a href="http://twitter.com/mbauwens" target="_blank">http://twitter.com/mbauwens</a>; <a href="http://www.facebook.com/mbauwens" target="_blank">http://www.facebook.com/mbauwens</a><br>
<br><br><br><br><br>