Re: [dtn-interest] DTN BoF Proposal for IETF90

Kevin Fall <kfall@kfall.net> Mon, 05 May 2014 19:02 UTC

Return-Path: <kfallca@gmail.com>
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 1F3531A0189 for <dtn-interest@ietfa.amsl.com>; Mon, 5 May 2014 12:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 3BjbGwH-nywh for <dtn-interest@ietfa.amsl.com>; Mon, 5 May 2014 12:02:37 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id A2D2A1A00ED for <dtn-interest@irtf.org>; Mon, 5 May 2014 12:02:37 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id bs8so3157733wib.3 for <dtn-interest@irtf.org>; Mon, 05 May 2014 12:02:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=xIdsOVKDb06F8M8pyGbGcZ8WdNJsJlQb9fEGmOVP4J0=; b=CeHwb/skTguBiIzUlfa4G4Cmn0MeWwaOmCZH5/bXWe7XEeExL/qBLg7dJBVKGBi40G sqF4gRWWV8PdFOCGqD9tdASLt/ZHnMQt2egi/yVBc9ssLIev7VPdA+6uaQQ5Ng/TAnq8 kJEMhaQm6Bjl6Gy93cs7bZfAVU1lZ48c1ZlsKZd62DdJ5l8ni6mxHSZa4l8QSsKS+MU8 GzSPK51WiyWzYa6/VsZWah8HbWLgsvbAT/zm4qfCo6+k0NKen2+Rg82hbjIEKFKjyBLX 7vbHdom1cvTX9unmp77D6ZALcQRvyCBIX/fuHoDjAaTHMzDSKw9KpZsCgkFfxF2pAVZx lW3w==
MIME-Version: 1.0
X-Received: by 10.194.19.161 with SMTP id g1mr28825844wje.20.1399316553619; Mon, 05 May 2014 12:02:33 -0700 (PDT)
Sender: kfallca@gmail.com
Received: by 10.194.80.33 with HTTP; Mon, 5 May 2014 12:02:33 -0700 (PDT)
In-Reply-To: <2134F8430051B64F815C691A62D983181B298264@XCH-BLV-504.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D983181B28DD43@XCH-BLV-504.nw.nos.boeing.com> <1399071941.29419.823.camel@mightyatom> <A5BEAD028815CB40A32A5669CF737C3B4238AFF1@ap-embx-sp40.RES.AD.JPL> <1399191573646.95282@surrey.ac.uk> <536660D6.1060306@cs.tcd.ie> <1399273959592.9040@surrey.ac.uk> <2134F8430051B64F815C691A62D983181B298264@XCH-BLV-504.nw.nos.boeing.com>
Date: Mon, 05 May 2014 15:02:33 -0400
X-Google-Sender-Auth: 6A8Y1-rJ62uX5VunlnUiXMIxc-s
Message-ID: <CAEFTjmWS17fxrysmHRbNp-wzXkV_3+UkLqXm2MTwMrpPNJub9g@mail.gmail.com>
From: Kevin Fall <kfall@kfall.net>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/dtn-interest/Z2EcmZDpruK_f5cyF2zLO6PFNYQ
Cc: "dtn-interest@irtf.org" <dtn-interest@irtf.org>
Subject: Re: [dtn-interest] DTN BoF Proposal for IETF90
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: Mon, 05 May 2014 19:02:40 -0000

I can see a couple of ways you might go forward.  If you start off as
a "fix 5050/BP" you will encounter disagreement as to what are
problems and what are not.  This is evident from the various exchanges
over the years.  Alternatively, you can start somewhat higher level
with the notion that the area of challenged/DTN/DIL networks is to be
addressed with a standard protocol (set), that there is now sufficient
insight and knowledge thanks to DTNRG, and the field is open.  There
may be different design goals potentially (e.g., some web
compatibility or whatnot) which was/were not a particular driving goal
for DTNRG or BP.

- Kevin

