WASHINGTON—The comment period has been extended for weighing in on the TV channel repack reporting requirements proposed Jan. 10 by the Federal Communications Commission. Comments are now due Feb. 17 with replies due Feb. 27.
“The Media Bureau hereby extends the filing deadlines for public comment in the pending proceeding proposing to require certain broadcast television stations that are not eligible to receive reimbursement from the TV Broadcast Relocation Fund but must transition to new channels during the post-auction transition period to provide progress reports,” the commission said in a Feb. 6 Public Notice.
The comment deadline was initially set for Feb. 6, but the Public Notice was not published in the Federal Registeruntil Feb. 2.
The proposed rules would require periodic progress reports from all auction-eligible TV stations, including those not eligible for reimbursement from the $1.75 billion relocation fund to be set aside from auction proceeds. Stations eligible for reimbursement comprise all full-power and some Class A stations involuntarily assigned to a new channel. Stations ineligible for reimbursements include reverse auction winners, non-Class A low-power TV stations and translators.
For more TV Technology coverage, see our spectrum auction silo.
“NAB Asks for Repack Reporting Tweaks”
Yes or no does not always the question answer, the National Association of Broadcasters told the folks at the Federal Communications Commission regarding a proposed form for periodic channel-repacking reports.
Jan. 10, 2017
“FCC Seeks Feedback on Repack Reporting Process”
Stations eligible for reimbursement comprise all full-power and some Class A stations involuntarily assigned to a new channel. The PN said a “small number of Class A stations are not protected during the repacking process, and if displaced as a result of repacking will not be eligible for reimbursement.”
Future US's leading brands bring the most important, up-to-date information right to your inbox
Thank you for signing up to TV Tech. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.