News for hackers. Stuff that matters.
Re:Verizon's accidental mea culpa by rhino369 on Thursday July 17, 2014 @03:11PM (#8049539)
PUSH and PULL don't really describe how it works.

Its the senders responsibility to deliver data to the local ISP of the recipient. It doesn't matter if the person asked for the data, you still have to pay to get it there.

The issue is that Verizon is both a national transit provider and a local ISP. If you just dump your data on the nearest Verizon peering port, you aren't fulfilling your end of the bargain. You are asking Verizon to do it for you, as a transit provider.

However, if you are delivering it to the last mile, you have "paid for it" it already.

The issue is where are these congestion issues occurring. At the last mile or at the edges of Verizon's transit network.

Verizon absolutely has the right to bill for providing transit.

Re:Verizon's accidental mea culpa by rahimnathwani on Friday July 18, 2014 @01:24AM (#8051800)
"Verizon absolutely has the right to bill for providing transit."

Even if we agree that Verizon has the right to bill Level 3 for transit within _Verizon's own network_, it seems odd that they are not taking advantage of Netflix's CDN boxes, which would drastically reduce the amount of transit required.

If you just dump your data on the nearest Verizon peering port, you aren't fulfilling your end of the bargain.

So, let's say I build a new skyscraper with 10,000 apartments, and I set myself up as the exclusive ISP to the tenants of that skyscraper. I wire up the building nicely, and have some big switches and routers in the basement. Does every content provider (e.g. Netflix) or company working on their behalf (e.g. Level 3) now have an obligation to build new circuits, and deliver the traffic all the way to my basement?

Re:Verizon's accidental mea culpa by 15thandwhatever on Friday July 18, 2014 @03:35AM (#8052063)
If this were telecom/PSTN, yes. I know this is not the PSTN, but bear with me for a second.

For years, this is how Verizon/AT&T/SBC/BellSouth/etc had structured telephone networks. And this is probably the same structure they want to extend to shared data networks aka the Internet.

If you were a competitive telco carrier who wanted to deliver a massive amount of phone calls to Verizon customers in a particular region, you couldn't just dump it off at the tandem (which you can think of like a telecom peering point), you had to extend your network to the end offices where the Verizon customers were aggregated.

The thought there being there's finite capacity between the end office and the tandem. And if you're going to use most of it, you should either pay for it or build your own facilities to alleviate congestion.

You're dealing with a traditional telecom company (Verizon) in its telecom mindset (build to me/mid-span meet, and keep a very tight watch on ratios/meet points via accounting, billing, and state regulation), vs. a traditional Internet company (Level 3) in its traditional peering mindset (build to the exchange, then build to me, and keep a loose observation on ratios/meet points with no regulation).

I hope I haven't gone too far off track.

Re:Verizon's accidental mea culpa by rahimnathwani on Friday July 18, 2014 @04:02AM (#8052099)
So, let's say I build a new skyscraper with 10,000 apartments, and I set myself up as the exclusive POTS/PSTN provider to the tenants of that skyscraper. I wire up the building nicely, and have some big switches and routers in the basement. Does every other phone company now have an obligation to build new circuits, and extend their network all the way to my basement?
Re:Verizon's accidental mea culpa by 15thandwhatever on Friday July 18, 2014 @09:22AM (#8052848)
As a registered telecom provider with the state, you need to file at least one interconnection agreement (the telecom equivalent of a peering agreement) with the regulatory body showing that you are connected with the incumbent (Verizon) or someone who's going to transit calls for you to the incumbent.

The state won't let you take on calls as a local access provider if they're going to end up going nowhere.

You also have a regulated obligation to provide working 911 service so you need to interconnect with the incumbent's 911 tandem switches. So, off the bat, you have multiple connections with or to Verizon.

Now, if there are some really popular people in your building who attract a certain amount of calls, YES, you can demand that the other telecom carriers extend facilities to your switch (which is located in your basement).

Those carriers will decide if they want to build facilities to you, or work with another carrier (remember the one interconnection agreement you had to sign?), to pay them to deliver calls to you on the agreement that they have enough facilities with you.

You are compensated, per minute for any call that terminates on your skyscraper network through a process called reciprocal compensation, whose rates are laid out in the interconnection agreement you signed.

Is old-timey Verizon's attitude starting to make sense?

Re:Verizon's accidental mea culpa by kbutler on Thursday July 17, 2014 @06:04PM (#8050488)
So Netflix should pay Verizon $1/month/customer. And pass that cost on to the Verizon subscribers...

