The Technology Policy Institute's Scott Wallsten says the FCC has provided no economic rationale to justify its new set-top box proposal, and provides no evidence of consumer harm from the current set-top marketplace or evidence that consumers would be better off under the FCC's proposal.
In comments to the FCC, Wallsten, VP for research and senior fellow at TPI, says that, by contrast, there is clear evidence that the set-top box marketplace is competitive.
Wallsten, says the FCC needs to explain why it believes the set-top marketplace is not competitive and why regulatory intervention is necessary.
FCC chairman Tom Wheeler has said the set=top marketplace is not competitive, pointing to the fact that 99% of boxes are still leased from MVPDs.
Wallsten says the set-top marketplace is robustly competitive. He also says that the FCC's proposal would do damage to the business models of both programmers and MVPDs.
"Despite the FCC’s assurances, given the many details involved in negotiations between programmers and MVPDs it is unlikely that existing contracts could survive the new rules," he told the FCC. "The new rules would change incentives facing both programmers and MVPDs with uncertain consequences. At a minimum, the FCC should take those concerns seriously and consider the potential effects of its proposed rules."
TPI supporters include both Comcast, the largest member of set-top proposal opponent, the National Cable & Telecommunications Association, and Google, one of the set-top proposals biggest backers.
Asked about that, a spokesperson for TPI said: "We have supporters from all sides of most issues we deal with, and we don’t take positions on issues as an organization - It allows the Fellows to be independent. Scott pretty thoroughly went through the FCC’s justifications for regulation and found them to be severely lacking.
The smarter way to stay on top of broadcasting and cable industry. Sign up below.
Thank you for signing up to Broadcasting & Cable. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.