<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>I listened to TWIT podcast with Rich Chenock, of ATSC 3.0
committee:</p>
<p><a class="moz-txt-link-freetext" href="http://atsc.org/news-release/atsc-board-names-rich-chernock-as-next-tsg-chairman/">http://atsc.org/news-release/atsc-board-names-rich-chernock-as-next-tsg-chairman/</a></p>
<p><br>
</p>
<p>He mentioned DRM as part of ATSC 3.0, detailed here:</p>
<p><a class="moz-txt-link-freetext" href="http://atsc.org/newsletter/atsc-3-0-where-we-stand/">http://atsc.org/newsletter/atsc-3-0-where-we-stand/</a></p>
<p><strong>APPLICATIONS AND </strong><strong style="line-height:
1.5;">PRESENTATION LAYER</strong></p>
<p>The applications and presentation layer represents essentially
the elements that the viewer experiences, including video coding,
audio coding and the run-time environment. The service model for
ATSC 3.0 allows for more complex services to allow broadcasters to
evolve their business. Major elements include:</p>
<ul>
<li>Enhanced linear TV, plus on-demand support</li>
<li>Subscription and pay-per-view (PPV) support</li>
<li>Conditional access and digital rights management (DRM)
capabilities</li>
<li>Mobile and fixed device, plus companion device support</li>
<li>Hybrid delivery (broadcast and broadband), combined with
pushed content</li>
</ul>
<p>This can't be good for MythTV, assuming same DRM rules about
decoding apply for broadcast as for cable. Maybe they won't apply
DRM to network shows, but not sure why they wouldn't if they
could.<br>
</p>
<p>OTA is the last refuge from this and it looks like this is going
away in a few years, some say 2018.</p>
<p><br>
</p>
</body>
</html>