From hiccup-bounces@ietf.org Wed Jul 25 15:10:52 2007 Return-path: 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 ; 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" To: hiccup@ietf.org Message-id: 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 From hiccup-bounces@ietf.org Wed Jul 25 17:29:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDoPz-0003l8-Vu; Wed, 25 Jul 2007 17:29:15 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDoPz-0003l3-1A for hiccup@ietf.org; Wed, 25 Jul 2007 17:29:15 -0400 Received: from peter.ietf69.org ([130.129.5.6] helo=smtp.ietf69.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDoPy-00054y-Mw for hiccup@ietf.org; Wed, 25 Jul 2007 17:29:15 -0400 Received: from [130.129.39.250] (dhcp-27fa.ietf69.org [130.129.39.250]) by smtp.ietf69.org (Postfix) with ESMTP id 67F26D68001; Wed, 25 Jul 2007 16:29:14 -0500 (CDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2A1E424B-FEE4-40CF-8D86-883FB1002798@g11.org.uk> Content-Transfer-Encoding: 7bit From: ken carlberg Subject: Re: [HICCUP] Any interest? Date: Wed, 25 Jul 2007 16:29:12 -0500 To: "Kantawala, Anshul" X-Mailer: Apple Mail (2.752.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: hiccup-bounces@ietf.org 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 From hiccup-bounces@ietf.org Wed Jul 25 17:39:14 2007 Return-path: 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 User-Agent: Thunderbird 2.0.0.5 (Windows/20070716) MIME-Version: 1.0 To: ken carlberg Subject: Re: [HICCUP] Any interest? References: <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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 From hiccup-bounces@ietf.org Wed Jul 25 18:23:40 2007 Return-path: 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: In-Reply-To: <46A7C2FF.5040901@gmx.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [HICCUP] Any interest? Thread-Index: AcfPBETskGXlkJRqT4SwGdG4kJma0wABKUvg References: <2A1E424B-FEE4-40CF-8D86-883FB1002798@g11.org.uk> <46A7C2FF.5040901@gmx.net> From: "Ivancic, William D. (GRC-RCN0)" To: "Hannes Tschofenig" , "ken carlberg" 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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. =20 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=20 =20 > -----Original Message----- > From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net]=20 > Sent: Wednesday, July 25, 2007 5:39 PM > To: ken carlberg > Cc: hiccup@ietf.org > Subject: Re: [HICCUP] Any interest? >=20 > Ken, you phrased the challenge quite well. >=20 > Another problem is that there isn't a detailed description of=20 > the planned work available. >=20 > Good luck! >=20 > Ciao > Hannes >=20 > ken carlberg wrote: > > While your intentions are probably fair, I feel your line=20 > of reasoning=20 > > will not go far in advancing HICCUP in the IETF beyond a=20 > mailing list. > > > > If there are some distinct and succinct problem(s) you=20 > think need to=20 > > be addressed, please feel free to bring them up. I would also=20 > > recommend trying to present your thoughts beyond a specific=20 > > customer/client and/or a private network. Work in the IETF=20 > should not=20 > > 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=20 > Chicago, but=20 > >> that didn't happen. HICCUP is also highly relevant for military=20 > >> networks and thus I would presume there would be good support from=20 > >> defense contractors and other companies supporting DoD networks. > >> > >> Hope we can generate enough interest to at least hold a BOF during=20 > >> the next IETF meeting. Also, in the interim, maybe we could start=20 > >> 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 >=20 >=20 > _______________________________________________ > HICCUP mailing list > HICCUP@ietf.org > https://www1.ietf.org/mailman/listinfo/hiccup >=20 _______________________________________________ HICCUP mailing list HICCUP@ietf.org https://www1.ietf.org/mailman/listinfo/hiccup