[HICCUP] Any interest?

"Kantawala, Anshul" <anshul.kantawala@lmco.com> Wed, 25 July 2007 19:10 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 1IDmG0-0006Q6-W3; Wed, 25 Jul 2007 15:10:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDmFz-0006Pb-FD for hiccup@ietf.org; Wed, 25 Jul 2007 15:10:47 -0400
Received: from mailgw1a.lmco.com ([192.31.106.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDmFz-00027K-3K for hiccup@ietf.org; Wed, 25 Jul 2007 15:10:47 -0400
Received: from emss07g01.ems.lmco.com (relay5.ems.lmco.com [166.29.2.16])by mailgw1a.lmco.com (LM-6) with ESMTP id l6PJAI1c013907for <hiccup@ietf.org>; Wed, 25 Jul 2007 13:10:34 -0600 (MDT)
Received: from CONVERSION2-DAEMON.lmco.com by lmco.com (PMDF V6.3-x3 #31239) id <0JLR0000119QH4@lmco.com> for hiccup@ietf.org; Wed, 25 Jul 2007 13:10:38 -0600 (MDT)
Received: from EMSS09I00.us.lmco.com ([158.183.26.31]) by lmco.com (PMDF V6.3-x3 #31239) with ESMTP id <0JLR00IA519K4J@lmco.com> for hiccup@ietf.org; Wed, 25 Jul 2007 13:10:37 -0600 (MDT)
Received: from EMSS09M03.us.lmco.com ([158.183.26.17]) by EMSS09I00.us.lmco.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 25 Jul 2007 15:10:34 -0400
Date: Wed, 25 Jul 2007 15:10:34 -0400
From: "Kantawala, Anshul" <anshul.kantawala@lmco.com>
To: hiccup@ietf.org
Message-id: <A55DB203FF9BCF478586DB2350863864751C26@emss09m03.us.lmco.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Thread-Topic: Any interest?
Thread-Index: AcfO73npR5R1hdoMTPmBiwObxUfTSA==
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-OriginalArrivalTime: 25 Jul 2007 19:10:34.0511 (UTC) FILETIME=[7A2529F0:01C7CEEF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Subject: [HICCUP] Any interest?
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

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