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?
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.
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?
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.
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.
Is that accurate? Or no?
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.
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
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
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.