OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Fwd: Re: [CAP] CAP Security Using Digital Signatures


Eight.

>X-ASG-Debug-ID: 1236878604-1d6c035f0000-8wEmJ8
>X-Barracuda-URL: http://10.10.11.60:8000/cgi-bin/mark.cgi
>Date: Thu, 12 Mar 2009 10:22:55 -0700
>From: "Art Botterell" <ABott@so.cccounty.us>
>To: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>,
>	<cap-list@lists.incident.com>
>X-ASG-Orig-Subj: Re: [CAP] CAP Security Using Digital Signatures
>X-Barracuda-Connect: UNKNOWN[1.16.10.4]
>X-Barracuda-Start-Time: 1236878605
>X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at co.contra-costa.ca.us
>X-Barracuda-Spam-Score: -1002.00
>X-Barracuda-Spam-Status: No, SCORE=-1002.00 using global scores of
>	TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=1000.0
>Subject: Re: [CAP] CAP Security Using Digital Signatures
>X-BeenThere: cap-list@lists.incident.com
>List-Id: Common Alerting Protocol Public Discussion
>	<cap-list.lists.incident.com>
>List-Unsubscribe: <http://lists.incident.com/mailman/options/cap-list>,
>	<mailto:cap-list-request@lists.incident.com?subject=unsubscribe>
>List-Archive: <http://lists.incident.com/pipermail/cap-list>
>List-Post: <mailto:cap-list@lists.incident.com>
>List-Help: <mailto:cap-list-request@lists.incident.com?subject=help>
>List-Subscribe: <http://lists.incident.com/mailman/listinfo/cap-list>,
>	<mailto:cap-list-request@lists.incident.com?subject=subscribe>
>Sender: cap-list-bounces@lists.incident.com
>X-Nonspam: Statistical 61%
>
>There's definitely a need to deal with interoperable authentication, 
>Hannes, at least here in the U.S. where we have several federal 
>warning systems attempting to integrate with state and local systems 
>built by various providers.
>
>As for your comment re the semantics, not sure what your concerns 
>are there, but we could certainly discuss any specific suggestions 
>you might have, especially now that we have a number of implementers 
>with several years of real-world operation under their belts.
>
>- Art
>
>Art Botterell, Manager
>Community Warning System
>Contra Costa County Office of the Sheriff
>50 Glacier Drive
>Martinez, California 94553
>(925) 313-9603
>fax (925) 646-1120
>
>>>>  "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> 3/12/2009 9:40 AM >>>
>Hi Art,
>
>I believe a more urgent item for work on CAP is to come up with better
>semantic of the elements in the CAP XML spec itself.
>The lack of precise semantic will IMHO make end-to-end usage challenging.
>
>On the digital signature aspects I wonder whether there are (not just
>theoretical) threats that demand it's usage in the envisioned usage
>scenarios.
>
>Ciao
>Hannes
>This list is not for announcements, advertising or advocacy of any 
>particular program or product other than the CAP itself.
>
>_______________________________________________
>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 Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]