[EAS] Required Periodic Test

Mon Nov 28 15:39:24 CST 2011

I like it... good idea...

However.

With the burying of them at 1am, 2am, etc, that's pandering to the
conglomerates. As the rule stands now, you cannot schedule RWT/RMTs at
all. I would suggest the same goes here. If you bury them in the
middle of the night, how are we to know if they actually worked?
(Besides logs, and sitting up at 3am to find out?) I would suggest a
"random time between 6a-10p". This ensures verification by a human
being. Automation is nice and all, but with something like EAS, i'm
just a little hesitant to "take the computers word" that it did what
it was supposed to, nor will i sit by my EAS box at all hours to find
out.

I like the rotating factor of the agencies, this allows everyone to
test their systems independently.

I however do not like the FCC website mandated reporting tool idea.
This just gives the FCC ammo to come after certain stations, nor will
the religious satellators comply with it. They'll be the first to
raise hell (so to speak) because they have hundreds of stations, none
of which except the primary actually has EAS hardware. It'd be a
full-time job for someone to enter in all the data for all those
stations within their network.

I do like removing the opt-out clause that's currently in place.
Everyone who holds a license is required to comply with EAS/CAP.

Withholding funding from the state is going to be a hard one to pass,
but it might actually get stuff done. Unfortunately, most states,
unless spelled out *word for word, line by line* exactly how much,
where it is, etc each state must do, will end up getting minimal
funding just to keep the federal money coming in. IE, throw a computer
in a corner somewhere, that should do it, right?!

If you're using and requiring CAP as the protocol, it can be improved
right now to be bi-directional communications between the end user and
the state/federal agency. They can mine this information themselves
with just a little footwork by the programmers of such boxes.

PEP:"Hey,this is FEMA, i'm sending a message"
Local Station: "oh, okay, what's the message?"
PEP: "RPT"
Local Station: "Oh, okay, i've received the message"

... 24 hours later ...

FCC: "Hey, this is the FCC server, would you please report your latest RPT?"
Local Station: "Oh, yes, we played the RPT at 14:21CST 28Nov2011
activated by FEMA"
FCC: "okay, thank you. This complies."
(Otherwise)
FCC: "This is not the date that was scheduled." (if this is the
response, then the local ENDEC should then log/send a message to
someone making them aware that something is wrong)

Similar to polling on SMTP/POP mail boxes. Of course, we'd have to
change the name from CAP to SKYNET.

Again, however, not hard once you're in the IP world to do these types
of transactions. Each issuing entity is given a "key" to identify
itself with, or a hash algorithm that the decoders can...decode
(redundant i know) to secure each transaction and account. If the key
does not fit, simply log the attempt, and do nothing.

I will stress however that all of the control *should* lie with the
state/local agencies as they're the ones doing 99% of the activations
of this system, the feds should just be nothing more than another
entry point, not "skynet" particularly. A nice distributed system will
give plenty of redundancy all over and can be made to work darn near
anywhere in the world. We're Americans, we innovate!

--
Alex Hartman

On Mon, Nov 28, 2011 at 2:23 PM, Bill Ruck <ruck at lns.com> wrote:
> Having spent most of this weekend in a turkey and pumpkin pie induced
> coma compounded by a head cold I have just been reading the mail.
>
> However, I do have the following suggestion.
>
> We recognize (1) one size does not fit all, (2) tests need to be
> meaningful and monitored, (3) parts of the existing system does work
> well and (4) this is a chance to start with a blank sheet of paper.
>
> I want to remind all that my goal is "The citizens of the United
> States deserve no less than prompt and accurate emergency public information."
>
> Take a look at this.  It is only a rough draft and clearly needs some
> of the rough edges cleaned up and the more vague areas clarified.
>
> Eliminate the RWT and RMT and replace it with the Required Periodic
> Test (RPT) as follows:
>
> 1.  Required Periodic Test (RPT) sent on a rotating basis every 15
> days starting with the first Monday in January at 12 Midnight.  The
> next test will be Tuesday at 1 AM; then Wednesday at 2 AM; etc.  RPT
> rotates through days and hours for a total of 20 tests a year.  The
> whole nation does the RPT at the same time.  (Since the world
> revolves around the Beltway use East Coast Time.)  Schedule the start
> of the RPT for :10 as to not interfere with top of the hour news or
> starting programs.
>
> 2.  Every other RPT (the first test, third, fifth, etc.) will be
> originated by a local agency as described in that local operating area plan.
>
> 3.  The other RPTs (the second, fourth, sixth, eighth) will be
> originated by state and federal agencies on an alternating rotating
> basis.  The state will originate the second, sixth, tenth, etc., as
> described in each state's plan.  The feds (White House, FEMA, NWS)
> will originate on the fourth, eighth, 12th, etc., as described in the
> federal plan.
>
> 4.  Each RPT will be reported within 72 hours by all
> participants.  The FCC will set up an intelligent web site (a first
> for them) to log the RPTs.  Sign in with your Facility ID and
> password.  Form is pre-filled with identification and
> location.  Check () YES or () NO.  If NO a dialog box appears with
> likely sources that can be checked.  If OTHER is checked a box
> appears to be filled in with the problem.  And another box appears
> labeled STEPS TAKEN TO RESOLVE PROBLEM.
>
> The data will be mined by the FCC.  If a whole area is missing an RPT
> then the originating agency for that test gets a visit from the
> FCC.  If just one participant reports missing the RPT too often they
> get a visit from the FCC.  The results will be published.
>
> 5.  Everybody participates.  Part 73, cell phones, personal
> communications devices, satellite program sources, Internet.  Sources
> that can not geolocate (e.g. a one way satellite service like Sirius)
> is exempt from local and state tests but do have to carry federal
> tests.  If Earthlink can send emails on how wonderful they are they
> can also forward a CAP formatted email message.
>
> 6.  CAP will be the protocol to be followed.
>
> 7.  The feds will provide grants to local and state agencies to write
> the plan and to support the RPTs.  Failure to comply with the plan at
> the local and state level will result in the withholding of ALL
> federal funding as well as potential loss of ALL Part 90
> frequencies.  (Justification: Eligibility for Part 90 is "Government
> activity protecting life and property."  A licensee that fails to
> protect life and property by not participating in the plan is no
> longer eligible to hold a license.)
>
> 8.  No broadcast station will originate any RPTs or messages, only
> local, state, and federal agencies.
>
> 9.  Congressional action may be required to implement this plan.
>
> Advantages:
>
> 1.  All streams to consumers are represented.
>
> 2.  Both a carrot and a stick are used to encourage local and state
> participation.
>
> 3.  Regular meaningful tests.
>
> 4.  Tests that are reported.
>
> 5.  Because each local and state plan can be customized to the needs
> of the area and state this is not a "one size fits all" plan.
>
> I know that there are people much smarter than I on this list (like
> most of you...) so please improve it.
>
> Bill Ruck
> Curmudgeon
> San Francisco
>
> _______________________________________________
> This is the EAS Forum Discussion List
>
> Please invite your friends to join our Forum!
> http://lists.radiolists.net/mailman/listinfo/eas
>
> And, remember the main page: http://eas.radiolists.net
>