Re: [dtn-interest] FW: New Version Notification for draft-wood-dtnrg-http-dtn-delivery-08.txt

Thanks, Kevin.

Our Bundle of Problems paper cites your architectural paper.

On Stoica/Popa's work,
http://www.eecs.berkeley.edu/Pubs/TechRpts/2012/EECS-2012-5.pdf
HTTP: an evolvable narrow waist for the future internet, Popa, Wendell, Ghodsi and Stoica, Tech report UCB-EECS-2012-5, University of California at Berkeley, 4 Jan 2012
is even more interesting (and less constrained for space) than their earlier Hotnets 2010 paper that you mention. It shows use of explicit intermediaries in http deliveries, and that http use performed well with little overhead. That work seems to be heading in HTTP-DTN's direction.

Thanks for the pointer!

Lloyd Wood
http://sat-net.com/L.Wood/dtn/http-dtn
________________________________________
From: kfallca@gmail.com <kfallca@gmail.com> on behalf of Kevin Fall <kfall@kfall.net>
Sent: Wednesday, 7 May 2014 3:05 AM
To: Wood L  Dr (Electronic Eng)
Cc: dtn-interest@irtf.org
Subject: Re: [dtn-interest] FW: New Version Notification for draft-wood-dtnrg-http-dtn-delivery-08.txt

I'd suggest that if you wish to reference material outside RFCs and
you wish to reference your problems paper, you also reference the
architectural retrospective paper and possibly Ion Stoica's "HTTP as
the narrow waist of the future internet" paper from HotNets-IX.  I'd
also suggest the (work in progress) from 2011 reference be fixed
somehow.

- Kevin

On Tue, May 6, 2014 at 9:07 AM,  <l.wood@surrey.ac.uk> wrote:
> http://tools.ietf.org/html/draft-wood-dtnrg-http-dtn-delivery
>
> Based on recent discussion, we have just updated our http-dtn draft.
>
> http://sat-net.com/L.Wood/dtn/http-dtn
>
> has related papers, and there's also some discussion of http-dtn in our
> 'Bundle of Problems' paper, which I may have mentioned previously.
>
>
>>> In particular, the HTTP-DTN concept clearly merits serious
>>> consideration as a way of addressing the well-known challenges of
>>> delay-tolerant networking, but I don't think this BoF request
>>> discussion is the right place to try to conduct that serious
>>> consideration.
>>
>> I think Lloyd's http-dtn stuff is maybe one possible approach but the
>> issue of whether or not an IETF WG prioritises ease of terrestrial
>> deployment or prioritises minimal change to 5050 is basically
>> independent of http-dtn. So we shouldn't get hung up on a false
>> dichotomy there.
>>
>>> What I think would make more sense would be for a couple of
>>> experimental HTTP-DTN implementations to be developed and exercised
>>> in practical deployment scenarios, just as has been done with the
>>> DTNRG's BP-based protocol suite over the past decade, so that we
>>> can all get a better sense of the architecture's demonstrated
>>> advantages and disadvantages.  The DTNRG seems to me to be the
>>> right venue for that research.
>
>
> Lloyd Wood
> http://about.me/lloydwood
>
> On Tuesday, 6 May 2014, 22:53, "internet-drafts@ietf.org"
> <internet-drafts@ietf.org> wrote:
>
> A new version of I-D, draft-wood-dtnrg-http-dtn-delivery-08.txt
> has been successfully submitted by Lloyd Wood and posted to the
> IETF repository.
>
> Name:        draft-wood-dtnrg-http-dtn-delivery
> Revision:    08
> Title:        Using HTTP for delivery in Delay/Disruption-Tolerant Networks
> Document date:    2014-05-06
> Group:        Individual Submission
> Pages:        11
> URL:
> http://www.ietf.org/internet-drafts/draft-wood-dtnrg-http-dtn-delivery-08.txt
> Status:
> https://datatracker.ietf.org/doc/draft-wood-dtnrg-http-dtn-delivery/
> Htmlized:
> http://tools.ietf.org/html/draft-wood-dtnrg-http-dtn-delivery-08
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-wood-dtnrg-http-dtn-delivery-08
>
> Abstract:
>   This document describes how to use the Hypertext Transfer Protocol,
>   HTTP, for communication across delay- and disruption-tolerant
>   networks, by making every transit node in the network HTTP-capable,
>   and doing peer HTTP transfers between nodes to move data hop-by-hop
>   or subnet-by-subnet towards its final destination.  HTTP is well-
>   known and straightforward to implement in these networks.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
>
> _______________________________________________
> dtn-interest mailing list
> dtn-interest@irtf.org
> https://www.irtf.org/mailman/listinfo/dtn-interest
>