II. Authority and Responsibility
Information Systems and Computing's Networking & Telecommunications organization is responsible for the operation of Wireless-PennNet (Penn's wireless data networks) and has the authority and responsibility to specify requirements for any devices connecting to PennNet that can be used to extend network connectivity. This authority extends to devices that could adversely impact the operation of ISC N&T registered network-connected devices.
III. Executive Summary
This policy specifies the requirements and limitations for the operation of Wireless Access Points (APs) and related wireless LAN infrastructure on PennNet. It also provides related "best practice" recommendations on how to do so without impacting other network users.
The purpose of this policy is to specify the requirements and limitations for wireless LAN operation on PennNet. While wireless LANs can provide a very efficient and convenient way to maintain access and provide some limited user mobility, their use under certain circumstances can cause significant problems (see VI. Risk of Non-compliance).
Access Point or AP
A device that provides radio signal connectivity for wireless LAN clients and a wired-network connection, bridging the wireless and wireline networks.
A network node using wireless radio signalling to reach a network through an association with a wireless AP.
Center Frequency or Channel
The specific frequency range at which a given AP and its wireless clients operates within the larger frequency range used by wireless Local Area Networks.
Wireless service that is installed and operated by ISC Networking and Telecommunications
School/Center or Department Supported Wireless Network
A wireless network that is installed and operated by a School/Center or department and connects to PennNet. These wireless networks tend to be much larger, and their coverage can range from an office area to an entire building or complex of buildings. The design and installation of these networks are those that are jointly approved, and in some cases installed by ISC Networking & Telecommunications.
A locally supported wireless LAN consisting of at least one AP that is installed and operated by Penn faculty, staff, consultant, contractor, or student. These wireless LANs are not necessarily supported by a School/Center or Department LSP.
VI. Risk of Non-compliance
IEEE standard 802.11 networks operate using unlicensed wireless spectrum. Given that, only a very small number of wireless APs can be in active operation within a given geographic area without creating performance-degrading interference for each other. Even given limited deployment, it is important to have the AP frequency settings configured in a non-interfering way. For this reason, coordination among those wanting to operate wireless LAN APs is essential.Improper configuration of wireless access points can cause significant networking problems for other users of PennNet, and it can cause interference with other wireless devices. This can make troubleshooting the network more difficult and time consuming, and thus could have financial implications to the user or department.
This policy applies to any device acting as a wireless AP on PennNet and/or in any University of Pennsylvania campus building or open area.
VIII. Statement of policy
B. Notification: Notification shall be made to the LSP and/or
server administrator for the area whenever possible and
C. Remedy: Remedy will normally be the removal of the access
point (AP) from the network until such time as it can be brought
into compliance. ISC Networking & Telecommunications will offer
assistance to the LSP for the area in bringing AP configuration and
registration into compliance.
D. Financial Implications: Charges may be assessed for time
spent by ISC Networking & Telecommunications in troubleshooting
problems attributable to a non-compliant or misconfigured AP.
Please see the Policy on Troubleshooting Charges for Violations of
PennNet Policies for information on additional fees that may be
assessed to cover the costs incurred in troubleshooting related to
violations of this policy.
E. Responsibility: Responsibility for remedy lies with those
responsible for the AP and/or the local area network. In the vast
majority of cases, the area LSP will have involvement in the
implementation of the remedy.
F. Time Frame: AP registration requests that fall within policy compliance can be granted within 2 business days. Requests that involve appeals to this policy can take substantially longer. Non-compliant APs must be remedied immediately to reduce risk of networking failures for other network users. Confirmation of AP validation period should be within 45 days after the report gets sent to the LSP and/or server administrator. No responses after 45 days will be considered non-compliant.
G. Enforcement: Please see the Policy on Computer Disconnection from PennNet at http://www.upenn.edu/computing/policy/disconnect.html.
H. Appeals: Please see the Appeals section of the Policy on
Computer Disconnection from PennNet at http://www.upenn.edu/computing/policy/disconnect.html.