Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://feeds.feedburner.com/lxbCommLawBlog?format=xml

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  4. xmlns:dc="http://purl.org/dc/elements/1.1/"
  5. xmlns:atom="http://www.w3.org/2005/Atom"
  6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  8. >
  9.  
  10. <channel>
  11. <title>CommLawBlog</title>
  12. <atom:link href="https://www.commlawblog.com/feed/" rel="self" type="application/rss+xml" />
  13. <link>https://www.commlawblog.com/</link>
  14. <description></description>
  15. <lastBuildDate>Tue, 23 Apr 2024 23:08:36 +0000</lastBuildDate>
  16. <language>en-US</language>
  17. <sy:updatePeriod>
  18. hourly </sy:updatePeriod>
  19. <sy:updateFrequency>
  20. 1 </sy:updateFrequency>
  21. <generator>https://wordpress.org/?v=6.5.2&amp;lxb_maple_bar_source=lxb_maple_bar_source</generator>
  22. <item>
  23. <title>FTC Votes to Ban Noncompete Agreements</title>
  24. <link>https://www.commlawblog.com/2024/04/articles/broadcast-2/ftc-votes-to-ban-noncompete-agreements/</link>
  26. <dc:creator><![CDATA[Anne Goodwin Crump]]></dc:creator>
  27. <pubDate>Tue, 23 Apr 2024 23:08:36 +0000</pubDate>
  28. <category><![CDATA[Broadcast]]></category>
  29. <category><![CDATA[Federal Trade Commission]]></category>
  30. <category><![CDATA[FTC]]></category>
  31. <category><![CDATA[Noncompete Agreements]]></category>
  32. <guid isPermaLink="false">https://www.commlawblog.com/?p=16686</guid>
  33.  
  34. <description><![CDATA[<p>In late-breaking news, the Federal Trade Commission (“FTC”) has adopted a final rule banning new noncompete agreements for all workers and effectively nullifying existing agreements and requiring companies to notify most current and past employees that the company will no longer enforce such agreements. In a change from the prior FTC proposal, however, the agreements...… <a class="read_more" href="https://www.commlawblog.com/2024/04/articles/broadcast-2/ftc-votes-to-ban-noncompete-agreements/">Continue Reading</a></p>]]></description>
  35. <content:encoded><![CDATA[<p>In late-breaking news, the Federal Trade Commission (“FTC”) has adopted a final rule banning new noncompete agreements for all workers and effectively nullifying existing agreements and requiring companies to notify most current and past employees that the company will no longer enforce such agreements. In a change from the prior FTC proposal, however, the agreements may remain in effect for senior executives.</p>
  36. <p>This rule is scheduled to go into effect 120 days after publication in the Federal Register, though its future is a bit uncertain. Various business groups, including the U.S. Chamber of Commerce, have indicated that they will sue to stop the rule from becoming effective. After receiving over 26,000 comments, the FTC adopted the rule on a 3-2 vote. Proponents argue that noncompete agreements are unfair and suppress worker pay and entrepreneurship, while also imposing costs and unfair terms of competition on firms wanting to hire workers bound by the agreements. Business groups, on the other hand, say noncompete agreements are critical for protecting proprietary information and intellectual property and for justifying investments in workers and their training. Without noncompetes, employers would need to worry that after sinking much time and money into training, employees might immediately jump to a better-paying competitor that did not have those costs. Nondisclosure agreements might protect some secrets but would not fully solve the problem.</p>
  37. <p>Leaving aside policy questions, the dissenting Commissioners strongly questioned whether the FTC had the authority to issue such a blanket ban on noncompetes without an express directive from Congress. While various members of Congress on both sides of the aisle have introduced bills to reform noncompete agreements, none of them has been enacted. The dissenters argued that without a valid grant of authority from Congress, the final rule is unlawful. The retroactive nature of the ban adds further legal issues.</p>
  38. <p>While there does seem to be a general move toward requiring certain reforms in noncompete agreements, it remains to be seen how the new FTC rule will fare in court. It is sure to face strong opposition both on policy grounds and due to claims of regulatory overreach.</p>
  39. ]]></content:encoded>
  43. </item>
  44. <item>
  45. <title>Broadcast Station Contest Rules Aren’t Just for Contestants, They Apply to the Stations, Too!</title>
  46. <link>https://www.commlawblog.com/2024/04/articles/broadcast-2/broadcast-station-contest-rules-arent-just-for-contestants-they-apply-to-the-stations-too/</link>
  48. <dc:creator><![CDATA[Anne Goodwin Crump]]></dc:creator>
  49. <pubDate>Thu, 18 Apr 2024 21:48:27 +0000</pubDate>
  50. <category><![CDATA[Broadcast]]></category>
  51. <category><![CDATA[Contest Rules]]></category>
  52. <category><![CDATA[Contests]]></category>
  53. <category><![CDATA[FCC Proposed Fine]]></category>
  54. <category><![CDATA[Fine]]></category>
  55. <category><![CDATA[Radio]]></category>
  56. <category><![CDATA[Television]]></category>
  57. <guid isPermaLink="false">https://www.commlawblog.com/?p=16684</guid>
  58.  
  59. <description><![CDATA[<p>The FCC recently released a Notice of Apparent Liability (“NAL”) for a forfeiture of $8,000 that should be a cautionary tale for other broadcast licensees that conduct contests for listeners or viewers.  This fine arose out of the station’s failure to conduct a contest in accordance with its announced terms, and specifically to make payment...… <a class="read_more" href="https://www.commlawblog.com/2024/04/articles/broadcast-2/broadcast-station-contest-rules-arent-just-for-contestants-they-apply-to-the-stations-too/">Continue Reading</a></p>]]></description>
  60. <content:encoded><![CDATA[<p>The FCC recently released a Notice of Apparent Liability (“NAL”) for a forfeiture of $8,000 that should be a cautionary tale for other broadcast licensees that conduct contests for listeners or viewers.  This fine arose out of the station’s failure to conduct a contest in accordance with its announced terms, and specifically to make payment of a prize by the deadline which the station had established for itself.  The FCC found that this failure was a violation of its contest rules. </p>
  61. <p>Section 73.1216 of the FCC’s rules requires that broadcast licensees must fully and accurately disclose the material terms of any licensee-conducted contest and also must conduct such contests substantially as announced and advertised.  Included among “material terms” are not only eligibility restrictions and details as to how winners will be selected, but also the extent, nature, and value of prizes, which must be awarded promptly. </p>
  62. <p>In this case, Station KXOL-FM, Los Angeles, California, conducted a contest in 2019 which promised to award each winner a cash prize of $396.  KXOL-FM’s announced contest terms specified how and when winners would receive their prizes, with a self-imposed payment deadline of 30 business days after a winner had submitted all required documentation to the station.  One listener won the prize on October 24, 2019, and had turned in all of the required documentation by January 16, 2020, but the station did not award the prize until May 2021.  Although the FCC focused on this incident, it also indicated that KXOL-FM had admitted that payment of a large number of other prizes also was delayed. </p>
  63. <p>When asked to explain itself, KXOL-FM pointed to the beginning of the COVID-19 pandemic and inability to access files during the transition to work-from-home, a ransomware attack that disabled corporate IT systems from October 2020 until March 2021, and staffing shortages after the ransomware attack.  Unfortunately for the station, the payment deadline established by the contest terms was March 2, 2020, and the problems used as excuses all started after that.  No matter how compelling they may have been, they did not explain why the prize was not awarded when due.  That fact left the station with no reasonable explanation for what could only be described as undue delay in paying the prize.   </p>
  64. <p>As a result, the FCC determined that a fine was warranted.  Fortunately for the licensee, the decision was made that a forfeiture would be assessed for only the one incident about which the full facts were known and not for the other, admitted prize payment delays.  Less fortunately, while the base fine for violation of the contest rules is $4,000, the FCC has proposed a fine double that amount because the licensee’s corporate parent is large and prosperous.  It is not clear why good business management increases culpability, but the FCC has long said that profitable businesses may expect increased fines so that such punishments create some pain and are not viewed as acceptable costs of doing business.   </p>
  65. <p>The lessons from this case are that stations need to pay attention to the rules that they have established for contests, follow them carefully, and award the stated prize reasonably promptly.  Before announcing contest terms, a station should be confident that it can carry them out and has access to the prize described.  In particular, while a station should not unreasonably delay awards of prizes, it also should not set for itself too short a deadline because the licensee will be bound by its own rules.  Here, contest terms that allowed for a slightly longer period before payment was due might have made all the difference.  For this reason, stations would be advised to periodically review, and where warranted, update their contest rules.  If they have questions, they should consult with their counsel here at FHH.</p>
  66. ]]></content:encoded>
  70. </item>
  71. <item>
  72. <title>Comments on Proposed Rules for Program Originating Booster Stations Due May 16, Reply Comments Due June 17</title>
  73. <link>https://www.commlawblog.com/2024/04/articles/broadcast-2/comments-on-proposed-rules-for-program-originating-booster-stations-due-may-16-reply-comments-due-june-17/</link>
  75. <dc:creator><![CDATA[Mark Malonzo]]></dc:creator>
  76. <pubDate>Tue, 16 Apr 2024 21:27:05 +0000</pubDate>
  77. <category><![CDATA[Broadcast]]></category>
  78. <category><![CDATA[FCC]]></category>
  79. <category><![CDATA[Notice of Proposed Rulemaking]]></category>
  80. <category><![CDATA[NPRM]]></category>
  81. <category><![CDATA[Notice of Proposed]]></category>
  82. <category><![CDATA[NPRM Rulemaking]]></category>
  83. <guid isPermaLink="false">https://www.commlawblog.com/?p=16679</guid>
  84.  
  85. <description><![CDATA[<p>The FCC released a Public Notice today establishing deadlines for submitting comments on its proposed rules to permit limited, voluntary program origination on FM boosters.  Comments must be filed no later than May 16.  Reply comments must be filed no later than June 17.  The proposed rules would provide flexibility for stations to use boosters...… <a class="read_more" href="https://www.commlawblog.com/2024/04/articles/broadcast-2/comments-on-proposed-rules-for-program-originating-booster-stations-due-may-16-reply-comments-due-june-17/">Continue Reading</a></p>]]></description>
  86. <content:encoded><![CDATA[<p>The FCC released a <a href="https://docs.fcc.gov/public/attachments/DA-24-356A1.pdf">Public Notice</a> today establishing deadlines for submitting comments on its <a href="https://docs.fcc.gov/public/attachments/FCC-24-35A1.pdf">proposed rules to permit limited, voluntary program origination on FM boosters</a>.  Comments must be filed no later than May 16.  Reply comments must be filed no later than June 17. </p>
  87. <p>The proposed rules would provide flexibility for stations to use boosters to transmit hyper-local advertising and programming, independent of the primary station signal.  </p>
  88. <p>As discussed <a href="https://www.commlawblog.com/2024/04/articles/broadcast-2/hyper-local-programming-gets-a-boost/">in our prior post</a>, the FCC is seeking comment on issues including:  </p>
  89. <ul>
  90. <li data-leveltext="-" data-font="Times New Roman" data-listid="23" data-list-defn-props='{"335551671":0,"335552541":1,"335559685":720,"335559991":360,"469769226":"Times New Roman","469769242":[8226],"469777803":"left","469777804":"-","469777815":"hybridMultilevel"}' data-aria-posinset="0" data-aria-level="1">Whether to limit each full-service FM station to 25 program originating boosters; </li>
  91. <li data-leveltext="-" data-font="Times New Roman" data-listid="23" data-list-defn-props='{"335551671":0,"335552541":1,"335559685":720,"335559991":360,"469769226":"Times New Roman","469769242":[8226],"469777803":"left","469777804":"-","469777815":"hybridMultilevel"}' data-aria-posinset="0" data-aria-level="1">How to select between mutually exclusive booster applications; </li>
  92. <li data-leveltext="-" data-font="Times New Roman" data-listid="23" data-list-defn-props='{"335551671":0,"335552541":1,"335559685":720,"335559991":360,"469769226":"Times New Roman","469769242":[8226],"469777803":"left","469777804":"-","469777815":"hybridMultilevel"}' data-aria-posinset="0" data-aria-level="1">Whether rules should include a mechanism for addressing claims of predicted interference while the booster’s construction permit is pending; </li>
  93. <li data-leveltext="-" data-font="Times New Roman" data-listid="23" data-list-defn-props='{"335551671":0,"335552541":1,"335559685":720,"335559991":360,"469769226":"Times New Roman","469769242":[8226],"469777803":"left","469777804":"-","469777815":"hybridMultilevel"}' data-aria-posinset="0" data-aria-level="1">Whether to require broadcasters to synchronize the signal of a program originating booster with the signal of its primary station; </li>
  94. <li data-leveltext="-" data-font="Times New Roman" data-listid="23" data-list-defn-props='{"335551671":0,"335552541":1,"335559685":720,"335559991":360,"469769226":"Times New Roman","469769242":[8226],"469777803":"left","469777804":"-","469777815":"hybridMultilevel"}' data-aria-posinset="0" data-aria-level="1">Whether broadcasters should be required to notify all EAS participants monitoring the primary station that its booster originates programming; and </li>
  95. <li data-leveltext="-" data-font="Times New Roman" data-listid="23" data-list-defn-props='{"335551671":0,"335552541":1,"335559685":720,"335559991":360,"469769226":"Times New Roman","469769242":[8226],"469777803":"left","469777804":"-","469777815":"hybridMultilevel"}' data-aria-posinset="0" data-aria-level="1">Whether broadcasters should be required to maintain a political folder for the booster within the political file of its primary station. </li>
  96. </ul>
  97. <p><i>For more information or to discuss commenting on any of the proposed rules by the May 16 and June 17 deadlines, please contact your attorney at Fletcher, Heald &amp; Hildreth.</i> </p>
  98. ]]></content:encoded>
  102. </item>
  103. <item>
  104. <title>Fletcher, Heald &#038; Hildreth Attorney Peter Tannenwald Recognized by LPTV Broadcasters Association with Gravino Lifetime Achievement Award at NAB 2024 </title>
  105. <link>https://www.commlawblog.com/2024/04/articles/broadcast-2/fletcher-heald-hildreth-attorney-peter-tannenwald-recognized-by-lptv-broadcasters-association-with-gravino-lifetime-achievement-award-at-nab-2024/</link>
  107. <dc:creator><![CDATA[Madison Laton]]></dc:creator>
  108. <pubDate>Mon, 15 Apr 2024 23:46:49 +0000</pubDate>
  109. <category><![CDATA[Broadcast]]></category>
  110. <category><![CDATA[Class A]]></category>
  111. <category><![CDATA[FHH]]></category>
  112. <category><![CDATA[LPTV]]></category>
  113. <guid isPermaLink="false">https://www.commlawblog.com/?p=16674</guid>
  114.  
  115. <description><![CDATA[<p>At this year’s LPTV Broadcasters Association meeting during the NAB convention in Las Vegas, Peter Tannenwald, retired member of Fletcher, Heald &amp; Hildreth, received the Mike Gravino Lifetime Achievement Award. This award recognizes individuals who contribute to the advancement of the low power TV industry and who exemplify the highest standards of excellence in their...… <a class="read_more" href="https://www.commlawblog.com/2024/04/articles/broadcast-2/fletcher-heald-hildreth-attorney-peter-tannenwald-recognized-by-lptv-broadcasters-association-with-gravino-lifetime-achievement-award-at-nab-2024/">Continue Reading</a></p>]]></description>
  116. <content:encoded><![CDATA[<p>At this year’s LPTV Broadcasters Association meeting during the NAB convention in Las Vegas, Peter Tannenwald, retired member of Fletcher, Heald &amp; Hildreth, received the Mike Gravino Lifetime Achievement Award. This award recognizes individuals who contribute to the advancement of the low power TV industry and who exemplify the highest standards of excellence in their work with LPTV stations. Keith Larson, Larry Rogow, and Paul Koplin were also recognized for their service.  </p>
  117. <p>Over the course of his career spanning more than 40 years, Peter Tannenwald was an early advocate for LPTV stations and was instrumental in the creation of the Class A television service through the passage of the Community Broadcasters Protection Act of 1999.  Mr. Tannenwald attended President Clinton’s signing of the legislation.  </p>
  118. <p>Congratulations to Peter and all those honored by the LPTV Broadcasters Association!</p>
  119. <p><img fetchpriority="high" decoding="async" class="alignleft size-large wp-image-16682" src="https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-597x320.jpg" alt="" width="597" height="320" srcset="https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-597x320.jpg 597w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-300x161.jpg 300w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-240x129.jpg 240w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-768x411.jpg 768w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-1536x822.jpg 1536w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-960x514.jpg 960w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-670x359.jpg 670w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-335x179.jpg 335w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-224x120.jpg 224w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-168x90.jpg 168w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-84x45.jpg 84w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-40x21.jpg 40w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-80x43.jpg 80w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-160x86.jpg 160w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959-320x171.jpg 320w, https://www.commlawblog.com/files/2024/04/thumbnail_20240414_165959.jpg 1920w" sizes="(max-width: 597px) 100vw, 597px" style=" max-width: 100%; height: auto; "></p>
  120. ]]></content:encoded>
  124. </item>
  125. <item>
  126. <title>Hyper-Local Programming Gets a Boost</title>
  127. <link>https://www.commlawblog.com/2024/04/articles/broadcast-2/hyper-local-programming-gets-a-boost/</link>
  129. <dc:creator><![CDATA[Mark Malonzo]]></dc:creator>
  130. <pubDate>Fri, 05 Apr 2024 19:06:34 +0000</pubDate>
  131. <category><![CDATA[Broadcast]]></category>
  132. <category><![CDATA[FCC]]></category>
  133. <category><![CDATA[Notice of Proposed Rulemaking]]></category>
  134. <category><![CDATA[NPRM]]></category>
  135. <guid isPermaLink="false">https://www.commlawblog.com/?p=16672</guid>
  136.  
  137. <description><![CDATA[<p>On April 2, 2024, the FCC released a Report and Order (“R&amp;O”) and Further Notice of Proposed Rulemaking (“FNPRM”) adopting rule changes that will allow FM booster stations to originate up to three minutes of programming per hour.  Prior to adopting the changes, the FCC generally defined a booster as a “fill-in” translator that is...… <a class="read_more" href="https://www.commlawblog.com/2024/04/articles/broadcast-2/hyper-local-programming-gets-a-boost/">Continue Reading</a></p>]]></description>
  138. <content:encoded><![CDATA[<p>On April 2, 2024, the FCC released a <a href="https://docs.fcc.gov/public/attachments/FCC-24-35A1.pdf">Report and Order (“R&amp;O”) and Further Notice of Proposed Rulemaking (“FNPRM”)</a> adopting rule changes that will allow FM booster stations to originate up to three minutes of programming per hour.  Prior to adopting the changes, the FCC generally defined a booster as a “fill-in” translator that is restricted to retransmission of the primary station’s existing broadcast on the primary station’s frequency.  Now, the FCC has adopted an additional definition for “program originating FM booster stations.”  These boosters serve primarily as a fill-in station but originate programming on a limited basis.   </p>
  139. <p>The changes provide flexibility for stations to use boosters to transmit hyper-local advertising and programming, independent of the signal of their primary station.  A booster could, for example, air geo-targeted advertising and programming that is specific to a particular portion of the primary station’s signal contour. </p>
  140. <p>Pending adoption and final implementation of licensing, processing, and service rules, licensed broadcast stations may now apply for a renewable, one-year experimental authorization to originate programming over an FM booster.  The FCC is seeking comment on proposed processing, licensing, and service rules for boosters.  </p>
  141. <p><b>Proposed Processing, Licensing, and Service Rules</b> </p>
  142. <p><i>Applications for New Boosters, Notifications for Licensed Boosters</i> </p>
  143. <p>The FCC proposed processing new booster applications, whether used as fill-in stations or for program origination, on a first-come/first-served basis under existing application procedures.  The Commission is specifically requesting comment on how it should resolve or select between mutually exclusive FM booster applications. </p>
  144. <p>Under the proposed rules, licensees of existing boosters would not need to file a separate application to begin program origination.  Instead, licensees would simply file with the FCC’s  Licensing and Management System (LMS) system a formal notification at least <i>15 days prior to commencing</i> program origination.  Licensees would likewise need to file an LMS notification at least <i>30 days after suspending</i> operations.  The proposed rules also require that a booster suspend operations anytime that its primary station is not broadcasting. </p>
  145. <p>In addition, the FCC is seeking comment on its proposal to limit each full-service FM station to 25 program originating boosters. </p>
  146. <p><i>Interference  </i> </p>
  147. <p>With respect to interference, the FCC proposed to eliminate a rule that bars boosters from causing <i>any </i>interference to the primary station’s signal within the boundaries of the primary station’s community of license.  Instead, the FCC would maintain the general requirement that a booster cause no more than  <i>limited</i> interference to its primary station’s signal. </p>
  148. <p>The Commission noted that the existing rule for claims of predicted interference did not apply to booster stations.  The FCC is seeking comment on whether the rules should include a mechanism to address predicted interference while a booster’s FCC construction permit is pending.   </p>
  149. <p>The Commission is also requesting comment on whether it should require broadcasters to synchronize the signal of its program-originating booster with the signal of its primary FM station.  This would be to prevent self-interference. The FCC is similarly seeking input on whether codifying technical requirements for synchronization could impose unnecessary burdens on broadcasters. </p>
  150. <p><i>EAS and Political File Rules</i> </p>
  151. <p>Program-originating boosters would be required to receive and broadcast all emergency alerts in the same manner as their primary stations.  In light of that requirement, the FCC is seeking comment on whether it should nevertheless require FM primary stations to notify all EAS participants monitoring the primary station that its booster originates programming.  The FCC is also seeking comment on whether it should implement any additional EAS rules specific to program-originating boosters. </p>
  152. <p>Broadcasters that accept advertising on a booster would be required to maintain a political folder for the booster within the same online political file as its primary station.  The FCC is seeking comment on these proposed rules. </p>
  153. <p><i>Programming</i> </p>
  154. <p>Finally, the FNPRM proposed prohibiting program-originating boosters from broadcasting content that is already prohibited on its primary station.  For example, the program-originating booster of a noncommercial educational primary station would be prohibited from transmitting commercial broadcasts.  But noncommercial educational booster stations would be allowed to accept underwriting announcements targeted to specific areas.  </p>
  155. <p>Comments in this proceeding will be due 30 days from Federal Register publication of the NPRM, and reply comments will be due 60 days after such Federal Register publication. </p>
  156. <p><i>For more information or to discuss commenting on any of these proposed rules, please contact your attorney at Fletcher, Heald &amp; Hildreth. </i> </p>
  157. ]]></content:encoded>
  161. </item>
  162. <item>
  163. <title>FCC Reinstates Workplace Diversity Reporting Requirement</title>
  164. <link>https://www.commlawblog.com/2024/02/articles/fcc/fcc-reinstates-workplace-diversity-reporting-requirement/</link>
  166. <dc:creator><![CDATA[Madison Laton]]></dc:creator>
  167. <pubDate>Mon, 26 Feb 2024 16:45:19 +0000</pubDate>
  168. <category><![CDATA[Broadcast]]></category>
  169. <category><![CDATA[EEO]]></category>
  170. <category><![CDATA[FCC]]></category>
  171. <guid isPermaLink="false">https://www.commlawblog.com/?p=16668</guid>
  172.  
  173. <description><![CDATA[<p>The FCC issued an Order last Friday reinstating the collection of workforce composition data for television and radio broadcasters, requiring broadcast licensees to file Form 395-B, which collects race, ethnicity, and gender information about the licensee’s employees, on an annual basis.  The requirement to file Form 395-B had been suspended for almost 20 years, but...… <a class="read_more" href="https://www.commlawblog.com/2024/02/articles/fcc/fcc-reinstates-workplace-diversity-reporting-requirement/">Continue Reading</a></p>]]></description>
  174. <content:encoded><![CDATA[<p>The FCC issued an Order last Friday reinstating the collection of workforce composition data for television and radio broadcasters, requiring broadcast licensees to file Form 395-B, which collects race, ethnicity, and gender information about the licensee’s employees, on an annual basis.  The requirement to file Form 395-B had been suspended for almost 20 years, but in July of 2021, the FCC issued a Further Notice of Proposed Rulemaking in an effort to refresh the public record regarding the form and determine whether the requirement should be implemented again.  The Commission’s stated goal in reestablishing this requirement is to facilitate analysis and understanding of the broadcast industry’s workforce and changes and trends occurring in the industry. </p>
  175. <p>The FCC’s EEO rules prohibit employment discrimination on the basis of race, color, religion, national origin, or sex and require almost all broadcast licensees to develop and maintain an EEO program to ensure equal opportunity and nondiscrimination in employment policies.  Between 1970 and 2001, the FCC required the submission of Form 395-B, listing the composition of broadcasters’ workforce in terms of race, ethnicity, and gender.  After a series of court rulings which determined that aspects of the FCC’s EEO rules at that time were unconstitutional, and called into question the legitimacy of the Form 395-B requirements, the FCC suspended the Form 395-B filing requirement in 2001.  According to the FCC, these decisions did not directly implicate Form 395-B—they implicated how the data collected by the form was to be used.  Accordingly, the Commission claims to maintain the authority to require broadcast licensees to submit Form 395-B.   </p>
  176. <p>In reinstating the Form 395-B requirement, the FCC restates that diversity in media organizations is critical for successfully serving viewers, listeners, and readers, but the Commission also noted that station-specific employment data would not be used for the purpose of assessing compliance with EEO regulations.  The data collected with Form 395-B will be published publicly on a station-by-station basis.  Commenters have expressed concerns with how this publicly-disclosed information may be used, claiming it could stir third parties to place pressure on hiring processes.  In response, the Commission stated that it may reconsider its approach to such data collection if such issues arise, but it also stated that such concerns were overstated and outweighed by the FCC’s overarching goals in this proceeding.  If, however, the Commission views diversity of employees is key to a broadcaster’s public service, it would seem that Form 395-B records would necessarily be considered at license renewal time.  Dissents by Commissioners Carr and Simington echoed concerns regarding the value of the data collected and the potential for improper outside use of the publicly-disclosed data to pressure licensees’ hiring decisions.   </p>
  177. <p>The FCC also concurrently issued a Second Further Notice of Proposed Rulemaking on the establishment of a similar data collection requirement for multichannel video programming distributors on Form 395-A.  The FCC tentatively concluded that the collection of Form 395-A should be reinstated along with Form 395-B and that the data collected by this form should also be made available for public review.   </p>
  178. <p>Broadcast licensees should make preparations to comply with this revived filing requirement and may want to review the status of their EEO programs.  It is anticipated that the first filing of the revived Form 395-B will be due by September 30, 2024.  If you have questions about Form 395-B, Form 395-A or any EEO requirements, please contact your FHH attorney.</p>
  179. ]]></content:encoded>
  183. </item>
  184. <item>
  185. <title>FHH Protects Client Rape Victim’s Privacy in    U.S. Fourth Circuit</title>
  186. <link>https://www.commlawblog.com/2024/02/articles/litigation/fhh-protects-client-rape-victims-privacy-in-u-s-fourth-circuit/</link>
  188. <dc:creator><![CDATA[FHH Law]]></dc:creator>
  189. <pubDate>Fri, 23 Feb 2024 19:06:48 +0000</pubDate>
  190. <category><![CDATA[First Amendment]]></category>
  191. <category><![CDATA[Litigation]]></category>
  192. <guid isPermaLink="false">https://www.commlawblog.com/?p=16666</guid>
  193.  
  194. <description><![CDATA[<p>On February 21, 2024, an FHH attorney, Thomas F. Urban II, won an important victory for the firm’s client, Jane Doe, to protect her right to pursue her civil claims against her rapist without having to expose her identity.  Due to Urban’s efforts and those of his co-counsel, Walter Steimel of Steimel Counselors Law Group,...… <a class="read_more" href="https://www.commlawblog.com/2024/02/articles/litigation/fhh-protects-client-rape-victims-privacy-in-u-s-fourth-circuit/">Continue Reading</a></p>]]></description>
  195. <content:encoded><![CDATA[<p>On February 21, 2024, an FHH attorney, Thomas F. Urban II, won an important victory for the firm’s client, Jane Doe, to protect her right to pursue her civil claims against her rapist without having to expose her identity.  Due to Urban’s efforts and those of his co-counsel, Walter Steimel of Steimel Counselors Law Group, LLC, the U.S. Court of Appeals for the Fourth Circuit issued a published Opinion protecting the anonymity of Doe.  Doe’s counsel established that her assailant was liable for the rape after he not only refused to provide a DNA sample that would have confirmed his culpability but also failed to mount a defense on default judgment.  <i>Doe v. Sidar</i>, No. 23-1177 (4th Cir. 2024).  In acknowledging the need to protect Doe’s identity, the Fourth Circuit vacated an order issued by Senior Judge Claude Hilton of the U.S. District Court for the Eastern District of Virginia issued just eleven days before trial in the case was to begin, where Doe’s identity would have been revealed. </p>
  196. <p>In its Opinion, the Fourth Circuit held that it was “conclusively established that Cenk Sidar raped Jane Doe [the anonymous rape victim] in London in September 2017.”  Sidar is the CEO of a Washington, D.C.-based Artificial Intelligence company, Enquire AI.   As the Court explained,  </p>
  197. <p>“[t]he legal effect of a default judgment [issued by the district court for Sidar’s failure to provide the DNA sample] is that [Sidar] is deemed to have admitted the plaintiff ’s well-pleaded allegations of fact . . . and is barred from contesting . . . the facts thus established.”  For that reason, we must assume that Sidar “admitted that he . . . raped” Doe and the truth of her allegations about how he did so. </p>
  198. <p>The Fourth Circuit also acknowledged that “[t]here is a ‘presumption’ that parties must sue and be sued in their own names,” and that “[f]or that reason, few cases warrant anonymity.”  The Court evaluated Doe’s request for anonymity based upon the Fourth Circuit’s existing test, which looks at five non-exhaustive factors when ruling on motions to proceed by pseudonym.   </p>
  199. <p>In this case, the Court held that the district court’s “decision to remove Doe’s anonymity on the eve of the damages-only trial” strained the bounds of its permitted discretion in three ways:  First, the district court failed to adequately take into account the nature and strength of Doe’s legitimate interest in anonymity by seriously understating Doe’s legitimate privacy interests.  The Court held that the issues here were not merely sensitive—they involved intimate details of Doe’s sexual assault by Sidar and resulting psychological trauma.   </p>
  200. <p>Second, the Fourth Circuit found that the district court’s analysis was legally flawed in its suggestion that fairness considerations invariably cut against anonymity unless the opposing party was also proceeding anonymously.  Judge Hilton had ruled that allowing Doe to remain anonymous while requiring Sidar to use his name at trial was unfair to Sidar.  Noting that Sidar had never requested anonymity, the Fourth Circuit held that Sidar having been found liable for the rape through a default judgment weighed in Doe’s favor to use a pseudonym.   </p>
  201. <p>Third, the Fourth Circuit found that the district court’s decision was based on a “flawed . . . legal premise” because it did not address the fact that its entry of a default judgment tipped powerfully in Doe’s favor.  The Court held that because Sidar was already found liable and because further proceedings would be limited to determining the damages he must pay, the “risk of any unfairness to” Sidar from Doe’s continued anonymity was significantly reduced. </p>
  202. <p>For these reasons, the Fourth Circuit concluded that the district court exceeded the bounds of its discretion in its order requiring Doe to use her real name at trial, and thus vacated Judge Hilton’s order and remanded it with directions to reconsider in light of its opinion.   </p>
  203. <p>Thomas F. Urban II is a civil litigator who was recently named a <i>Best Lawyer</i> TM for commercial litigation in Virginia, with a specialization in First Amendment and privacy matters<i>.  </i>Urban was recently lead counsel for an <i>amicus </i>brief on behalf of several women’s groups such as the National Organization for Women and groups advocating for the protection of sexual assault victims filed in the appeal of the Amber Heard v. Johnny Depp case shortly before that case settled.  Currently, Urban and other FHH attorneys are counsel for Subspace Omega, LLC in an antitrust lawsuit seeking over $500 million from Amazon Web Services, Inc. in the U.S. District Court for the Western District of Washington.  Case No. 2:23-cv-01772-TL (W.D.Wa.).  Urban is also currently defending a favorable judgment for his clients Jeffrey Lohman and The Law Offices of Jeffrey Lohman in a RICO case against an appeal by Navient Solutions, LLC in the U.S. Fourth Circuit. </p>
  204. <p>If you have any questions about representation for future litigation, please contact Fletcher, Heald &amp; Hildreth. </p>
  205. ]]></content:encoded>
  209. </item>
  210. <item>
  211. <title>FCC Clarifies that AI-Generated Voices are Subject to TCPA</title>
  212. <link>https://www.commlawblog.com/2024/02/articles/fcc/fcc-clarifies-that-ai-generated-voices-are-subject-to-tcpa/</link>
  214. <dc:creator><![CDATA[Madison Laton]]></dc:creator>
  215. <pubDate>Fri, 09 Feb 2024 21:50:25 +0000</pubDate>
  216. <category><![CDATA[FCC]]></category>
  217. <category><![CDATA[Robocalls]]></category>
  218. <category><![CDATA[Telecommunications]]></category>
  219. <guid isPermaLink="false">https://www.commlawblog.com/?p=16664</guid>
  220.  
  221. <description><![CDATA[<p>Given the increasing power of artificial intelligence (AI) technologies to generate content that mimics human voices, the FCC issued a unanimous Declaratory Ruling clarifying that current AI technologies that generate human voices constitute “artificial or prerecorded voices” subject to the Telephone Consumer Protection Act (TCPA). The TCPA protects consumers from unwanted calls made using artificial...… <a class="read_more" href="https://www.commlawblog.com/2024/02/articles/fcc/fcc-clarifies-that-ai-generated-voices-are-subject-to-tcpa/">Continue Reading</a></p>]]></description>
  222. <content:encoded><![CDATA[<p>Given the increasing power of artificial intelligence (AI) technologies to generate content that mimics human voices, the FCC issued a unanimous <a href="https://docs.fcc.gov/public/attachments/FCC-24-17A1.pdf">Declaratory Ruling</a> clarifying that current AI technologies that generate human voices constitute “artificial or prerecorded voices” subject to the Telephone Consumer Protection Act (TCPA). The TCPA protects consumers from unwanted calls made using artificial or prerecorded voices by prohibiting the making of such calls to residential and wireless lines without the prior express consent of the party receiving the call.   </p>
  223. <p>With this Declaratory Ruling, the FCC seeks to deter negative uses of AI and ensure that the protection of the TCPA covers emerging technologies without unintentionally creating carve-outs for technologies that may otherwise be able to exploit perceived ambiguities in the FCC’s rules. Chairwoman Rosenworcel cited a recent scam perpetrated against potential primary voters in New Hampshire who received a call with an AI-generated voice that seemed to be that of President Biden, and which urged potential voters not to vote in the upcoming election. Other scams target parents or grandparents with voices that appear to be those of their children or grandchildren and request money to help the “child” get out of trouble. </p>
  224. <p>While the FCC’s primary target is scammers, the Declaratory Ruling makes clear that the TCPA applies to all calls made using an artificial or prerecorded voice. “[T]he TCPA’s demands fully apply to those calls and, thus, consumers can themselves choose whether to receive them.” Even if a live agent selects the prerecorded message to be played, the TCPA requires prior express consent from the called party. “[T]he presence of a live agent on a call selecting the prerecorded messages to be played ‘does not negate the clear statutory prohibition against initiating a call using a prerecorded or artificial voice.’” Likewise, “this rationale applies to AI technologies, including those that either wholly simulate an artificial voice or resemble the voice of a real person taken from an audio clip to make it appear as though that person is speaking on the call to interact with consumers.”   </p>
  225. <p>For both businesses that rely on telephone sales or marketing and telecommunications providers that offer outbound calling platforms, now is a good time to review your TCPA compliance polices generally and to ensure those policies cover AI-generated voices. If you have any questions or would like assistance with TCPA compliance, please contact your FHH attorney.</p>
  226. ]]></content:encoded>
  230. </item>
  231. <item>
  232. <title>Corporate Transparency Act Triggers  New Federal Filing Requirement for  Most Small and Medium Companies.</title>
  233. <link>https://www.commlawblog.com/2024/02/articles/uncategorized/corporate-transparency-act-triggers-new-federal-filing-requirement-for-most-small-and-medium-companies/</link>
  235. <dc:creator><![CDATA[Paul J. Feldman]]></dc:creator>
  236. <pubDate>Mon, 05 Feb 2024 20:44:31 +0000</pubDate>
  237. <category><![CDATA[Uncategorized]]></category>
  238. <guid isPermaLink="false">https://www.commlawblog.com/?p=16655</guid>
  239.  
  240. <description><![CDATA[<p>The federal Corporate Transparency Act (“CTA”), enacted by Congress on January 1, 2021, established new ownership disclosure and reporting requirements for most small and medium sized U.S. companies (“Reporting Companies”), including both existing and newly created companies. The deadline for filing the required report is January 1, 2025, but companies should not wait to review...… <a class="read_more" href="https://www.commlawblog.com/2024/02/articles/uncategorized/corporate-transparency-act-triggers-new-federal-filing-requirement-for-most-small-and-medium-companies/">Continue Reading</a></p>]]></description>
  241. <content:encoded><![CDATA[<p>The federal Corporate Transparency Act (“CTA”), enacted by Congress on January 1, 2021, established new ownership disclosure and reporting requirements for most small and medium sized U.S. companies (“Reporting Companies”), including both existing and newly created companies. The deadline for filing the required report is January 1, 2025, but companies should not wait to review CTA requirements and make this filing – there may be corporate steps that they have to take prior to filing.   The CTA’s requirement to disclose the owners of companies is designed to assist U.S. authorities in fighting tax evasion, organized crime, terrorism financing and money laundering.   But the impact will be felt by law abiding companies of all industries – including broadcasters and telecommunications companies.       </p>
  242. <p>The CTA requires that Reporting Companies file with the Financial Crimes Enforcement Network of the Treasury Department (“FinCEN”), personal identification information on the “beneficial owners” of their company at the time of the company’s formation.  The CTA also requires that such information be updated upon any change in beneficial ownership.    </p>
  243. <p><b>Who Needs to Report?</b> </p>
  244. <p>The CTA refers to companies that are required to file reports as “Reporting Companies.”    For the purposes of the CTA, a Reporting Company is defined to include any corporation, limited liability company, or other similar entity that is created by the filing of a document with the secretary of a state or similar office, or is formed under the laws of a foreign country and registered to do business in the U.S. by the filing of a document with the secretary of a state or similar office. So, sole proprietorships and certain trusts would not meet this definition.   In addition, applicants for new entities that meet the definition of Reporting Company need to report.   For the purposes of the CTA, “applicants” include the individual who directly filed the document that created or first registered a domestic or foreign Reporting Company, and the individual who was primarily responsible for directing or controlling the filing of the creation or first registration document.  </p>
  245. <p>The CTA contains a number of exceptions from the reporting requirement.  These exceptions include any entity that employs more than 20 people and has at least $5 million in annual revenue and a physical presence in the U.S. In addition, tax-exempt organizations do not need to comply with the reporting requirements.  Also subject to exceptions are publicly traded companies, “inactive” companies,  banks, insurance companies, certain registered investment companies,  investment advisors and registered public accounting firms.  </p>
  246. <p> </p>
  247. <p><b>What Information is Required to Be Reported?</b> </p>
  248. <p>The information that must be reported includes the identity of each beneficial owner of the Reporting Company, or each applicant to form a new Company. A “beneficial owner” is defined generally as an individual who, directly or indirectly, exercises substantial control over a Reporting Company or owns or controls at least 25 percent of the ownership interests of the Reporting Company. This reported information includes full legal names, dates of birth, residential or business addresses, and an identification number (such as passport or driver’s license).   The Reporting Company must also disclose information about the Company itself, including  IRS Taxpayer Identification Number (“TIN”) (including an Employer Identification Number (“EIN”)), while foreign Reporting Companies without a U.S. TIN must provide tax ID issued by their foreign jurisdiction.  </p>
  249. <p> </p>
  250. <p><b>Who Has Access to the Reported Information? </b> </p>
  251. <p>The Treasury Department states that the reported information will be maintained in a secure federal database. The information will be treated as confidential and will not be made available to the public. The information may only be disclosed to federal and state law enforcement agencies under certain circumstances for national security, intelligence, or law enforcement purposes. Foreign law enforcement may also request information through the appropriate channels. Financial institutions, with the consent of the Reporting Company, will be able to access the database for customer due diligence requirements imposed by state and federal laws. The Treasury Department may also obtain access to the information for tax administrative purposes. </p>
  252. <p> </p>
  253. <p><b>When and How are Reports Filed? </b> </p>
  254. <p>Fillings must be made through the <a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fbroadcastingalliance.us16.list-manage.com%2ftrack%2fclick%3fu%3d34b55aed8d167fd8d8be001e3%26id%3dc25dd5a0b5%26e%3d9e6172e3c3&amp;c=E,1,cLW5ZhC0qDS4OnATP8_jLe2LJ_Rn7pFw6lSvCygBSzuw0J0NW6U8F13IZ2oimMVfzVSh2h51k-6sjJtZn3KbpxXiA8n88Z7lFnplUAUSdfCEWRt1&amp;typo=1">BOI E-Filing System</a>.  Filing deadlines depend on when the Reporting Company was created.   Domestic Reporting Companies created before January 1, 2024, and any foreign entity that became a Reporting Company before January 1, 2024, must file by January 1, 2025.   Domestic Reporting Companies created between January 1, 2024 and January 1, 2025, and any foreign entity that becomes a Reporting Company after January 1, 2024, must file within 90 days of registration.    </p>
  255. <p> </p>
  256. <p><b>What if My Company Fails to Properly File a Required Report? </b> </p>
  257. <p>Under the CTA, companies that fail to file a required report may be subject to both civil and criminal penalties. Any party that fails to comply with reporting requirements or willfully files false information will be liable for fines of not more than $500 for each day that the violation, not to exceed $10,000, or two years of imprisonment, or both. There is a safe harbor for individuals who believe that a submitted report contains inaccurate information, and then voluntarily and promptly submit a corrected information report. </p>
  258. <p> </p>
  259. <p><b>What Should I Do Now? </b> </p>
  260. <p><b>-Assess the Facts:</b>  Entities should evaluate whether they meet the criteria of a  “Reporting Company.”  If an entity meets the criteria for reporting, then further  steps should be taken.  </p>
  261. <p><b>-Prepare for and Gather Information:</b>  Entities should gather and maintain the  information needed for reporting.  This may require changes to the entity’s  corporate by-laws, in connection with obtaining information about the beneficial  owners, or authorizing the filing.  </p>
  262. <p><b>-Consult:  </b>Entities may want to seek legal advice, particularly regarding whether  the criteria for Reporting Company applies to the specific entity, as well as  regarding other requirements for reporting.  </p>
  263. <p><b>-File a Report if Required:</b>  Companies should not wait until December to file –  it is easy to forget the deadline, and questions can arise that can delay the filing  process.  </p>
  264. <p> </p>
  265. <p>Please contact us if you have any questions.  Also, please contact us as soon as possible if you would like our assistance with this, as we must prepare for this work.      </p>
  266. <p> <img decoding="async" class="alignleft size-large wp-image-16656" src="https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-597x398.jpg" alt="" width="597" height="398" srcset="https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-597x398.jpg 597w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-300x200.jpg 300w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-240x160.jpg 240w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-768x512.jpg 768w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-1536x1024.jpg 1536w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-2048x1365.jpg 2048w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-960x640.jpg 960w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-670x447.jpg 670w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-335x223.jpg 335w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-224x149.jpg 224w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-168x112.jpg 168w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-84x56.jpg 84w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-40x27.jpg 40w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-80x53.jpg 80w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-160x107.jpg 160w, https://www.commlawblog.com/files/2024/02/pexels-marek-levak-2265488-320x213.jpg 320w" sizes="(max-width: 597px) 100vw, 597px" style=" max-width: 100%; height: auto; "></p>
  267. ]]></content:encoded>
  271. </item>
  272. <item>
  273. <title>FCC Releases NPRM Seeking Comment on Proposal to Require Subscriber Rebates for Retransmission Consent Blackouts</title>
  274. <link>https://www.commlawblog.com/2024/01/articles/broadcast-2/fcc-releases-nprm-seeking-comment-on-proposal-to-require-subscriber-rebates-for-retransmission-consent-blackouts/</link>
  276. <dc:creator><![CDATA[Daniel Brown]]></dc:creator>
  277. <pubDate>Wed, 24 Jan 2024 16:00:32 +0000</pubDate>
  278. <category><![CDATA[Broadcast]]></category>
  279. <category><![CDATA[Class A]]></category>
  280. <category><![CDATA[FCC]]></category>
  281. <category><![CDATA[LPTV]]></category>
  282. <category><![CDATA[Media]]></category>
  283. <category><![CDATA[Must-Carry]]></category>
  284. <category><![CDATA[NPRM]]></category>
  285. <category><![CDATA[Retransmission Consent]]></category>
  286. <category><![CDATA[Television]]></category>
  287. <category><![CDATA[.media]]></category>
  288. <category><![CDATA[Must carry]]></category>
  289. <category><![CDATA[Retransmission consent]]></category>
  290. <guid isPermaLink="false">https://www.commlawblog.com/?p=16653</guid>
  291.  
  292. <description><![CDATA[<p>On January 17, 2024, the FCC released a Notice of Proposed Rulemaking (“NPRM”) seeking comment on a newly proposed requirement for cable operators and direct broadcast satellite (“DBS”) providers, which, if enacted, would require those cable operators and DBS providers to make available rebates to their subscribers for programming blackouts caused by failed retransmission consent...… <a class="read_more" href="https://www.commlawblog.com/2024/01/articles/broadcast-2/fcc-releases-nprm-seeking-comment-on-proposal-to-require-subscriber-rebates-for-retransmission-consent-blackouts/">Continue Reading</a></p>]]></description>
  293. <content:encoded><![CDATA[<p>On January 17, 2024, the FCC released a <a href="https://docs.fcc.gov/public/attachments/FCC-24-2A1.pdf">Notice of Proposed Rulemaking</a> (“NPRM”) seeking comment on a newly proposed requirement for cable operators and direct broadcast satellite (“DBS”) providers, which, if enacted, would require those cable operators and DBS providers to make available rebates to their subscribers for programming blackouts caused by failed retransmission consent or carriage renegotiations. </p>
  294. <p>If adopted, the new rule would add an arrow to the Commission’s quiver as it seeks to address what the FCC states is an <a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3749577">increasing number and duration</a> of broadcast station blackouts across the country over the past decade.  This NPRM comes while <a href="https://www.commlawblog.com/2024/01/articles/fcc/fcc-releases-nprm-proposing-new-reporting-requirements-for-retransmission-consent-blackouts/">another FCC proposal</a> is being considered that would require multichannel video programming distributors (“MVPDs”) to notify the Commission when a blackout occurs due to a breakdown in retransmission consent negotiations. </p>
  295. <p>The NPRM specifically seeks comment on (i) how to apply the new rule; (ii) whether to specify the method that cable operators and DBS providers must use to offer the rebates and, if so, how they should issue rebates; (iii) the FCC’s statutory authority to adopt the proposed rebate rule; (iv) how the FCC should enforce the proposed rebate rule; (v) the costs and benefits of such a rule; (vi) the effects that such a rule would have on digital equity and inclusion; and (vii) any other alternative proposals to ensure that subscribers are made whole when they lose access to programming due to blackouts, which are inherently beyond their control.  The Commission also invites the public to provide comments on why the number of blackouts has increased so substantially in recent years.  </p>
  296. <p>If you have any questions or would like assistance with preparing comments to the NPRM, please contact your FHH attorney.</p>
  297. ]]></content:encoded>
  301. </item>
  302. </channel>
  303. </rss>
  304.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//feeds.feedburner.com/lxbCommLawBlog%3Fformat%3Dxml

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda