Several years ago, AOL decided that internet downloaded pictures (JPGs, GIFs, ...) were taking a huge chunk of the AOL bandwidth, so they implemented a caching proxy that was transparent to their users, so any queries to the internet for an image first checks the cache. That way no internet bandwidth is wasted on repetitive fetches of the same data. This is done with a lot of ISPs for images and is a fairly common practice nowadays.
Now, the ISPs are complaining about basically the same thing, but with bittorrent traffic. In my mind, they should just do the same thing that they did with images and use it for caching bittorrent traffic. The ISPs bandwidth to the internet is expensive, but the ISP's bandwidth to their customers is free (they own the infrastructure). So, if they could cache the bittorrent traffic, it would take a *huge* chunk of traffic out of their upstream bandwidth usage and also provide faster bittorrent downloads for their customers. Win-win! The ISPs wouldn't have to throttle the bandwidth and they wouldn't look like the bad guy anymore. I believe that bittorrent supports the Cache Discovery Protocol - the ISPs just have to implement it and we're golden!
I've got comcast service at home and I occsionally will pull down a TV show that I like to watch it in HDTV on my PS3 since I don't have an HDTV Tivo yet via bittorrent, and I upload tons of (legal, non-bittorrent) data that I generate by myself to the internet (which is slow as a dog under comcast's basic plan (like 300kbit/sec or something like that). If they could free-up the bittorrent traffic, they might allow for giving customers fatter pipes for transferring non-fileshring data just as a normal service upgrade!!! :)
Just a thought.
- Steve
Recent comments
5 weeks 5 days ago
6 weeks 5 days ago
17 weeks 3 days ago
24 weeks 13 hours ago
24 weeks 14 hours ago
24 weeks 20 hours ago
24 weeks 21 hours ago
24 weeks 22 hours ago
24 weeks 1 day ago
24 weeks 1 day ago