Slashdot Mirror
Enabling Bittorrent at the University Level?
Sorthum asks: "I'm a network administrator for a small university (approximately 5000 students all told). We're running NAT in the dorms, which obviously restricts BitTorrent traffic. We do an annual student survey, on which 'Residential Network' is listed as the number 2 complaint. This translates more or less into 'Bittorrent is slow here.' My boss is in a frenzy to appease the users at virtually any cost, but it seems to me from my research that the only real way to improve Bittorrent speeds is to start assigning public IPs to the dorms. Add to that the potential liability of making a service that by most reports has upward of 90% of its traffic fall into a 'legally questionable' gray area, how can I win in this situation?"
BitTorrent, like any other technology, protocol, or tool, can be used for things that are legal, illegal, or questionable in various jurisdictions. Are you prepared to continue quashing a protocol or service simply because it may be abused?
On the other hand, almost all (or at least a great deal) of the BitTorremt traffic may be currently used for sharing copyrighted materials. We all know that to be the case. Is it responsible to open up the pipes for what you know is almost exclusively illegitimate usage, within the context of the law (regardless of how you or anyone else feels about copyright infringement, and so on)?
On yet another hand, what happens if BitTorrent usage becomes largely legitimate because some large legitimate service begins using it? (And yes, to those reading this, I'm more than aware BitTorrent is used for a variety of legitimate large downloads.) In that event, can you afford to continue treating any protocol or service as if it's illegitimate, just because some level of it is now?
During the heyday of Napster (1999-2000), UW-Madison estimated that Napster accounted for over half (!) of our inbound and outbound traffic. There was a lot of talk about how to deal with this. Ultimately, UW-Madison decided that as a large public research university, we can't afford to police a particular kind of traffic wholesale: any network protocol can be abused, used for illegal purposes, and so on. We felt that the academic arguments and responding to usage demands of the campus trumped making judgment calls about the appropriateness of the use. Granted, the appropriate use policy of the university forbade some of the things people were using the network for, but we didn't actively police (or restrict) traffic. In the end, this provided the university with the impetus to examine ways of meeting increased demand and come up with novel solutions to our neverending bandwidth needs. One interesting example is that we now locally host a collection of Akamai's servers on our own network, which serves UW-Madison, the 25 other UW System Schools, and WiscNet. However, some of the smaller schools couldn't afford to make those same determinations: they either restricted or blocked Napster (and other things, like Gnutella) completely.
Today, the university does shape and restrict traffic to the residence halls in various ways; but it's designed to do so in a way such that users almost always won't notice any impact and allows equal access for all. All of our residence halls feature 100mbit ethernet, and that full pipe may be taken advantage of. Some users do use the network for inappropriate purposes, and those cases are dealt with individually when needed. Still, there is no proactive policing unless there are clear abuse/misuse issues. For what it's worth, BitTorrent (and all other protocols) are fully usable here.
If you can afford it, politically and financially, I'd say you should be looking into opening this up. The school does not bear responsibility for the actions of its users unless there is a lack of good faith attempts to stop abuse when requested by, e.g., copyright holders. There always is the argument of customer satisfaction, as well, that must be responded to - whether some students' use is appropriate or not.
If they mirror the linux distro, it'll download even faster. Perhaps they should figure out what students are downloading most (i.e. linux distros, game patches, movies that are in the public domain.. and keep local copies of those things. Once they learn of its existance, students will pretty much always go to the local cache for it's much much greater bandwidth and far lower latency.
They could even use mediawiki to allow the students to take some control of the cache.
Can you be Even More Awesome?!