Re: [earlywarning] [CAP] Definition of Warning Categories
"David Aylward \(Comcare\)" <daylward@comcare.org> Mon, 13 July 2009 17:26 UTC
Return-Path: <daylward@natstrat.com>
X-Original-To: earlywarning@core3.amsl.com
Delivered-To: earlywarning@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0AF5D28C4F5 for <earlywarning@core3.amsl.com>; Mon, 13 Jul 2009 10:26:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Level:
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pco0UkRIrqtW for <earlywarning@core3.amsl.com>; Mon, 13 Jul 2009 10:26:33 -0700 (PDT)
Received: from server514.appriver.com (server514d.exghost.com [72.32.253.69]) by core3.amsl.com (Postfix) with ESMTP id 365CB28C513 for <earlywarning@ietf.org>; Mon, 13 Jul 2009 10:24:38 -0700 (PDT)
Received: by server514.appriver.com (CommuniGate Pro PIPE 5.2.14) with PIPE id 59809050; Mon, 13 Jul 2009 12:24:41 -0500
Received: from [72.32.253.141] (HELO FE02.exg4.exghost.com) by server514.appriver.com (CommuniGate Pro SMTP 5.2.14) with ESMTP id 59809027; Mon, 13 Jul 2009 12:24:38 -0500
Received: from FE02.exg4.exghost.com ([10.242.228.18]) by FE02.exg4.exghost.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 13 Jul 2009 12:25:05 -0500
Received: from DavidPC ([67.192.118.156]) by FE02.exg4.exghost.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 13 Jul 2009 12:25:05 -0500
From: "David Aylward (Comcare)" <daylward@comcare.org>
To: 'Rex Buddenberg' <budden@nps.navy.mil>, Bob Robinson <rwrobinsonme@yahoo.com>
References: <901124.96019.qm@web50909.mail.re2.yahoo.com> <1247504112.2203.67.camel@localhost.localdomain>
In-Reply-To: <1247504112.2203.67.camel@localhost.localdomain>
Date: Mon, 13 Jul 2009 13:25:04 -0400
Message-ID: <003601ca03de$dcc03ed0$9640bc70$@org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcoD2pE40aXC+Va5TFSEsrB4fVCyAgAAsUow
Content-Language: en-us
X-OriginalArrivalTime: 13 Jul 2009 17:25:05.0456 (UTC) FILETIME=[DCBE4300:01CA03DE]
X-Policy: GLOBAL - natstrat.com
X-Policy: GLOBAL - natstrat.com
X-Policy: GLOBAL - natstrat.com
X-Policy: GLOBAL - natstrat.com
X-Policy: GLOBAL - natstrat.com
X-Policy: Too many policies to list
X-Primary: daylward@natstrat.com
X-Note: This Email was scanned by AppRiver SecureTide
X-ALLOW: daylward@natstrat.com ALLOWED
X-Virus-Scan: V-
X-Note: Spam Tests Failed:
X-Country-Path: UNITED STATES->PRIVATE->UNITED STATES->UNITED STATES
X-Note-Sending-IP: 72.32.253.141
X-Note-Reverse-DNS: fe02.exg4.exghost.com
X-Note-WHTLIST: daylward@natstrat.com
X-Note: User Rule Hits:
X-Note: Global Rule Hits: 114 115 116 117 121 122 133 214
X-Note: Mail Class: ALLOWEDSENDER
Cc: EM Groups <emergency-management@yahoogroups.com>, earlywarning@ietf.org, IAEM List <iaem-list@iaem.com>, cap-list@incident.com
Subject: Re: [earlywarning] [CAP] Definition of Warning Categories
X-BeenThere: earlywarning@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for Authority-to-Individuals \(Early Warning\) Emergency " <earlywarning.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/earlywarning>
List-Post: <mailto:earlywarning@ietf.org>
List-Help: <mailto:earlywarning-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2009 17:26:38 -0000
Rex: Very insightful comments. Certainly you are pointing in the right direction. Many of us are working with alliances to make sure that safety uses are part of this stimulus. The law and regulations call for safety to be part of the mix. However, our enthusiasm should be tempered a bit by the emphasis the recently issued rules make for use of the funds. With a relatively small amount of money (a one time shot of $7 billion is small potatoes compared to something like $35-40 billion annually in industry capex), many of us had hoped that the rules would leverage this one time investment by focusing on building integrated demand, i.e. get safety, healthcare, etc sharing information and thus using broad band more and more. However, the predominant designated use for the first tranche of the stimulus funds (only 1/3 of the NTIA amount) is digging trenches for fiber into rural America. Nothing inherently wrong with that if someone has a future business model to support the capex. But the problem in the safety/healthcare eco-system is not primarily access to IP communications trunks, but application layer capability and interoperability issues. Part of the first part of the stimulus funds are devoted to "Innovative and sustainable uses of broadband". Hopefully more will be in the future. -----Original Message----- From: cap-list-bounces@lists.incident.com [mailto:cap-list-bounces@lists.incident.com] On Behalf Of Rex Buddenberg Sent: Monday, July 13, 2009 12:55 PM To: Bob Robinson Cc: IAEM List; EM Groups; earlywarning@ietf.org; cap-list@incident.com; Art Botterell Subject: Re: [CAP] Definition of Warning Categories Bob, You point into a very interesting parallel development out there in the world. In the stimulus bill last spring was $7.2B in grant money that went to USDA ('broadband' and 'reach to rural') and NTIA in Commerce ('broadband' and 'reach to underserved'). The FCC was also charged with drafting a 'national broadband plan'. FCC published a Notice of Inquiry, for which the comment period just closed last week. About the first comment they sought was a definition of 'broadband'. (For paper coming from inside the beltway, this NOI is pretty good stuff, IMHO). Whatever your definition of broadband, you can look behind it and see 'extension of the internet'. And you should recognize that extension of internet to rural and extension of internet to emergency services has a whole lot of overlap. Just to complete the federal nethead - bellhead list of players, DHS and DoJ are still in circuit-switch. ... and didn't get this batch of grant money. What you ought to get out of this is is that - emergency services vehicles will soon be routinely on the internet. - the citizenry that emergency services exists to serve will increasingly be on the internet. This observation is progressively true in any event -- the netheads always win -- but the stimulus subsidies are probably going to be a substantial accelerant.... Santa Ana winds behind a California wildfire. On Sun, 2009-07-12 at 17:50 -0700, Bob Robinson wrote: > Art, > > Very good analysis. In fact I think the question of user (consumer) disconnect can be put to the broader field of general emergency management communications and in fact it can be a very important part of any attempt to build "standards" that are to be applied across groups/agencies/etc. involved in emergency management. But what the heck, that's just my nickels worth based on 25+ years of EM experience. > > Bob Robinson > > --- On Sun, 7/12/09, Art Botterell <acb@incident.com> wrote: > > > From: Art Botterell <acb@incident.com> > > Subject: Re: [CAP] Definition of Warning Categories > > To: earlywarning@ietf.org, cap-list@incident.com > > Date: Sunday, July 12, 2009, 2:23 PM > > > I'm wondering whether it might be > > simpler, at least in the near term, to let consumers > > subscribe to selected sources rather than to topical > > categories. That pushes the question of message > > authoritativeness / jurisdiction /credibility out of > > the CAP infrastructure and into the larger field of > > inter-agency and inter-jurisidictional coordination, where > > it more properly belongs. > > > > Taxonomies tend to be culturally loaded and can never be > > guaranteed to be complete. Thus there's a real risk of > > "categorical disconnects" leading to missed alerts either > > because of differing interpretations of categories or of > > unforeseen events that don't fit our preconceived > > categories. Maybe someday we'll have a reliable > > taxonomy of the unexpected, but right now a degree of > > deliberate imprecision seems to be the best we can do... and > > I sometimes wonder whether even that is more helpful than it > > is risky. > > > > - Art > > > > > > On Jul 12, 2009, at 7/12/09 11:58 AM, Hannes Tschofenig > > wrote: > > > > > I should provide a bit more feedback about the > > background to my question. > > > > > > If you only set the value in the category field for > > the purpose of human > > > consumption then there is not really an > > interoperability issue. > > > > > > Now, with the work on http://tools.ietf.org/html/draft-rosen-sipping-cap-03 > > > we wanted to define an event package for SIP that > > allows you to "subscribe" > > > to certain type of events: you might indicate > > something like location and > > > the type of events you are interested in. > > > > > > Now, the semantic of the category field suddently > > matters. With the > > > individuals-to-citizen emergency services we tried to > > come up with a > > > description of the emergency services categories, see > > RFC 5031. > > > > > > Ciao > > > Hannes > > > > > _______________________________________________ > This list is for public discussion of the Common Alerting Protocol. This list is NOT part of the formal record of the OASIS Emergency Management TC. Comments for the OASIS record should be posted using the form at http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=emergency > CAP-list mailing list > CAP-list@lists.incident.com > http://lists.incident.com/mailman/listinfo/cap-list > > This list is not for announcements, advertising or advocacy of any particular program or product other than the CAP itself. -- Rex Buddenberg Naval Postgraduate School Code IS/Bu Monterey, Ca 93943 831/656-3576 _______________________________________________ This list is for public discussion of the Common Alerting Protocol. This list is NOT part of the formal record of the OASIS Emergency Management TC. Comments for the OASIS record should be posted using the form at http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=emergency CAP-list mailing list CAP-list@lists.incident.com http://lists.incident.com/mailman/listinfo/cap-list This list is not for announcements, advertising or advocacy of any particular program or product other than the CAP itself.
- Re: [earlywarning] [CAP] Definition of Warning Ca… Tony Rutkowski
- [earlywarning] Definition of Warning Categories Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… Art Botterell
- Re: [earlywarning] [CAP] Definition of Warning Ca… Art Botterell
- Re: [earlywarning] [CAP] Definition of Warning Ca… Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… David Aylward (Comcare)
- Re: [earlywarning] [CAP] Definition of Warning Ca… Art Botterell
- Re: [earlywarning] [CAP] Definition of Warning Ca… Henning Schulzrinne
- Re: [earlywarning] [CAP] Definition of Warning Ca… David Aylward (Comcare)
- Re: [earlywarning] [CAP] Definition of Warning Ca… David Aylward (Comcare)
- Re: [earlywarning] [CAP] Definition of Warning Ca… James M. Polk
- Re: [earlywarning] [CAP] Definition of Warning Ca… David Aylward (Comcare)
- Re: [earlywarning] [CAP] Definition of Warning Ca… DRAGE, Keith (Keith)
- Re: [earlywarning] [CAP] Definition of Warning Ca… Tony Rutkowski
- Re: [earlywarning] [CAP] Definition of Warning Ca… Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… Tony Rutkowski
- Re: [earlywarning] [CAP] Definition of Warning Ca… Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… creed
- Re: [earlywarning] [CAP] Definition of Warning Ca… Art Botterell
- Re: [earlywarning] [CAP] Definition of Warning Ca… Art Botterell
- Re: [earlywarning] [CAP] Definition of Warning Ca… Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… Timothy Grapes
- Re: [earlywarning] [CAP] Definition of Warning Ca… Rex Buddenberg
- Re: [earlywarning] [CAP] Definition of Warning Ca… Rex Buddenberg
- Re: [earlywarning] [CAP] Definition of Warning Ca… Tony Rutkowski
- Re: [earlywarning] [CAP] Definition of Warning Ca… Brian Rosen
- Re: [earlywarning] [CAP] Definition of Warning Ca… Timothy Grapes