Commentary

Richard Martin
 

FCC Chair Must Face Down The Carriers In 700-MHz Auction Flap

I have wondered in this space before whether FCC chairman Kevin Martin has the, uhh, intestinal fortitude to pull off what will undoubtedly be seen as the defining task of his career: seeing through the auction of valuable 700-MHz spectrum so that it benefits consumers, breeds competition in the carrier-dominated U.S. wireless industry, and brings in many billions to the U.S. Treasury. Judging from events of the last month, the answer seems to be "Nope."

I have wondered in this space before whether FCC chairman Kevin Martin has the, uhh, intestinal fortitude to pull off what will undoubtedly be seen as the defining task of his career: seeing through the auction of valuable 700-MHz spectrum so that it benefits consumers, breeds competition in the carrier-dominated U.S. wireless industry, and brings in many billions to the U.S. Treasury. Judging from events of the last month, the answer seems to be "Nope."Let's recap, shall we? Verizon Wireless, the No. 2 U.S. carrier, filed suit three weeks ago to have the rules for the auction -- in particular the provisions calling for open access to devices and solutions over any network the auction-winner builds -- struck down as "arbitrary and capricious" (which, I must point out, is a fair description of the terms of many wireless contracts in this country). At about the same time, on Sept. 17, Verizon Wireless CEO Lowell McAdam and other executives met privately with Martin and the chief of the FCC's wireless bureau and staffers.

Since then, according to RCR Wireless News, Martin -- who made some fairly eloquent calls over the summer for open, competitive networks -- has been "aggressively pushing for prompt revisions to the 700 MHz open-access rule."


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

So, after a few rounds of whist and some martinis with Verizon suits, Martin changes his tune and now wants to scotch the very provisions on which he had previously staked his legacy. It's no wonder that interlopers who want to upset the carriers' oligopoly, like Google and start-up Frontline Wireless, have decried the "opaque" nature of the Verizon meeting and demanded that the chairman not waver from his previously stated positions.

"We hope the FCC sticks to its guns as it tries to introduce the open ethos of the Net to a small segment of the closed wireless world," wrote Richard Whitt, Google's D.C. lobbyist, on his policy blog yesterday.

Interestingly, Whitt now says that Verizon is using a clever feint to convince the commission to dilute the open-access requirements. Rather than striking down the provisions altogether, Whitt says, "Verizon appears to be arguing that . . . the requirements for open devices and open applications should not apply to a licensee's own devices."

Under this scenario, you could bring an unlocked device from a handset vendor to a Verizon-owned network, but you couldn't buy unlocked devices from Verizon -- a ploy that would preserve the cornerstone of the wireless carriers' fortress, their ability to control what their customers can do with the devices they sell them.

Martin looks like a clever high-school sophomore, and he's a somewhat colorless public figure (he entirely lacks the panache and quotability of his predecessor Reed Hundt, who happens to be a co-founder of Frontline). There's nothing in his biography to suggest that he has the sangfroid to be a staunch and vigilant supporter of the consumer in the face of corporate muscle. Let's hope he finds some.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links