[EAS] 6th FCC report and order on EAS

Rich Parker rparker1 at gmail.com
Thu Jun 4 11:05:12 CDT 2015


I'm a little confused by this as well - especially given the extensive
work and recommendations from the last CISRIC I participated in  (and
I apologize, but changing jobs and locations has kept me out of the
loop for a while) - How in the world could they require 'updating' of
this information, while at the same time, deciding that SECC's 'can't
be trusted' to update the data themselves? How is this supposed to be
done, if the 'responsible parties' are considered 'too unreliable' or
'too untrustworthy' to update their own information for their state?

So we  "Subsequently, at its March 20, 2014 meeting, the
Communications Security, Reliability, and Interoperability Council
(CSRIC) also recommended that the Commission develop a federal
government database to contain EAS Participants' monitoring
assignments.78"

And as far as it goes, it does look like the basic ideas of using
pre-existing data is a good addition and implementation was preserved
-

but they then go on to say:

"32. We also do not adopt the suggestion that, because the ETRS
database will be used to construct the EAS Mapbook, State Emergency
Coordination Committees (SECCs) must be granted access to the ETRS
beyond that envisioned by the presumptively confidential nature of
ETRS filings.110 It is not feasible to provide SECCs with such access
without compromising the confidentiality of EAS Participant's filings,
or risking that the SECC might unintentionally delete or corrupt a
filing. Rather, we will, upon request from an SECC, provide the SECC
with a report of their state's aggregated data. 111 SECCs can use
these reports to remedy monitoring anomalies evident from EAS
Participant filings in their state.112"

Am I misreading this somehow? - if the primary underlying data is
public (via ULS/CDBS/published state plans) what is the problem here?
...or in modern parlance WTF?

Again, apologies if I'm just too far 'out of the loop' to parse this
correctly, but on the surface this seems like a big, fat, slap in the
face....

Don't get me wrong, a lot of this is very good - including some new
marine codes, which, until I moved to Alaska, had never occurred to me
that they might be very helpful...

Rich Parker
Director of Engineering
CoastAlaska, Inc.
360 Egan Drive
Juneau, Alaska
richp at coastalaska.org

On Wed, Jun 3, 2015 at 5:57 PM, Mike McCarthy <towers at mre.com> wrote:
> In para. 30, there is mention of a "day-of yes/no" test reporting in
> addition to the ETRS general filing. HUH??? I didn't see that mentioned or
> futher elaborated elsewhere.
>
> And more over, each station needs to keep that on-line database updated
> annually too? Are both put in place just to further enrich the all the
> counsels who will file on many station's behalf?
>
> That's just nuts.
>
> MM
>
> On Wed, June 3, 2015 7:09 pm, Edward Czarnecki wrote:
>> Out today. https://apps.fcc.gov/edocs_public/attachmatch/FCC-15-60A1.pdf
>>
>
> __________________________________________________________
> The EAS Forum Discussion List is hosted by the BWWG (Broadcast Warning Working Group). http://eas.radiolists.net
> Please invite your friends to join our Forum! The sign up is at: http://lists.radiolists.net/mailman/listinfo/eas
> ___________________________________________________________
>



More information about the EAS mailing list