<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="https://purl.org/dc/elements/1.1/"
     xmlns:dcterms="http://purl.org/dc/terms/"
     xmlns:media="http://search.yahoo.com/mrss/"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:cf="https://www.futureplc.com/rss/content-flags"
>
    <channel>
                    <atom:link href="https://www.nexttv.com/feeds/tag/title-6" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Next TV in Title-6 ]]></title>
                <link>https://www.nexttv.com/tag/title-6</link>
        <description><![CDATA[ All the latest title-6 content from the Next TV team ]]></description>
                                    <lastBuildDate>Mon, 16 Jul 2012 13:17:00 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ What Is Title 6 Video? ]]></title>
                                                                                                                                                                                                <link>https://www.nexttv.com/news/what-title-6-video-381860</link>
                                                                            <description>
                            <![CDATA[ What Is Title 6 Video? ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">fp3vVTsGz76WEieFjDLYD5</guid>
                                                                                                                            <pubDate>Mon, 16 Jul 2012 13:17:00 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Title 6]]></category>
                                                    <category><![CDATA[Translation Please]]></category>
                                                    <category><![CDATA[Leslie Ellis]]></category>
                                                                                                                    <dc:creator><![CDATA[ MCN Staff ]]></dc:creator>                                                                                                        <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                        <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Maybe this is happening to you, too. A conversation begins. It’s about over-the-top video, or usage-based broadband, or any of the tangents that go with the new world of video on TVs and screens not necessarily connected to a set-top box.</p><p>Then you hear it: “Title 6 video.” Here’s an example, from several batches of notes. “Look. To be a multichannel- video provider (MVPD), you have to comply with the Title 6 rules.” Here’s another: “Anyone with a video server at the edge of the network wants to think they’re an MVPD. But they’re not Title 6.”</p><p>And because “Title 6″ is a term that’s been around so long (nigh on 30 years), the natural reaction is to nod solemnly: Ah yes. Title 6.</p><p>Which raises the question: What is Title 6 video?</p><p>Short version: It’s an outgrowth of the Communications Act, and is the chapter that includes the Cable Act, etched in 1984. Title 1 is general info; Title 2 regulates common carriers; Title 3 applies to broadcasters; and so on up to Title 6, cable.</p><p>It mandates all the things one needs to do, in order to be a multichannel video provider. Or, in regulatory lingo, an MVPD.</p><p>Here’s a sampling of what’s in the Title 6 rules: Franchising. Closed captioning. Must-carry. Ownership. Emergency alerts. Blackouts. PEG (public, education and government) channels. Program access. Navigation devices.</p><p>There’s more, but it turns out that Title 6 is more dated than practical these days, given the volume and pace of technological change over the last 28 years. Why? Those rules were made at a time when signal paths were in silos, and few of them. Phone service came from the phone company over twisted pair. Cable TV came from cable operators over their plant.</p><p>These days, everything’s an app, with plenty of pathways into the home.</p><p>Should any guy with a video server at the edge of the network be considered an MVPD, without complying with Title 6 commitments? The knee-jerk answer is no. But maybe a better question is this: Rather than try to shoehorn old rules into a new scene, why not ask what’s to be expected from video providers?</p><p>There are those who would say that the over-the-top video community views such regulations as a tool kit, from which to help themselves to the assets of others. Take the good or doable parts - think program access and compulsory copyright. Leave the rest, like retransmission consent and the complexity of the Title 6 obligations.</p><p>That’s a very short look at a very complicated cog in the tech regulatory machinery. More to come.</p><p><em><br/>Stumped by gibberish? Visit Leslie Ellis at translation-please.com or multichannel.com/blog.</em></p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>