[EAS] EAS Digest, Vol 15, Issue 19

[Harold Price]

The footnotes indicate that the FCC is going to defer action on this until after they finish their review of the Nov 9 test. 

      "Accordingly, it would be premature to take any actions with respect to adding a new national EAS location code until after we have reviewed and processed the test data from the November 9, 2011 Nationwide EAS Test. Accordingly, we defer taking any action on this matter at this time."

The sticking point on this is the old legacy devices in the field, i.e., those that intermediary devices must depend on.  Many of those 16 year old devices can't handle a new 000000 code.  Some of those devices can't be updated.  The FCC can't mandate that those old devices be updated, only that they no longer be used if they don't conform with the new rules. Adding the 000000 code would make the use of the intermediary devices problematic.  Keeping EANs mired in 1996 may be an unintended side effect of allowing intermediary devices.

Harold

At 12:38 PM 1/19/2012, Steven C Johnson wrote:
>One item notably missing from the order is the assignment of a national location code such as 000000.  I did not see this addressed one way or another.  I can only assume that we are to continue using the DC FIPS code.  Anyone know for sure?
>--
>Steven C Johnson