Skip to main content

Net Neutrality: Quick Highlights


Looks like there's a new set of proposals coming regarding Net Neutrality from FCC Chairman Tom Wheeler. Some details have been leaked, but we'll have to wait until May 15th to see everything. More than a few people have been asking my opinion, so I'm going to dump everything here, and refer back to it.

1) Net Neutrality is a loaded term.
On the surface, I'm a huge proponent of Net Neutrality. But when I say that, I want to see exactly what the TCPIP protocol was built for: best-effort per-packet delivery, end to end. However, I can promise you that if you put any two people in a room, you're going to come up with two different definitions of Net Neutrality. My idea of Net Neutrality, for example, is much different than Netflix's. (Netflix reluctantly signed an agreement this year where they had to pay Comcast to connect to their network in order to get the speeds necessary to make sure your House of Cards marathon didn't stutter. ) [1] In many cases, you don't want your traffic treated neutrally, you want it prioritized. Which brings us to...

2) Paid Peering.
Paid Peering is the process by which, essentially, big content providers host copies of their servers directly adjacent to or within ISPs so the traffic doesn't have to cross the whole internet to get from Netflix/Google/Microsoft to you, the end user. These agreements have never been covered by Net Neutrality, and it appears the new rules won't try and curb them either. This is a good thing. Network congestion scales exponentially over distances (hops), meaning that every hop we can remove between that Microsoft Update and your home PC is bandwidth freed up. Of course, the difference between Paid Peering and simply connecting edge networks directly together is a bit fuzzy, which is why the FCC wants to address complaints on a case-by-case basis, which Net Neutrality advocates are opposed to. I'm pretty much for it, pending some conditions, for example...

3) Transparency and "Reasonable Network Management Practices"
This is the crux of the recent hissy-fit. The 2010 Open Internet Order from the FCC barred "unreasonable discrimination" against traffic; the new (leaked) proposal allows for "commercially reasonable" traffic management. The difference is a fine one, but it should be noted that the first order was struck down largely because of this wording. Thus the proposed changes. The thing I'll be combing through the May 15th release for is protections providing for transparency and disclosure of the network management practices by ISPs and other carriers. Disclosure isn't going to be an absolute necessity. If you recall the evidence that Comcast was holding up BitTorrent traffic purposely on its network was rooted out by everyday Internet users, using free tools. However,anything that promotes sunlight would help. But the most vociferous advocates of Net Neutrality just aren't going to be happy until we have...



Telecom Regulated: the first 80 years

Telecom Deregulated: the last 20 years 


4) Reclassifying Broadband as a Tier II  telecommunication service by the FCC.
This is what most of the online petitions, and carefully crafted outrage by organizations like Free Press and Public Knowledge are really after. How anybody can look at the track record of the FCC ruling the common carriers and think that it's the way forward to innovation on the Internet, I do not know. It's very tough for me to equate the days of Ma Bell, where the Western Electric Model 302 didn't change for 60 years, to 1984's breakup of AT&T created an explosion of new phone technology and the creation of cellular networks and free long distance calls.

When the proposal is made public on the 15th, I'm sure I'll be revisiting the topic. Wheeler wants to get something approved by the end of the year, which would be at light-speed for the FCC. We'll have plenty of time to argue over it, but until then, don't sign any petitions until you really know the details. You may not be getting what you bargain for.

Updates:
[1]: (4/30/2014): In the Netflix example, Netflix wanted to use Net Neutrality to force Comcast to cover the cost of providing high-speed access from Netflix to Comcast users at no charge to Netflix. This would ultimately mean that non-Netflix-using Comcast customers would foot the bill to subsidize their Netflixing brethren. See how the some interpretations of "Net Neutrality", and their unintended consequences, can get messy fast?

[2]: (2/27/2015): Well, we had to wait a lot longer than until May. In fact, I thought this was a dead issue, until the President revived it. And it pretty much looks like we exactly what I mentioned in #4 above, reclassifying broadband as a Tier II Telecommunication service.



Comments

Popular posts from this blog

The Re-Opening Experiment

We should remind ourselves that, this Memorial Day weekend and the weeks that follow, we are subjects in a grand experiment to see how good we are at social distancing as stay-at-home orders are being slowly lifted. The state's stay-at-home order was never meant to keep you, individually, safe from infection. It was meant to keep hospital's safe from being overwhelmed by too many of us needing them at the same time. In Michigan, the daily new cases of COVID-19 are higher today than they were when we locked down in late March. We are testing whether or not we can open up (with all of our new precautions and protocols) without spiking the rate of spread, but make no mistake: it *is* an experiment, and we *are* the test subjects. Please don't get careless as things start to open up. We need to get our economies back on track, but we are still a long way (and a vaccine away) from being out of the woods. Stay vigilant, folks. Wash your hands. Wear a mask. As has always been the

VMWorld Wednesday

Today I noticed three things: 1) All the good sessions ran today. 2) Lines for everything! 3) You can't do back-to-back sessions all day without burning out. Today's sessions were not to be missed, and everybody knew it because lines starting forming 45 minutes before some sessions. VMWorld has been on their toes, however: I didn't miss any session that I wanted to hit, and the most popular sessions from Monday and Tuesday got added back to the schedule on Wednesday and Thursday so everyone would have a crack at them. This is some very nimble work for a conference this big. Well done, VMWorld! Here's the photolog: My morning run takes me down to ferry building and up the Embarcadero. Here's the view at sunrise. This lovely scene is the hallway in my hotel. Creepy, but swank! Lines! Today was the day of lines! This was the line first thing in the AM for the Labs. More sidewalk art outside of Moscone South. Bean-bag Alley - where people and devic

You are going to get COVID-19. Now what?

In my best estimation, this is how we should address COVID-19 at this point:  1. You are going to get COVID-19. It's very likely endemic now. Breakthrough Delta infections carry the same viral load in the nasopharynx of the vaxxed and unvaxxed alike. Resign yourself to this fact. You are going to get COVID-19. If not Delta, then whatever variant comes next due to antigenic drift.  2. There is no herd immunity. There is no eradicating this virus. "Zero COVID" is a fantasy. It's too widespread, too mutable, and too contagious. Eventually, this will join the other common coronaviruses in circulation (229E, NL63, OC43, and HKU1).  3. The vaccines shouldn't be considered vaccines. Consider them similar to seasonal flu shots. They are here to make sure that when you get COVID-19 (And let me reiterate: You are going to get COVID-19), you are far less likely to be hospitalized or die.  4. When enough people, vaxxed and unvaxxed, get COVID-19 (And let me reiterate: You are