Fri

Jun 23
2006

Tim O'Reilly

Tim O'Reilly

Net Neutrality: Rules vs. Principles

There's been a lot of great discussion on Dave Farber's IP List about Net Neutrality. But what just tipped me over to blog about it was a great post today by Chris Savage making a distinction between rules and principles. This is a distinction that needs to go into every thinking person's mental toolkit. Chris writes:

A lot of confusion in the Net Neutrality debate has do with the hoary distinction in jurisprudence between "rules" and "principles."

A first approximation for the non-lawyers here: the tax code is full of RULES: Take this number, divide it by that number, place the result on line 17 if it's greater than $57,206 and on line 19 if it's less. Etc. RULES are intended to direct or forbid very specific behaviors.

PRINCIPLES, on the other hand, are more general. When driving you are required to use "reasonable care." If you don't, then you are negligent and can be held liable, in a tort case, for the damages you cause. And though there are plenty of rules about driving, tort liability is based on the PRINCIPLE of reasonable care, and is assessed on a case-by-case basis.

"Net Neutrality" is a principle, not a rule. Without getting into endless and mind-numbing discussion of how the FCC might or might not classify this or that IP-enabled service, what Net Neutrality is basically about is the principle of non-discrimination. The principle of non-discrimination doesn't say that you cannot make any distinctions at all as between customers, services, what you charge, etc. It just says that whatever distinctions you make, have to be reasonable.

So, Professor Yoo's discussion of particular ways that network operators today treat traffic differently in different circumstances is kinda beside the point. It just shows that there are reasonable distinctions that can be made. E.g., sure, give live video packets priority over email attachment packets. That's reasonable. Net Neutrality says, though, that normally you shouldn't give YOUR video packets priority over a COMPETITOR's video packets.

Chris' point struck me as bloggable whether or not you give a hoot about net-neutrality. Certain ideas, like the difference between rules and principles, are building blocks that make you smarter, exemplars of Edwin Schlossberg's maxim that "the skill of writing is to create a context in which other people can think." But for those of you who do care about net-neutrality, some other thoughtful posts about this topic on the mailing list include:

Overall, the disputants fall into two camps, based on which of two principles (the end to end nature of the current internet, or the power of markets to set efficient pricing) seems more important to them. So ultimately, even though Chris Savage made the distinction between rules and principles, we still need mechanisms for deciding about the relative importance of competing principles.

P.S. This is just a small sampling of the heated but thoughtful discussion on the list. When I want to understand the various points of view on any technology policy issue, there is rarely a better place to go than the IP (Interesting People) list. Unfortunately, the search interface is only so-so, and the mailing list posts themselves don't include web archive links, so it's always a bit of a chore to find and link to postings, even when I've already read them in email. But subscribe to the email list, and you'll discover that there's a world of conversation going on in venues that bloggers normally don't report.

tags:   | comments: 3   | Sphere It
submit:

 
Previous  |  Next

0 TrackBacks

TrackBack URL for this entry: http://blogs.oreilly.com/cgi-bin/mt/mt-t.cgi/4755

Comments: 3

  Ian [06.23.06 07:43 AM]

It is also a three-dimentional argument, which is to say that there is a Rules:Principles relationship (A:B) that the data network operator must abide by, _as a wires and signals provider_ and another, independent Rules:Principles relationship (C:D) that the data network operator must mabide by _as a content producer, owner, and distributor_.

The most basic relationship between A:B and C:D is to say you can be one or the other but not both. If you are a carrier, you can't be in the content business or vice versa.

That isn't going to happen, so now we are debating how to formulate the definition that makes A:B::C:D a true statement, and it would be nice if it were predicated on the fundemental incompatability between the business interests of carrier services and content services, that is, that carriers want to be as open to as many content services as possible to make themselves attractive to their customers and content services want to be as unique as possible to lock in their customers and keep them coming back for more.

When you are both a carrier and a content provider, you can't do both, and the one with higher profits will win. That usually means the customer will lose.

  Richard Bennett [06.23.06 03:00 PM]

Chris Savage is not correct. The net neutrality bills contain actual rules, such as this one in the Markey Amendment:

"If a broadband network provider prioritizes or offers enhanced quality of service to data of a particular type, it must prioritize or offer enhanced quality of service to all data of that type (regardless of the origin or ownership of such data) without imposing a surcharge or other consideration for such prioritization or enhanced quality of service."

The ban on QoS fees is a rule.

Post A Comment:

 (please be patient, comments may take awhile to post)






Type the characters you see in the picture above.