How quickly would this change Verizon's policy?

As a customer of an ISP, I pay for access to servers on the internet. My ISP charges me for a level of bandwidth. If they are the bottleneck slowing down my connection to the services I want to access, they should fix it, and give me what I'm paying them for.

Re:Verizon's accidental mea culpa by rhino369 on Thursday July 17, 2014 @06:56PM (#8050726)
You aren't paying Verizon to transit L3's traffic. Even if it's going to you.
Re:Verizon's accidental mea culpa by vertex-four on Friday July 18, 2014 @09:00AM (#8052749)
My contract says I'm paying for access to the Internet. Access to the Internet involves transmitting data outwards, and receiving data inwards. So yes, I am paying them to transmit L3's traffic.
Re:Verizon's accidental mea culpa by seanflyon on Friday July 18, 2014 @05:34PM (#8055755)
That's what I thought I was paying for when I agreed to give my service provider money.
Re:Verizon's accidental mea culpa by rhino369 on Sunday July 20, 2014 @01:12PM (#8060868)
No it's not. You pay to send to them, and to receive data people send to you. You don't pay for your ISP to transit data from whoever is sending you data.

For example, you want to download something off a Server in Germany. Your ISP is responsible for getting your initial message to the server. But it's not responsible for taking that information in Germany and carrying to back to the US for you. The Server's ISP has to carry it to the USA and then dump it off at your local ISP.

Now your ISP and the Server ISP may have a peering point in Germany, but they might not. But either way, your ISP isn't under any obligation to pay for transit of data being sent to you. That's just not how it works. And that definitely isn't what is in your agreement with your ISP.

Re:Verizon's accidental mea culpa by simcop2387 on Thursday July 17, 2014 @03:20PM (#8049601)
The question then becomes does the contract Verizon have for peering with other transit providers allow them to charge the other transit customers for that? And if they do what's to stop every transit provider from charging every other transit provider's customers for the same thing? And then the all important question, SHOULD they be stopped from doing it? The current structure of the internet was built around this not happening that way, but is that the way it should be? I strongly believe that letting it happen would cause many other political and routing problems for the internet as a whole to the point where it'll end up being regulated against doing it that way anyway. It could also end up then as a zero sum game between all the transit providers ending "free" peering agreements.
Re:Verizon's accidental mea culpa by malchow on Thursday July 17, 2014 @03:36PM (#8049710)
It's a fair distinction. Here, I believe, the movie is going AWS Seattle to L3 to the front door of Verizon's consumer network in LA, and Netflix is paying for it all the way to the front door.

Is that accurate? Or no?

Re:Verizon's accidental mea culpa by msandford on Thursday July 17, 2014 @03:43PM (#8049744)
Normally I pay for transit from my house to my ISPs peering points. And other service providers pay their ISPs for transit from their "houses" to the same peering points.

In this case Netflix is being forced to pay for transit from their "house" all the way to mine. Not how the internet normally works.

Re:Verizon's accidental mea culpa by wmf on Thursday July 17, 2014 @04:29PM (#8050020)
Netflix does not serve video out of AWS. If you're in LA, Netflix is probably serving from a server in LA.
Re:Verizon's accidental mea culpa by lemming on Thursday July 17, 2014 @05:37PM (#8050337)
Netflix very publicly went all AWS a couple of years ago: http://techblog.netflix.com/search/label/AWS.
Re:Verizon's accidental mea culpa by jauer on Thursday July 17, 2014 @06:17PM (#8050560)
Netflix CDN is distinct from AWS.

AWS may be the origin for content distributed via peering, appliances, and CDN partners but your videos aren't streaming from AWS: https://www.netflix.com/openconnect

Re:Verizon's accidental mea culpa by misframer on Thursday July 17, 2014 @05:31PM (#8050303)
I didn't know that. Can you link to a reference? I thought they used AWS for everything.
Re:Verizon's accidental mea culpa by pwarner on Friday July 18, 2014 @01:38AM (#8051832)
basically they build their own hardware: https://www.netflix.com/openconnect

you can't put your own hardware at AWS.

they are the poster child for using AWS for what it is good for, general purpose compute (storing your play list, the list of all movies, controlling the CDN etc)

but I imagine for streaming you need bare metal

Re:Verizon's accidental mea culpa by caust1c on Friday July 18, 2014 @01:45AM (#8051848)
They're actually one of the most prominent companies with a large deployment of FreeBSD (the OS they use for their CDN).

https://www.netflix.com/openconnect/software