|
|
|
|
|
by Swannie
5612 days ago
|
|
1) Does it matter if they pay for their peering arrangements? (See who they peer with here: http://www.datacentermap.com/as/577_upstreams.html ). They still need to carry this traffic to a peering location. That's not free. They still need to support their peering agreements with staff & seriously expensive routers. Not free. They need to support the ISP's whose traffic they are carrying - arguably they ISP's have paid for this, but per GB pricing is fair. It is cheaper to run the content over their own network. They will run over an internal CDN, reducing transit costs to a fraction of say Netflix. 2) I think there is some misunderstanding. The way I read all these articles, the problem is the link from the exchange to the provider PoP, and not in the local loop. Bell got the nod from the regulator 3 months ago to do capacity based charging on links from the exchange to the ISP PoP. If it follows the same model as elsewhere in the world, this is usually on a wholesale, per customer basis. If the ISP in question used a 3rd party supplier then they bypass this cost. Unfortunately it appears that Bell can say no to the ISP leasing fiber capacity from exchange to PoP, which IS abusing their monopoly position. The point is they are establishing a precedent. Even if their network is not overloaded at the moment (I suspect it's getting there) it will be soon. If a web company has to pay per GB of transit from Amazon EC2, but not within the AWS network, why should charging at a communications provider be different? |
|