[e2e] a means to an end

Tue Dec 2 00:24:03 PST 2008

as well as DTN folks combatting layering and assumptions
(which we took on board in haggle, for example, and adopted - viz
www.cl.cam.ac.uk/~ph315/publications/haggle-ubicomp2007.pdf
(as have others)
and 
van et al combatting point-to-pointless networking, there are quite a
few other people reaching out along these directions - i blogged some
of the pieces as part of a course in comms i teach to undergrads in
cambridge 

notably psirp...

http://clogspotclog.blogspot.com/2008/12/dcii-11208.html

i think the conversation recently has confused (or conflated) several
different pieces of architecture
1. protocol system composition
2. data driven networking paradigms
3. information coding and representation

I certainly would be kean in the very long term to conflate these,
especially in multi"hop" wireless nets where the efficiency gains are
big, but I am not so sure about mixing them up on the next stage of
the internet, principally because of ownership and privacy.
(yes, i realize that there are extreme ways one can provie even more
privacy as well as censorship proof networking by doing clever 
co-coding of oobjects during transmission and caching (or however you
want to view it in a DONA world...) - i just dont think certain
agencies will let us build the whole net that way

btw, there's a cool description of such a net in Neal Stepheson's
Diamond Age
(as well as an aweseome envisaging of Kay's
"A personal computer for children of all ages" 
http://www.mprove.de/diplom/gui/Kay72a.pdf
which we could well read - it probably invalidates most of the mobile 
handset industry's patents:)

In missive <4835AFD53A246A40A3B8DA85D658C4BE7B0D7D at EVS-EC1-NODE4.surrey.ac.uk>,
 L.Wood at surrey.ac.uk typed:

 >>This is a multi-part message in MIME format.
 >>
 >>------_=_NextPart_001_01C9540E.AB036396
 >>Content-Type: text/plain;
 >>	charset="iso-8859-1"
 >>Content-Transfer-Encoding: quoted-printable
 >>
 >>David,
 >>
 >>Interesting that he thrust of current IRTF delay-tolerant
 >>networking work has effectively turned your statement below
 >>on its head, in believing that there is no need for reliability
 >>at the top of the network, and no need for location at the top
 >>of the network, either.
 >>
 >>How the network base assures sufficient reliability and assures
 >>that endpoint identifiers map to something meaningful would seem
 >>to be open problems...=20
 >>
 >>L.
 >>
 >><http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood at surrey.ac.uk>
 >>
 >>> Just as there is no need for "reliability" at the base of the network, =
 >>
 >>> there is no need for "location" at the base.
 >>
 >>------_=_NextPart_001_01C9540E.AB036396
 >>Content-Type: text/html;
 >>	charset="iso-8859-1"
 >>Content-Transfer-Encoding: quoted-printable
 >>
 >><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
 >><HTML>
 >><HEAD>
 >><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
 >>charset=3Diso-8859-1">
 >><META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
 >>6.5.7653.38">
 >><TITLE>RE: [e2e] a means to an end</TITLE>
 >></HEAD>
 >><BODY>
 >><!-- Converted from text/plain format -->
 >>
 >><P><FONT SIZE=3D2>David,<BR>
 >><BR>
 >>Interesting that he thrust of current IRTF delay-tolerant<BR>
 >>networking work has effectively turned your statement below<BR>
 >>on its head, in believing that there is no need for reliability<BR>
 >>at the top of the network, and no need for location at the top<BR>
 >>of the network, either.<BR>
 >><BR>
 >>How the network base assures sufficient reliability and assures<BR>
 >>that endpoint identifiers map to something meaningful would seem<BR>
 >>to be open problems...<BR>
 >><BR>
 >>L.<BR>
 >><BR>
 >>&lt;<A =
 >>HREF=3D"http://www.ee.surrey.ac.uk/Personal/L.Wood/">http://www.ee.surrey=
 >>.ac.uk/Personal/L.Wood/</A>&gt;&lt;L.Wood at surrey.ac.uk&gt;<BR>
 >><BR>
 >>&gt; Just as there is no need for &quot;reliability&quot; at the base of =
 >>the network,<BR>
 >>&gt; there is no need for &quot;location&quot; at the base.<BR>
 >></FONT>
 >></P>
 >>
 >></BODY>
 >></HTML>
 >>------_=_NextPart_001_01C9540E.AB036396--

 cheers

   jon