NAADS LMD User Guide - National Alert Aggregation
Contents
1. 5 AGON IMI ae HET AVRUDEN I ERES ONKEL EMT TOR TUNER Sateancesaaacnebumascay apt 5 TERMS AND CONDITIONS OF USE sir r du h Ua ud 7 NAAD System e T 8 POU WAS ONADIE MN TTE Omm 8 NAAD System MOTO ONT PTT E 8 Information for LIDS 9 General RuUl si CONCC DIS er nse inde nd ne ken nd n n he po d kone 9 NEART RR E 10 Trusted Feed EC ANGIS T TT 10 UU DIGA OS RIO CIS aga pr malet inta P ee e AEEA EEEREN Tan Rr AE 10 Rules for atac IER ITE TTE 11 Display of special characters for LM DS aaa nene nan eee eee eee ee nete eee nnnm 11 Rules Governing NAAD System Testing amp Test Messages aaa ann anen eee e eee eee eee eee 12 ebllons TO TOON T S wee 12 ROOT eG OGUR Em EE 12 NI RIC e e ne T E m 12 ilo Roc X 7 M Y A00 14 NAAD System Feed Specifications eeee eee ESSE eee Er PER S SEE SEE E tet enne SE SEE eee annu sean ansa asas nennt 14 About Ei BS C EE nz OS NERONE NR RR as 14 Satellite and TCP Streaming Feed General Information ana aaaa na anaaaaanaaaaneeaa eee ene nenen ee eee eee eee eee 14 1 US MEU FECU e e deemed 15 Summary and additional notes for the Satellite Feed una nana aa aaaaaana nana anen eee eee ee nete e r2. Connect the LNB to the RF 1 Connect the AC cord Configuration Press MENU Press the arrow right button to select PRESET Press SELECT button Press SELECT Pelmorex Communications Inc NAAD System LMD User Guide Page 24 of 52 Press SELECT and dial the default frequency 04 0600 Press SELECT Press the arrow right to change the NET ID Press SELECT Dial the value 00002 Press SELECT Press MENU Press the arrow right button to select CONTINUE Press SELECT Pelmorex Communications Inc NAAD System LMD User Guide Page 25 of 52 Press MENU Dial the virtual channel 206 Press SELECT The signal led should be now on Pelmorex Communications Inc NAAD System LMD User Guide Page 26 of 52 EXAMPLE B CONFIGURING CISCO D 9850 RECEIVER SECONDARY FEED Connect the LNB to the RF 1 Connect the AC cord PRESS MENU USE THE ARROW RIGHT TO SELECT PRESET PRESS SELECT PRESS THE ARROW DOWN Pelmorex Communications Inc NAAD System LMD User Guide Page 27 of 52 PRESS SELECT USE THE ARROW RIGHT AND SELECT CONTINUE PRESS SELECT PRESS SELECT PRESS MENU USE THE ARROW RIGHT TO SELECT CONTINUE PRESS SELECT PRESS MENU DIAL 550 SELECT SIGNAL LIGHT SHOULD BE ON Pelmorex Communications Inc NAAD System LMD User Guide Page 28 of 52 ADDENDUM B Ku Band e Ku Band antenna 0 98m to 2 4m on Anik F2 The size of the antenna depe
3. i COMMON ALERTING PROTOCOL VALUES FOR URGENCY Immediate Responsive action SHOULD be taken immediately Expected Responsive action SHOULD be taken soon within next hour Future Responsive action SHOULD be taken in the near future Past Responsive action is no longer required Unknown Urgency not known COMMON ALERTING PROTOCOL VALUES FOR SEVERITY Extreme Extraordinary threat to life Severe Significant threat to life Moderate Possible threat to life Minor Minimal to no known threat to life Unknown Severity unknown ii COMMON ALERTING PROTOCOL VALUES FOR CERTAINTY Observed Determined to have occurred or to be ongoing Likely Likely p gt 50 Possible Possible but not likely p lt 50 Unlikely Not expected to occur p O Unknown Certainty unknown Pelmorex Communications Inc NAAD System LMD User Guide Page 40 of 52 Appendix 4 Digital Signatures For security reasons and being in line with CAP V1 2 Alert Messages will contain 1 or 2 signatures 1 First one is a digital signature produced by the Issuer AGA allowing verification to Alerts as being genuine to that specific Issuer and not tempered with This signature is optional and is at the discretion of the Issuer s organization So it may or may not be present 2 Second is the NAAD System s digital signature in the alert message in addition to the Issuer s signature It will always be present in aler
4. The date portion YYYY MM DD of the sent date time from the references element found in the heartbeat e SENT The sent date time from the references element found in the heartbeat Including time and time zone information e IDENTIFIER The identifier found inside the references element in the heartbeat Additional important notes e Some characters are substituted for other ones this substitution must be applied to create the final valid URL o The minus sign or dash is replaced by underscore character o The plus sign is replaced by P o The colon character is replaced by underscore character o This replacement must be done only on the SENT and IDENTIFIER part of the URL Examples Information from the heartbeat references NAADS Heartbeat NAADS PelmorexCommunicationsInc DD9216B4 2A6C 8514 4332 85B7359FE2E0 2011 06 22T04 59 00 00 00 lt references gt Resulting URL http capcp1 naad adna pelmorex com 2011 06 22 2011 06 22TO05 06 49p00 O00I5A89A6FD ODS89 1C6C 46D5 B535F61CO068F x ml and any of the 2 URLs will work http capcp2 naad adna pelmorex com 2011 06 22 2011 06 22TO05 06 49p00 O0I5BA89A6FD ODS89 1C6C 46D5 B535F61CO068F x EN COUTE Pelmorex Communications Inc NAAD System LMD User Guide Page 31 of 52 Appendix 2 Sample Alert Messages Samples of Alert Messages as if they were received from C band Ku band or TCP stream or retrieved from missed alerts r
5. filter the entries For example language en CA category will allow the RSS Reader to display only entries for the en CA language locale Pelmorex official URLs to access the GeoRSS feed are e http rssi naad adna pelmorex com Oakville e http rss2 naad adna pelmorex com Montreal p It is the responsibility of the LMD to reconnect to the E second site if the first site is down and vice versa Under normal conditions both sites should be active The GeoRSS feed provides list of alerts with some basic information reference is made to the real alert which is in the same CAP CP format and identical to the version received via satellite or TCP streams not the geo codes as they are in CAP CP so it can t replace 1 The GeoRSS only contains the geometry information and completely the geography defined in the real alert and should not be used as a base for public display by f The GeoRSS is only a subset of the actual Alert Message LMDs Summary and additional notes for the GeoRSS Feed e The alerts from the last 48 hours are formatted into a RSS feed in a simple GeoRSS Atom format e The URLs for this feed are o http rssi naad adna pelmorex com Oakville o http rss2 naad adna pelmorex com Montreal e Each Alert Message is presented as an entry in the feed e For each entry Pelmorex Communications Inc NAAD System LMD User Guide Page 19 of 52 o AURL to the Alert Message XML file is present o URLs to
6. z parameter lt note gt Minor Update en CA Sample test content noter lt note gt Minor Update en CA Test EN Comment fr CA Test FR Comments note Pelmorex Communications Inc NAAD System LMD User Guide Page 36 of 52 Appendix 3 Broadcast Intrusive Alerts The concept of Broadcast Intrusive Immediate alerts is supported in NAADS The Broadcast Intrusive criterion is based on the SOREM s list of CAP CP event codes and their respective CAP severity urgency and certainty values list attached as follows If the Broadcast Intrusive criterion is met the sender will be notified on the interface while still creating the alert Once the alert is sent a Broadcast Intrusive flag value will be set as Yes or NO respectively in the alert From this release forward every NAADS alert will now contain this parameter in the alert s XML form Example lt xml version 1 0 encoding UTF 8 gt alert xmins urn oasis names tc emergency cap 1 2 gt lt identifier gt BO24E3AB D421 813C BE9C FD6591FE8082 lt identifier gt lt sender gt SDA PublicAlerting PelmorexCommunicationInc lt sender gt lt sent gt 2011 10 13T18 45 09 04 00 lt sent gt lt status gt Actual lt status gt lt msgType gt Alert lt msgType gt lt scope gt Public lt scope gt lt code gt profile CAP CP 0 3 lt code gt lt info gt lt language gt en CA lt language gt category Safety category category Infra category event Dam
7. 09 xmldsigZsha1 gt lt DigestValue gt 5vp71PoJwex9R3VQhDsdiInVv 7AA lt DigestValue gt lt Reference gt Pelmorex Communications Inc NAAD System LMD User Guide Page 51 of 52 SignedInfo SignatureValue ENNOVHCPhuX9PfXxBTeSZtzxVLf9OWbiknBLtvNsXThsGxKdCaB6 B7fXnITSNJxX fOMzohQ1FwOAIiEDFAUIOZsqeb530JOxr0800uYmErJ9pwJX53ANyK5q6XJALUeO4 QonCIiqBkgOP 11krsLJSDCcIESNSBCETmj6fhZSnOEY tWZEv59KOvfMiqRT1OGf4 W F aZ6674yOkIWSaAK3BGXxUS8aSwnEVAGCN7rjYv61y9kqB7GiWZkrdx8pF6YQw m2StXM1ph4J WO6ZXvkF OIRQQsZLaiYFioPm1a vaJy5LHebzAkpkxrrSD9czGN9 K9FbqNF5C2BkPGtpeEFXLg lt SignatureValue gt KeyInfo lt X509Data gt X509Certificate MIIE1DCCA7ygAWIBAgIETBpRgDANBgkqhkiG9OwOBAQUFADCBsT ELMAkGA1UEBhMC VVMxFjAUBgNVBAoTDUVudHJic3QsIEluYyAxOTA3BgNVBASsTMHd3dy5IlbnRydXNO Lm5idC9ycGEgaXMgaW5jb3Jwb3JhdGVkIGJ5IHJIZmVyZW5jZTE MBOGA1UECXMW KGMpIDIwMDkgRW50cnVzdCwgSW5jLjEuMCwGA1UEAXMIRW 50cnVzdCBDZXJOaW Zp Y2FOaW9uIEFidGhvcmlOeSAtIEwxQzAeFwOxMTA1MDKkxNTIxMzVaFwOxNTA3MTA Ww MzMxMzZaMIGEMQswCQYDVQQGEwJDQTEPMAOGA1UECBMGUXVIYmVjMREwDwYD VQQH EwhHYXRpbmVhdTEbMBkGA1UEChMSRW52aXJvbmilbnQgQ2FuYWRhMRAwHAYD VQQL 4e2 3iVoJpS 6PNwIliAxxImrnhdZ1iEZ77PQhpfyrchhYSDAVJs2vjA X509Certificat e lt X509Data gt lt KeyInfo gt lt Signature gt lt alert gt Pelmorex Communications Inc User Notes Pelmorex Communications Inc
8. 549832 99 209311 51 548486 99 207949 51 543643 99 210667 51 545245 99 215015 51 551858 99 217815 51 551197 99 215461 51 552994 99 216119 lt polygon gt lt geocode gt lt valueName gt profile CAP CP Location 0 3 lt valueName gt lt value gt 4619068 lt value gt lt geocode gt lt area gt lt info gt Signature Id NAADS Signature xmIins http www w3 org 2000 09 xmidsig gt lt SignedInfo gt lt CanonicalizationMethod Algorithm http www w3 org TR 2001 REC xml c14n 20010315 lt SignatureMethod Algorithm http www w3 org 2000 09 xmlidsig rsa sha1 gt lt Reference URI gt lt Transforms gt Transform Algorithm http www w3 org 2000 09 xmidsig enveloped signature gt lt Transforms gt lt DigestMethod Algorithm http www w3 org 2000 09 xmlidsig sha1 gt DigestValue ahWoGkAEkIeRmdY2DuuduBzhvQg lt DigestValue gt Reference SignedInfo SignatureValue LIQwBSeKRzLW8vdvOa8ri6gO0aiUeFgDVMngubvBvaDXGuaSGz VR OH LCuSvpOKOzqG SNXV7tJkObP1GXI P5v3bbrFksxurpCJp892H2z2V 4f1jLTiwZw6abC430sOzZRNvVUSXE9segE3rkCLQrQueL by Bxmnz OIlZ84knyh555hL ucdGvOYnMiMi rKYfqYt5pruOgQ7TAG6c3KIXBJdtOEnahqqH9srZjmVjI8de6 07B5BBCokUcNtMSgumoio2WG6UOO0SXPR271h5PKDdMoNYpO3 MLznQzschUbkbPCtS4XBWK4QxEGnJUG edn7qCdyhBzQTgAIJBYMIDp9qQ SignatureValue KeyInfo lt X509Data gt X509Certificate MIIFazCCBFOgAwIBAgIQBO1UgIlUDPqeqqRrvrn 2JTANBgkqhkiG9wOBAQUFADCBS3TEL MAkGA1UEBhMCVVMXxF
9. Met category lt event gt high heat and humidity event responseType Monitor responseType urgency Future urgency severity Moderate severity certainty Likely certainty gt audience General Public lt audience gt eventCode valueName profile CAP CP Event 0 4 valueName value heatWave value eventCode eventCode lt valueName gt SAME lt valueName gt lt value gt DMO lt value gt lt eventCode gt effective 2012 07 06T08 46 00 00 00 lt effective gt expires 2012 07 07T00 46 00 00 00 expires senderName Environment Canada senderName headline high heat and humidity warning headline description instruction Please monitor for further updates to this alert instruction web http www weatheroffice gc ca warnings warnings e html web contact parameter Pelmorex Communications Inc NAAD System LMD User Guide Page 50 of 52 lt valueName gt layer EC MSC SMC 1 0 Alert_Type lt valueName gt value warning value parameter parameter lt valueName gt layer EC MSC SMC 1 0 Broadcast_Intrusive lt valueName gt lt value gt no lt value gt lt parameter gt lt parameter gt lt valueName gt layer EC MSC SMC 1 0 Parent_URI lt valueName gt lt value gt msc alert environment hazard mfile 1 0 ascii decoded consolidated xml 2 0 20120706084600000 ww 10 70 cwul hhw ww 10 7
10. NAAD System and only on the communications channel where the transmission error was detected This does not necessarily mean that the data received by the LMD was invalid corrupted but the LMD clients should always validate the data and be capable of handling duplicate alerts For internet feeds there are 2 geographical locations where the feed is available Oakville and Montreal The CAP CP XML form of the Alert Message will contain 1 or 2 XML signatures from which a LMD can verify that the alert is from a genuine source and or from the NAAD System Alerts will always have a NAAD System Digital Signature and may have an Issuer AGA Signature When both are present the NAAD System signature encompasses the AGA signature without invalidating the Issuer Signature Satellite and TCP Streaming feeds will contain the original Alert Message that was sent and any attachments will be in base 64 AGAs may include Links to attachments in which case LMDs will need to retrieve the attachment from the location identified by the Issuer To summarize AGA may include attachments in two forms including both simultaneously in the same message e Attachment s may be embedded in the message embedded attachment s are in base64 and require extraction base64 decoding to retrieve the original attachment e Links to attachment s hosted on AGA external systems in which case LMDs will need to retrieve it from the location identified by the AGA link NAAD Heartb
11. The NAAD System also provides a User Resource Centre This is in the form of a website where users including LMDs can view general NAAD System related information including a Pelmorex Communications Inc list of vendors and distributors of equipment for LMDs Users can also register on the website for free and receive further information and updates on the NAAD System For further information please visit https alerts pelmorex com English https alerts pelmorex com lang fr French Or contact our support team at Support PublicAlerting Pelmorex com Pelmorex Communications Inc NAAD System LMD User Guide Page 14 of 52 Chapter 2 NAAD System Feed Specifications This chapter includes Satellite and TCP Streaming Feed General Information Satellite Feed Summary and additional notes for the Satellite Feed Internet TCP Streaming Feed Summary and additional notes for the TCP Streaming Feed Internet GeoRSS Feed based on Atom and GeoRSS Simple Summary and additional notes for the GeoRSS Feed Troubleshooting Internet TCP Streaming Feed About NAAD System Feeds The NAAD System provides 3 different communication channels in order to receive Alert Messages e CBand Satellite e Ku Band Satellite e Internet TCP Streaming Feed A 4 auxiliary communication channel Internet GeoRSS Feed based on Atom and GeoRSS Simple is also available but should not be used to feed a 24 7 automated system This c
12. WQtZzMtY3JsLnZicmizaWduLmNvbS9JbmRDMURpZ2l10OYWxJRC1HMy5jcmwwDQYJKoZIhvcNAQEFBQAD ggGEBAD305bsnBvkF5zkd1A nEf3yXOJPhjWTzswwkliAFSwo1FiDcRpBzd98 SjBFs7hG2VuP 5qxudLxCP2 vC6x8HnQAXjmSPx1d95V8UUKkOSLaABSHNri85AalpQRAR7t9Vr2hrYOFOT7ftOIvclaRuOBAzUXA4uHYFY yuI 9knyJtomAbA4HyVSeKpXA4fg87bFK3h94z9p4 13 44nSWia1MKrpQarjQj9TCxZgHN1JEMQtpWNEWeRS p g4rymNHvq9ZvYOEQ6LXWgVuqzZUB irFintQxIGH4gzIso4mOZVayTQ8cZDpOCFQh7WUIroZyruOlvD8 erZ CijYVjeXtotwESCgY lt X509Certificate gt lt X509Data gt lt KeyInfo gt Object xmlnsz lt SignatureProperties gt lt SignatureProperty Id NAADS DSS1 Target http dss1 staging naad adna pelmorex com gt lt xc value xmlns xcz http docs oasis open org emergency cap v1 2 CAP v1 2 xsd lt SignatureProperty gt lt SignatureProperty Id NAADS DSS2 Target http dss2 staging naad adna pelmorex com gt xc value xmlns xcz http docs oasis open org emergency cap v1 2 CAP v1 2 xsd lt SignatureProperty gt lt SignatureProperties gt lt Object gt lt Signature gt lt alert gt 3 DSS Verification Request SOAP Request on https To verify a signed alert a SOAP request on https must be made to the DSS server as identified in the Signature Property Target of the signed message The method that must be called is DSSVerifySignedNaadsAlert The following request must be passed as string parameter The request below follows the OASIS DSS specification The request ID is used to iden
13. been sent completely e Attachments will be embedded in the CAP CP XML as Base64 encoded data in the resource tag e Heartbeats are sent at specific intervals 1 minute to indicate that the system is up and running see Appendix 1 for details on Heartbeats 2 Internet TCP Streaming Feed This feed is accessible through the Internet In order to receive this feed a TCP IP socket application client must be used by the LMD and it must be able to connect to the following domains Pelmorex Communications Inc NAAD System LMD User Guide Page 17 of 52 e streamingl naad adna pelmorex com Oakville e Streaming2 naad adna pelmorex com Montreal e TCP port is 8080 for both sites It is recommended for redundancy purposes to connect to both TCP streaming feeds or to one of the satellite feeds C band or Ku band at the same time and discard any duplicate alerts since under normal operation both feeds will be active and sending alerts almost at the same time If one feed is down the application should try to reconnect at a pre set interval while continuing to receive the data from the active feed In order to detect connection issues and missing alerts the NAAD Heartbeat CAP CP data is sent every minute If the application does not receive any NAAD Heartbeats after an expected delay 2 minutes for example then it is recommended that the application should start a reconnection procedure The NAAD Heartbeat CAP CP data contain
14. for verification 2 Server answers with aVerify response OK Not OK DSS Server Pelmorex Communications Inc NAAD System LMD User Guide Page 43 of 52 Sample Messages Digital Signature This section shows sample CAP CP Alert Messages Alert Message with no digital signature Alert Message with digital signature DSS Verification Request DSS Verification Response DSS Verification Response Failed 1 Alert Message with no digital signature lt xml versionz 1 0 encoding UTF 8 gt alert xmIns urn oasis names tc emergency cap 1 2 gt lt identifier gt A2433D85 DB53 263A 998A 085EA5386C9A lt identifier gt sender NAADS TestingONAADSQPelmorexCommunications Testing lt sender gt sent 2011 06 22T06 08 09 00 00 sent status Actual status lt msgType gt Alert lt msgType gt lt scope gt Public lt scope gt code profile CAP CP 0 3 lt code gt info language en CA language category Met category event Tornado event responseType Nonec responseType lt urgency gt Immediate lt urgency gt lt severity gt Extreme lt severity gt certainty gt Observed lt certainty gt lt eventCode gt valueName profile CAP CP Event 0 3 lt valueName gt svalueztornados values lt eventCode gt lt expires gt 2011 06 23T13 00 00 00 00 lt expires gt lt senderName gt Pelmorex Communications Testing lt senderName gt lt head
15. the NAADS KU band signal the LMD must purchase a HN7700S iMpACT terminal from TELESAT TELESAT will define and commission the terminal and will Ship the unit to the LMD Beside the iMpACT terminal the LMD site must be equipped with a satellite antenna dish pointed to the Anik F2 satellite Telesat can provide installation services for LMDs if required Pelmorex does not provide or pay for equipment or installation services For more technical details please see Addendum B Pelmorex Communications Inc NAAD System LMD User Guide Page 22 of 52 Anik Fo AX I LMD site Figure 2 Satellite Dissemination Ku Band ADDENDUM A C Band e A minimum 3 meter C Band dish pointed to Anik F1R is required at the receiving site e Any DVB S or DVB S2 receiver with IP output is compatible with the service PELMOREX is using a Cisco D 9850 receiver IRD with IP output e Primary feed transponder 9B 4 060 MHz vertical polarization virtual channel 206 e Secondary feed transponder 10B 4 100 MHz vertical polarization virtual channel 550 e Primary feed Network ID 2 e Secondary feed Network ID 1 e Main frequency 1050 00 MHz e FCC Rate 7 8 e Symbol Rate 28 3465 e Bit rate 500 Kbits sec 500000 could be increased in the future if needed Pelmorex Communications Inc NAAD System LMD User Guide Page 23 of 52 EXAMPLE A CONFIGURING CISCO D 9850 RECEIVER PRIMARY FEED F ti Tier V L
16. well such as limits on message sizes attachment sizes and types mandatory expiry language codes etc For details refer to the technical information section at https alerts pelmorex com The NAAD System streams Alert Messages in CAP format as they are received The NAAD System may repeat transmission of an Alert Message only if a transmission error has been detected on a specific stream transmission is only repeated on the data stream containing the error The NAAD System does not filter interpret or change the content of the Alert Messages a Digital Signature is added by Pelmorex to each Alert Message to validate its authenticity A specific Alert Message received on a system stream C band Ku Band or TCP feeds or accessed from the short term retrieval repository is identical byte for byte regardless of the medium from which it was obtained Pelmorex Communications Inc NAAD System LMD User Guide Page 10 of 52 A NAAD System Heartbeat message is sent regularly every 60 seconds to provide LMDs with the capability to monitor that the feed is live as well as to detect the loss of an Alert Message The Heartbeat message Contains a list of the latest 10 transmitted Alert Messages Js not digitally signed Is compliant with CAP CP standards A GeoRSS link is provided by the NAAD System to allow users to manually see in their native i e in XML form the Alert Messages issued in the last 48 hours The
17. 0 cwul 20120706084 6 hhw public 2012 83526 non bi en upper preliminary fr not present value parameter parameter lt valueName gt layer EC MSC SMC 1 0 CAP_count lt valueName gt lt value gt 34299 lt value gt lt parameter gt area areaDesc Metro Montr al Laval lt areaDesc gt lt polygon gt 45 3667 73 55 45 3333 73 7833 45 3487 73 8063 45 3488 73 8065 45 3889 73 8366 45 405 73 9709 45 481 74 0046 45 5325 73 9026 45 534 73 8997 45 6168 73 8331 45 6654 73 7524 45 6656 73 7522 45 6662 73 7511 45 7 73 632 45 7164 73 4688 45 7255 73 4378 45 7207 73 427 45 5 73 3667 45 4999 73 3667 45 4333 73 4 45 4332 73 4003 45 369 73 5447 45 3667 73 55 lt polygon gt lt geocode gt lt valueName gt layer EC MSC SMC 1 0 CLC lt valueName gt lt value gt 032400 lt value gt lt geocode gt lt geocode gt valueName profile CAP CP Location 0 3 lt valueName gt value 2458007 value geocode info Signature xmlns http www w3 org 2000 09 xmldsig Z Id Environment Canada SignedInfo CanonicalizationMethod Algorithm http www w3 0org 2001 10 xml exc c14n gt lt SignatureMethod Algorithm http www w3 org 2000 09 xmldsigZrsa sha1 gt lt Reference URI gt Transforms Transform Algorithm http www w3 org 2000 09 xmldsigZ enveloped signature gt lt Transforms gt lt DigestMethod Algorithm http www w3 org 2000
18. 509Certificate X509Data KeyInfo Object xmlnsz lt SignatureProperties gt lt SignatureProperty Id NAADS DSS1 Target http dssi1 staging naad adna pelmorex com gt xc value xmlns xcz http docs oasis open org emergency cap v1 2 CAP v1 2 xsd lt SignatureProperty gt lt SignatureProperty Id NAADS DSS2 Target http dss2 staging naad adna pelmorex com gt xc value xmlns xcz http docs oasis open org emergency cap v1 2 CAP v1 2 xsd lt SignatureProperty gt lt SignatureProperties gt lt Object gt lt Signature gt lt alert gt lt Document gt lt InputDocuments gt lt OptionalInputs gt SignaturePlacement WhichDocument 0822D9A5 B7B0 OEFB 47F6 A47F2EF12347 CreateEnvelopedSignature true gt lt OptionalInputs gt lt SignatureObject gt SignaturePtr WhichDocument 0822D9A5 B7B0 OEFB 47F6 A47F2EF12347 XPathz cs Signature Id amp quot NAADS Signature amp quot gt lt SignaturePtr gt lt SignatureObject gt lt VerifyRequest gt 4 DSS Verification Response Verification Success SOAP response on https NAADS DSS will return the following response over SOAP as string as a return value The ResultMajor field will be success if the message verified successfully and will be ResponderError if the message did not verify successfully VerifyResponse RequestID 0822D9A5 B7B0 OEFB 47F6 A47F2EF12347 Profile xmins ds http www w3 org 2000 0
19. 9 xmidsig xmins http www docs oasis open org dss oasis dss 1 0 core schema cd 02 xsd gt Result lt ResultMajor gt urn oasis names tc dss 1 0 resultmajor Success lt ResultMajor gt lt ResultMinor gt lt ResultMessage gt lt Result gt lt VerifyResponse gt 5 DSS Verification Response Failed VerifyResponse RequestID 0822D9A5 B7B0 OEFB 47F6 A47F2EF12347 Profile xmins ds http www w3 org 2000 09 xmidsig xmins http www docs oasis open org dss oasis dss 1 0 core schema cd 02 xsd gt lt Result gt lt ResultMajor gt urn oasis names tc dss 1 0 resultmajor ResponderError lt ResultMajor gt lt ResultMinor gt urn oasis names tc dss 1 0 resultminor GeneralError lt ResultMinor gt lt ResultMessage gt lt Result gt lt VerifyResponse gt NAADS DSS will return a value in ResultMessage apart from error shown in sample above if there is some error in the request or XML as follows Pelmorex Communications Inc NAAD System LMD User Guide Page 48 of 52 1 Wrong DSS request format The XML document is incorrect 2 Wrong alert format in Verify Request The XML document provided is not a signed alert 3 The alert received doesn t have a NAADS Signature element The alert wasn t signed by NAADS If the request alert is correct but the alert cannot be verified i e digital signature did not verify error will be returned in ResultMajor and Minor as in sample above The ResultMessag
20. DSS protocol to either DSS servers as NAADS has a redundant infrastructure indicated in the NAADS Digital signature as part of SignatureProperty ID element They can also verify locally without making a request to DSS if they have their own cryptographic verification tools using the information in KeyInfo part of the digital signature Pelmorex Communications Inc NAAD System LMD User Guide Page 42 of 52 Alert Creation On user inerass Trusted Feed Unique Signatur ID to ieencityexclude Signature A J Signed CAP with T Bey clude 1 eignature es T Request i Inser NAADS HOME KAADS Central Processing B Insert NAADS 6 Validation resli signatura Issuer s Infrastructure g flori with HAAS Sagnenure and unique ID io identihynexelude aigngture HNAADSS Satellite Fead Camponent 10 1 1 Re Jost ip validate l n nians signature 1 3 Request bo validate l i t Fegussi bo saldate anat i I h 1 j Sa i L l R amp p FEE 12 Validation resuk 1 4 Validation resuk Validating a Signed Message User has received a signed document Originator User sends Verify request signed document
21. NAAD System also provides A short term repository up to the last 48 hrs where alerts missed by a LMD can be retrieved A user archive site where all Alert Messages are kept LMDSs should listen to more than one feed for redundancy purposes these can be C Band Ku Band or TCP Streaming or a combination of these feeds The NAAD System will support only the following 3rd language coding over and above the two official languages Third Language E MEN Creede Inuktitut 5 MB Alert Size In June 2010 when the NAAD System first launched the maximum size of an alert was limited to 1 MB This limit has been changed amp increased to 5 MB in NAADS Release R4 0 The system Supports the size of 5 MB per alert Trusted Feed EC Alerts The NAAD System also supports a Trusted Feed from Environment Canada EC and EC alerts are available on the NAAD System feeds outputs in addition to alerts issued through the NAAD System Issuer Interface An LMD can identify EC alerts by the lt source gt tag in the CAP XML For example EC alerts will contain the following lt source gt Environment Canada Environnement Canada Toronto CWTO lt source gt See Appendix 5 for a Sample EC Alert Multiple Info Blocks Alerts issued by EC through their trusted feed may contain multiple info blocks Alerts with Multiple info blocks contain 2 different kinds of description severity certainty and urgency for the same Event type In other wor
22. National Alert Aggregation amp Dissemination System Last Mile Distributor User Guide Release 7 0a 2655 Bristol Circle Oakville Ontario L6H 7W1 T 905 829 1159 F 905 829 5800 Pelmorex Communications Inc NAAD System LMD User Guide Page 2 of 52 Pelmorex Communications Inc 2655 Bristol Circle Oakville Ontario L6H 7W1 T 905 829 1159 F 905 829 5800 Copyright 2015 Pelmorex Communications Inc All rights reserved This document was last updated on 03 30 2015 All other product names and trade names used herein are trademarks of their respective owners Information in this document is subject to change without notice No part of this document may be reproduced or transmitted in any form or by any means electronic or mechanical including photocopying or recording for any purpose without the express written permission of Pelmorex Communications Inc Pelmorex Communications Inc NAAD System LMD User Guide Page 3 of 52 Table of Contents i e 5 eund N 5 NAAD Service Desk aaa eee een epe eee e e eee dine pike enet ee eee e eee bene teke nete eee ee piken e eee eee epike peten eee ssa sss snas assess 5 Who Should Use this GUId Ona maca cosstosis erecinste nse it cover b shese s ndete n dores esi idene e siiohes ccs usar Ra rei se gg abcr s Resa c Ka is 5 Symbols Used in this Guide
23. Overflow event lt urgency gt Immediate lt urgency gt severity Extreme severity gt certainty Observed certainty eventCode valueName profile CAP CP Event 0 3 valueName value damOverflow lt value gt eventCode lt expires gt 2011 10 14T09 43 00 04 00 lt expires gt lt senderName gt Pelmorex lt senderName gt headline damOverflow lt headline gt description damOverflow description instruction en CA instruction area areaDesc Test Area areaDesc lt polygon gt 48 250074 88 836514 48 304678 When the alert meets the Broadcast Immediately criteria following will be the flag value parameter valueName layer SOREM 1 0 Broadcast Immediately valueName parameter In all other cases Pelmorex Communications Inc lt parameter gt valueName layer SOREM 1 0 Broadcast Immediately valueName parameter Pelmorex Communications Inc NAAD System LMD User Guide Page 38 of 52 Broadcast Intrusive SOREM List Tier I Event Code CAP Code CAP Code CAP Code Additional for for for Comments Urgenc Severit Certainty Extreme Civil civilEmerg Immediate Severe or Observed Definition is required Extreme but intention is to cover events such as large riots muy ee e o000 Activit Extreme ae eee mee ur TJ Animal Extreme Fire wildFire Immediate Severe or Likely or Definition required and Extreme O
24. Pelmorex is also disseminating alerts through the internet and KU band Satellite 1 A simple approach option A is to have one dish and one receiver IRD The downside of this approach is that requires manual change between virtual channels if alerts feed fails for any reason 2 If the LMD wants to have a transparent operation when the feeds are being switched then the receiving site should be equipped with two receivers IRD and data routers option B Pelmorex Communications Inc NAAD System LMD User Guide Page 21 of 52 3 Instead of using the data router software application may accept two data feeds from two receivers option C S LMD Option A IRD Ch 550 S X IRD Ch 550 LMD Option C LMD Option B Figure 1 Satellite Dissemination C Band Each receiver IRD must be tuned to assigned virtual channel Please see addendum A for the technical specifications For redundancy TCP or Ku feeds may also be used as an alternative instead of monitoring the 2 C Band channels 2 Satellite Dissemination Ku Band Due to rain and snow fades the Ku Band dissemination system has been designed with two simultaneous up down links at all times active active up down link The receiving terminal is configured to receive either primary or secondary feed or both feeds simultaneously The NAAD System Ku Band dissemination is provided by iMpACT satellite telecommunication service In order to receive
25. Type gt Alert lt msgType gt Pelmorex Communications Inc NAAD System LMD User Guide Page 44 of 52 scope Public scope code profile CAP CP 0 3 code info language en CA language category Met category event Tornado event lt responseType gt None lt responseType gt lt urgency gt Immediate lt urgency gt lt severity gt Extreme lt severity gt certainty gt Observed lt certainty gt lt eventCode gt valueName profile CAP CP Event 0 3 lt valueName gt lt value gt tornado lt value gt lt eventCode gt lt expires gt 2011 06 23T13 00 00 00 00 lt expires gt lt senderName gt Pelmorex Communications Testing lt senderName gt lt headline gt Sample alert with Digital signature lt headline gt lt area gt lt areaDesc gt Test NAADS signature lt areaDesc gt lt polygon gt 51 552994 99 216119 51 564488 99 219607 51 575448 99 219861 51 576326 99 221583 51 559342 99 225395 51 552488 99 236193 51 538291 99 244281 51 529917 99 245778 51 528724 99 256742 51 523192 99 261972 51 516722 99 263953 51 510717 99 263414 51 507501 99 265974 51 504579 99 265929 51 502849 99 263657 51 498802 99 26395 51 497321 99 266635 51 49194 99 264386 51 490075 99 266247 51 479374 99 262484 51 473999 99 265706 51 474256 99 204523 51 503636 99 204828 51 503875 99 193096 51 532352 99 192697 51 535124 99 19768 51 537876 99 19726 51 553234 99 202605 51
26. attachment files are present if they exist in the Alert Message Note most Geo RSS Readers can only display O or 1 attachment s e Filter category tags are present to allow the Geo RSS Reader to filter entries in the feed Example Internet Explorer is a reader that can filter entries using the category field 4 Troubleshooting Internet TCP Streaming Feed Web Interface Most recent up to date Connection Java Recommendations Most recent version of a Web browser Feeds Connection Average users home internet Dial up internet connection Recommendations speed is not recommended e Standard 1 5 Mbps downstream speed A normal DSL internet with 6mb download minimum The ability to reconnect within 1 minute if 384 kbps upstream speed Socket feed connection timeout disconnected times Missed alerts can be e 2ms when connection is retrieved using heartbeats established 1 005 ms when host is alive but not listened to on the specified socket port 21 000 ms when host is down If internet connections are dropped by either the LMD or Pelmorex the last 10 alerts are available through the NAAD heartbeat CAP CP data This list is used to detect any missed alert LMD s application could retrieve it from the HTTP short term repository Alert Messages are kept for 48 hours in the HTTP short term repository for retrieval purposes by automated systems Alerts can be received as soon as the application has connected it waits to receive a
27. bserved maybe customized depending on regional Significance Extreme Fire urbanFire Immediate Severe or Observed Definition required and Extreme maybe customized depending on regional Significance m rowers mee me eee 00 Extreme Observed er mses pr oi NR Extreme Extreme Observed Flood damOverflow Immediate Severeor Likely or Extreme Observed Extreme Observed Extreme Observed Can be solar flare dl NN eee eee Extreme Observed Lil nc mmm eme mm 0 Extreme Extreme Observed memes que mee mr umm Extreme Observed memes ma mee E 0 Extreme Observed memes meer mem Em umm Extreme Observed Extreme Observed E M NN me a NNNM Materials Extreme Pelmorex Communications Inc NAAD System LMD User Guide Page 39 of 52 Tier I Event Code CAP Code AP Code CAP Code Additional Urgenc Severit Certainty ES NN e po E RN Materials Extreme Materials Extreme Materials Extreme Observed Materials Extreme Extreme Rm me mem mr TJ Person Extreme Extreme and call to action per e mem ee ee 7 Extreme fem e pe M a NN Extreme Extreme Observed Emergency Public Alert is defined in the NAAD Authorized User Agreements as an Alert Message issued by an Authorized Government Agency or an Authorized User in respect of an imminent or unexpected threat to life caused by severe weather disturbances natural disasters or other emergencies that meets the criteria for immediate distribution in the Standards
28. c210b3J5L1JQQSBJb mNvcnAuIGJ5SIFJIZiA4sTEIBQIb5MVEQoYyk5ODEeMBWwWGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkM TMwMQYDVQQLEypEaWdpdGFsIEIEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNIcnZpY2UxGzAZBgNVB AMUEKk5BQURTIERTUyBQZW xtb3JIeDEIiMCAGCSqGSIb3DQEJARYTbmVOb3BzQHBIbG1vcmV4LmNvbTCCA SIwWDQYJKoZIhvcNAQEBBQADggEPADCCAQOoCggEBAK305DHFqHh9MnBOpzoBBRvck 7XLTbyDjREb 4 kY K9eoiSdwpHA4UIo9HRFLq6WAUjsq24082PysoFk4j131COw4bHbfhf2k47e5BQGR 4 SGEOkNLziSg2I 2X ErMtO c Yb ZtMGL5GdNr YNunlYahdhWQdAASefio r313TGRyw9cbhYiOxhHFdVWfr rOlci1RrIrwEiqMA3 4TNIjYknk77ODTvXSDOIQ SxcXRbkASstTGROGUERZzFrTLHUSDhYEThhPiRwi1RAxUO5tzVy6Sxt401JHsY3O V8npBnfFGErG1U1SH6fWiYu9S5c8JDeheit75TwyVA9R RlaxEMCAwEAAaOBGDCBS5TAJBgNVHRMEAjAAM EQGA1UdIAQ9MDswOQYLYIZIAYbARQEHFwEwKjAoBggrBgEFBQcCARYcaHROCHMG6Ly93d3cudmVyaXNp Z24uY29tL3JwYTALBgNVHQSEBAMCBaAwHQYDVROIBBYwFAYIKwYBBQUHAWQGCCSGAQUFBwMCMBQG CmCGSAGG EUBBgcEBhYETm9uZTBQBgNVHRSESTBHMEWgQGBBhj9odHRwOiS8vaW5kYzFkaWdpdGFsa WQtZzMtY3JsLnZicmizaWduLmNvbS9JbmRDMURpZ2l0OYWxJRC1HMy5jcmwwDQYJKoZIhvcNAQEFBQAD ggEBAD3o5bsnBvkF5zkd1A nEf3yXOJPhjWTzswwkIlAFSwo1FiDcRpBzd98 SJBBFs7hG2VuP 5bqxudLxCP2 vC6x8HnQAXjmSPx1d95V8UUKkOSLaABSHNri85AalpQRAR7t9Vr2hrYOFOT7ftOIvclaRuOBA4zUXA4uHYFYyuI 9knyJtomAb4HyVSekpXA4fg87bFK3h94z9p4 1 44nSWiaiMKrpQarjQj9TCxZgHNiJEMQtpWNEWeRS p Pelmorex Communications Inc NAAD System LMD User Guide Page 47 of 52 g rymNHvq9ZvYOEQGLXWgVugqzUBirFIntQxIGHAgzIso4mOZVqyTQ8cZDpOCFQh7WUIroZyruOI vD8 t erZ CijYVjeXtotwESCgY X
29. d LMDs to effectively monitor Alert Messages disseminated over the NAAD System NAAD Service Desk The Service Desk is the Single Point of Contact for all NAAD System users The Service Desk analyst can be reached at Support PublicAlerting Pelmorex com Who Should Use this Guide Participating LMDs or those who are interested in participating in receiving alerts from the NAAD System should read this guide symbols Used in this Guide Look for the following symbols as you read through this guide for further assistance Note Calls your attention to additional information Tip Calls your attention to a useful tip Warning Calls your attention to an important warning New Feature Calls your attention to features introduced in the new release Acronyms Authorized Government Agencies Common Alerting Protocol Common Alerting Protocol Canadian Profile Pelmorex Communications Inc NAAD System LMD User Guide Page 6 of 52 Transmission Control Protocol Uniform Resource Locator Extensible Markup Language Environment Canada Pelmorex Communications Inc NAAD System LMD User Guide Page 7 of 52 TERMS AND CONDITIONS OF USE By using the National Alert Aggregation and Dissemination NAAD System Alerting Data Feed you agree to accept and abide by these Terms and Conditions of Use You further acknowledge and agree that Pelmorex Communications Inc Pelmorex may revise and update these Terms and Co
30. ds these alerts contain 2 different set of values for the same Event type in 2 different info blocks within the same alert Alerts with multiple info blocks vary slightly in the xml structure from alerts issued through the NAAD System interface Alerts issued from the NAAD system will not contain multiple info blocks Pelmorex Communications Inc NAAD System LMD User Guide Page 11 of 52 Rules for attachments The following types of attachments are supported by the NAAD System Attachment types Audio file attachments if included must be in one of the MP3 WMA or Wav file formats Image file attachments if included must be in either the png or jpeg file format Attachment size The cumulative size of all file attachments in any single Alert Message will not exceed 800 Kbytes prior to conversion to base64 Alert Message size The size of any single Alert Message including all file attachments must not exceed 5 Mbytes prior to conversion to base64 URL Attachments AGAS can also attach files using a link To avoid potential issues Pelmorex has recommended the following guidelines to AGAs 1 Ensure the server where the URL is hosted is up and running at all times 2 The server where the URL is hosted can support reasonable traffic and has sufficient bandwidth for users to grab the URL If there is insufficient bandwidth for let s say 100 users at a time trying to connect to the server it could result in LMDs gettin
31. e will be blank 6 Process to validate the digital signature using a NAAD public key withoutconnecting to the DSS SOAP server LMDs with embedded systems i e with no access to the internet receiving CAP alerts by satellite can validate alerts by running OpenSSL commands Secure Sockets Layer Alerting website https alerts pelmorex com register so they can get the updated certificate information 1 It is strongly advised that LMDs register on Pelmorex Public Pelmorex Communications Inc NAAD System LMD User Guide Page 49 of 52 Appendix 5 Sample EC Alert Following is a SAMPLE of an EC Alert Please note this is a SAMPLE only and has been modified to fit as the content of this document This alert will not validate lt xml version 1 0 encoding UTF 8 alert xmlns urn oasis names tc emergency cap 1 2 identifier 2 49 0 1 124 b29ebdf5 2012 identifier sender capQ ec gc ca sender sent 2012 07 06T08 46 53 00 00 sent status Actual status msgType Alert msgType source Environment Canada Environnement Canada Toronto CWTO lt source gt lt scope gt Public lt scope gt lt restriction gt lt addresses gt code profile CAP CP 0 4 code lt code gt layer EC MSC SMC 1 0 lt code gt lt code gt layer SOREM 1 0 lt code gt lt note gt lt references gt lt incidents gt info language en CA language category
32. eats All NAAD System satellite and TCP streaming feeds include Pelmorex originated CAP CP XML NAAD Heartbeats NAAD Heartbeat CAP CP XML data is sent to allow LMDs to determine if the feed is operational The Heartbeat also contains the list of the last 10 transmitted alerts on this feed For the TCP Streaming Feed heartbeats are sent at a specific interval 1 minute For the Satellite Feed heartbeats are sent at a specific interval unless an alert is being sent at the same time In this case the alert has a higher priority and will be sent before the heartbeat NAAD heartbeats contain a history of the top 10 most recent alerts that were sent See Appendix 1 for an example of the heartbeat and to see how the list of recent alerts is structured Satellite Feed This feed is accessible from a satellite receiver on both C and Ku Band Pelmorex Communications Inc NAAD System LMD User Guide Page 16 of 52 C Band For specific details about C Band feed reception see Chapter 3 Section 1 Satellite Dissemination C Band Ku Band For specific details about Ku Band feed reception see Chapter 3 Section 2 Satellite Dissemination Ku Band In order to receive the UDP packets from the satellite receiver regardless of whether it is from C Band or Ku Band satellite a UDP socket application client should be used by the LMD NAAD System doesn t provide this application This application will need to be in the same network s
33. egment as the satellite receiver and it should register and receive packets sent to the IP multicast group 224 0 10 10 The UDP destination port 25555 must be used to receive data The application should receive data from this port and reassemble the packets to receive CAP CP XML data The UDP packets should be assembled in the sequence in which they are received in order to reassemble the packets into CAP CP XML data There is no additional information used to indicate the sequence of the UDP packet s data within the CAP CP XML In order to minimize the UDP packets re ordering issue since it could happen according to protocol specifications LMD should connect the decoding system computer directly to the satellite receiver using an Ethernet cable summary and additional notes for the Satellite Feed e he data will come out of the satellite receiver as unidirectional IP from the RJ45 Ethernet connection The data is send using a IP multicast group address 224 0 10 10 The IP protocol used to multicast the data is UDP The UDP destination port is 25555 Since UDP has limitation of about 64 KB in size the Alert Messages are separated into segments e The size of a UDP segment is 1024 bytes of usable data payload this is not the actual Ethernet packet size e Alert Messages will always start at the beginning of a UDP packet and all subsequent segments for the same alert are sent sequentially one after the other until the alert has
34. ene e eee eee eee vene 16 2 internet TOF Streaming Feed gas ase se dk gets dhon n de e onc is entes dies coat tUto 16 Summary and additional notes for the TCP Streaming Feed aa aaa aaa nan eee enen nare nanes eee ee eee eens 17 S Anteimet GOO S R BU eaaaacuceee cree saat E cid eaaearenonniaagusuencetnacdarcessaaemtanr 18 Summary and additional notes for the GeoRSS Feed cccccccseeccccesseceeeeeeceeceeeeeeseeecesseeeeeseaes 18 4 Troubleshooting Internet TCP Streaming Feed uu aaa eee enen rrene nenes teren 19 MADE Sashes ek sene sl e tees een ae annie rset EE T e e eden E 20 Salellll DISS OMNIA QI ssnsdin n ah E 20 About Satellite Dissemination aa una aaaaaa aa aanane anen a eee e eee e tipe nete rekate eee nete pene eee eee ete teen eee e eee eee eee tete teen eee e eee eee eee 20 1 Satellite Dissemination C Band aaa aa aaaaanaaaaaana an ana ne ae ee nan ee eee eee e rene e tere enet e eee ete teve eee eee ete teke eee eee eee 20 2 calellile DISSEMINATION Ku Band x5 ed e e de de e 21 ADRENDON AS BAND cc e ae ee ee er eee ee re eer ee ene ee eee ee eee 22 EXAMPLE A CONFIGURING CISCO D 9850 RECEIVER PRIMARY FEED aaa 23 EXAMPLE B CONFIGURING CISCO D 9850 RECEIVER SECONDARY FEED 26 ADIJENDUMB KU Band e A eid eee meee Uds ee ree 28 ADDENON Te FIG ARDC AUS ERE CO 29 Appendix 2 Sample Alert Messages sesa es sm n s oan oan SH S e s 31 Appendix 3 Broadcast Intrusive Alerts na
35. ernalUse 1 lt valueName gt lt value gt Polygon lt value gt z parameter area Desc Capital H and Capital c areaDesc 18 346288 123 669953 48 355871 123 664117 48 354502 123 652272 123 6699532 polygon gt 48 339214 123 673901 48 346288 123 669953 geocode valueName z profile CAP CP Location 0 3 lt valueName gt lt value gt 591 054 lt value gt z geocode lt geocode gt lt valueName gt profile CAP CP Location 0 3 lt valueName gt lt value gt 591 7054 lt value gt lt geocode gt Pelmorex Communications Inc NAAD System LMD User Guide Page 34 of 52 parameter lt valueName gt NAADS InternalUse 1 lt valueName gt lt value gt Cirde lt value gt parameter gt lt area gt aDesc gt Capital H and Capital lt areaDesc gt K lci s 48 3459 10 123 661900 lt geocode gt valueNamez profile CAP CP Location 0 3 valueName lt value gt 5917054 lt value gt z geocode geocode zvalueName profile CAP CP Location 0 3 valueName lt Value gt 5917054 lt value gt z geocode lt geocode gt parameter valueNamezlayer NAADS 1 0 eventlocation points valueNamez lt value gt 49 009327 127 815854 lt value gt lt parameter gt Minor Update Pelmorex Communications Inc NAAD System LMD User Guide Page 35 of 52 parameter zvalueName profile CAP CP 0 4 MinorChange valueName zvalue otherz value
36. es The purpose of these rules is to set out the policies and procedures for tests performed by Authorized Provincial Territorial P T Emergency Management Organizations EMOs Alerting Authorities and Pelmorex to ensure Alert Messages are received and submitted successfully and that the NAAD System is available and operational at all times To that end the NAAD System supports two different ways of testing A Test messages not intended for broadcast 1 Heartbeat Message 2 Test message with Message status Test B Test messages intended for broadcast 1 Test message with Message status Actual 2 Public awareness test messages To ensure not intended for broadcast and intended for broadcast Test Messages are easily identified and dealt with appropriately by LMDs Authorized Government users must comply with the rules For further details please refer to the Test Message Policy V2 0 at this LINK A Sections to follow The subsequent chapters of this document provide information on How to listen to Satellite C band amp Ku band and or TCP feeds Details on the GeoRSS auxiliary service Description of the Heartbeat message Sample Alert Messages Information on Digital Signatures Reference Documents CAP Standards CAP CP Standards Statistics Canada Standard Geographical Codes These and other documents can be found at https alerts pelmorex com techinfo currentcapmaterial User Resources
37. etrieval site are described below Pelmorex NAAD System Alert Message Examples in CAP CP format The following Pelmorex NAAD System Alert Message examples are based on CAP CP beta version 0 3A and presented in valid XML format as defined by the CAP Oasis 1 2 XML schema Encoding is UTF 8 Pelmorex Communications Inc NAAD System LMD User Guide Page 32 of 52 Alert Locations Area NAADS interface does not recommend or check the sequence preference for location selections This selection E J order preference is solely the Issuer s own choice For f instance an Issuer can select a sub division first and then select the corresponding province This order is not changed and will appear as is in the Alert Message The sequence of Polygons and their corresponding Geocodes is the same as selected by an Issuer The first Polygon has the first Geocode second Polygon has the second Geocode and SO on See example below lt area gt lt areaDesc gt Test Area lt areaDesc gt Pelmorex Communications Inc NAAD System LMD User Guide Page 33 of 52 lt polygon gt 49 000038 96 784563 49 266276 96 780004 49 266301 96 376094 49 186899 97 310227 49 095757 97 214918 49 022915 97 201883 49 000038 96 784563 lt polygon gt m T lt geocode gt valueName profile CAP CP Location 0 3 valueName svalue 4602 value lt geocode gt lt area gt s RR o lt parameter gt lt valueName gt NAADS Int
38. g disconnected from the server and not gaining access to the URL Please note that the NAAD System cannot guarantee the po existence and validity of the attachment being referenced L through a URL nor does the system store or provide these files It is the Issuers sole responsibility to ensure the existence and validity of these attachments Display of special characters for LMDs Websites generally use the ISO standard which supports 1 million characters which is LESS than the UTF 8 standard the NAAD system uses What this means for LMDs is that certain special characters used by AGA such as etc may show up on their websites either differently or get is replaced by or by a blank space If normal keyboard characters such as those on the keyboard are used while creating an alert directly into the NAAD application most characters are supported To avoid a potential issue Pelmorex recommends that AGA avoid using special characters when creating an alert and do not cut and paste text from a Word document You can find more information on the ISO and UTF 8 standards below Characters supported in ISO 8859 1 also called Latin 1 which is the default encoding in Windows http en wikipedia org wiki ISO IEC 8859 1 Codepage layout Characters supported in UTF 8 http www utf8 chartable de Pelmorex Communications Inc NAAD System LMD User Guide Page 12 of 52 Rules Governing NAAD System Testing amp Test Messag
39. h entry e Entries are listed from the oldest to the most recent transmission based on the transmission time not the issued time most of the time thus will correspond also to the sequence they have been issued too e References is used here to express a list and does not means any links references between the alerts identified in the list similarly the list does not imply any update cancel on the identified alerts This is purely a list of recent transmission on the feed from which the Heartbeat is received Lists may differ slightly between communication channels pa Feeds as heartbeats are not synchronized between channels Sent and ID are the same for the same alerts whatever channels as those are the Issue ID from the Issuer ES Heartbeats are not digitally signed and respect CAP CP f formatting enn The heartbeats can be identified easily by checking the J status is System and Sender is NAADS Heartbeat Pelmorex Communications Inc NAAD System LMD User Guide Page 30 of 52 Retrieving missed alerts using heartbeat information In order to retrieve alerts that were missed and that are referenced in the heartbeats a HTTP URL can be recreated using the following method http capcp site domain SENT DATE SENT ILIDENTIFIER xml Where e capcp site domain capcpi naad adna pelmorex com Primary Site gt Oakville or capcp2 naad adna pelmorex com secondary Site gt Montreal e SENT DATE
40. hapter describes each of these different feeds Satellite and Internet TCP Streaming Feeds are 22 recommended for use by LMDs for real time and or t automated 24 7 applications The Internet GeoRSS Feed is an auxiliary feed for human access amp for checking alerts and should not be used for feeding a real time automated system pa An Alert Message received through any of the three main communications channels is identical byte by byte on the other communications channels Satellite and TCP Streaming Feed General Information The start and end of each CAP CP XML formatted Alert Message is detected using the start and end tags lt alert and lt alert gt If the CAP CP XML starts with the optional XML declaration lt xml version then the declaration is part of the CAP CP XML and the encoding attribute should be used to process the data correctly Pelmorex Communications Inc NAAD System LMD User Guide Page 15 of 52 Alerts Alert Messages in CAP CP compliant format are sent to all feeds once they are received by the Pelmorex NAAD System There will be slight differences in the actual time that the alerts are received by the LMD over these data feeds due to different bandwidth and connection speed constraints of the Satellite and Internet TCP feeds Alert Messages may occasionally be sent multiple times over a communications channel only if a transmission error was detected by the Pelmorex
41. lerts and heartbeats from the connected TCP socket Alerts are also archived at alerts pelmorex com See https alerts pelmorex com filearchiveaccess Pelmorex Communications Inc NAAD System LMD User Guide Page 20 of 52 Chapter 3 Satellite Dissemination This chapter includes Satellite Dissemination C Band Satellite Dissemination Ku Band Addendum A C Band Example A Configuring CISCO D 9850 Receiver Primary Feed Example B Configuring CISCO D 9850 Receiver Secondary Feed Addendum B Ku Band About Satellite Dissemination The NAAD System provides satellite dissemination through C Band and Ku Band as described below While receiving alerts through Satellite LMDs should connect directly to the receivers through the Ethernet port ZN without any switch router etc in the middle Failing to do so will not guarantee the packet order and they might receive some packets in the wrong order 1 Satellite Dissemination C Band C Band dissemination is provided by Telesat over Anik FIR Satellite It is expected that most BDUs and TV broadcasters already possess a receiving satellite antenna pointed to this satellite The main C Band feed is on virtual channel 206 In the unlikely event that the main feed will be disabled then the service will be transferred to the virtual channel 550 There are three ways a receiving site may be equipped to receive alerts messages over the C Band Please note
42. line gt Sample alert with Digital signature lt headline gt lt area gt lt areaDesc gt Test NAADS signature lt areaDesc gt lt polygon gt 51 552994 99 216119 51 564488 99 219607 51 575448 99 219861 51 576326 99 221583 51 559342 99 225395 51 552488 99 236193 51 538291 99 244281 51 529917 99 245778 51 528724 99 256742 51 523192 99 261972 51 516722 99 263953 51 510717 99 263414 51 507501 99 265974 51 504579 99 265929 51 502849 99 263657 51 498802 99 26395 51 497321 99 266635 51 49194 99 264386 51 490075 99 266247 51 479374 99 262484 51 473999 99 265706 51 474256 99 204523 51 503636 99 204828 51 503875 99 193096 51 532352 99 192697 51 535124 99 19768 51 537876 99 19726 51 553234 99 202605 51 549832 99 209311 51 548486 99 207949 51 543643 99 210667 51 545245 99 215015 51 551858 99 217815 51 551197 99 215461 51 552994 99 216119 lt polygon gt lt geocode gt lt valueName gt profile CAP CP Location 0 3 lt valueName gt lt value gt 4619068 lt value gt lt geocode gt lt area gt lt info gt lt alert gt 2 Alert Message with digital signature lt xml version 1 0 encoding UTF 8 gt alert xmins urn oasis names tc emergency cap 1 2 gt lt identifier gt CE1336F2 24ED 5A25 93A4 1F3C4ACA071E lt identifier gt sender NAADS TestingONAADSQPelmorexCommunications Testing lt sender gt lt sent gt 2011 06 22T06 14 25 00 00 lt sent gt lt status gt Actual lt status gt lt msg
43. nMethod Algorithm http www w3 org TR 2001 REC xml c14n 20010315 lt SignatureMethod Algorithm http www w3 org 2000 09 xmidsig rsa shal1 gt lt Reference URI gt lt Transforms gt Transform Algorithm http www w3 org 2000 09 xmldsigZ enveloped signature Transforms lt DigestMethod Algorithm http www w3 org 2000 09 xmldsigZsha1 lt DigestValue gt u wAlHg nmiuW UzZDBypGdvpxHo lt DigestValue gt lt Reference gt SignedInfo lt SignatureValue gt BbHbaLc4 i6EHRPW uUMJqlHEbDWNUrWAS3hRS1Bsn7inG5F8Q1X2vWLOUOITzEv4 Z FEHGCYC10kO0layIPDaUTd070nMXIKXHP626iT99IgMwAuh5GO03IQt NOfhac61u8wl6ZUNmUyPeNqdk7NSI LrZJydv7Oq6Lu0 60BpfQNDbQINVJBA9CvrAVVY7iajSvP5bkZqDhlgLBwMS3LIMyk2IjzFPvJEG6Va70GVrHd Maa0HOOPA7MKN 6yybewGCrBOekVL3epISLpMUxxSgEF53juqX4DjCNotbtFE IbSTNjKcvIttO1D35wWF 2bckydi0o0qRDbJ980X96XZ3Nkw SignatureValue KeyInfo lt X509Data gt X509Certificate MIIFazCCBFOgAwIBAgIQBO1UgIlUDPqeqqRrvrn 2JTANBgkqhkiG9wOBAQUFADCBS3TEL MAkGA1UEBhMCVVMXxFzAVBgNVBAoTDIZIcCmITaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2InbiBUcnV zdCBOZXR3b3JrMTswOQYDVQQLEZzJUZXOtcyBvZIiB1c2UgYXQgaHROCHMG6Ly93d3cudmVyaXNpZ24uY29tL 3JwYSAoYykwOTEeMBWwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU 2inbiBDbGFzcyAxIEluZGI2aWR1YWwgUS3Vic2NyaWJIciBDQSAtIECZMBAXDTEXMDUWMZAwMDAwWwMFOXDT EyMDUwWNTIzNTk1OVowggEYMRCwWFQYDVQQKEW5WZXJpU2InbiwgSW5jLjETMBOGA1UECXMWVmVyaVN pZ24gVHJ1c3QgTmVOd29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv
44. nauunnnnnnnanaese ena ese ner e non see rere RSS ESSE rr ESSE SEE Ere ESSE SEE re RSS ES err em nna nana n nana ee 36 Broadcast Intrusive SOREM LISI gas gen cccs soni c sa ona oda sdo eo dend sin oe 38 Appenaix 4 Digital Signatures duan cai vu vuash ad usa ad S vd s 40 Append S Sample EC AQ II pasa sd ada nude aaa ra aaa sien ue ea n s 49 Pelmorex Communications Inc Table of Figures Figure 1 Satellite Dissemination C Band nana aaa aaa aa aa p RR R RA RR RR RR RR ARRA nennen nnn 21 Figure 2 Satellite Dissemination Ku Band aaa aaa aaa aaa enen enen RR RR RR RR ARRA R hehe 22 Pelmorex Communications Inc NAAD System LMD User Guide Page 5 of 52 Welcome This document provides information and describes the features of the National Alert Aggregation amp Dissemination NAAD System provided by Pelmorex Communications Inc Pelmorex It is intended to assist Last Mile Distributors LMD so LMDs can receive and pass on Alert Messages to the public Overview The NAAD System collects public alert messages from Authorized Government Agencies AGA and makes them available without any alteration or interpretation of the contents to LMDs such as radio and television stations as well as cable and satellite TV companies for display to the Canadian public thereby helping forewarn the public of any imminent danger related to persons or property This User Manual will provide the information necessary for intereste
45. nditions of Use without notice to you at any time All alerts content material and information hereafter emergency information provided on the NAAD System Alerting Data Feed is obtained by Pelmorex from a government agency in Canada that is authorized to issue emergency information and is provided on an as is basis Pelmorex makes every reasonable effort to ensure the NAAD System Alerting Data Feed contains only emergency information received from a government agency in Canada that is authorized to issue emergency warnings and that the public safety messages comply with agreed to standards as posted elsewhere on Pelmorexs website at https alerts pelmorex com However Pelmorex does not guarantee or make any representation or warranty express or implied i that the messages contained in the emergency information are current accurate truthful or complete or ii that the emergency information will be available without interruption error or omission Under no circumstances including but not limited to negligence gross negligence negligent misrepresentation and fundamental breach shall Pelmorex or its affiliates and related companies and each of their respective directors officers employees consultants and agents be liable for any direct indirect incidental special or consequential damages or any loss that results from the use of or the failure to use any emergency information or postings on the NAAD System Alerting Da
46. nds on the geographical position of the receiving site Please consult Telesat for detailed information e HN7700S iMpACT terminal must be purchased from Telesat e Configuration to be done by Telesat e Bit rate 500 Kbits sec 500000 could be increased in the future if needed Pelmorex Communications Inc NAAD System LMD User Guide Page 29 of 52 Appendix 1 Heartbeats Example lt xml version 1 0 encoding UTF 8 alert xmlns urn oasis names tc emergency cap 1 2 identifier 5BAS9AGFD 0D89 1C6C 46D5 B535F61CO068F lt identifier gt sender NAADS HeartbeatoNAADSOPelmorexCommunicationsinc sender lt sent gt 2011 06 22T05 06 49 00 00 lt sent gt status System status lt msgType gt Update lt msgType gt lt scope gt Public lt scope gt lt code gt profile CAP CP 0 3 lt code gt lt references gt NAADS Heartbeat NAADS PelmorexCommunicationsInc DD9216B4 2A6C 8514 4332 85B7359FE2E0 2011 06 22T04 59 00 00 00 lt references gt lt alert gt The format of the heartbeats conforms to the same CAP Oasis 1 2 and CAP CP standards as Alert Message disseminated by the NAAD System do Heartbeats are sent each minute on both Internet TCP Streaming and Satellite feeds The GeoRSS feed does not contain NAAD heartbeats e Each entry in the lt references gt list is composed of the 3 elements Sender Identifier Sent with a comma between Sender Identifier and Identifier Sent and a space between eac
47. ocument alert and alert There are no special or proprietary headers added to the data only raw XML e If the alert contains an XML declaration lt xml version then the encoding attribute should be used to process the data correctly e Heartbeats are sent a specific interval 1 minute to indicate the connection is alive see Appendix 1 Pelmorex Communications Inc NAAD System LMD User Guide Page 18 of 52 3 Internet GeoRSS Feed The Pelmorex NAAD System GeoRSS feed is provided as an alternate method for viewing alerts but is not intended for feeding 24 7 automated systems This feed is accessible through the Internet and is formatted in Atom Syndication Format See http en wikipedia org wiki Atom 28standard 29 and also includes the GeoRSS Simple support see http www georss org simple to include additional geographical information related to the affected area included in the original alert This feed can be viewed using any RSS reader that supports an Atom feed however standard RSS readers such as Internet Explorer Firefox etc will only display the RSS Atom portion and not the geographical information included by the GeoRSS portions In order to see the geographical information a GeoRSS reader must be used The GeoRSS feed contains the last 48 hours of alerts listed as Atom entry elements Each alert info element will be represented as an entry in the feed Categories in the feed can be used to
48. or occasional access Information for LMDs To receive Alert Messages for dissemination to the general public an LMD should be aware of the basic rules concepts of the NAAD System set out below Multiple feeds are made available it is recommended that LMDs listen to more than one feed for redundancy purposes Use CAP amp CAP CP standard to interpret select and publish the Alert Messages Alerts contain all the information for the LMD to filter interpret profile as needed by their own network Use Digital Signatures to verify that Alert Messages are from a genuine source Alerts contain 1 or 2 Digital Signature s it is recommended that LMDs verify signatures to ensure the message is from a genuine AGA as well as received via the NAAD System Use auxiliary mechanisms to retrieve Alert Messages if message loss is detected Messages are kept in their integral form for 48 hours short term repository for automated retrieval if an alert was missed by a LMD Know the concept of Heartbeats Heartbeats let an LMD know that the NAAD System is operating properly and provides information about previous Alert Messages S More detail on all of the above mentioned points is provided Ey in the subsequent chapters General Rules Concepts An LMD should be aware of the following rules and concepts governing Alert Messages All Alert Messages follow the CAP CAP CP approved standards All Alert Messages have certain Business rules as
49. r Guide Page 46 of 52 eventCode svalueNamez profile CAP CP Event 0 3 lt valueName gt lt value gt tornado lt value gt lt eventCode gt lt expires gt 2011 06 25T13 00 00 00 00 lt expires gt lt senderName gt Pelmorex Communications Testing lt senderName gt lt headline gt Sample alert with Digital signature lt headline gt lt area gt lt areaDesc gt Crane river Manitoba lt areaDesc gt lt polygon gt 51 552994 99 216119 51 564488 99 219607 51 575448 99 219861 51 576326 99 221583 51 559342 99 225395 51 552488 99 236193 51 538291 99 244281 51 529917 99 245778 51 528724 99 256742 51 523192 99 261972 51 516722 99 263953 51 510717 99 263414 51 507501 99 265974 51 504579 99 265929 51 502849 99 263657 51 498802 99 26395 51 497321 99 266635 51 49194 99 264386 51 490075 99 266247 51 479374 99 262484 51 473999 99 265706 51 474256 99 204523 51 503636 99 204828 51 503875 99 193096 51 532352 99 192697 51 535124 99 19768 51 537876 99 19726 51 553234 99 202605 51 549832 99 209311 51 548486 99 207949 51 543643 99 210667 51 545245 99 215015 51 551858 99 217815 51 551197 99 215461 51 552994 99 216119 lt polygon gt lt geocode gt lt valueName gt profile CAP CP Location 0 3 lt valueName gt lt value gt 4619068 lt value gt lt geocode gt lt area gt lt info gt Signature Id NAADS Signature xmIins http www w3 org 2000 09 xmidsig gt lt SignedInfo gt lt Canonicalizatio
50. referenced resource s content lt Re ference gt before it was digested SignedInfo The lt OigestValue gt element carries the value of SignatureValue the digest of the referenced resource Keylnfo 7 Ne Object N The lt SignatureValue gt element carnes Signature the value of the encrypted digest of the Signedinfo element The Keylnfo element indicates the key to be used to validate the signature Possible forms for identification include certificates key names and key agreement algonthms and information The data flow for the overall solution is as follows Refer to Figure on next page To make it easier for the LMDs points that are of concern for an LMD are shown in BOLD text Pelmorex Communications Inc NAAD System LMD User Guide Page 41 of 52 ja Issuer creates Alert Message through the NAADS user interface 1 in dravving 2 Issuer submits Alert Message for signing through the NAADS user interface to the DSS of their organization The Message is signed and the issuer then submits it to NAADS central processing through the NAADS user interface 2 8 3 This step is optional depending on whether issuer adds their signature 3 NAADS central processing receives the Message 4 4 NAADS validates the signature by verifying against the issuer DSS 5 amp 6 This guarantees no tampering in transmission If the signature is not validated the Alert Message will be rejected and the i
51. s the list of recent alerts that were sent by the Pelmorex NAAD System on that specific feed The application can use this list to detect if an alert has been missed In this case the LMD s application could retrieve it from the HTTP short term repository site See Appendix 1 Heartbeats for details Alert Messages are kept for 48 hours in the HTTP short term repository for retrieval purposes by automated systems See Appendix 1 for an example of the heartbeat and to see how the list of recent alerts is structured As soon as the application has connected alerts can be received there is nothing that should be sent by the application itself to initiate the reception It should just wait to receive alerts and heartbeats from the connected TCP socket Since this feed is a live TCP stream of alerts the start and end tags of the CAP CP XML document lt alert and lt alert gt must be used to detect the start and end of an Alert Message within the stream There are no special or proprietary headers added to the data only raw XML is transmitted Summary and additional notes for the TCP Streaming Feed Alert Messages are provided as a data stream using TCP IP protocol The host and port of the socket to connect to receive this stream is o streaming1 naad adna pelmorex com Oakville o Streaming2 naad adna pelmorex com Montreal o TCP port 8080 e The start and end of an alert is detected using the start and end tags of the XML d
52. ssuer notified This step is optional depending on whether issuer adds their signature 5 NAADS central processing adds its own signature using NAADS DSS 7 amp 8 6 Alert Message which has two signatures is delivered by various mechanisms to LMD 9 amp 10 If issuer has no signing DSS only NAADS signature will be appended to the Message 7 LMD verifies the Message is sent by NAADS by validating NAADS digital signature against NAADS DSS 11812 This verifies that Message is not tampered in transmission from NAADS to LMD If this is valid then LMD can further validate that original Alert is not modified or tampered in any way from the Original issuing source by validating the issuer s signature against the issuing organization DSS 13 amp 14 For both these validations the LMDs will need to form XML based SOAP requests on https following the OASIS DSS standard to the NAADS Issuer DSS to get the signatures validated 8 Once both validations are successful the LMD can process the actual Alert Message If the Message was signed only by NAADS LMD will validate against NAADS DSS only 9 LMD s that prefer not to process either signature can just ignore the signatures and process the alert LMD s that prefer to valid just one signature can filter out either signatures using XPath or other mechanisms and validate the required signature 10 LMD s can verify the NAADS Signature by making a SOAP request on https following the OASIS
53. ta Feed directly or indirectly These limitations apply regardless of whether the party liable or allegedly liable was advised had other reason to know or in fact knew of the possibility of such damages Further in viewing the NAAD System Alerting Data Feed you specifically acknowledge and agree that neither Pelmorex nor its affiliates and related companies nor each of their respective directors officers employees consultants and agents shall be liable for any defamatory offensive or illegal conduct of any user including you Pelmorex Communications Inc NAAD System LMD User Guide Page 8 of 52 Chapter 1 NAAD System Overview This chapter includes NAAD System Introduction Information for LMDs General Rules Concepts Rules for attachments Display of special characters for LMDs Rules Governing NAAD System Testing amp Test Messages Sections to follow Reference Documents User Resources About this chapter The aim of this chapter is to provide the basic concept and information about the NAAD System and Alert Messages issued through the NAAD System and to give an overview of the Alert Message rules rules refer to the CAP CAP CP standards and policies adopted by the Council to the LMDs NAAD System Introduction The NAAD System provides 3 basic features as described below 1 Collection of Alert Messages The NAAD System provides the ability for AGAs to create Alert Messages or issue alerts through a tr
54. tify the request from LMD This should be unique for each request and should have a way to identify the requestor NAADS will include this Request ID in the response The document ID will be a unique ID for each specific alert that is being verified and the same ID needs to be repeated in the WhichDocument field under OptionalInputs part of the Verify Request Under the Document Id the entire signed alert that is to be verified is to be provided by the LMD VerifyRequest RequestID 0822D9A5 B7B0 OEFB 47F6 A47F2EF12347 xmins ds http www w3 org 2000 09 xmidsig xmlns http www docs oasis open org dss oasis dss 1 0 core schema cd 02 xsd Profile gt lt InputDocuments gt Document ID 0822D9A5 B7B0 0OEFB 47F6 A47F2EF12347 gt alert xmlns urn oasis names tc emergency cap 1 2 identifier 0822D9A5 B7BO OEFB 47F6 A47F2EF12347 lt identifier gt sender NAADS TestingONAADSQPelmorexCommunications Testing lt sender gt sent 2011 06 24T05 38 35 00 00 sent status Actual status msgType Alert msgType scope Public c scope code profile CAP CP 0 3 code info language en CA language category Met category event Tornado event responseType Nonec responseType lt urgency gt Immediate lt urgency gt lt severity gt Extreme lt severity gt certainty gt Observed lt certainty gt Pelmorex Communications Inc NAAD System LMD Use
55. ts disseminated by NAAD System but not in Heartbeat messages It may be used by LMD s to confirm that the Alert Messages are received from the NAAD System LMD point of view Alert Messages are not encrypted and are human readable regardless whether signatures are present It is up to the discretion of the LMD to verify or ignore alert signatures When an Alert is received the Last Mile Distributor has the option of checking either or both of the signatures to validate that the Alert did originate from NAADS system i e not tampered in internet transmission after issuing and also validate that the original Alert Message from the issuer is genuine and intact It is recommended that LMDs verify signatures for all Alert Messages intended to be displayed to the Public When both signatures are present it is preferable to check Issuer signature as it verifies the originators source Verification Process Digital signatures are included in the CAP 1 2 specification and utilize the XML Sig standard The XML Sig standard identifies the various elements of the signature as below Each resource to be signed has its own Reference element identified by the URI attribute Signature Signed Info CanonicalizationMethod SignatureMethod Reference URI gt Transforms lt __ The Transform element specifies an DigestMethod ordered list of processing steps that were DigestVa lue applied to the
56. usted feed is an organization has a public alerting system as in the case of Alberta and EC Therefore Alert Messages can be sourced from The User Access System provided by the NAAD System Issuers create alerts which are then submitted for dissemination to LMDs As Trusted Feeds where Alert Messages are received from an AGA s system as a data feed already assembled and validated by the issuing AGA as CAP CP compliant 2 Aggregation of Alert Messages Aggregation of Alert Messages implies the aggregation of alert messages submitted by the AGAs the participating sources for sending alerts in Canada Information is collected stored processed and validated against CAP CP standards permissions authorizations and agreed upon rules The basic steps are Validate the alert message format amp authority Merge all sources Log record amp archive Alert Messages j The NAAD System does not aggregate certain elements of Ey an alert for instance the attachments referenced by URL Pelmorex Communications Inc NAAD System LMD User Guide Page 9 of 52 3 Dissemination of Alert Messages Dissemination of alert messages implies making the Alert Message available to various LMDs for further dissemination to the general public Alert Messages are disseminated to LMDs in the following manner via real time streaming feeds for 24 7 automated system implementations through an auxiliary repository as well as GeoRSS feed f
57. zAVBgNVBAoTDIZIcCmITaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2InbiBUcnV zdCBOZXR3b3JrMTswOQYDVQQLEZzJUZXJtcyBvZIiB1c2UgYXQgaHROCHMG6Ly93d3cudmVyaXNpZ24uY29tL 3JwYSAoYykwOTEeMBWwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU 2iInbiBDbGFzcyAxIEluZGI2aWR1YWwgUS3Vic2NyaWJIciBDQSAtIECZMBA4XDTEXMDUWMZAWMDAwMFOXDT EyMDUwWNTIzNTk1OVowggEYMRCwWFQYDVQQKEW5WZXJpU2InbiwgSW5jLjETMBOGA1UECXMWVmVyaVN pZ24gVHJ1c3QgTmVOd29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc210b3J5L1JQQSBJb mNvcnAuIGJ5SIFJIZiA4sTEIBQI5MVEQoYyk5ODEeMBWwWGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkM TMwMQYDVQQLEypEaWdpdGFsIEIEIENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNIcnZpY2UxGzAZBgNVB AMUEKk5BQURTIERTUyBQZWXxtb3JIeDEIiMCAGCSqGSIb3DQEJARYTbmVOb3BzQHBIbG1vcmV4LmNvbTCCA SIwWDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAK305DHFqHh9MnBOpzoBBRvck 7XLTbyDjREb 4 kY K9eoi8dwpHA4UIo9HRFLq6WAUJjsq24082PysoFk4j131COw4bHbfhf2k47e5BQGR SGEOkNLziSg2I 2X ErMt0 Yb ZtMGL5GdNr YNunlYahdhWQdA4Sefio r313TGRyw9cbhYiOxhHFdVWfr rOlci1RrIrwEiqMA3 Pelmorex Communications Inc NAAD System LMD User Guide Page 45 of 52 4TNIjYknk77ODTvXSDOIQ SxcXRbkASstTGROGUERZzFrTLHUSDhYEThhPiRwi1RA4xUO5tzVy6Sxt401JHsY3O V8npBnfFGErG1U1SH6fWiYu9S5c8JDeheit75TwyVA9R RIaxXEMCAwEAAaOBG6DCB5TAJBgNVHRMEAjAAM EQGA1UdIAQ9MDswOQYLYIZIAYbARQEHFwEwKjAoBggrBgEFBQcCARYcaHROCHMG6Ly93d3cudmVyaXNp Z24uY29tL3JwYTALBgNVHQ8S8EBAMCBaAwHQYDVROIBBYwFAYIKwYBBQUHAWQGCCSGAQUFBwMCMBQG CmCGSAGG EUBBgcEBhYETm9uZTBQBgNVHRS8SESTBHMEWgQ6BBhj90dHRwOi8vaW5kYzFkaWdpdGFsa
Download Pdf Manuals
Related Search