Re: [dtn-interest] RFC 5050 revision?

Stephen Farrell <stephen.farrell@cs.tcd.ie> Sun, 20 May 2012 10:47 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: dtn-interest@ietfa.amsl.com
Delivered-To: dtn-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 914B421F851B for <dtn-interest@ietfa.amsl.com>; Sun, 20 May 2012 03:47:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cAz4OeVJXWXI for <dtn-interest@ietfa.amsl.com>; Sun, 20 May 2012 03:47:16 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id B4B0C21F8503 for <dtn-interest@irtf.org>; Sun, 20 May 2012 03:47:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 271A117153E; Sun, 20 May 2012 11:47:16 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1337510835; bh=GZbtbfDBp/ewzG UPTX/EjJxWXq+zOoB1zKnUoYBSRBY=; b=ssF0DY5L/qcFBjZBdRiSmiz2/vw7Ff 4Gp2qK0ejje7qFMjcTrz4UDTwhjfUUcVrG8OBgxMrZ0Fa3U02AL4fYrYqCE9NCEn vA08x99hmWS2NjVE6Hf6wLVvc6zZbsPAj9qlDrjvn+pVbeIGyOGziXefZtKe6yFF ps+1uFSDilTYz7Yq+aPEDltB+/EcA46g1ufjy5UoVBXE8rtv5WNncDIE7mffyNha ccJ8Nee+wdtr80SvsQunKzpI5mQllEXFeHaPS3ui5TtM8bfXWJrz+8LBpIdRWSYh dUV7Os5dxuN/JsTpGoCUTm+dQf0whw4gnSGUaWZ39BYscU4x38cGdMQQ==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id s0c8lssvG4om; Sun, 20 May 2012 11:47:15 +0100 (IST)
Received: from [10.87.48.3] (unknown [86.42.20.120]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 406D417153D; Sun, 20 May 2012 11:47:15 +0100 (IST)
Message-ID: <4FB8CBB2.1000304@cs.tcd.ie>
Date: Sun, 20 May 2012 11:47:14 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: L.Wood@surrey.ac.uk
References: <4FB2B614.1090303@cs.tcd.ie> <FD7B10366AE3794AB1EC5DE97A93A37341C5B16AE7@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <FD7B10366AE3794AB1EC5DE97A93A37341C5B16AE7@EXMB01CMS.surrey.ac.uk>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: dtn-interest@irtf.org
Subject: Re: [dtn-interest] RFC 5050 revision?
X-BeenThere: dtn-interest@irtf.org
X-Mailman-Version: 2.1.12
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, 20 May 2012 10:47:17 -0000

On 05/20/2012 09:30 AM, L.Wood@surrey.ac.uk wrote:
> Stephen Farrell wrote:
>> In addition, we'd be interested in hearing whether
>> folks would like to explore doing DTN based not on
>> a straight revision of the BP, but maybe e.g. based
>> on CoAP, SPDY, websockets, or other protocols.
> 
> Since this group was set up to push and develop only the bundle protocol, the group will probably need to be rechartered to allow this. Non-bundle protocol work has been ignored previously.

I don't think rechartering is a must-do, but I do agree that
if enough people want to do credible DTN work not associated
with the BP then we probably should update the charter text
so the very few people who read the charter [1] don't get
confused.

   [1] http://irtf.org/dtnrg

> To consider CoAP or SPDY or websockets in dtns, it is necessary to consider how HTTP - which CoAP, SPDY and websockets are based on - fits into dtns. And since HTTP assumes full path connectivity between the endpoints, and dtns don't have that, it's not as easy as one might think...
> 
> Fortunately, that consideration and mapping HTTP to dtns has already been thought out, and has been previously presented to the group:
> http://sat-net.com/L.Wood/dtn/http-dtn
> http://tools.ietf.org/html/draft-wood-dtnrg-http-dtn-delivery

I agree that if we seriously discuss non-BP things then HTTP
ought be considered.

S.


> 
> 
> 
> 
>