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

<l.wood@surrey.ac.uk> Sun, 11 May 2014 14:01 UTC

Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: dtn-interest@ietfa.amsl.com
Delivered-To: dtn-interest@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 845641A01EA for <dtn-interest@ietfa.amsl.com>; Sun, 11 May 2014 07:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 74KIavAGGYsH for <dtn-interest@ietfa.amsl.com>; Sun, 11 May 2014 07:01:03 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.173]) by ietfa.amsl.com (Postfix) with ESMTP id 92B891A01C9 for <dtn-interest@irtf.org>; Sun, 11 May 2014 07:01:02 -0700 (PDT)
Received: from [195.245.230.131:56558] by server-13.bemta-3.messagelabs.com id 95/98-18692-7928F635; Sun, 11 May 2014 14:00:55 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-5.tower-78.messagelabs.com!1399816854!30492977!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received:
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17369 invoked from network); 11 May 2014 14:00:55 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-5.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 11 May 2014 14:00:55 -0000
Received: from EXHY021V.surrey.ac.uk (131.227.200.104) by EXHT012P.surrey.ac.uk (131.227.200.39) with Microsoft SMTP Server (TLS) id 8.3.348.2; Sun, 11 May 2014 15:00:54 +0100
Received: from emea01-db3-obe.outbound.protection.outlook.com (131.227.200.4) by email365.surrey.ac.uk (131.227.200.104) with Microsoft SMTP Server (TLS) id 14.3.174.1; Sun, 11 May 2014 15:00:54 +0100
Received: from AMSPR06MB439.eurprd06.prod.outlook.com (10.242.23.19) by AMSPR06MB439.eurprd06.prod.outlook.com (10.242.23.19) with Microsoft SMTP Server (TLS) id 15.0.939.12; Sun, 11 May 2014 14:00:53 +0000
Received: from AMSPR06MB439.eurprd06.prod.outlook.com ([10.242.23.19]) by AMSPR06MB439.eurprd06.prod.outlook.com ([10.242.23.19]) with mapi id 15.00.0939.000; Sun, 11 May 2014 14:00:53 +0000
From: l.wood@surrey.ac.uk
To: jcnobre@inf.ufrgs.br, dtn-interest@irtf.org
Thread-Topic: [dtn-interest] HTTP-DTN implementations was RE: New Version Notification for draft-wood-dtnrg-http-dtn-delivery-08.txt
Thread-Index: AQHPbEJ5oWTNjGkPKUuxpxuhT7u/uJs6dreAgADyta4=
Date: Sun, 11 May 2014 14:00:52 +0000
Message-ID: <1399816851828.47346@surrey.ac.uk>
References: <20140506125304.1992.83382.idtracker@ietfa.amsl.com> <1399381055.47658.YahooMailNeo@web28902.mail.ir2.yahoo.com> <1399381624373.33057@surrey.ac.uk> <1399721290076.88633@surrey.ac.uk>, <CABv6xLscSfv6pj5COY=dsY7+3OxwTBt9o52EXATfBemB4NHv+g@mail.gmail.com>
In-Reply-To: <CABv6xLscSfv6pj5COY=dsY7+3OxwTBt9o52EXATfBemB4NHv+g@mail.gmail.com>
Accept-Language: en-AU, en-US
Content-Language: en-AU
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [124.149.119.170]
x-forefront-prvs: 020877E0CB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(428001)(24454002)(377454003)(189002)(199002)(377424004)(51704005)(164054003)(92726001)(81542001)(74482001)(20776003)(83322001)(85852003)(99396002)(83072002)(2656002)(79102001)(19580405001)(19580395003)(74662001)(81342001)(15202345003)(86362001)(64706001)(66066001)(80022001)(4396001)(77096999)(76176999)(36756003)(50986999)(15975445006)(87936001)(74502001)(101416001)(77982001)(54356999)(46102001)(21056001)(76482001); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR06MB439; H:AMSPR06MB439.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (: surrey.ac.uk does not designate permitted sender hosts)
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: AMSPR06MB439.eurprd06.prod.outlook.com
X-OriginatorOrg: surrey.ac.uk
X-CrossPremisesHeadersPromoted: EXHY021v.surrey.ac.uk
X-CrossPremisesHeadersFiltered: EXHY021v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/dtn-interest/ioEzadu846WPw_IHpEWn5CuWUNg
Subject: Re: [dtn-interest] HTTP-DTN implementations was RE: New Version Notification for draft-wood-dtnrg-http-dtn-delivery-08.txt
X-BeenThere: dtn-interest@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." <dtn-interest.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/dtn-interest>, <mailto:dtn-interest-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/dtn-interest/>
List-Post: <mailto:dtn-interest@irtf.org>
List-Help: <mailto:dtn-interest-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 May 2014 14:01:06 -0000

Thanks, Jéferson.

Changes from even -00 of the http-dtn draft aren't that major. Interesting how the IETF's legal boilerplate has changed over the years, though...

http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=draft-wood-dtnrg-http-dtn-delivery-00.txt&url2=draft-wood-dtnrg-http-dtn-delivery-08.txt

Lloyd Wood
http://sat-net.com/L.Wood/dtn/http-dtn.html
________________________________________
From: jeferson.nobre@gmail.com <jeferson.nobre@gmail.com> on behalf of Jéferson Campos Nobre <jcnobre@inf.ufrgs.br>
Sent: Sunday, 11 May 2014 9:28 AM
To: dtn-interest@irtf.org; Wood L  Dr (Electronic Eng)
Subject: Re: [dtn-interest] HTTP-DTN implementations was RE: New Version Notification for draft-wood-dtnrg-http-dtn-delivery-08.txt

Hi there.
Just to add up some context on Lloyd's email.
The HTTP-DTN code mentioned is a component of a prototype P2P-based
network management framework called ManP2P-ng. My research group
developed this component in order to investigate DTN management
considering terrestrial environments.
The code is really experimental (pre-alpha) and it is based on
previous versions of the HTTP-DTN draft. Thus, I am not sure how it
compares to the last draft.
Cheers.

Jéferson Campos Nobre
PhD Student
Computer Networks Group -  Institute of Informatics
Federal University of Rio Grande do Sul
http://www.inf.ufrgs.br/~jcnobre

On Sat, May 10, 2014 at 8:28 AM,  <l.wood@surrey.ac.uk> wrote:
> 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: dtn-interest@irtf.org
> 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
>
> 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, "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
>