I haven't managed a network for years, but our approach was to provide a broad statement of what the network was for and to make it clear the network couldn't be used for malicious or illegal purposes.
The CYA policy is a start but you'll still have to deal with problems such as people using the network to stalk/harass others, intentionally or unintentionally attack other systems, and piracy. Balancing user needs with very real privacy issues, network capacity, and the sad fact that some people act like jerks when they can hide behind a veil of anonymity is challenging. I'm glad I don't have to worry about that kind of stuff anymore. kyle On Thu, Jan 22, 2015 at 6:11 AM, Nate Hill <nathanielh...@gmail.com> wrote: > Hi all, > > I wonder if libraries that manage their own networks, either academic or > public, would be willing to share their wifi / network use policies with > me? I'm working with the city of Chattanooga to separate our library's 4th > Floor GigLab <http://blog.giglab.io/> from the city's network. The 4th > Floor is our library's beta space / makerspace / civic lab, and we are > constantly running public experiments of one kind or another here. Our ISP > has given us a separate 1gig fiber drop for this space, and we intend to > use (or keep using) the whole area as a public laboratory to experiment > with the network, hardware, and software. > > So... I need to get a policy to city legal for review and to my board > before we actually make this separation. I don't really want to go to jail > when someone hacks North Korea from the library's GigLab. > > Thanks for any documents or input you all might provide, > > Nate > > > -- > Nate Hill > nathanielh...@gmail.com > http://4thfloor.chattlibrary.org/ > http://www.natehill.net >
