Jim Harper at Technology Liberation Front pinged me (sort of) to comment on reports that anyone who subscribes to Verizon's FIOS broadband service who mistypes a domain name will now land on a Verizon search page. So, for example, trying to get to i-want-sprint-cell-phones.com will land you on a a page like this (my thanks to ace domain name practitioner John Berryhill for capturing this in a screen shot and putting it up on his web page). Meanwhile, reports have surfaced that Cox cable is also interfering with BitTorrent uploads, although at least Cox has the intelligence to admit from the start that it actively manages traffic, rather than go through several rounds of idiotic denials like Comcast (which is probably why the Cox issue is getting a lot less notice).

Briefly:

1) I ain't that excited about the Verizon DNS redirection in the grand scheme of things. Yes, it breaks end-to-end, and I'm not happy about it. But unlike traffic shaping, this development was foreseen and approved of by the FCC and the Supreme Court in the Brand X case when both pegged DNS as the thing that made broadband access an “information service” and therefore free from pesky regulation. At least Verizon's redirection doesn't actually hurt the average user.

2) OTOH, it does raise serious privacy issues and highlights the general problems of letting the ISPs control all of this. There was, after all, a reason we regulated telcos and cable cos to keep user information private. It also starts to raise a very troubling question — what happens when network operators and application developers learn to distrust all the basic protocols under which the 'net operates? It works fine for the first few guys. But what holds this together is everyone agreeing on a set of basic protocols. Eliminate the trust in those protocols, and things start to break down.

3) Some folks that gave a great big yawn to Comcast's traffic shaping have gone ballistic over messing with DNS lookup. But both are natural consequences of turning this stuff over to ISPs. Folks who hate the thought of even limited government regulation of network management but also hate the thought ISPs messing with DNS and other protocols have some tough choices ahead.

Thoughts below . . . . [Read More!]

When the FCC deregulated broadband by declaring it an “information service,” it also adopted four principles that purported to give broadband subscribers a right to “access lawful content of their choice,” “run applications and services of their choice,” “connect their choice of legal devices that do not harm the network,” and enjoy “competition among network providers, application and service providers.” All subject to “reasonable network management,” of course. So when a bunch of us in 2006 pressed Congress to pass a network neutrality law, a lot of folks claimed we didn't need one because the FCC already had the authority to deal with any problems that might arise. And, when questioned on this very subject at his confirmation hearing for a second term, FCC Chairman Martin said the FCC had ample authority to deal with any violations of the four principles that might arise.

Thanks to Comcast and their decision to “manage” their network load by degrading BitTorrent,it's put up or shut up time at the FCC. My employer, Media Access Project, along with Free Press and Public Knowledge, just filed a formal complaint against Comcast and a general Petition for Declaratory Ruling asking that the FCC hold that deliberately messing with a customer's application while refusing to admit doing it when asked pint blank violates the FCC's “four principles” and does not constitute a “reasonable network management practice.” This will also press the FCC to find out exactly what the heck Comcast is actually doing (since some folk remain uncertain). Given that Comcast initially denied the very idea as “internet gossip,”, instructed their line staff to lie to customers about it, and are still maintaining that nothing of interest is going on, it looks like the only way will actually find out what the heck is going on and why is to have the FCC pry it out of them.

Hey, maybe they are telling the truth. But the FCC is in a much better position to know whether Comcast is deliberately lying to its customers and, if so, why. Because while my friend and opposite number Jim Harper at Technology Liberation Front may be content to see if the market punishes Comcast for its “lack of transparency”, I see a lot of bad consequences in letting Comcast throttle traffic as a network management tool and then lie (or, at best, mislead) about it when asked about it point-blank by their customers.

At any rate, whether folks think we should regulate this kind of behavior or not (and I recognize that a number of smart folks not employed by cable operators feel we shouldn't regulate this even if everything bad said about Comcast is true), we deserve to know whether the FCC has the authority to regulate this behavior, and the willingness to do so on an enforcement basis. Because if the cable and telco companies that swore up and down that we didn't need new rules now come in and say the FCC has no authority to take complaints about their behavior after the fact or no authority to order any remedies, then we should know that. And if the FCC is going to leave us high and dry when broadband providers start degrading applications, then we should know that. Because while some folks may think that lying to your customers is an acceptable network management technique, or even an acceptable technique for managing elected members of Congress, I think most Americans would disagree. And I certainly want to know that by November '08.

Stay tuned . . . .