On Mon, May 5, 2014 at 11:02 AM, Templin, Fred L
<Fred.L.Templin@boeing.com> wrote:
> Hi Lloyd,
>
> I have to say that I mostly agree with Stephen. IMHO, "Bundle of Problems"
> is a very useful document and still applies today, but I see it as an
> actionable problem statement and not an end-of-the-road pronouncement.
> I believe most of the BoP problems can be addressed in an RFC5050(bis)
> and we would tackle this in the initial working group work items.
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>> -----Original Message-----
>> From: dtn-interest [mailto:dtn-interest-bounces@irtf.org] On Behalf Of l.wood@surrey.ac.uk
>> Sent: Monday, May 05, 2014 12:13 AM
>> To: stephen.farrell@cs.tcd.ie; dtn-interest@irtf.org
>> Subject: Re: [dtn-interest] DTN BoF Proposal for IETF90
>>
>> Stephen,
>>
>> I would discourage others from using or building on
>> RFC5050, based on our experience in testing the Bundle
>> Protocol in space [1], analysing the protocol's failings
>> [2], and a variety of previously suggested fixes and drafts
>> in this RG that never went anywhere, which aren't published.
>>
>> That's our engineering judgement on RFC5050 as it stands,
>> and many long-time readers will be familiar with our arguments.
>> But, as far as discussing the proposed WG and a modified
>> RFC5050bis goes:
>>
>> Any protocol is simply an artefact that is an outcome of a process by people.
>> It's reasonable to have doubts about the same pool of people producing anything
>> better in a similar process. If there's a new crowd from Boeing et al with
>> relevant expertise and funding/resources/time, that may help.
>> (Or not, depending on the learning curve.)
>>
>> Will the putative IETF WG be as wholly focused on, say, security?
>> I don't see how having a set of milestones magically fixes things
>> that years in this research group, with discussion between the interested,
>> did not. I don't see how an RG with failing output and limited adoption
>> can be transformed into a WG with successful output and widespread (even
>> terrestrial?) adoption, and I have never seen that done.
>> (RGs have transformed and mutated into other RGs, with rather
>> varying success.)
>>
>> How can a WG with the mandate 'fix the bundle protocol' succeed?
>> Is it just being set up to fail? Should it therefore not be set up at all?
>>
>> [1] Will Ivancic, Wesley M. Eddy, Dave Stewart, Lloyd Wood, James Northam
>> and Chris Jackson, 'Experience with delay-tolerant networking from orbit',
>> peer-reviewed journal paper, International Journal of Satellite
>> Communications and Networking, special issue for best papers of the Fourth
>> Advanced Satellite Mobile Systems Conference (ASMS 2008), vol. 28,
>> issues 5-6, pp. 335-351, September-December 2010.
>> http://dx.doi.org/10.1002/sat.966
>> http://personal.ee.surrey.ac.uk/Personal/L.Wood/publications/ijscn-asms-bundle-paper-submitted.pdf
>>
>> [2] Lloyd Wood, Wesley M. Eddy and Peter Holliday, 'A Bundle of Problems',
>> peer-reviewed conference paper, IEEE Aerospace Conference, Big Sky,
>> Montana, March 2009.  16 pages.  http://dx.doi.org/10.1109/AERO.2009.4839384
>> http://personal.ee.surrey.ac.uk/Personal/L.Wood/publications/wood-ieee-aerospace-2009-bundle-
>> problems.pdf
>>
>> Lloyd Wood
>> http://sat-net.com/L.Wood/dtn
>>
>> that was a Star Wars reference, btw. May the 4th: may the force...
>> ________________________________________
>> From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
>> Sent: Monday, 5 May 2014 1:46 AM
>> To: Wood L  Dr (Electronic Eng); dtn-interest@irtf.org
>> Subject: Re: [dtn-interest] DTN BoF Proposal for IETF90
>>
>> Lloyd,
>>
>> On 04/05/14 09:19, l.wood@surrey.ac.uk wrote:
>> > I have a bad feeling about this.
>>
>> FWIW, my impression is that you'd have a bad feeling about
>> anything related to rfc5050 regardless. IMO, it'd be quite
>> reasonable for people to disregard quite a bit of what you
>> say on that basis, i.e. that you appear to be interested
>> in being destructively critical. That's a pity, since there
>> are things to be improved/fixed for which you have argued,
>> and with which others agree.
>>
>> Its even more a pity as it somewhat poisons the discussion,
>> so I'd ask that if you can, please you try to put aside your
>> distaste for rfc5050 and your annoyance at dtnrg history and
>> try constructively discuss the proposed IETF wg.
>>
>> S.
>>
>>
>> _______________________________________________
>> dtn-interest mailing list
>> dtn-interest@irtf.org
>> https://www.irtf.org/mailman/listinfo/dtn-interest
>
> _______________________________________________
> dtn-interest mailing list
> dtn-interest@irtf.org
> https://www.irtf.org/mailman/listinfo/dtn-interest
>