Re: [HICCUP] Any interest?

Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Wed, 25 July 2007 21:39 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 1IDoZe-0001iL-KO; Wed, 25 Jul 2007 17:39:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDoZd-0001iF-7m for hiccup@ietf.org; Wed, 25 Jul 2007 17:39:13 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IDoZc-0005GY-NO for hiccup@ietf.org; Wed, 25 Jul 2007 17:39:13 -0400
Received: (qmail invoked by alias); 25 Jul 2007 21:39:11 -0000
Received: from dhcp-15f4.ietf69.org (EHLO [130.129.21.244]) [130.129.21.244] by mail.gmx.net (mp007) with SMTP; 25 Jul 2007 23:39:11 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19XWRUxKkpXhcuGIudxVSZ1QsUbD/dldzjBjEQuC3 BfHHDLeORueuzc
Message-ID: <46A7C2FF.5040901@gmx.net>
Date: Wed, 25 Jul 2007 23:39:11 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [HICCUP] Any interest?
References: <A55DB203FF9BCF478586DB2350863864751C26@emss09m03.us.lmco.com> <2A1E424B-FEE4-40CF-8D86-883FB1002798@g11.org.uk>
In-Reply-To: <2A1E424B-FEE4-40CF-8D86-883FB1002798@g11.org.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
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

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