Practitioner Special Interest Group Meeting January 19, 2011 Integrated Public Alert and Warning System Open Platform for Emergency Networks(IPAWS-OPEN) Common Alerting Protocol (CAP) Message Construction Guide Gary Ham System Architect Avagene Moore: May I have your attention, please: Ladies and Gentlemen: Welcome to the first IPAWS OPEN SIG event of 2011. I wish each of you a belated Happy New Year! We are pleased that each of you could join us for our meeting today. I am Avagene Moore and will serve as your Moderator. We are recording today’s Webinar but we are especially glad that you are here in person to see and hear what we have planned for today. As usual, we ask your assistance once again with our recording. Please mute your phone to avoid any background noise. However, do not put us on hold. If you would like to expand your desktop to full view, please look to the bottom right corner of your screen. Use the monitor there with the 4 arrows coming out – to expand your screen. To go back to a smaller screen, just hit ‘escape.’ As stated in our Mail List notice, IPAWS-OPEN will be upgraded to implement CAP Version 1.2 and the IPAWS CAP Profile during the next few months. The IPAWS-OPEN CAP Message Construction Guide is being prepared to assist third party developers with designing their CAP Alert applications. Our speaker will provide a preview of the guide and review basic requirements for us. We are pleased to have Gary Ham with us. Gary is a friend to us all and serves as System Architect for this project. Please jot down your questions as Gary goes through his presentation. I will monitor the attendees list. Please change the color by your name to purple. Look to the top right hand corner of the Live Meeting screen to do this. We will call upon you and ask that you please state your name and affiliation. We sometimes have people on the conference bridge and not in Live Meeting. If that is the case, you will have an opportunity to speak as well. Thanks for being here once again, Gary. I now turn the floor to you. Thank you, Gary. You did a very good job covering a lot of material for us. I am sure there are questions for you at this time. Folks, if you want to ask a question, please change the color by your name to purple. I will call upon you by name and ask you to state your name and affiliation. Gary Ham: Slide 1 Integrated Public Alert and Warning System Open Platform for Emergency Networks (IPAWS-OPEN) Special Interest Group Presentation Slide 2 IPAWS Architecture Diagram OPEN (Open Platform for Emergency Networks) is a message broker for exchanging standards compliant emergency messages. OPEN v1.0 aka as DMIS, has been fielded in some localities to provide alert and warning message exchange with NOAA for non-weather hazard activation of the National Weather Radio network (HazCollect System). .Authorized alerting officials at all levels of government access the IPAWS service and send CAP messages through OPEN to public information distribution systems. Standard based CAP format emergency alert messages. .IPAWS builds and maintains the OPEN standards based interface and connection to public information dissemination channels: - radio and TV via EAS - cellular phone broadcast via CMAS - NOAA Weather Radio via HazCollect - Internet services via TBD - Local Unique systems – such as Emergency Telephone Networks and local phone dialing system as well as other local alerting systems (e.g. siren, signboard) IPAWS does not replace local alerting systems, but can be used by and integrated with local alerting systems Slide 3 CAP Content as Driver of IPAWS-OPEN Message Distribution All posted alerts must validate to CAP, allowing IPAWS-OPEN to further inspect the contents of the message for data that determines the actual distribution path(s) for the message. Based on the data, an originator can: .Create a non-IPAWS CAP message that is sent only to specific addresses (COGs) in IPAWS. This message can be: –Private –Intended only for the recipient, –Restricted –Allowing the recipient to know the rules for redistribution, or –Public –Giving the recipient (and others) full latitude in redistribution. .Create an IPAWS Profile conformant CAP message for availability to the general public all via RSS Feed. The IPAWS Profile message can also be distributed via: –Emergency Alert System (EAS) Broadcast, –NOAA Radio as a Non-weather Emergency Message (NWEM), and/or –Cell phone via the Cellular Mobile Alert System (CMAS). Slide 4 CAP Construction Guide TOC The purpose of the guide is to consolidate seven different specification documents totalling 700-800 pages between them. This guide focuses on the construction of CAP messages. This is an outline of the Table of Contents. .SOAP Validation .CAP 1.2 Validation .IPAWS Profile Validation .CAP Level Signatures .IPAWS Dissemination Channel Processing Rules: –EAS –NWEM –CMAS .IPAWS-OPEN Process Flow Summary (Next two slides) .Accessing IPAWS-OPEN Messages The document is entirely CAP-centric. It is about 85% complete. I hope to have it done in a week or two. Maybe next month we can answer questions based on the actual document itself. I have two more slides that I want to talk about that describes the process flow as a CAP message goes through the system. Slide 5 Processing a CAP Message Within IPAWS-OPEN Client CAP Message as SOAP Content 1. Is SOAP signature valid? If no, Return Authorization Error Message. Basic Validation Failure. Else 2. Is CAP message content valid to CAP 1.2 schema? If no, Return Validation Error message. Basic Validation Failure. Else 3. Is CAP Message Marked IPAWS Profile? If no, Record message and metadata in OPEN DB. All validated CAP messages are recorded in the DB and can be retrieved using authorizations and metadata. Else 4. Does CAP Message pass basic IPAWS Profile requirements? If no, Return IPAWS Profile validation error message. Error Returned - Message saved but not available for retrieval by recipients. Else Process for IPAWS Dissemination (see next slide) Record message and metadata in OPEN DB Send acknowledgement and post status. The acknowledgement returned with a CAP message includes the distribution channels it was successfully posted to. Successful completion Slide 6 IPAWS Dissemination Channel Processing IPAWS Profile Conformant Message 5. Does CAP message have a validated signature? If no, back to CAP Process. Else Post for General RSS Feed 6. Is Message EAS? If yes, post to private EAS Feed 7. Is Message NWEM? IF yes, post to HazCollect 8. Is Message CMAS? If yes, post to CMSP Gateways Record "push" metadata for message. This represents the extra metadata associated with the CAP message that lets a system retrieve information about what dissemination channels were used for the message. Slide 7 IPAWS-OPEN “Horizon” Items .Signatures –Need two more in test environment –Need .Net or how to convert .jks correctly for .Net .Reference Implementation –Basic connection in .Net and Java .CAP examples and explanation (this presentation is outline) –Private –Public Non-IPAWS –EAS push –CMAS –NWEM .RSS feeds –Private for EAS –Public Release schedule: OPEN 2.0.01–Very soon OPEN 2.1–depends on Oracle 11G adoption in FEMA SOA – Needed for EAS. TDL in March? OPEN3.0–Feb 2012 CMAS release Slide 8 IPAWS-OPEN 2.0 MOA Status .61 MOAsin development –32 Executed MOAs –7 Others in Active process –22 Identified with Questionnaires .Representing all aspect of IPAWS-OPEN –Disseminators (Cable TV –EAS –RBDS) –Originators (PSAP, EM, Notification and Alerting, Military) –DE systems Slide 9 Comments and Questions .IPAWS Website -http://www.fema.gov/emergency/ipaws Mark.Lucero@dhs.gov Office (202) 646-1386 Chief, IPAWS Engineering, National Continuity Programs, DHS FEMA Gary.Ham@associates.dhs.gov Office: (703) 899-6241 Contractor, Systems Architect, IPAWS-OPEN Avagene Moore: Thank you Gary. Again, if you have a question or comment, you can change the color to purple indicating you wish to speak. I will call upon you by name. Once you have asked your question or made your comment, please change the color back to green. Audience Question: For the National Association of Broadcasters demonstration in April, will we be using CAP 1.2 and OPEN 2.0? Gary Ham: I am hoping we will be able to use OPEN 2.0, however it depends on this depends on this issue of Oracle 11G adoption in FEMA SOA. I am suspicious that if it the NAB event is in this timeframe, we will be DM-OPEN 1.0 for that. Audience Question: I am just getting into the IPAWS Discussion and don't have that much background. We have a Digital Alert System box that we bought three years ago. As a local agency, are we going to have to have the ability to create a CAP-compliant message? Gary Ham: Normally that would be handled by your vendor, and this program today is geared for the programmers who will implement the new requirements. Avagene Moore: Gary, speaking on behalf of the IPAWS OPEN SIG, we all thank you for the update today - you always do a great job of sharing with our virtual audience. To you the audience – thank you for being here today. We appreciate your presence, questions and interest. Please note Gary’s contact information is included on the closing slide and he is happy to help you if you contact him. It is our goal to keep you informed as progress is made on IPAWS and IPAWS OPEN. We hope you will join us each time we meet – you are important to the outcome of our mutual interests. Please stay in touch with us. We look forward to next month’s presentation on Weds Feb 16, and ask everyone to mark the date on your calendars and join us in Live Meeting for another good discussion. Amy will now tell you how to subscribe to our Mail Lists – Amy? Amy Sebring: If you would like to be added to the mailing list, please contact me at asebring@emforum.org. Please specify the Developer List or the Practitioner List or both. If you need a copy of the MOA Questionnaire, you can download via the Handouts icon. Avagene Moore: Thank you all – the IPAWS OPEN SIG is adjourned.