<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [e2e] end of interest</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Rajesh,<BR>
<BR>
The DTN Bundle Protocol uses an obscure binary format for its<BR>
metadata blocks. If you want flexible user-definable metadata,<BR>
it really has to be text. For this reason, we proposed using HTTP<BR>
as a transport-layer-independent session layer for DTN networks:<BR>
<BR>
<A HREF="http://tools.ietf.org/html/draft-wood-dtnrg-http-dtn-delivery-01">http://tools.ietf.org/html/draft-wood-dtnrg-http-dtn-delivery-01</A><BR>
<A HREF="http://www.ietf.org/proceedings/08mar/slides/DTNRG-6.pdf">http://www.ietf.org/proceedings/08mar/slides/DTNRG-6.pdf</A><BR>
<BR>
Getting content identification via MIME (which the Bundle Protocol<BR>
doesn't do) is a bonus. Gopher is an example of a binary format<BR>
that didn't succeed against HTTP.<BR>
<BR>
L.<BR>
<BR>
just another of those PhD-toting technicians.<BR>
<BR>
DTN work: <A HREF="http://www.ee.surrey.ac.uk/Personal/L.Wood/dtn/">http://www.ee.surrey.ac.uk/Personal/L.Wood/dtn/</A><BR>
<BR>
<<A HREF="http://www.ee.surrey.ac.uk/Personal/L.Wood/">http://www.ee.surrey.ac.uk/Personal/L.Wood/</A>><L.Wood@surrey.ac.uk><BR>
<BR>
Rajesh Krishnan wrote on Sat 2008-05-10 1:02:<BR>
<BR>
> Networks seem to need a critical mass of adoption, and usually an<BR>
> evolutionarily smart vector to succeed. The DTN Bundle Protocol (or its<BR>
> successor, with metadata extension block semantics that will hopefully<BR>
> remain flexible and user-definable) might just offer an opportunity for<BR>
> acquiring a new critical mass, but only if it finds the smart vector<BR>
> (that does what Mosaic did for HTTP/HTML, and perhaps BSD for TCP/IP).<BR>
</FONT>
</P>
</BODY>
</HTML>