5/31/23 – The FCC, in a last minute action, granted a waiver to the new rule that TV stations must audibly repeat any emergency text messages scrolling ont he screen. The wavier runs until 11/26/24.

5/22/23 – Florida’s RMT, scheduled for today, did not happen. Reason not yet known, but the FAB rescheduled it for the 23rd at 1:50 PM

5/17/23 – Digital Alert Systems has released version 5.1 software (click this link here) for the DASDEC. The company said this version was intended for all current units, including the DASDEC-II and One-Net models (shipped since 2016 with a 32/64-bit processor).

A version 5.2 is expectd this year, prior to the December deadline for upgrades – this will be at no cost to users with V5.x.

3/20/23 – All time zones: the IPAWS CAP RWT failed again, for the fourth week in a row.

According to information, for some reason, the test was *not* sent this morning.

If you are keeping score:

* Feb 20: RWTs went out normally
* Feb 27: RWTs went out with invalid signature
* Mar 6: RWTs went out with invalid signature
* March 13: RWTs went out with invalid signature
* March 20: RWTs were not sent

At this moment, it is unclear what will happen next week. But we will let you know when we do.

3/13/23 – All time zones should find the IPAWS CAP RWT failed again, for the third week in a row.

According to information, the new digital certificate is now due to be installed mid-week. The previous one expired in late February.

If you normally log the CAP RWT, mark this down as a failed test.  If you have a DASDEC and it looks like a normal test, you need to fix a selection at: Setup > Net Alerts >CAP Deconde, and uncheck “Accept unverifiable signed alerts” under “View Advanced Options.”

3/3/23 – We are informed that the FEMA still has only an old certificate, which means the RWT on Monday, March 6th will fail. 

The FEMA letter states:

EAS Participants,

The last scheduled RWTs (Monday, February 27) went out with an invalid signature. This means your EAS device should have received it but should have rejected it as invalid. Unfortunately, we will not have the signature issue resolved in time for the next scheduled RWTs (Monday, March 6) so you should expect similar behavior. This issue will be noted in the monthly report for March.

This issue does not affect EAS messages sent by state/local agencies, it only affects the IPAWS automated RWTs.

v/r
Mark A. Lucero, CISSP
Chief, IPAWS Engineering
FEMA National Continuity Programs

2/27/23 – The FEMA used an expired certificate, hence all the RWTs from IPAWS CAP failed.

2/10/23 – Sage Alerting announced their upgrade to meet the FCC’s 12/12/23 deadline will be ready in June, at a price of $159. 

This will be Rev96 and will require stations to have a Rev95 at any patch level before Rev96 will work. Stations that have purchased a new model 3644 since December 12, 2021 can get a free upgrade. 

1/26/23 – the FCC hit Fox with a $504k fine for misusing EAS tones.

1/9/23 – For the second week in a row, the regular Monday test from the FEMA on IPAW CAP did not happen normally. Last week only some areas got the test. This week no one did; the word from the FEMA is the tests “were not properly sent.”

If you do log the FEMA tests, this is the explanation to enter in the log: “Failed Test – per FEMA notification.” 

12/16/22 – Did you file a Form One on the ETRS this year? It is requred.

Of course, you did not. Until this week, the FCC did not open the ETRS (Emergency Test Reporting System) this year. And no, do not rush to the ETRS before 2022 ends. It will not open until January 3rd. (However, the FCC says that Form One will be “open” until February 28th. ) 

There is no indication yet of when the next NPT will occur –  likely sometime in the first half of 2023. 

12/12/22 – The FEMA advises their weekly RWTs were not sent to the Atlantic, East and Central time zones this morning.

In your logs, just put “failed, on notice from the FEMA.”

12/5/22 – We previously mentioned the FCC’s new rule that EAS boxes will need to hold for 10 seconds and run the audio from IPAWS CAP if available. 

All EAS boxes will need to be capable by next December. Right now DASDEC boxes are able to do this if on Version 4. The other manufacturers are preparing updates … to be announced.

11/23/22 – a draft NPRM has now been published in the Federal Register, with comment due 12/23. If adopted as written it will add more items said to strengthen security and operation readiness of the EAS (and WEA). The Commission will seek notification of any unauthorized access, annual certification of system cybersecurity, and how such controls are implemented. If adopted at the October Open Meeting on 10/27/22 it will go to Comments and then to be published in the Federal Register.

11/22/22 – The NWS, which has been testing PCA – Partial County Alerting – for the past year, is going roll it out in more areas in 2023, with consulation to modify/set boundaries in each area to better target alerts.

