[EAS] BLU Alert Comments.

[Ed Czarnecki]

Yes, it is rarely simple.  The DASDEC and One-Net (cable/IPTV version of the
DASDEC) manages over 50 digital (IP based) formats (including several
version of EAS-net to handle proprietary middleware signaling), and over 70
serial based formats used to communicate with downstream systems.  And these
formats are not just about forwarding the EAS or CAP content, not by a long
shot.  We're managing a range of signaling to a variety of systems.  Frankly
the alert information is the easy (and even minor) part of the exchange in
many cases.  

Radio can be blessedly simple compared to cable TV and IPTV implementations.
Broadcast TV is starting to migrate towards an IPTV environment in a lot of
ways.  And we spend a fair amount of time ourselves explaining why things
aren't as "simple" as some would like to characterize things.  And that goes
for broadcast TV too.

And BTW great fun is to be had when the middleware developer is overseas and
has no clue on what EAS is about.  And even more fun when the middleware
company gets bought and sold several times, and loses their institutional
knowledge - and we know more about their source code than they do.

-----Original Message-----

On Fri, 4 Aug 2017, Ed Czarnecki wrote:
> Not sure if you were being ironic, but part of this has existed for 
> quite a while - for example on the DASDEC,  the EAS-Net communications 
> protocol software provides data and audio transmission over a TCP/IP
network.
> EAS-net is supported by a wide range of automation systems for store 
> and forward (within the allowable transmission time) including