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. -- Cal Frye, www.calfrye.com --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected]