You can learn more here. And here.

11/14/22 – A fifth state has had their EAS plan approved. Alaska joins the others: IL, NV, AL, and MN.

The list of approved state plans is here.

9/29/22 – More EAS changes: The FCC has approved changes that may make alerts more user friendly. Within the next year or so, stations are expecting a software update to “select” IPAWS CAP audio when available over local LP audio. Also, multilingual alerts will be easier to use, and alerts on TV will be better formatted for the deaf and /or blind. 

Some adjustments to the way tests are worded has been arranged to make things clearer to listeners:

• The event code *EAN* will now be phrased as a “National Emergency Message,” instead of the old “Emergency Action Notification.”
• NPT will nowbecome “Nationwide Test of the Emergency Alert System.”
• The originator code “PEP” turns into “United States Government.”

9/7/22 – The FCC Chairwoman has circulated a Notice of Proposed Rulemaking (NPRM) regarding EAS. 

The idea is to bolster security of the EAS, reducing time stations may operate without a receiver, requiring stronger security, and yearly reports to the FCC that it is being done. 

Given the events in LA and Boston over the past week or so, this is becoming a major issue.

9/4/22

Reports and logs show someone in the Boston area tried to send an EAN, perhaps as a prank. Details are still coming in, but it seems someone took audio from the 2011 NPT or a movie and tried to send it out. 

In several cases, the DASDEC and Sage receivers noted a date in November being used and did not forward the alert. 

Why some air “talent” continues to think it is funny to “prank” they syatem is unclear, but this is likely to set off some more requirements from the FCC, which just instituted a requirement to report fake alerts.  

9/2/22

NBC News reports
“An evacuation order telling residents to leave Los Angeles immediately was accidentally broadcast on television Wednesday, authorities said. “

It apparently originated at the County of Los Angeles and referred to the “Eastern North Pacific Ocean” as also needed evacuation.

One might suspect a report will be made to the FCC?

8/10/22 – IL and NV now make three state plans now approved by the FCC. While the FCC required them to be submitted early last month, vetting is taking time. Also, some states are still having trouble finishing the task, but the FCC seems to be a bit patient for the most part.

8/2/22 – The FEMA and the FCC issued Public Notices warning about potential issues with EAS receivers causing some worry. Specifically, a hacker apparently bought one or more old DASDEC units and demonstrated an issue that has been known and largely fixed for the past three to five years. Any station doing minimal IT security and software updating is well protected. 

Bill Robertson of DASDEC (Digital Alert Systems) was on our Thursday video presentation to answer questions and share information. The video is located here. 

7/11/22 – The FCC has issued a Notice for any state SECC that has not been able to upload a current State Plan for EAS. There is also a page with a list of accepted Plans. (As of this morning, only Illinois is shown, although Washington and another state or two have filed but not yet been approved.)

4/28/22 – The FEMA announced during the NAB Spring Show that there was not going to be a National Periodic Test (NPT) this year, with one tentatively scheduled for early 2023.

2/20/22 – The NWS is moving along with Partial County Alerting, an attempt to reduce the load on some areas as relatively small areas are affected by some emergencies. Perhaps you saw the presentation the NWS did for the BDR last year.
It might motivate you to visit their page and comment on the proposals, which anticipate implementation next year.

Also, the NWS has even more information here. 

1/20/22 – Starting on January 27th, SiriusXM said they will enhance the value of their Preview Channel for EAS with weekly “log only” RWT’s as assurance for those who are taking advantage of this means to receive Primary Entry Point tests and alerts. (Some EAS Participants in the CONUS still cannot reliably monitor a PEP station. Some have already purchased low cost home SiriusXM receivers with analog jacks for this purpose. SiriusXM weekly tests will enhance the value of this means of PEP reception.) – Thanks to Richard Rudman.

1/10/22 – The RWT from the FEMA failed today for all time zones up to Hawaii. Word is that a software update killed the cron job – something that can happen to any of us! Tests will resume next week.

Just log that no RWT came from IPAWS this week.

12/31/21 – The report on the 2021 EAS NPT has been released by the FCC. According to their report, August 11 test reached 89.3% of participants, better than the 2019 test which reached 82.5% of participants, with 87.1% of those retransmitting the test. Some 6,300 participants (59% of the Radio, TV, Cable) did not report participation.

The FCC has noted that the next test will emphasize the mandatory nature of the participation. 

