<?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"
>
    <channel>
                    <atom:link href="https://www.tvtechnology.com/feeds/tag/email" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Tv Technology in Email ]]></title>
                <link>https://www.tvtechnology.com/tag/email</link>
        <description><![CDATA[ All the latest email content from the Tv Technology team ]]></description>
                                    <lastBuildDate>Wed, 26 Feb 2020 16:20:37 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ FCC Now Requires LPTVs to Email Carriage Elections ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/news/fcc-now-requires-lptvs-to-email-carriage-elections</link>
                                                                            <description>
                            <![CDATA[ Unlike full power TV stations, will not have to make statements available for public inspection ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">kfevbSi6z2qxfGr6MKcGoj</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/yr6piBHNg93kxDtJGxBDba-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 26 Feb 2020 16:20:37 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[FCC]]></category>
                                                    <category><![CDATA[Regulatory &amp; Legal]]></category>
                                                                                                                    <dc:creator><![CDATA[ Michael Balderston ]]></dc:creator>                                                                                                        <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/yr6piBHNg93kxDtJGxBDba-1280-80.jpg">
                                                            <media:credit><![CDATA[FCC]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/yr6piBHNg93kxDtJGxBDba-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>WASHINGTON—</strong>The FCC has adopted a proposal that would require low power television stations that qualify as must-carry stations to send email notices of carriage election status to affected multichannel video programming distributors. This is a similar requirement the <a href="https://www.tvtechnology.com/news/fcc-proposes-to-bring-retrans-notification-process-into-the-21st-century"><u>FCC gave to full power TV stations</u></a> in 2019.</p><p>LPTVs will be subject to the same procedures for emailing MVPDs in the event of a change of carriage election status as full power TV stations. However, one area where they will differ is that LPTVs will not be required to make their carriage election statements available for public inspection.</p><p>In replacing the public file obligation, LPTVs, as well as qualified NCE translator stations, will be required to send a “single ‘baseline’ notice via email to MVPDs on which they will be seeking or expecting carriage in the 2021-2023 carriage cycle, even if they are making no change in their election status,” the FCC report and order reads.</p><p>All email notice to MVPDs must be sent by Oct. 1, 2020, per the FCC.</p><p>The full <a href="https://docs.fcc.gov/public/attachments/FCC-20-14A1.pdf" target="_blank"><u>FCC report & order</u></a> is available online. </p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Use This Email to Contact Enforcement Bureau ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/news/use-this-email-to-contact-enforcement-bureau</link>
                                                                            <description>
                            <![CDATA[ Effective Jan. 9, the FCC Enforcement Bureau has created a new general email address to use when responding to an enforcement action originating from a field office. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">dMPtKr5Hv6cukjYAnsQHdX</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/ZLoi8VwVcbnWe4tFvkUxcN-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 10 Jan 2018 14:45:00 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Business]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emily Reigart ]]></dc:creator>                                                                                                        <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/ZLoi8VwVcbnWe4tFvkUxcN-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/ZLoi8VwVcbnWe4tFvkUxcN-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>WASHINGTON—</strong>Effective Jan. 9, the FCC Enforcement Bureau has created a new general email address to use when responding to an enforcement action originating from a field office.</p><figure class="van-image-figure pull-" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' ><p class="vanilla-image-block" style="padding-top:56.25%;"><img id="ESaCWGxXaioxrxTMVQ3aUS" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/ESaCWGxXaioxrxTMVQ3aUS.jpg" mos="https://cdn.mos.cms.futurecdn.net/ESaCWGxXaioxrxTMVQ3aUS.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p>If you need to respond to an action, you should now email field@fcc.gov, rather than the individual three regions, according to the <a href="https://transition.fcc.gov/Daily_Releases/Daily_Business/2018/db0109/DA-18-23A1.pdf" data-original-url="http://transition.fcc.gov/Daily_Releases/Daily_Business/2018/db0109/DA-18-23A1.pdf">announcement</a>.</p><p>This applies to new enforcement actions and will be reflected in the documents sent by the Enforcement Bureau.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>