[EAS] Who and when should 000000 be used?

Mike McCarthy towers at mre.com
Wed Sep 14 18:58:26 CDT 2016


Use should be consistent across all messages employing the ALL-USA FIPS
code. At this point, my understanding is only top level federal are to
send NPT, EAN, and EAT with the ALL-USA FIPS. I see no reason why not to
include the RWT in that pool...and to use it periodically.

It is further my opinion all industry and non-federal encoders contain a
firmware restriction which disallows/prohibits originating any message
with the ALL-USA FIPS code. I might also argue the same for the EAN given
it is a presidential level only activation. Aside from the virtual red
envelope, limiting EAN at the non-federal/local levels would go a long
ways towards preventing accidental triggers. EAT OTOH should be employable
by anyone...

If states want to do closed circuit EAN testing, they should coordinate
testing from the locations which will initiate the messages. Whether that
test can be coordinated by a NAWAS call is subject to further discussion
by those involved.

Just my random musings....

MM

On Wed, September 14, 2016 6:27 pm, Sean Donelan wrote:
>

> Should 000000 be limited to only national originators, i.e. Primary
> Entery
> Point (PEP) Org-Code or used by any type of originator (CIV, EAS, NWS)? Or
>  does this increase the risk of someone accidently sending a local EAS



More information about the EAS mailing list