12/15/21 – During the Open Meeting this week, the FCC adopted the Proposed RuleMaking with several facets: a proposal to require broadcasters and other EAS particpants to use Internet-based alerts when available, rather than over the air alerts; another “to improve the clarity and descriptiveness of the visual messages” to better serve the hard of hearing. And there is a proposal to change EAS architecture to relay more visual information. 

The Commission is also continuing to explore potential changes in the basic architecture of EAS, given the Internet, ATSC 3, HD Radio, and other changes – although it does recognize the existing EAS can reach 90% of the country with audio alerts.  Should there be two (or more) EAS systems be put in place?

11/29/21 – Someone at Fox Sports thought it would be a good idea to run a promo for in the NFL Pre-game for a “FoxEmergencyAlert” … complete with a sound-alike EAS tone.  https://staging.thebdr.net/nal-watch-fcc-enforcement/Yes, it got worse. The link shown on the screen was just a dummy. But someone grabbed it and put up a page that, essentially, used the meme “Let’s Go, Brandon.” 

You can expect this one to turn up in the Enforcement Watch with a hefty fine … but there are still people out there that think it is funny.

11/15/21 – There was an “early termination of the Chron job” at the FEMA, and the Mountain, Pacific, Alaska, and Hawaii time zones did not get the weekly EAS test from the IPAWS/CAP server.

8/14/21 – What did we learn from the 2021 NPT?

Early reports indicate a large part of the country got “something” and while audio could be improved (always), a couple of sites found issues with their EAS receivers. Still, most were able to “relay something” – even if only the tones.

What we believe we know:

1. Stations using Premier as a source got tones, but no audio.
   1. This could be why Western NC stations had no audio
   2. Some stations in WA and OR likewise had silent NPTs.
   3. Kansas stations did not get audio, as the state primary, in Topeka had the no-audio test from Premier.
2. Stations using NPR got clean audio, but a slight fade a the end was reported.
3. Stations in the Philadelphia and South Jersey area did not get the NPT, as the PEP was apparently unable to relay.
4. The audio in Maryland was rather distorted and largely unintelligible. 
5. Reports from Ohio indicate either no audio or distorted audio there, as well as no audio in a number of locations in KY and MI.
6. Similar reports indicate that much of Florida apparently did not get the NPT. Tampa area had only tones/no audio. SW Florida got the NPT via NPR and LP1, clean.
7. Washington DC, LP1 had good audio, some others were degraded.
8. In West Virginia, station relying on the WV Metro News Network did not get the NPT as the WV MNN did not relay the test. 
9. In NW Missouri and some other places, including Southern Arizona, the audio was there, but very distorted – some thinking that it would be hard to hear. 
10. Cell phones expecting the WEA test alert were often disappointed, as it turns out that even if you are subscribed to WEA alerts – the WEA *test* alerts are not included. The instructions are on the FCC site here.
11. More than a few youtube videos show stations that did not run audio, or otherwise “bootlegged” the NPT. 
12. A lack of testing audio from NPR and SiriusXM was said to contribute to distortion or very low audio at some stations.
13. Similarly, each iteration of the audio through additional audio processors or A/D D/A conversions adds to the degradation of the message. 

Still, although we expect more information soon from the FCC and the FEMA, even with these notes, the vast majority of daisy chained stations seemed to handle the task. 

7/21/21 – If you have a Sage EAS box, the company has posted a new update “CR-Rev6” on their website that must be downloaded and installed by August 21st.

Digital Alert Systems has one here. And, Instructions are here.

For Sage: click here. 

Note: Use or non-use of the updates will not affect the August 11th NPT.  And it can be done any time before August 21st. 

7/21/21 – Sage and DASDEC have issued information to help you ensure your EAS receiver is programmed correctly for August 11th. Both presented on the BDR Lunch Gathering on Thursday, July 22. The video is here. 

7/20/21 – Clay Freinwald, Chair of the Washington State SECC has announced his retirement from the position. Why is this important?  Washington State is among the most active and pioneering with EAS activities, cooperation with local EM agencies, and Clay, in particular, has been an EAS evangelist across the country for well over 20 years. Clay says he will be available for helping transition, but has decided to let “younger ones” now carry the load. 

7/20/21 – the FCC has issued a Public Notice regarding the one-year deadline for filing State EAS Plans via the ARS, and the deadline for compliance with both the State EAS Plan content rules in sections 11.21(a)(1)-(7) and the EAS designations in section 11.18 of the EAS rules, is July 5, 2022.2

6/17/21 – As expected, the FCC has made some changes to the EAS during their Open Meeting.

