[EAS] IPAWS and NOAA

[Mike McCarthy]

One possible way around this duplication avoidance matter is to create a
serialized message code embedded within the header that downstream relay
partners could use to screen out duplicate messages. Something as simple
as a two character alpha-numeric code would be embedded as part of the
header. The decoder would compare that code to any messages received in
the past, say, 4 hours. If the serial code matches, it would either relay
(per box programming) or ignore and log.

This becomes exceptionally important if/when the NWS creates a broadcast
specific weather alert product that would be relayed exclusively by CAP.
Broadcasters will need to filter out those cross airing messages from NWR
and CAP to avoid duplication.

The serial code would follow the same thought process as the virtual red
envelope except there would be no security/validation look-up and fewer
digits.

Sure, it would require a change in the message header standard, rules,
programming changes, and adoption by the various silo stakesholders.

But if the goal is to get most broadcasters to auto-relay the important
call to action messages, the messages need to be shortened and duplication
avoided in addition to changing how polygons are geographically applied
over counties to reduce message flooding.

MM

On Sat, July 7, 2018 8:05 pm, Harold Price wrote:
> Dave,
>
> EAS vendors, FEMA, FCC, and NOAA, are continuing to look into the
> issue, even so far as considering changes to the basic EAS protocol.
>
> There are some other issues, including the intelligibility of lengthy