For anyone interested, I'll be participating in a panel at this event sponsored by Arts and Lab. Should be an interesting and robust debate about the upcoming evolution of networks. My panel also features Rob Topolski, Richard Bennet, and Dave Farber.
I recently complained that no one else ever seems to follow the record on the network neutrality stuff. But Commissioner McDowell took the prize for failure to remember what he had previously voted for in this very proceeding back in March 2007 when the Commission voted out the Notice of Inquiry that started this whole thing. Mind you, McDowell should not feel too bad, given that nobody else at the FCC seems to remember this stuff either. Not when they wrote the Comcast/BitTorrent Order, nor even when they wrote the Notice of Proposed Rulemaking last week. Despite the fact that both items are actually in the same blasted docket. Because good God almighty, how hard is it for the staff at the FCC to actually know the friggin' docket? It's just the basis for this entire proceeding. And the entire collective agency cannot remember that it voted as settled law by 5-0 that it has authority to regulate and enforce network neutrality rules. And that McDowell not only voted in favor, he explicitly concurred!
I swear, it's enough to make a poor obsessed policy wonk tear out what's left of his hair and beard.
On the eve of the FCC's upcoming Network Neutrality rulemaking, Canada has now settled its definition of “reasonable network management” and set rules for traffic throttling. Amazingly, the rules the Canadian Radio-television and Telecommunications Commission (CRTC) settled on for “reasonable network management” look a lot like the standard our own FCC settled on in the Comcast/BitTorrent Order, but even stronger on the notice and transparency side. Hopefully, the FCC is paying attention here as it considers its own rulemaking on the definition of “reasonable network management.”
You can read the CRTC press release here and the detailed order here. The CRTC also says that it will sue this new framework “to review practices that raise concerns or generate complaints.” i.e., it will treat this as the equivalent of the Internet Policy Statement and entertain complaints like the Comcast/BitTorrent complaint.
While this means I will no longer have my realtime experiment to see if unrestricted traffic shaping screws up broadband, it does make the FCC look less like whacked out nutbars who don't understand engineering and threaten the entire internet and more like foresighted regulators who are ready now to move on to a formal rulemaking rather than merely rely on a framework.
The problem with argument is that broadcasters could already do this. Under 47 USC 336(b), broadcasters can use their digital spectrum to provide “ancillary and supplementary services.” In a series of orders, the FCC has said that as long as full-power broadcasters provide one free over the air digital channel, they can do whatever they want with the remaining spectrum — including lease it out in the secondary markets to someone else. Under the statute, broadcasters need to pay a fee for any such ancillary services that would be the functional equivalent of what the broadcasters would have paid for the spectrum at auction (47 USC 336(e)), which the FCC has fixed at 5% of any annual revenue from the ancillary services.
Adam Thierer, long-time friend and opposite number in the Libertarian Camp, has just been named President of the Progress and Freedom Foundation, replacing Ken Ferree. Frankly, I hope Adam will bring a dose of new thinking tp PFF, since Ken Ferree has pretty much spent the last several years explaining at great length why everything the Powell FCC did was wonderful, rational, and the epitome of all that was right in public policy whereas Kevin Martin was a revisionist wanker and traitor to the Neocon Revolution. Much as I'm sure this was amusing for the participants, it did get old after a bit.
I expect Adam and I (and PFF) will continue to disagree on most things regulatory. But I have found in the past that Adam is an intelligent and engaging person willing to actually listen to what other people have to say before responding — and generally sticking to substance rather than the ad hominem or mindless talking points favored by too many here in DC. In other words, he is the sort of Free Market enthusiast/anti-regulatory advocate who makes me work for a living and is a necessary counterpoint to make any system work.
I wish him luck, but (if you will excuse me) not too much success.
An interesting tidbit from Washington Post Reporter Celia Kang's interview with Ruth Milkman, the FCC's Wireless Bureau Chief. Of interest, Milkman states that the application of network neutrality to wireless would still allow cellular companies to lock cell phones to wireless providers.
How are the proposed rules different from conditions on the C block during the 700 MHZ auction? There, net neutrality rules were put in place that allow any device to attach to the network and prevent Verizon Wireless, who won the spectrum, from blocking Web content.
The difference between what we are thinking about in the general NPRM (notice of proposed rule-making) and the C Block is that we are not proposing a no-locking rule. So I guess it’s no block but not no-lock. If consumers can get an unlocked device and not harm the network, the consumer ought to be able to attach that device to a network. Does a service provider have to unlock the device it provides to the consumer? The draft doesn’t go that extra step.
To encourage broadband deployment and preserve and promote the open and interconnected nature of the public Internet, consumers are entitled to connect their choice of legal devices that do not harm the network.
(emphasis in original). This is generally taken as the application of the “Carterfone” principle (and the Internet Policy Statement cites the Carterfone decision in case anyone misses this point). This is the decision that held that AT&T could not refuse to allow you to connect any device, like and answering machine or a phone you owned or a dial-up modem, to the phone network.
Milkman is right that the freedom to connect to a network is not necessarily the same thing as the freedom to move a device that comes locked from one network to another. In the old days, it wasn't necessary to say it that way because there weren't other networks to attach your device. The question was whether somebody other than Ma Bell could make something and attach it to the phone network. By the time we got to multiple wireline networks serving the same neighborhood, the consumer electronics market was so well developed that the idea of trying to lock particular laptops or wireless routers to specific network providers did not make much sense. Indeed, even in the never ending fight over set-top boxes and cablecard, the fight is over the ability to attach to an MVPD network, not the ability to unlock a device and move it from one MVPD network to another.
Most of us have always assumed that network neutrality applied to wireless would include both “no blocking” of content and applications and “no locking” devices to networks. But I suppose it doesn't have to be that way. And, of course, this does not stop the FCC from dealing with handset exclusivity separately.
Still, it comes as a bit of a surprise. Nice to have the heads up, and tip 'o the hat to Celia for doing this series of interviews with important folks at the FCC.
St. Cloud's political fight over its municipal wireless network cuts to the heart of one of the core debates in the national broadband plan. Do we regard connectivity as a service on the same level as schools, sewage, and public transportation — where we expect the city to subsidize the service because it provides needed social benefits? Or do we insist that we only provide broadband where it can pay for itself on a going forward basis (after some initial stimulus money to get the network built and get the ball rolling)? There is no doubt that for a city of 30,000, a fair number of people use the St. Cloud wireless network (at least 8500 unique connections/month) and enough regard it as sufficiently important to lobby their city council to keep the network in the face of a financial shortfall. At the same time, no one argues with the fact that the network costs the city $30K/month and seems likely to do so for the foreseeable future.
So how do we measure waste or success? I've argued on more than one occasion that we should look on these networks as the equivalent of a public transportation system. They don't compete with cabs or car sales despite the fact that many people rely on them to avoid driving. In fact, cabs and auto dealers benefit because public transportation systems because they keep traffic manageable. And, as the iPhone and other smartphones continue to increase the demand for spectrum for data traffic, licensed wireless operators like AT&T are finding it beneficial to encourage customers to use wifi hotspots and offload the traffic whereas previously carriers resisted letting customers use wifi at all.
We have until February to debate how we want to incorporate this into our national broadband plan. Broadband as utility — where we encourage local governments to offer services like St. Cloud for the positive externalities for everyone even if it requires continuing subsidy? Or does it only make sense to have municipal broadband where it can pay for itself? With the final decision on St. Cloud now due in January 2010 — a month before the National Broadband Plan — it will be very interesting to see what the citizens of St. Cloud and their local government decide.
• A Searchable Database of All BRS and EBS Licensees and Spectrum Lessees. Anyone who has used the FCC’s Universal License Service knows how difficult it is to search for even basic information. The master database takes all the information and puts it into an easily searched Excel® spreadsheet.
• Special breakout tables and coverage maps for Clearwire and Sprint. Convenient tables and coverage maps show the coverage and relationships of these WiMAX giants.
• Analysis of the top 35 other providers. The report also lists the top 35 licensees in the band after Sprint and Clearwire, describing their general market areas and what their spectrum holdings say about their strategies.
The report cost $499 until FCC Auction 86 beginson October 27, at which point it goes up to $799. Those purchasing at $499 may buy the post-Auction update, scheduled to come out 3 months after Auction 86 closes, for a savings of $200 off the full post-auction price.
I happen to like Scott Cleland as a person, and I recognize he's got job to do, but certain kinds of ad hominem attacks are just lazy — and stupid. I'm referring here to Cleland's to attempts at “gotcha” posts in recent days. One directed against my employer Public Knowledge, the other directed against fellow traveler Free Press.
First, in the flap over Google Voice and blocking, Cleland accused PK of having a double standard — demanding AT&T not use “self-help” on blocking traffic stimulator sites while turning a blind eye to GV doing the same thing. I can understand Scott missing my quote the week earlier in Communications Daily condemning the practice (and suggesting that if they claim the right to block calls then networks can refuse to complete GV originating calls), Communications Daily is a paid subscription and not available online. But how did Cleland miss my initial post on the subject in which I said the FCC should investigate if Google really were blocking calls? (I'll cut Cleland slack for not predicting my subsequent upping the urgency when Speakeasy's decision to block these sites indicated that more VOIP providers are going to push this route.)
Now, Cleland has gone after Free Press by claiming that FP does not disclose its funders. As FP puts its annual reports and 990s online, this is a pretty stupid claim. Mind you, while I approve of disclosure, I'm always a big fan for answering substance. I get equally annoyed at my colleagues for acting as if the fact that someone once worked for a telco or takes money from some industry source automatically discredits them without looking at the merits of the argument. But claiming folks are hiding something when they put the information in a fairly accessible place on their webpage is just silly.
I anticipate that the response from Scott (and, inevitably, Brett — whose customers must be used to long ques for service given how much time he spends commenting on my blogs) will boil down to “well, under my definition of what I say your argument is, you are really hypocrite.” Happily, having now raised child up to age 11, and having grown up on Usenet in the 1980's, I am familiar with this invitation to a meaningless debate whose purpose is to allow the other side to declare victory by continually redefining terms and reserving the right to be the ultimate judge of my conduct. I decline. Likewise, I decline the inevitable “Hah, your declining just proves I am right — you lying hypocrite loser” (I swear I can just write a Brett-bot. Heck, I would think he was a bot if I hadn't met him). The beauty of the internet is that folks are free to draw their own conclusions.
Which is why skipping the silly ad hominems is probably the best route entirely. But if one does engage in such tactics (and folks on the pro-NN side are sadly just as guilty on occasion), at least try to avoid attacks so easily proven to be factually wrong.