News for hackers. Stuff that matters.
Re:Verizon's accidental mea culpa by malchow on Thursday July 17, 2014 @03:30PM (#8049676)
@sheetjs: I'm sorry, but I simply cannot follow the logic in the Verizon argument that you quote. You quote:

"Netflix chose to attempt to deliver that traffic to Verizon through a few third-party transit providers with limited capacity over connections specifically to be used only for balanced traffic flows"

But isn't that a misstatement of fact? CDNs like Level3 do nothing but transfer data, usually media files, onto consumer ISP networks when those ISP's customers' request them.

In what dream world are Akamai and Level3 receiving as much data from Verizon's consumer network as they are sending? Why would any ISP expect a link with a CDN to have a balanced traffic flow?

Re:Verizon's accidental mea culpa by wmf on Thursday July 17, 2014 @03:34PM (#8049704)
Level 3 is not just a CDN; it's a major backbone. Likewise Verizon is not just DSL & FIOS because Verizon Business is also a major backbone. Apparently Level 3 and Verizon did have balanced traffic for many years.
Re:Verizon's accidental mea culpa by malchow on Thursday July 17, 2014 @03:45PM (#8049757)
@wmf, OK, I did not know that background. But I can easily imagine that the AWS infrastructure is geographically diverse enough that Netflix is using Level3 only as a CDN, not as an NTP.
Re:Verizon's accidental mea culpa by wmf on Thursday July 17, 2014 @04:33PM (#8050043)
This dispute isn't just about Netflix (although they precipitated it); all traffic between Level 3 and Verizon is being affected.