Re: [Ieprep] Hiccup Bar BOF

Fred Baker <fred@cisco.com> Tue, 20 March 2007 05:19 UTC

Return-path: <ieprep-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTWlG-0003kH-9f; Tue, 20 Mar 2007 01:19:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTWlE-0003kC-LT for ieprep@ietf.org; Tue, 20 Mar 2007 01:19:52 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTWlC-0007Al-9s for ieprep@ietf.org; Tue, 20 Mar 2007 01:19:52 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93]) by sj-iport-5.cisco.com with ESMTP; 19 Mar 2007 22:19:51 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l2K5Jnw6018926; Mon, 19 Mar 2007 22:19:49 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l2K5Jnwn023696; Tue, 20 Mar 2007 05:19:49 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Mar 2007 22:19:49 -0700
Received: from [10.0.0.240] ([10.21.122.88]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Mar 2007 22:19:49 -0700
In-Reply-To: <200703200432.l2K4WGR8035543@abenaki.wabanaki.net>
References: <04EBAA920483D946AC97C8F8DE79FD9501A56302@RSRCNEX01CN1.rsrc.osd.mil> <46E7B21EF4A45749B2432ABDCDE6FEA1018C6859@MCLNEXVS12.resource.ds.bah.com> <B91F7246-24F8-45A4-A931-6AC0FF5AA4B3@cisco.com> <200703200432.l2K4WGR8035543@abenaki.wabanaki.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A8B9EAB1-2FF1-4ECB-BF1D-A4C1B0719707@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: [Ieprep] Hiccup Bar BOF
Date: Tue, 20 Mar 2007 06:19:46 +0100
To: Eric Brunner-Williams in Portland Maine <brunner@abenaki.wabanaki.net>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 20 Mar 2007 05:19:49.0251 (UTC) FILETIME=[6197D530:01C76AAF]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1885; t=1174367989; x=1175231989; c=relaxed/simple; s=sjdkim8002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20[Ieprep]=20Hiccup=20Bar=20BOF=20 |Sender:=20; bh=XsQdiOIh5r7E44SFPaTfxP9oBmUtit5Z6Tu+s2BDR90=; b=d8MSghnwzdbybkqQ5fZE3au9aTCUw5sKx/vYmdBvqn6N+ROT/shuSYwEgfDwMT5drgEkUIo4 mz925TtMIjYYH2n+GzDsOEbJWN5D6CEPrTxDO5ynuXMKGoz2yadU0TKY;
Authentication-Results: sj-dkim-8; header.From=fred@cisco.com; dkim=pass (si g from cisco.com/sjdkim8002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
Errors-To: ieprep-bounces@ietf.org

There were a lot of things that didn't work in Katrina. Fuel trucks  
that would have run communications diverted to fuel hospitals, for  
example. The delayed recognition at the state level of the emergency  
that legally prevented the deployment of federal resources, later  
reported as a delay on the part of FEMA. The fact that wireless  
networks deployed for use by first responders were swamped by well- 
meaning volunteers who set up their web sites over those same  
networks. ...

The fact that COs were ripped out of the ground bodily, or being 25'  
below sea level had their generators flooded, really didn't help.

There are a lot of issues above the application layer.

Note that this refers to "times of crisis". I don't think it has in  
view times when one has to parachute in a new network because the old  
one has been swept away bodily. It has to do with the one we've got.



On Mar 20, 2007, at 5:32 AM, Eric Brunner-Williams in Portland Maine  
wrote:

> Fred,
>
> I'm out in the middle of Joshua Tree, so I won't be at the bar.
>
> After the Katerina landfall the wireless volunteer efforts, plus  
> the Naval Post-Graduate School group that had prior exercise in the  
> Boxing Day Tsunami aid effort found some pretty banal problems.
>
> Nothing sexy like QoS, but lack of "I am alive (or not)" db app and  
> or protocol, formal relief efforts that attempted to field VoIP  
> with a centralized directory (in Washington) to camps served by  
> very fragile networks, junk like that.
>
> It isn't rocket science, but not everything we do is, and when it  
> doesnt' work, for many days at a time, due to lack of clarity at  
> level 9 that non-first responders, non-privileged users, need to  
> have dialtone and email and a browser, its wicked awkward for the  
> people who are having he emergency.
>
> Eric

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep