1. Introduction

This section contains Mobile Wireless Networking Regulations as approved by ICTC. These rules and regulations will evolve as experience is gained, and should be considered a supplement to the existing University IT facility regulations. The following represents the current thinking and is similar to that in use elsewhere; a short rationale for each point is given.

2. Regulations - Terminology

To avoid ambiguities, we have used particular terminology when explaining the rules:

This word, or the terms "REQUIRED" or "SHALL", mean that the item is an absolute requirement of any Mobile Wireless Network.

This phrase, or the phrase "SHALL NOT", mean that the item is an absolute prohibition of any Mobile Wireless Network.

This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.

3. Requirements

A wireless network must not be operated without the knowledge and permission of the unit in which it operates. Rogue access points compromise security and interfere with normal operations.

This is in order to ensure users can configure their clients in any part of the Collegiate University, and receive an equivalent service wherever else that SSID is in use.

It is a requirement of the University's participation in the Eduroam Federation that we undertake to protect the use of the eduroam SSID namespace.

A database of all established networks, and who is responsible for them, will assist in maintaining control of the network and when considering and advising upon the installation of further networks.

This is a basic security procedure. If it is part of a unit's main network, then anyone who connects to that access point will become part of that network.

This is self explanatory, and exists to support the University and Janet IT use regulations.

Wireless network traffic is readily available for anyone to see, even if they have not associated with an access point. Encryption is necessary to ensure that data, such as passwords, cannot be seen.

Examples of this include proxy, relay, DHCP, routing services etc. This refers to client operations, not system provided facilities.

In the event of abuse of the connection, for whatever reason, it is vital that the user concerned can be identified.

4. Recommendations

This is the Wi-Fi standard most commonly be available on clients.

Compatibility between equipment cannot be guaranteed unless it has been tested. Wi-Fi approved equipment has been through the approval process - so it will work.

IP is the protocol of choice - all others are treated as legacy protocols by the University and have dwindling support

Use of high signal strengths causes the signal to propagate into areas where coverage may not be required and, indeed, could provide potential connectivity to people for whom it is not intended. Reducing power levels reduces leakage and interference problems.

Suitable choices of channel allocations can reduce interference between multiple access points, thus improving signal strength to clients and allowing higher throughput. The limited number of available channels (three) at 2.4 GHz means that this is recommended.

As wireless technology is a shared medium with limited bandwidth, it is possible for one user to utilize the majority of the bandwidth. If anyone has high bandwidth needs then a normal 'wired' connection should be used.