[dtn-interest] HTTP-DTN implementations was RE: New Version Notification for draft-wood-dtnrg-http-dtn-delivery-08.txt

[<[e-mail]>]

Oh, there's a public HTTP-DTN implementation (with open MIT License) in ManP2P-NG.

https://github.com/ComputerNetworks-UFRGS/ManP2P-ng/


Papers describing this HTTP-DTN implementation include:


http://dx.doi.org/10.1109/ISCC.2013.6755026

Self-* properties and P2P technology on disruption-tolerant management,
J. Campos Nobre, P. Arthur Pinheiro Rosa Duarte, L. Zambenedetti
Granville and L. Margarida Rockenbach Tarouco, 2013 IEEE Symposium on
Computers and Communications (ISCC), pp. 676-681, 7-10 July 2013.

http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6573064
Delay-Tolerant Management Using Self-* Properties and P2P Technology,
J. Campos Nobre, P. Arthur Pinheiro Rosa Duarte, L. Zambenedetti
Granville and L. Margarida Rockenbach Tarouco, IFIP/IEEE International
Symposium on Integrated Network Management (IM 2013), Ghent, pp.
728-731, 27-31 May 2013.



Lloyd Wood
http://sat-net.com/L.Wood/dtn/http-dtn.html
________________________________
From: Wood L Dr (Electronic Eng)
Sent: Tuesday, 6 May 2014 11:07 PM
To: [e-mail]
Subject: FW: New Version Notification for draft-wood-dtnrg-http-dtn-delivery-08.txt


http://tools.ietf.org/html/draft-wood-dtnrg-http-dtn-delivery<http://tools.ietf.org/html/draft-wood-dtnrg-http-dtn-delivery-08>

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.


On Tuesday, 6 May 2014, 22:53, "[e-mail]" <[e-mail]> 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