• The 2021 version of the FCC’s Emergency Alert System Operating Handbook is now available, replacing the 2017 version.  FCC rules require that a copy of the Handbook be maintained by stations and be immediately available to staff responsible for authenticating messages and initiating actions. Download the 2021 Handbook here. Additionally, a docx version is available here.
• The FCC set up the new SECC requirements, including posting the State EAS Plan on the (restricted) ARS site. 
• False alerts must be reported by broadcasters, but now national, state, and local officials are able (and encouraged) to report not only false alerts but inappropraite alerts (Tsunami in Oklahoma).
• In a fit of correctness, the Presidential Alert has been renamed a “National Alert.”

6/10/21 – It is now official: The FCC’s PSHSB has issued a Public Notice designating August 11th at 2:20 PM EDT for the National Periodic Test of the EAS. 

5/29/21 – The FCC has set up the ARS for SECCs to upload their State Plans. At this time, it is not publicly available, but only to SECC people.

5/15/21 – Perhaps you are aware of the FCC’s ongoing plan to review Part 11, a proposal was set up to require Internet servers to add EAS delivery. One of the commenters – the NAB – made its view clear: trying to interface EAS to the Internet is not currently viable, as it would be too complex to do it in any useful way. Let us hope the result will be a technical one, not a political one. 

5/5/21 – We are encouraged by the willingness of the FEMA’s Mark Lucero to explain the issues that have confronted the IPAWS CAP RWTs since they changed servers. Mark graciously spent more than an hour directly answering questions posed. The video is here.

In addition, there have been reports of some alerts failing due to mp3 attachments. According to the FEMA, this is another effect of the server change, mostly affecting Everbridge users, due to the formatting of the URL for the audio. It is in the process of being corrected.

4/26/21 – The FEMA’s Monday morning RWT failed again – this time for stations that check the digital signature. Many receiver logs will show “digital signature invalid.” Thus, if that is what you got, just more the test “failed.” Some indications are that you might have gotten the test via a secondary source, like Em-Net. How receivers react to events though such second source may vary.

It is worth mentioning that 11.56 (c) requires EAS devices to check digital signatures.  

4/23/21 – The FEMA sent an unscheduled RWT this afternoon, around 4:30 EDT, using a different script, to see if they can fix what happened on Monday. The test used the 00000 code, which is normally only for EAN and NPT, so most boxes may not respond or log it as they would not be looking for 00000 for an RWT.

This was a test, and should not cause you to reprogram your EAS units.

4/19/21 – The FEMA was unable to send the RWT correctly this morning. Apparently, it seems to have affected mostly sage boxes rather than DASDEC/Monroe or Trilithic units.

We have been told there was a recent change in servers – and the new server had some trouble handling the normal script used. The result was some difficulty for sage units to decode. The IT folks are scrambling to correct the script used. This can be logged as a “failed test” if you did not get it. 

As the day progressed, it was clearer what happened, and that it involved all time zones in the US. 

4/13/21 – The FEMA is said to be close to locking in August 11 and 25 as the main and alternate dates for an NPT for the EAS this year.

Test is said to be based on the PEP system, which showed some major problems in 2019, during storms. WEA is also to be included.  More information is expected, including the Form (One, Two, Three) dates. 

3/29/21 – Digital Alert Systems has released software Version 4.3 for the DASDEC EAS boxes. The update s free, and contains security upgrades and a Single Sign On (SSO) feature so administering multiple boxes can be done with one login and password. 

3/22/21 – The FCC is moving the Notice of Proposed Rulemaking and Notice of Inquiry along. There are a number of items that broadcasters will want to notice.

You likely heard that the FCC wants the SECCs to ensure they are operating along the lines of the NPRM and adjust the information sent to the FCC on an annual basis; they want to provide from repeating of EAN would like to investigate Internet relay of alerts by streamers; they want to have more reporting of false alerts – and allow governmental agencies to report false alerts;  and make it impossible for cell phone users cannot opt out of  WEA alerts from the FEMA.

Comment and Reply Comment dates are set for relatively short periods: 21 days and 14 days. You are encouraged to read the NPRM and tell the FCC what you think on Proceeding 15-94. 

1/22/21 – There are reports of many stations not receiving the local RWTs nor those on each Monday  from the FEMA. This is almost exclusively Sage EAS boxes that have not been fully updated. The version 95 that many got last year did not include the CR rev5 patch. 

Checking your EAS receiver, under VERSION, you should see CR-REV5, P4     If not, get the latest download. 

