[EAS] This weeks IPAWS RWT

[Dave Turnmire]

I'd like to note two key observations on my DASDECs for today's alerts:

 1. All IPAWS alerts originated from emergency management in Idaho were
    received w/o problem, with my DASDEC indicating they have a valid
    signature.  In our case, those were all originated via AlertSense
    under the same COG but from different offices (one state, one
    county).  So... while it is important for FEMA to sort out this
    current problem, at least I have a reasonable degree of confidence
    that if we had a "real" alert to issue... that the public would get it.
 2. As has been the case in at least one previous occasion, I MISSED the
    fact that the FEMA originated IPAWS alerts had failed due to a bad
    signature, because on the DASDEC, it is literally mentioned "in the
    fine print".  I don't know how other EAS boxes behave in this
    regard, but my hope is that a future release of the DASDEC software
    would implement a simple change of putting critical message failures
    such as a bad digital signature in red letters so it is easily
    noticeable.  I still like the fact that a bad message shows up in
    the log... I just want my attention drawn to the fact there was a
    problem that would keep it from being forwarded had it been
    something other than an RWT.

Dave