3 ms·

Packets != Electricity -- in boston, I'm not getting electricity generated in california. When we send a package the price consists of 3 things - size, distanc

Packets != Electricity -- in boston, I'm not getting electricity generated in california. When we send a package the price consists of 3 things - size, distance, and speed. I think that's a much better way of thinking about bandwidth than electricity is. Peering agreements can be seen as one UPS taking my package to memphis and then fedex taking it to an area that only they serve. If fedex and UPS have similiar amount of packages going between them then they may decide to not bother charging each other. However, if fedex decides to reduce their territory to only major factories (CDNs) then all of a sudden the amount of packages they're sending over UPS gets out of equilibrium and UPS may decide to charge them for their delivery service.

eggnet 16y ago
You are describing peering arrangements between ISPs quite well. The ISP that is sending the traffic will "hot potato" the packets to the closest peering port, so the ISP receiving the traffic is responsible for backhauling it. This is why there is a convention of charging for traffic sent between tier 1's. If it's a wash, then it's a wash. Otherwise, whoever sends more pays more. However, this is not how peering arrangements look between a CDN and an ISP. In that case, the CDN is responsible for the backbone traversal, because the CDN is proxying requests or delivering them from cache, at the local peering point relative to the consumer. In your example, if you are in boston accessing content with an origin in california, your ISP will receive the data in boston, and will not have to backhaul the traffic from california. The CDN will take care of that.
blhack 16y ago
>Packets != Electricity -- in boston, I'm not getting electricity generated in california. You're right. You're getting electricity that was produced several million years ago under ground in [probably] West Virginia, then transferred to a station near your house where it was released and made available to you. But where it is produced is a completely moot point. We're talking about the internet. The difference between sending a .jpg to my neighbor and sending a .jpg to you in Boston is trivial.

eggnet 16y ago

You are describing peering arrangements between ISPs quite well. The ISP that is sending the traffic will "hot potato" the packets to the closest peering port, so the ISP receiving the traffic is responsible for backhauling it. This is why there is a convention of charging for traffic sent between tier 1's. If it's a wash, then it's a wash. Otherwise, whoever sends more pays more. However, this is not how peering arrangements look between a CDN and an ISP. In that case, the CDN is responsible for the backbone traversal, because the CDN is proxying requests or delivering them from cache, at the local peering point relative to the consumer. In your example, if you are in boston accessing content with an origin in california, your ISP will receive the data in boston, and will not have to backhaul the traffic from california. The CDN will take care of that.

blhack 16y ago

>Packets != Electricity -- in boston, I'm not getting electricity generated in california. You're right. You're getting electricity that was produced several million years ago under ground in [probably] West Virginia, then transferred to a station near your house where it was released and made available to you. But where it is produced is a completely moot point. We're talking about the internet. The difference between sending a .jpg to my neighbor and sending a .jpg to you in Boston is trivial.