I've been staying out of it because I can't stand the 50 NDR and
vacation messages that come with posting :)
We use our Packetshaper to "control" P2P traffic, that is P2P for the
whole campus is limited to 1kbps of bandwidth. If they can get through
enough to cause a DMCA violation, we're proud of them for
determination. But we can still claim we don't block it, which was the
goal at the time of setting it up.
BitTorrent is throttled down to a small chunk (2Mbps if I recall) for
the campus, because like the argument over VCR's, there are
non-infringing uses.
However most of our copyright notices have to do with Bittorrent. That
is not a technical problem, but an "educational" one. First notice for
a user, they sign a form saying they have been educated and that they
now know what they did was wrong, 2nd time they get blocked and referred
to student affairs.
We have not made use of the NAC for checking for the existence of P2P
programs because of the tiny flow they are allowed.
On 9/14/2012 9:59 AM, Cal Frye wrote:
I hadn't wanted to discuss policy on a technical list, as I feel we're
veering somewhat off topic.
We treat P2P at Oberlin much like our other default-deny policies: Ask
for an exemption and ye shall receive. As you say, we treat them like
adults and don't quiz them about their reasons, but we do take the
opportunity to explain DMCA concerns at that time. It cuts down
considerably on the "copyright violation? I didn't even know I was
sharing that!" conversations.
We found that it was easy to evade the (not Enterasys) NAC checks for
P2P client applications by simply renaming the executables. Is your NAC
client able to track such actions?
Hawkins, Michael "Original" Stephen wrote:
To all:
We use our NAC implementation at UNC to treat our students in ResNet
like adults.
---
To unsubscribe from enterasys, send email to [email protected] with the body:
unsubscribe enterasys [email protected]
