[P2P-F] relation between patterns in different fields?

Tue May 10 17:41:54 CEST 2011

not sure about Alexander but this is a very important book.... however it is also one that i will not....now at least read.  From what i know of it it is i think rather technical.  days premise is that his architecture should replace or at least ride on top of tcp/ip.

if it could somehow get deployed it would be better than tcp/ip[

These entries from google are will tell you what you need to know my search was

 john day rina

Papers & Reports | RINA

The papers below were co-authored by members of the RINA team. John Day, Ibrahim Matta, and Karim Mattar. "Networking is IPC": A Guiding Principle to a ...
csr.bu.edu/rina/documents2.html - Cached - Similar
►
[DOC]
OOI Recursive Inter-Network Architecture (RINA)

File Format: Microsoft Word - Quick View
Dec 15, 2009 ... OOI Recursive Inter-Network Architecture (RINA). Final Report. Steve Bunch, John Day, Peter DeWolf, Mark Levine, Gilbert Glick ...
https://confluence.oceanobservatories.org/.../OOI+RINA+Final+Status+Report+20091216.doc?...
The Pouzin Society

Slides for the RINA Tutorial by John at FutureNet 2010 in Boston. Author: John Day. 2010 Pouzin Society Draft Meeting Agenda, PDF format ...
pouzin.pnanetworks.com/documentspublications.html - Cached
An Introduction to RINA

May 10, 2010 ... An Introduction to RINA Or How I Learned to Stop Worrying and Love the Internet FutureNet Tutorial Part I John Day May 2010 Good ...
www.slideshare.net/an3tnet/an-introduction-to-rina - Cached - Similar
[PDF]
(FIND)

File Format: PDF/Adobe Acrobat - Quick View
Jun 24, 2010 ... John Day 2010. 2. The Seven Unanswered Questions ..... Operate RINA over, under, around and through the Internet. ...
www.forumatena.org/Photos/futurinternet/John-Day.pdf

=============================================================
The COOK Report on Internet Protocol, (PSTN) 609 882-2572 (Skype-in) 609 643-4067
Back Issues: http://www.cookreport.com/index.php?option=com_docman&task=cat_view&gid=37&Itemid=61  
 Cook's Collaborative Edge Blog http://gordoncook.net/wp/   Subscription info: http://www.cookreport.com/index.php?option=com_content&view=article&id=54&Itemid=65
=============================================================

On May 10, 2011, at 3:23 AM, Michel Bauwens wrote:

> any relation with Alexander's work?
> 
> see:
> 
> Patterns in Network Architecture
> 
> From P2P Foundation
> 
> Jump to: navigation, search
> * Book: Patterns in Network Architecture: A Return to Fundamentals, by John Day, ISBN-10: 0132252422, ISBN-13: 9780132252423, Prentice Hall, 2007.
> 
> URL = http://www.informit.com/store/product.aspx?isbn=0132252422
> 
> 
> [edit] Review
> 
> Jon Crowcroft:
> 
> "It isn't every day (pun intended) that one of the true Old Guard writes and publishes a book, and it behooves us to take notice. In this case, the author's expertise and his subject matter are of particular timeliness, because of the worldwide resurgence of activities with regard to next-generation network architectures, that is, a replacement, or upgrade to the Internet (dare one say "Internet 2.0"?).
> 
> John Day is a well-known scholar of historical cartography, and this book, in a way, is a roadmap of network architecture. The roadmap starts back in 1970, tracing from the roots of connectionless packet-switched dynamically routed systems such as Cyclades, and the ARPANET, through to recent discussions on multihoming, multicast, and mobility, with a view along the way of naming, addressing, protocol stack design, protocol design, and concepts of layering.
> 
> That description makes the book sound fairly standard in terms of structure and content, but it isn't. The book includes many discursive elements whose intent is to provide a collection of patterns. Design patterns originated in the building trade as a way for crafts people to pass on successful methods of construction (in the sense of affordable and noncollapsing) to less-inventive people (or people who want to spend their inventive efforts in different areas). Software engineers picked up on this idea, applying the techniques in both the microscopic world: patterns allow you to decide what algorithm is applicable in solving a problem in the small; and the macroscopic world: architectural patterns allow you to decide on an approach to breaking down a large system into the right kind of components.
> 
> Essentially, this book does the same thing, at the protocol stack level, and at the system level, with a collection of historical and contemporary examples to support the arguments.
> 
> The book makes interesting reading, especially as it represents a fair balance in reporting the early ideas that came not just from the United States, and restates the importance of the Opens Systems Interconnection (OSI) model (not the ISO protocols) in understanding layering and beads-on-a-string, as well as reasserting the use of the model in clarifying the perennially confusing concepts of names, addresses, and routes.
> 
> The book begins with a discussion of seven principles that emerged through the early history of networking (I won't spoil the book for readers by listing them here), and ends in the tenth and final chapter, entitled "Backing Out of a Blind Alley," with an appeal to fundamentals. Essentially, the author points out that researchers (especially academics) are strongly motivated to keep moving on with claims of ever-newer tricks, but rarely to consolidate these tricks into a set of principles that stand for a long time (because then they would  have to completely change the topic of their research). Thus uncovering a foundational theory of networking would put a whole generation of networkers out of work (or funding at least).
> 
> The book is peppered (saltily) with fine quotes and fascinating asides from philosophy (for this reader, especially, the Chinese diversions were most novel and illuminating). Illustrative of the range is that one finds Wittgenstein and Dave Clark, Confucius, and Dr. Seuss—Frege's useful reminder that "The sign '=' should be read as 'is easily confused with'" would make an excellent IETF T-shirt.
> 
> I found the book extremely readable and enjoyable, and although I might argue with some of the opinions in the book, I think that this is just more evidence that I should recommend the book to anyone interested in knowing why we are where we are in networking, and being  better informed about where we should go next."
> 
> -- 
> P2P Foundation: http://p2pfoundation.net  - http://blog.p2pfoundation.net 
> 
> Connect: http://p2pfoundation.ning.com; Discuss: http://lists.ourproject.org/cgi-bin/mailman/listinfo/p2p-foundation
> 
> Updates: http://del.icio.us/mbauwens; http://friendfeed.com/mbauwens; http://twitter.com/mbauwens; http://www.facebook.com/mbauwens
> 
> 
> 
> 
> 
> _______________________________________________
> P2P Foundation - Mailing list
> http://www.p2pfoundation.net
> https://lists.ourproject.org/cgi-bin/mailman/listinfo/p2p-foundation

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ourproject.org/pipermail/p2p-foundation/attachments/20110510/8395d077/attachment.htm 