Ohio University Blocks P2P File Sharing

After receiving the highest number of notices from the RIAA about P2P file sharing, Ohio University has announced a policy that restricts all fire sharing on the campus network. Some file-sharing programs that could trigger action are Ares, Azureus, BitTorrent, BitLord, KaZaA, LimeWire, Shareaza and uTorrent. Claiming that this effort is 'to ensure that every student, faculty member and researcher has access to the computer resources they need,' is this another nail in the coffin of internet freedom in American universities or a needed step to prevent illegal fire sharing?

Comments

Makes sense

[MrCawfee]

I've worked at a college, in an average week we would get 10-15 riaa letters (with our seemly small number of 3000 residents), and responding to them gets to be a huge chore. Most campuses are taking the "we don't want to get sued, so we will not put ourselves in that position" approach, so ignoring those letters is not an option.

At the place i worked at, for a while we did try to block kazaa and the like, the problem was that there would always be a new protocol that would pop up to take it's place. We eventually gave up on blocking it because of this.

This story is really not a new thing in the university world, most have a policy of limiting the student's ability to fileshare (some through innocent means like NAT routing, others through throttling the bandwidth for those services).

So before we all get up in arms that people are limiting access, you'd think again when you have to call 20 people in a day, tell them why their access has been shut off, and have every one of them claim that they've never file shared in their lives. Only to get the call the next day where they complain that their their myspace is too slow.

Applause

[arivanov]

Applause to the BOFH that has pushed it through, though I would have done it differently.

Most university IPs are real on a really high speed connected LAN. As a result they get elected to supernode status by most modern P2P applications. As a result the university network becomes a jump point for NAT traversal for all leaches within 30-60ms rtt around it. As a result the resource usage is clearly disproportional to the actual on-campus usage. Essentially all small and medium corporates and home users sitting behind firewalls in the immediate vicinity live off that resource and steal a significant portion of the Ohio University network capacity.

Personally, if I was the admin, I would have tried to QoS P2P down (and net neutrality be damned) to the point where the campus is made equivalent to the rest of the world.

Unfortunately even if the protocols were easier to isolate, that may be quite difficult for a network the size of Ohio State. Most network equipment used at the bandwidths in question cannot do selective delays and probability drops very well. The P2P applications nowdays make the "if the protocols are easier to isolate" statement false anyway. All the developers know that they are committing a resource theft and they go way beyond what is considered spyware tactics to achieve their aims (current Skype is a fine example of this).

So on the balance of things, just banning them to hell is probably the most cost effective options. Congrats and applause. Can we have more of that please. A few more and the net economics will go back to where they belong so people actually start looking at things like multicast and frontline in-local-loop delivery instead emulating it through resource theft.