[EAS] Some clarifications RE: EAS vendor support for TLS versions

[Ed Czarnecki]

Dear colleagues:
 
In light of a robust discussion of EAS software updates, I wanted to setting the record straight on a number of points on NPTs, TLS and software updates, only as relates to Digital Alert Systems:
 
-	When we learned of the planned IPAWS TLS update - in April 2018 - we immediately checked to re-verify that our DASDEC v3.0 software would handle that update.  Both v3.0 and v4.0 will accommodate the TLS update.  No further action is required on the part of DASDEC users if you are using either v3.x or v4.0
 
-	Both DASDEC v3.x and v4.0 follow the FCC requirements for the NPT test.  No further action is required on the part of DASDEC users if you are using either v3.x or v4.0
 
There are many important reasons to consider upgrading to v4.0.  However, NPT and TLS are not among those reasons.  We were mindful to include forward-looking support in v3.0.  However, I will take a moment to note that v4.0 includes a complete OS upgrade (improved operating and security), Triggered CAP Polling(tm), and greater flexibility for future value-added enhancements.  V4.0 is a highly recommended but optional update.
 
Digital Alert Systems has never issued a fee-based software upgrade solely for regulatory or compliance purposes.  When the CAP capability was mandated by the FCC, we provided support for IPAWS CAP to all existing customers for FREE. as a free update.  All other vendors' systems required purchase of a new CAP unit or a CAP converter.  We did not.  When FCC clarified some of its rules regarding the EAN, we issued a free update to that as well, in the form of v2.6 with the Dynamic Validation Window(tm).  

The first fee-based update was v3.0 - coming after 12 years of free software updates.  Strictly speaking, DASDEC updates have not come out "every three years" - looking back at our software lifecycle of v1.0 through v4.0 the overall average is 5.3 years between any major update.  And, up till then, v3.0 was the ONLY fee-based update we had ever issued.  Statements that we had been charging "all along" are factually incorrect.

Additionally, we don't charge for support, so any customer going all the way to 2004 can call and our support team will help them in any way possible. 

V4.0 has been released as an optional though strongly recommended upgrade for our users.   At the same time, we deprecated development support on v3.0 because, frankly, it made no sense to continue patching a system that had become obsolete with an unsupported OS.  Hence, the move to the optional v4.0 platform upgrade.
 
V3.0 will function without issue for purposes of the NPT test and the FEMA TLS update.  And v3.0 will accept a certificate upgrade for FEMA IPAWS, when that is available for the Nov 2019 cert change.

Best regards,
Ed

Edward Czarnecki | Senior Director - Strategy & Government Affairs | ext. 122
Digital Alert Systems
100 Housel Ave., P.O. Box 535, Lyndonville, NY 14098
www.digitalalertsystems.com

-----Original Message-----
From: EAS <eas-bounces at radiolists.net> On Behalf Of Sean Donelan

Its Saturday, so I tried some experiments on a few different EAS boxes. 
I configured each EAS box to use a fake IPAWS server, and checked what each EAS vendor supported.  No actual FEMA servers were harmed or used :-)

DASDEC/Monroe - DASDEC-1EN v4.0-7 - supports TLS v1.2 Sage Systems - ENDEC 3644 v89.34 - supports TLS v1.0 Trilithic/Viavi - EASyCAP Broadcast 3.03.03 - supports TLS v1.2

__________________________________________________________
The EAS Forum Discussion List is hosted by the BWWG (Broadcast Warning Working Group). The Core members of the BWWG are Adrienne Abbott, Clay Freinwald, Suzanne Goucher, Barry Mishkind, David Ostmo, Darryl Parker, Richard Rudman, Gary Timm, and Sharon Tinsley. http://eas.radiolists.net Please invite your friends to join our Forum! The sign up is at: https://lists.radiolists.net/mailman/listinfo/eas
___________________________________________________________