-
Website
http://techliberation.com/ -
Original page
http://techliberation.com/2007/08/24/eric-schmidt-and-laurence-tribe-on-common-carriage-and-net-neutrality-regulation/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
MikeRT
184 comments · 6 points
-
eee_eff
800 comments · 8 points
-
mwendy
73 comments · 2 points
-
Ryan Radia
176 comments · 5 points
-
Richard Bennett
612 comments · 1 points
-
-
Popular Threads
-
The Ugliness of Privacy Notices
3 days ago · 4 comments
-
Google’s Privacy Dashboard: Another Major Step Forward in User Empowerment & Transparency
2 days ago · 2 comments
-
Open Source is Not the Enemy
4 days ago · 3 comments
-
Broadband as a Human Right (and a short list of other things I am entitled to on your dime)
3 weeks ago · 18 comments
-
“Internet Freedom”: How Statists Corrupt Our Language
1 week ago · 7 comments
-
The Ugliness of Privacy Notices
How would this work? The way computers and the Internet are typically configured, ISPs have little or no control over the content's of a browser's search bar. Those defaults are set by browser manufacturers such as Microsoft, Apple, and Mozilla. I realize this is just a hypothetical example, so maybe I'm nitpicking, but since the whole network neutrality debate is over what means ISPs should be allowed to avail themselves of in order to enhance their bottom line, I think it's important to be precise in our scenarios about things they might that would run afoul of neutrality regulation. While I don't think government regulations regarding search bars are desirable, I would certainly be pissed off if my ISP tried to dictate what appears in my browser's search bar.
Not only do you need to be more precise in your scenarios, you also need to lose the ridiculous long-winded, never-could-happen hypotheticals.
Why did everyone celebrate when the iPhone or AACS were cracked? It wasn't the traditional competitive market that caused the dominant companies to open up. It was individuals struggling for what they believed were opportunities to engage in open commerce. In the end, the tech community just wants to make money, and anyone who supports open commerce is their friend. Right now Libertarians and Conservatives appears to be on the side of closed commerce.
I would respectfully submit that it is the proponents of new regulation who have the responsibility to be precise in their scenarios so that regulation can be structured to minimize unintended consequences. We need to be concerned not only with how proposed regulation will impact that which already exists, but also how it will impact that which hasn't been thought of yet.
I think when you parse what Eric Schmidt is saying, it isn't at all clear what he is advocating.
Again, I'm not disagreeing with you on the policy argument, just trying to get a clarification on the scenario you're talking about and how it relates to net neutrality.
Jim, that's an intriguing example. It's not clear to me that network neutrality regulations would restrict ISPs' ability to do that, though. Ultimately, DNS is just an application, right? Most people use their ISP's DNS server, but if you don't like your ISP's DNS server, you can switch to someone else's right?
Needless to say, most people who ran the installer had the special Verizon IE browser as their default browser for years.
But it sounds like you're just talking about what happens on Comcast's own website, which I don't think would be affected by any of the network neutrality proposals out there. If I'm wrong and there's something in Snowe-Dorgan on what can appear on an ISP's website, please correct me.
Tim – Snowe-Dorgan (S. 2917, 109th Cong.) provides, among other things, that:
Now compare this with § 202 of the Communications Act of 1934 (47 U.S.C. § 202), applicable to telecommunications services:
The two provisions are nearly identical. Therefore, if Comcast makes its Comcast.net portal a default setting for its customers, for example, it is discriminating against competing services. Btw, here is another interesting article (“Pressuring Microsoft, PC Makers Team Up With Its Software Rivals,” by Robert A. Guth and Kevin J. Delaney, Wall Street Journal (Feb. 7, 2006)) which describes how computer makers prepackage software and how they seek to gain advantage simply by how they present set-up options to consumers:
Like it or not, this is discriminatory and if Snowe-Dorgan applied to computer and software makers, they wouldn’t be able to do this.
Speaking of Dell, every time I misspell a URL, I get redirected to a Dell search page crammed with sponsored links. If broadband providers wanted to do this, they couldn’t under Snowe-Dorgan (I hate the redirect and Dell’s search page, but I do defend the company’s right to do this).
I don't see how providing a CD containing software with a particular default falls under the language. With most broadband services I've signed up for, you've been able to throw the welcome CD in the garbage unopened and the broadband service works just fine. Even for consumers that do choose to install their ISP's suggested browser, I don't see how the presence of a search bar pointing to a particular search engine could "block, interfere with, discriminate against, impair, or degrade" the ability of a consumer to use a different search engine.
The misspelled URL issue is similar. In that case, what your ISP would be doing is providing a DNS server (the server that converts a name like techliberation.com to 72.32.122.135) that returns the IP address of their search page when you query for domain names that don't exist. Reading Snowe-Dorgan to cover this behavior isn't as big of a stretch as the browser search bar example, but I still think it's pretty implausible. That "service" may be annoying, but it doesn't in any way prevent you from getting to the websites you want. In fact, if you want to you can set your computer to use a DNS server other than the one provided by your ISP, in which case your ISP's DNS server settings won't have any effect on you at all.
Of course, we should never rule out the possibility that the FCC would twist the language of Snowe-Dorgan to dictate what can be on an ISP's installation CD or how an ISP can configure its DNS servers, but I don't think such a reading is very plausible. And it's certainly not consistent with the principles that Google and others have articulated.
If Comcast distributed a welcome CD with a browser that refused to go to Google's site, or a DNS server that refused to perform DNS lookups for google.com, then they'd likely be in violation of Snowe-Dorgan. But I don't think that merely setting defaults a particular way is.
That would be an example of blocking, which Snowe-Dorgan also prohbits, obviously. As long as Comcast doesn't prevent you from bypassing its affiliate, Comcast isn't guilty of blocking. But blocking and discriminating are different. If Comcast bundles a Yahoo browser in the installation CD it is discriminating in favor of its affiliate, Yahoo.
Black's Law Dictionary defines discrimination as follows:
When you present options to people, many choose the first one or whatever's at hand and that's a sigificant competitive advantage in the marketplace. For example, Google believes that built-in search boxes are the source of 30% to 50% of a user’s searches (see "New Microsoft Browser Raises Google's Hackles," by Steve Lohr, New York Times (May 1, 2006)). To use your example, Snowe-Dorgan would prevent Comcast from choosing Yahoo as the first choice its customers see. If Comcast were allowed to do so, that would deprive Yahoo's competitors of a marketing opportunity.