Level 3 vs. Comcast: Peering Dispute or Breach of Net Neutrality?
datacenterknowledge.com
datacenterknowledge.com
I believe Comcast is pointing at when Level 3 blocked Cogent for pushing too much traffic onto Level 3:
http://www.computerworld.com/s/article/105790/Level_3_Cogent...
An interesting article on why de-peering matters:
http://scrawford.blogware.com/blog/_archives/2005/10/22/1316...
http://www.comcast.com/About/PressRelease/PressReleaseDetail...
> Yeah I have seen the peering agreements with L3 and Comcast,
> this story is complete BS.
>
>> Before Level 3 Communications landed the Netflix CDN deal,
>> it sent approximately the same amount of traffic to Comcast
>> as it received.
>
> This is a flat out lie, end consumer networks like Comcast ALWAYS
> receive FAR more traffic then they send. Note how you get something
> like 5 megs down and 1 meg up... wonder why? Because as an end
> user you are not allowed to run any servers or serve any services.
>
> When you request a YouTube video you send maybe 20KB up stream
> and receive 50-200MB back. Comcast has NEVER had more then 5%
> upstream.
>
> I am smelling a Comcast fed story here.
http://www.reddit.com/r/technology/comments/edxjp/level_3_ou...So don't be so quick to dismiss this fact.
I have no doubt that Level 3's CDN traffic went through the roof when they took on Netflix. I also have no doubt that Comcast went "oh, we have them by the balls, lets get more money". It's not really a simple thing to take sides on.
It is a problem, though, that Comcast is operating as a de facto monopoly with their connected consumers. That's kind of the breaks of giving them that sort of leverage. Thank your congressman. Level3 is sure using that story to their advantage.
--Edit-- Also, Comcast apparently does charge other CDNs like this. My opinion has tilted slightly in their favor, it sounds like they're at least being consistant. CDNs always have the option of not using a peering connection but going through paid transit.
I'm sure Google has a lot more leverage in peering negotiations.
RIAA maybe you should find a few Comcast subscribers downloading and sharing illegal/pirated music then go after Comcast (who actually has the money to pay the fines) for not actively filtering said content out of their network.
Comcast, you are walking on a rope next to a slippery slope.
Comcast is an ISP. Just about every CDN out there pays to peer with Comcast to deliver bits faster and cheaper to Comcast eyeballs.
Level(3) is an ISP. Because they carry traffic Comcast customers want they have been able to peer at no-cost to Comcast historically. Now Level(3) is building and selling a large CDN. Level(3) is taking advantage of these existing peering circuits to be able to offer lower-cost CDN than their competitors because they don't have to pay Comcast to exchange traffic. As a consequence, their CDN has grown very large. They now dump far more traffic onto Comcast's network than Comcast sends them. Comcast says their peering policy is based on equal traffic ratios. Therefore, unless Level(3) can balance their peering circuits, they will be forced to pay.
This has little to do with Net Neutrality and has been happening between various ISPs over the last 10-20 years.
In IPv6 it's even worse. If you have Cogent as your ISP you can't reach Hurricane Electric's network over IPv6 because neither of them has transit and they don't peer with each other. :-(
Comcast should be thankful that their peer is sending them content directly, and that they don't have to pay transit costs from their upstream provider.
This is clearly an attempt by Comcast to put up a pay-wall for content from 3rd parties.
I've noticed more and more cable company manipulation of CDNs. For example, nothing scientific, but a few days out of each month, Cablevision, my ISP in Connecticut, starts randomly delaying traffic to Akamai CDN which serves Hulu content. It is difficult for me to scientifically prove anything is wrong, however, when the entire Internet is working flawlessly and a few random Akamai CDN content addresses, which just happen to have Hulu content, stop working, or are throttled, something stinks.
Most networks charge their neighbors -- be them customers or peers. That means when one neighbor sends traffic to another neighbor via the ISP, they both usually pay.
If you call that duplicitous, then every network is duplicitous.
Also -- Comcast's network is symmetrical to the head-ends. It's true the head-ends are configured to allow more spectrum to be used for download than upload, but that's easily changed if people's surfing habits changed. I imagine in the future it'll be dynamic, per customer (if we even continue to use this model for cable modems, which I think DOCSIS is starting to move away from).
Ignoring the fact that the entire DOCSIS standard was designed around downstream distribution of content, and simply would not function well if you try to reverse the flow, how do you determine who pays who in your world? If I'm Comcast, do I have to pay L3 because they have content my customers want? Or should L3 pay me because I have customers they want to deliver content to?
You see, it is not so cut and dried as "everybody pays for bandwidth." ISP customers pay for bandwidth because they are asking the ISP to transit traffic through their network. Peers typically don't pay because they are both endpoints.
2) Of course DOCSIS works if you reverse the flow. You already have separated spectrum in each channel. The wider one is typically for downstream, but could easily be converted for upstream. As I said, I think in the future it'll be dynamic.
DOCSIS only works in reverse if you are willing to install cable plant equipment at a customer site, which would mean a rack full of head-end gear at every house. Not feasible, and won't happen tomorrow.
I used to handle BGP and peering for a tier 1 ISP and CLEC in the western US, so I've seen my fair share of peering agreements, and I've run my fair share of DS3, OC3 and OC12 circuits to peering locations.
It sounds like you have a lot of credentials working for OpenDNS, so I don't mean to denigrate your experience, but OpenDNS seems more like a bandwidth customer and less like a provider/peer. I have a lot of experience with cable plant equipment because we provided cable modems and DOCSIS equipment to a lot of small business/enterprise customers in the late 90s/early 2000s.
They are "peering" their servers with L3 servers at the datacenter to bypass regular networks. "Peering" is when you basically interconnect the servers directly (more or less).
This saves on costs greatly and improves latency and congestion issues.
The problem here is that the peering is now imbalanced by a ratio of 5 and this is not a fair deal for Comcast.
I'm actually surprised how many people here have no knowledge of how peering really works, and are buying the propaganda that Comcast puts out.
Anything else is considered transit and one party becomes a "customer".
If L3 is now 5x asymmetrical with Comcast, they should do what everyone else in the industry does and pay a fee.