[EAS] Sage Update Available

[Sean Donelan]

On Mon, 4 Nov 2019, Tim Stoffel wrote:
> I think it's about what it cost.
>
> Only one of my clients, surprisingly, the one with the least money, has
> decided to upgrade their EAS box at this time. It would not surprise me
> if the FCC ends up having a big compliance problem with this rule.
> People don't like to be stiffarmed!

The IPAWS program management office can collect analytics about how many 
CAP boxes are polling using each connection protocol and vendor PIN. 
Although the aggregate data is semi-anonymous, IPAWS PMO should have a 
good idea how quickly EAS participants are migrating.  A clever I.T. 
person could likely traceback individual connections.

The November 8 deadline is a 'soft' deadline.  Participants can change the 
box configuration to ignore invalid signature problems.

However, sometime by the end of Q1 of calendar year 2020, I expect DHS 
OCIO to disable TLS 1.0 on the web site used by IPAWS. It shows up on the 
OCIO report card, and makes the DHS CIO look bad on his management 
reports. The IPAWS office won't have much control over that change.