1/21/21 – The National Weather Service offices that usually sent out an RWT on Wednesday, did NOT on January 20th, as part of an over-abundance of caution. Chief Operators reviewing logs should note the RWT was cancelled by the NWS.

9/22/20 – The National Weather Service has now introduced county subdivisions in some areas – Duluth, MN; Glasgow, MT; Rapid City, SD  and Tucson, AZ. EAS receivers in these areas should be programmed to respond to the subdivisions. Instructions are in the receiver manuals.

In addition, the NWS plans to install this capability at the Las Vegas office in the near future and then at other offices. Details on the Las Vegas proposal are provided here.

If you have technical questions about this new service, you may contact wayne.hart@noaa.gov or 240-938-1629.

For NWS Policy questions, you may contact  timothy.schott@noaa.gov or 301-427-9336

9/17/20 – The FEMA and the National Weather Service (NWS) have announced that the NWS will now be relaying “Non-Weather Emergency Messages (NWEMs, in bureaucratic speak) through the IPAWS – replacing the HazCollect program.
Right now, this is operating on a test basis in a limited number of markets during Q4 of 2020, with a national rollout in 2021.

 8/26/20 – Digital Alert Systems has prepared the small upload you need to make your EAS box work with the new FEMA certificate. The old one expires on October 28th. You can get the new one here

The FEMA certificate for CAP will expire on October 28th. Sage EAS boxes will require an update for this and a root certificate for downloading audio from IPAWS.  Digital Alert Systems also plans a tiny file to update the DASDEC machines. As of now, Gorman-Redlich says they do not need to do anything.

The FCC announced that Form One for the ETRS is not required this year, seeing as there will be no NPT.

According to the FEMA, support (EOS) for EAS receivers using IPAWS TLS security protocols 1.0 and 1.1 ended on July 6th. The FEMA had delayed this step for some 18 months since the initial EOS was announced, to give stations and entities time to upgrade their firmware. If you do not have TLS 1.2 installed, IPAWS tests and alerts will not function. The FEMA recommends contacting your EAS receiver manufacturer for more information.

At this point, you must have DASDEC 3.1 or later (4.2 is current); Sage needs rev 95 .. the current version; Gorman-Redlich requires at least ver 2.76.3; Trilithic/Viavi must be Version 3.0 or later (V19.10 is current).

The FEMA has opened a new web page “OpenFEMA” which is a database of all activity on IPAWS since June 2012. The Public Announcement is here.  Documentation is here. 

The FEMA announced today that the 2020 NPT for the IPAWS has been cancelled. The next test will be in 2021.

The IPAWS test this morning happened, but was one hour late in all time zones.

If you did not get an IPAWS test this week, still no need to panic – there was no RWT. The FEMA did not express a reason, but did confirm all time zones did not get a test today.

If you did not get an IPAWS test this week, there is no need to panic. It is probably due to the needed changes in the TLS security protocol and/or certificate.

Due to the inability of sage alerting to deliver the necessary software update for handing security protocol TLS 1.2 (Part 11.56) until this week, the FCC has issued a Public Notice stating that stations unable to install the update may operate until January 7, 2020 without further authority.

The FCC expects most stations to accomplish the update much more rapidly, but has noted the 60 day period in the Rules (Part 11.35) to help contractors with many stations, for example, not to be consumed with the upgrades to the exclusion of all else. Also, some entities require purchase orders to buy the upgrade, which now can be expedited.

If your station is unable to accomplish the upgrade by November 8th, a note in the EAS log is sufficient for the time being. (Users of any EAS receiver are also allowed the same period of time, but as the upgrade has been available for long time, the FCC is not noting the period merely for those who have no good reason for the delay. While there is no indication they are doing this at this time, it is not beyond possibilities for the FEMA to identify which stations are not polling IPAWS with TLS 1.2)

The FEMA has notified manufacturers that the new Federal Bridge certificate, needed to receive IPAWS/CAP tests and alerts after November 8th is now available.
     

NOTE: In addition to the new certificate, you need to be upgraded to TLS V1.2 protocols. DASDEC notes that their versions 3.1 and 4.1 are already TLS 1.2 ready. For sage units, you must get the upgrade Rev95.

IF YOU CANNOT DO IT BEFORE 11/8: IPAWS/CAP alerts/tests will not be received. If you are doing your best to update, but have time/availability problems, you should note it in the EAS log, that you were unable to accomplish this on time due to manufacturer delays. This is especially true for those of you who contact for a lot of stations.

