Senator John Thune (R-S.D.) is investigating how the FCC's compromise Lifeline proposal fell apart and what role the possible disclosure by the FCC of nonpublic information played in that process.
In a letter to FCC chairman Tom Wheeler, Thune, chairman of the Senate Commerce Committee, said events surrounding the FCC's March 31 meeting, at which the Lifeline proposal was voted, "raise new questions about the Commission's policies for the disclosure of nonpublic information."
The March 31 meeting was delayed for over three hours after the Republican-backed compromise was struck, and then fell apart after commissioner Mignon Clyburn concluded she could not support a cap on the Lifeline fund, which subsidizes advanced telecom to low-income residents. The FCC is migrating the fund to broadband but ultimately voted not to cap the fund, though approaching the $2.25 billion allocation will trigger a review of the fund.
Thune said the delays were "highly unusual—they certainly were for the generally punctual Wheeler commission—and cited media reports, including Broadcasting & Cable stories, about the compromise and the delay.
Thune said the proper functioning of the FCC depends on the confidentiality of deliberations and asked Wheeler to explain the disclosures of nonpublic information in those news reports, whether he or any other employee authorized disclosure and, if so, any legal justification for doing so.
Thune said the leaks of info appeared "designed to engage outside interest groups to disrupt the deal struck between the Republican Commissioners and Commissioner Clyburn."
He asked whether the FCC was planning to investigate who leaked the information about deliberations, and if not, why not.
Wheeler has said there was no such strategy to kneecap the compromise, and the suggestion that there was "balderdash."
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.