Changes between Version 139 and Version 140 of BluePrint/Messaging


Ignore:
Timestamp:
11/19/11 23:54:19 (10 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Messaging

    v139 v140  
    194194''Originating CAP alerts is one need, receiving them and using them to actuate alerting systems, be they SMS drivers or sirens or whatever is another.  Another is a message broker that can interoperate with the commercial boxes.  Authentication systems are also a factor, especially where cross-jurisdictional reciprocity is required''
    195195
     196''Ideally the CAP XML should be signed end-to-end, especially in a federated system where there's more than one authority running servers/aggregators.  Our current implementations sign the alerts at the originating server, so they're at least traceable to the source server but not necessarily the individual operator.  Current servers check integrity when they get a message from another server, but there isn't a regional PKI.''
     197
    196198 * http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2.html
    197199  * Use an XSLT