[EAS] Next Generation
Barry Mishkind
barry at oldradio.com
Thu Nov 13 15:22:32 CST 2014
At 01:57 PM 11/13/2014, Ed Czarnecki wrote:
>Adding such a feature is not overly complex via IP - developing the
>specification and coordinating with the parties will take a bit of time.
At the risk of sounding like something
involving the FEMA could be done in
a timely manner, without causing more
problems, maybe this will help:"
1. The FEMA (Neil) will generate a random series
of numbers. They will feed them to a
port number designated.
2. receiver manufacturers would simply add
code to monitor that port, and load
the numbers, FIFO. Software upload
provided to users.
3. Should an EAN come (or, frankly an RWT,
so it can be tested!), compare the number
in the message (could be the first thing
in the message, preventing a new set of
headers), and pass on or not.
4. Done. Secure, except from a takeover of the FEMA.
>Here's a radical proposal (from someone who's been going at it for 18 hours
>for 20 days straight). Consider the EAN code compromised, and simply
>replace it with another restricted event code. NEM = national emergency.
>RBD = Really Bad Day. Whatever. Just retire the letters EAN if they now
>present a "risk." The downside would be obsolete all legacy
>devices/converters, so I'm not necessarily pushing that.
The problem I have with this is that, like the EAN and other
similar tests, they are all over YouTube. Changing the code
would only work until the next test - and would not allow the
"open ended" timing without software changes. Since the
new code would be "done" as soon as the first YouTube
video was uploaded, the random number stored and compared
makes it easier to implement, faster (it could be as quick as
coders can do it), and basically secure, so long as the FEMA
and PEP sites are secure.
More information about the EAS
mailing list