[EAS] How should the IPAWS Alert - Update - Cancel message lifecycle work?

[Sean Donelan]

For the most part, the Emergency Alert System doesn't use the IPAWS CAP 
Alert - Update - Cancel lifecycle.  The EAS-CAP Industry Group 
implementation guide has a couple of paragraphs, but tries to avoid 
handling anything after the initial Alert CAP message. That made sense for 
EAS, because EAS is supposed to be a bell-ringer alert, not an on-going 
news-information service.

NOAA National Weather Service makes extensive use of the CAP 
Alert-Update-Cancel message life cycle. NOAA NWS' procedures appear 
internally consistent with itself, but I'm not sure how many NWS partners 
and non-weather partners procedures are compatible with the NOAA NWS 
message Alert-Update-Cancel lifecycle. It makes sense for the NOAA 
WeatherWire feed, but gets a little confused with processed through IPAWS 
to other alert channels.

This brings me to Wireless Emergency Alerts....

The FCC has changed WEA requiring mobile devices, i.e. cell phones, 
maintain WEA messages on the phone for 24 hours. That means the public is 
going to see a lot more stale WEA messages on their phones for longer time 
periods, even after the WEA message was canceled or superseded.

Are any groups thinking a better way for WEA and IPAWS to supersede and 
cancel messages, while still maintaining a 24 hour WEA history? Should the 
WEA history mark canceled or superseded messages, so the public knows the 
information is not current?