RE: [HICCUP] Any interest?

"Ivancic, William D. (GRC-RCN0)" <william.d.ivancic@nasa.gov> Wed, 25 July 2007 22:23 UTC

Return-path: <hiccup-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDpGe-0007xT-4t; Wed, 25 Jul 2007 18:23:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDpGd-0007xL-Hm for hiccup@ietf.org; Wed, 25 Jul 2007 18:23:39 -0400
Received: from ndjsbar01.ndc.nasa.gov ([198.120.25.38]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDpGb-00064K-S4 for hiccup@ietf.org; Wed, 25 Jul 2007 18:23:39 -0400
Received: from ndjsxgw04.ndc.nasa.gov (ndjsxgw04.ndc.nasa.gov [129.166.32.112]) by ndjsbar01.ndc.nasa.gov (Spam Firewall) with ESMTP id A9C873BB547; Wed, 25 Jul 2007 17:23:36 -0500 (CDT)
Received: from NDJSEVS23A.ndc.nasa.gov ([129.166.32.223]) by ndjsxgw04.ndc.nasa.gov with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Jul 2007 17:23:36 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [HICCUP] Any interest?
Date: Wed, 25 Jul 2007 17:22:36 -0500
Message-ID: <A3A356E39B867E4380966B0EB600C28F38E16E@NDJSEVS23A.ndc.nasa.gov>
In-Reply-To: <46A7C2FF.5040901@gmx.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [HICCUP] Any interest?
Thread-Index: AcfPBETskGXlkJRqT4SwGdG4kJma0wABKUvg
References: <A55DB203FF9BCF478586DB2350863864751C26@emss09m03.us.lmco.com><2A1E424B-FEE4-40CF-8D86-883FB1002798@g11.org.uk> <46A7C2FF.5040901@gmx.net>
From: "Ivancic, William D. (GRC-RCN0)" <william.d.ivancic@nasa.gov>
To: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>, "ken carlberg" <carlberg@g11.org.uk>
X-OriginalArrivalTime: 25 Jul 2007 22:23:36.0813 (UTC) FILETIME=[71BC31D0:01C7CF0A]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: hiccup@ietf.org
X-BeenThere: hiccup@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Harnessing IP for Critical Communications Using Precedence \(HICCUP\) list" <hiccup.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hiccup>, <mailto:hiccup-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/hiccup>
List-Post: <mailto:hiccup@ietf.org>
List-Help: <mailto:hiccup-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hiccup>, <mailto:hiccup-request@ietf.org?subject=subscribe>
Errors-To: hiccup-bounces@ietf.org

Having a draft problem statement would help greatly.  It is easier to
build and comment on something than start from scratch.  Consider this
sort of a brainstorming.  Sometimes a few ideas need to be put to
stimulate thought and activity.  

Without a problem statement, I don't think this group is ready for a
BOF.  Also, one needs a larger community than just DoD.  Having a
premature BoF without doing the upfront work will be counter productive.
What may be a worthwhile activity may come to a screeching halt.

NASA should have some interest in HICCUP, but they don't know it yet.
Regardless, NASA's use of HICCUP would be very limited and since most of
their communication is on closed networks, they can probably just solve
the problem with bandwidth - at least on the ground.


Will

******************************
William D. Ivancic
http://roland.grc.nasa.gov/~ivancic 
 

> -----Original Message-----
> From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net] 
> Sent: Wednesday, July 25, 2007 5:39 PM
> To: ken carlberg
> Cc: hiccup@ietf.org
> Subject: Re: [HICCUP] Any interest?
> 
> Ken, you phrased the challenge quite well.
> 
> Another problem is that there isn't a detailed description of 
> the planned work available.
> 
> Good luck!
> 
> Ciao
> Hannes
> 
> ken carlberg wrote:
> > While your intentions are probably fair, I feel your line 
> of reasoning 
> > will not go far in advancing HICCUP in the IETF beyond a 
> mailing list.
> >
> > If there are some distinct and succinct problem(s) you 
> think need to 
> > be addressed, please feel free to bring them up.  I would also 
> > recommend trying to present your thoughts beyond a specific 
> > customer/client and/or a private network.  Work in the IETF 
> should not 
> > be something that would only apply to an RFP.
> >
> > regards,
> >
> > -ken
> >
> >
> > On Jul 25, 2007, at 2:10 PM, Kantawala, Anshul wrote:
> >
> >>
> >> Hi,
> >> I was hoping there would be enough interest for a BOF in 
> Chicago, but 
> >> that didn't happen.  HICCUP is also highly relevant for military 
> >> networks and thus I would presume there would be good support from 
> >> defense contractors and other companies supporting DoD networks.
> >>
> >> Hope we can generate enough interest to at least hold a BOF during 
> >> the next IETF meeting.  Also, in the interim, maybe we could start 
> >> trying to put together a draft outlining the problem space?
> >>
> >> Thanks,
> >> Anshul Kantawala
> >> Lockheed Martin, IS&GS
> >> 301-240-7539
> >>
> >> _______________________________________________
> >> HICCUP mailing list
> >> HICCUP@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/hiccup
> >
> >
> > _______________________________________________
> > HICCUP mailing list
> > HICCUP@ietf.org
> > https://www1.ietf.org/mailman/listinfo/hiccup
> 
> 
> _______________________________________________
> HICCUP mailing list
> HICCUP@ietf.org
> https://www1.ietf.org/mailman/listinfo/hiccup
> 

_______________________________________________
HICCUP mailing list
HICCUP@ietf.org
https://www1.ietf.org/mailman/listinfo/hiccup