Working Group 9 EAS-CAP Migration Roadmap

1. Working Group 9 EAS-CAP Migration Roadmap Chris Homer, Chair Ed Czarnecki, Co-Chair WG 9 – Alerting Issues Associated with CAP Migration Communications Security, Reliability and Interoperability Council CSR C

2. CAP-EAS Roadmap – Basic Questions • Initial questions that WG9 is tackling: • What CAP-EAS Distribution Network architectures already exist at the Federal, state and local levels? • What are the physical and data components of these systems? • What prospective new architectures could be on the horizon? • What are the interface requirements for these systems?

3. EAS Network Questions • Capacity • What is “sufficient” capacity to relay CAP messages, audio files, possibly multimedia efficiently? • Are redundant transport paths desirable and attainable? • Availability • How can access to data and service be made reliable and have low-latency? • Authentication • How to assure data comes from the appropriate source? • Data integrity and non-repudiation • How best to maintain the correctness/accuracy of data, protect against unauthorized modification, deletion, creation and replication, and provide audit trails? Can we identify any best practices? • Communication security • What best practices or measures are needed to ensure that information only flows between authorized end-points?

4. EAS-CAP “State of the Feds” • The IPAWS OPEN CAP message aggregator v3.0 • up and operational in a production environment since 30 Sept. 2011 (capable of accepting and disseminating CAP messages to properly configured compatible CAP/EAS devices) • Minor upgrade to v3.01 is scheduled during week of 19 Dec. 2011 • IPAWS OPEN production system delivered its first series of CAP messages intended for CAP/EAS devices on Monday, 5 Dec. 2011. • Regularly scheduled CAP EAS Required Weekly Test messages • To be delivered by IPAWS OPEN during the 11 AM hour in each of 9 US time zones beginning 12 December 2011.

5. EAS-CAP “State of the States” • Approximately 25 states are known to have contracted some form of CAP EAS origination/relay capability • At least 23 of these are either operational or in advanced pilot status. • At least 18 have “IPAWS-conformant” systems (i.e., with origination tools successfully completing IPAWS testing, with Declaration of Conformity) • Satellite & Internet are the dominant CAP distribution means • 17 states use satellite distribution (with or without Internet backup) • 6 states rely on Internet-only dissemination • Monitoring ranges from primary sites, to all sites • At least 2 states have formal EAS plans that refer to CAP monitoring capability • At least 2 states formally relay CAP messages to all EAS participants

6. State CAP EAS Initiatives(estimate of contracted or piloted initiatives, as of 12-08-11) Communications Security, Reliability and Interoperability Council CSR C

7. WG9 – Subcommittee Progress • WG 9-1: CAP migration for IPAWS requirements • Obtained representation from FEMA IPAWS office onto subcommittee • Assigned subcommittee chair: Ed Czarnecki, Monroe Electronics • Scheduling first meeting • WG 9-2: CAP Migration for state/local system requirements • Assigned subcommittee chair: Gary Timm, Wisconsin SECC • WG 9-3: Next Steps in CAP Migration • Assigned subcommittee chair: Kelly Williams, National Association of Broadcasters