Today’s IPAWS RWT from the FEMA was missed in the Central and Mountain Time Zones – due to a FEMA server issue. Stations may wish to make a note in the logs, or wait for the FEMA’s monthly report in a week or so, and attach that. The FEMA reports that all was OK in the Pacific Time Zone.

The FCC released a Public Notice and a list of settlements (totaling $634,000) from the Enforcement Bureau for misuse/abuse of the EAS (and WEA) tones. The settlements range from broadcast television (ABC’s Jimmy Kimmel Live! – $395,000) and radio (KDAY/KDEY – $67,000) to cable channels (AMC and Discovery). The FCC has said for some time it is serious about using EAS tones in promos, news, or commercials, although it has been somewhat lenient for news items following the Hawaii false alert.

There is one exception, the FEMA has produced a set of “simulated tones” which sound similar, but will not set off an EAS receiver, and that may be used for promos, news, etc.

Well, the 2019 NPT came. Perhaps the best way to comment is that there is a lot work to do with the PEP (PEP Map is here) and daisy-chain – the way the EAS works when the Internet is down. Reports from Test Day noted quite a few stations reporting clean audio, and forwarded the test. However, other reports  noted a number of issues:
          1. The test did not reach some areas and states. Florida generally missed the test, as did the upper peninsula of Michigan, and parts of Georgia.
          2. In many places, there was no audio. Wisconsin generally had no audio due to a receiver failure. Some stations in ND, CO, NC, and NH also got no audio.
          3. Many sites reported “scratchy,” “unintelligible,” or audio with something underneath the NPT.
          4. Stations pulling from Sirius got overly hot audio, fairly distorted.
          5. It appears that Sirius sent a second NPT an hour later, perhaps in error.
          6. Some stations reported the same problem with the FCC’s ETRS site, where they were unable to file Form Two, but received messages essentially saying “the server is too busy.” Those that got to file Form Two, sometimes had to wait for well over an hour (or more) to get confirmation emails.

Already, some of the problems have been identified, and a few places are planning a “statewide re-do” to see if the daisy chain can be improved and made more reliable.

On the other hand, several states had severe storms occurring, which made reception of some sources difficult (or impossible) or crowded a bit by the local storms. Also, there were a number of RWT’s launched during the day by stations – nothing bad, but unnecessary.

There is no date for the FCC to report on the test, but we can hope they are able to summarize things quickly, so SECC’s and LECC’s can work on corrections.

The Federal Register has published the FCC’s August 2018 changes to the EAS rules, which now require reporting false alerts – known to be false – to the FCC within 24 hours, and SECC’s filing news plans electronically.

The FCC sent out letters today to a large number of stations – presumably testing the contact information from the Form One filings. Some person Kamal … no phone or other contact info, although the FCC servers do appear in the headers. After some calling to the FCC, it appears this was an attempt by someone at the FCC to push out a Public Notice. The link to the Public Notice is at here.

A later email says that there was some error on their part at alerting@fcc.gov:

“You are receiving this email because you have filed in the ETRS or because you are an EAS Participant registered within an FCC database.?

“Some of you received an email earlier today from FCC Alerting.  The email was sent in error.  We apologize for the inconvenience.”

Everything You Wanted to Know About the 2019 NPT But Were Afraid to Ask!

Sage Alerting announced a required update on their EAS boxes. The update, required by November 8th, in needed to continue using IPAWS CAP feeds from the FEMA, which will be using TLS 1.2/1.3 (Transport Layer Security, previously known as SSL). This update is apparently NOT NEEDED before the NPT. At this time, it is understood that the upgrade will cost $349 per receiver.

Most other EAS boxes will not need an update to comply with the TLS 1.2/1.3. DASDEC reports that anyone with Version 3.1 or later (4.0) will be fine, with no further update needed now, nor in the fall.

The FCC has again extended the Form One deadline. According to the ETRS site, the Form One deadline is now August 5th. If you have any questions on what to, there are now videos at the top of the ETRS page.  Additionally, the quickest way to get help – contact is at etrs@fcc.gov. In case ETRS cannot help (they seem to rely quickly), the Public Notice shows legal issues may be addressed to Elizabeth Cuttner, Attorney Advisor, Policy and Licensing Division, Public Safety and Homeland Security Bureau, at elizabeth.cuttner@fcc.gov or Maureen Bizhko, Attorney Advisor, Policy and Licensing Division, Public Safety and Homeland Security Bureau, at maureen.bizhko@fcc.gov.