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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 28 April 2014 22:43 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A167B1A6F0B for <dtn-interest@ietfa.amsl.com>; Mon, 28 Apr 2014 15:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 kb3tR0VmBkE1 for <dtn-interest@ietfa.amsl.com>; Mon, 28 Apr 2014 15:43:05 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id A74BF1A06C1 for <dtn-interest@irtf.org>; Mon, 28 Apr 2014 15:43:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 07686BEB3; Mon, 28 Apr 2014 23:43:03 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OojHXm3Vn8q7; Mon, 28 Apr 2014 23:43:01 +0100 (IST)
Received: from [10.87.48.3] (unknown [86.44.68.241]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id BF3A5BEB2; Mon, 28 Apr 2014 23:43:01 +0100 (IST)
Message-ID: <535ED975.70308@cs.tcd.ie>
Date: Mon, 28 Apr 2014 23:43:01 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Burleigh, Scott C (312G)" <scott.c.burleigh@jpl.nasa.gov>, "dtn-interest@irtf.org" <dtn-interest@irtf.org>
References: <535E9E2B.5020707@cs.tcd.ie> <CF841D37.16067%william.d.ivancic@nasa.gov> <A5BEAD028815CB40A32A5669CF737C3B42383180@ap-embx-sp40.RES.AD.JPL> <2134F8430051B64F815C691A62D983181B292D06@XCH-BLV-504.nw.nos.boeing.com> <A5BEAD028815CB40A32A5669CF737C3B423832C9@ap-embx-sp40.RES.AD.JPL> <2134F8430051B64F815C691A62D983181B292E9A@XCH-BLV-504.nw.nos.boeing.com> <535ED25B.2090007@cs.tcd.ie> <2134F8430051B64F815C691A62D983181B292F0A@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181B292F0A@XCH-BLV-504.nw.nos.boeing.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dtn-interest/CKPBCRHE_mIH0Zt5I5VCL4jVmFc
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, 28 Apr 2014 22:43:09 -0000

Hi Fred,

On 28/04/14 23:27, Templin, Fred L wrote:
> I submitted some mini problem statement drafts that touch on areas
> that I think would need to be addressed in a 5050bis, but my list
> was not exhaustive. Scott also posted a laundry list of 5050bis
> candidate items last year. In terms of Boeing's interests, security
> is a high priority for us for what we think we need in the near term.

All that's fair enough and sorry to hammer on about this, but I
do think its important to get this clear for the scoping of the
BoF/WG.

You say "not exhaustive" but do you mean that from your POV
your list is all you're really interested in working on? Which
would be entirely ok IMO, nothing wrong with that, but I think
it'd mean you're not interested in a re-design of 5050 but more
of a bug-fix type approach.

(Again, to be clear: by re-design, I mean to keep the gatewaying-
to-5050 ability but to look again at how we represent bundles
to see if its possible to come up with something much more easily
deployed.)

S.