Wondering if anyone has established policies, processes or procedures
for working with (responding to) vendors, groups and departments on
campus who have highly specialized wireless requests (err, demands?
needs?) Saying "no can do" might encourage creation of broad scale rogue
wireless networks. Bending to every whim could result in ssid overload,
PCI compliance verifications and maintenance-update race conditions (MAC
tables for hundreds of sensors).
Examples include SCADA networks (Coke machines, environmental
monitoring, Johnson Controls, etc.), POS handhelds (Ticketmaster,
Parking Services), research departments who demand "RF free" areas on
otherwise covered floors, classroom tablets, etc.
Has anyone streamlined these requests or achieved a balance of limiting
specialized wireless networks and a desire to provide customized
wireless services? Really not a question of "could we" (we can see
solutions for various requests) but rather "should we".
Thanks,
Mike
***********************************
Michael Dickson
Network Analyst
University of Massachusetts Amherst
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
