-
Website
http://techliberation.com/ -
Original page
http://techliberation.com/2006/09/25/skype-as-a-bandwidth-hog/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
MikeRT
184 comments · 6 points
-
eee_eff
800 comments · 8 points
-
mwendy
73 comments · 2 points
-
Ryan Radia
176 comments · 5 points
-
Richard Bennett
612 comments · 1 points
-
-
Popular Threads
-
The Ugliness of Privacy Notices
3 days ago · 4 comments
-
Google’s Privacy Dashboard: Another Major Step Forward in User Empowerment & Transparency
2 days ago · 2 comments
-
Open Source is Not the Enemy
4 days ago · 3 comments
-
Broadband as a Human Right (and a short list of other things I am entitled to on your dime)
3 weeks ago · 18 comments
-
“Internet Freedom”: How Statists Corrupt Our Language
1 week ago · 7 comments
-
The Ugliness of Privacy Notices
But- and this is an honest, serious question- why is this troubling? Isn't this kind of monitoring and traffic shaping exactly the kind of thing that poo-pooers of net neutrality say is perfectly legitimate for pipe-owners to do?
The vast majority of universities still permit Skype, and hopefully criticism from their students and faculties (and a little lobbying from eBay) will get these universities to change their mind. I'd rather have a thousand different network administrators making these kinds of decisions for their own campuses than have a federally-determined "bandwidth hog" list that determines which applications may be rate-limited by universities.
When running on a large campus network, it is possible for a p2p client to be mislead into believing you have greater bandwidth potential, because your campus backbone may be very fast , while individual uplinks to the greater network may be slower.
So while individually a client may only use a small bit rate, when aggregated across many possible clients on a campus you could potentially swamp the campus uplinks to the Internet (say 500 clients each handling 96kbs, resulting in a potential 48Mbs of bandwidth in use).
I've had to turn off Skype whenever I'm on wifi or gprs, not because it doesn't work (call quality is typically fine), but because it works too well and starts routing other calls through my system, consuming the limited bandwidth I have.
* there are of course exceptions to this, but they don't really impact the analogy.