The purpose of these procedures are (1) to document the requirements of organizations that are not part of the University of Georgia (UGA) that wish to connect to the UGA campus network in support of collaborative activities involving UGA and non-UGA personnel, and (2) to assist the central computing organization which operates the campus network, Enterprise IT Services (EITS), in assessing the need for such connectivity and administering this service when provided. The need to document the conditions under which such network connectivity can be established is a consequence of the general circumstance that use of UGA computing and networking facilities is limited to official University functions and then normally only by persons directly affiliated with the UGA.
Access to and use of UGA computing and networking facilities by organizations not directly affiliated with the University must involve work to be performed that relates directly to or is in support of UGA or University System of Georgia (USG) sponsored activities. The most common examples of these activities are cooperative research, service or instructional agreements between units of the University and governmental agencies (e.g. the U.S.D.A., E.P.A. or U.S. Forest Service), commercial sponsors (e.g., incubator programs such as the Synergy or Georgia BioBusiness Centers) or USG satellite programs (e.g., the MCG School of Nursing). When campus network connectivity is provided under these circumstances it will be to provide access to those information resources available at UGA that are vital to collaboration or to facilitate communication between the parties involved.
The non-UGA organization will be responsible for obtaining any network names and addresses such as domain names and IP addresses required to establish the requested connectivity. EITS can assist those organizations unfamiliar with this process. Unless otherwise agreed to in advance, any connectivity established must be mediated by router interfaces capable of supporting the protocols to be transported.
Access by persons not directly affiliated with the University of Georgia must also be sponsored by an established business or government office willing to assume responsibility for payment of any exceptional service fees, equipment costs or installation expenses incurred. Note that a monthly building connectivity fee is charged to both University and non-University network subscribers to defray in part the cost of deploying and supporting campus trunk network facilities. Access in the name of private individuals will not be established.
Campus network connectivity requests by organizations not directly affiliated with the University of Georgia must include the information specified in the UGA Network Connectivity Request Form for Non-UGA Organizations and be submitted to the following office:
David Matthews-Morgan
Associate Director, Network Operations & Infrastructure
Enterprise IT Services
Computer Services Annex
University of Georgia
Athens, Georgia 30602
Requests for network connectivity will be responded to promptly in writing.
This section is intended to provide a set of specifications for connecting non-UGA organizations to the campus network. The primary purpose for these specifications is to protect both UGA and non-UGA computing and information resources that are not in the scope of the sponsored projects. Although most organizations will be connected to the UGA network either via some form of telephony (e.g., 56 Kbps or 1.544 Mbps [T1]) wide-area network (WAN) service or a LAN service such as Ethernet, this document will only specify the requirements for routing devices and the attachment of those devices to the UGA network. Non-UGA organizations are free to specify and implement additional networking features such as security firewalls on these devices as they deem appropriate. It is important to recognize that the devices connecting the UGA and non-UGA networks may not be able to provide all of the necessary protection and that each organization is ultimately responsible for protecting their computing and information resources from inappropriate use. Although this document represents current specifications for connection to the UGA network, it is subject to review and modification as technologies and policies change.
All attachments to the UGA campus network will be coordinated through EITS Network Operations and Infrastructure (NOI). EITS NOI will assist with device installation and configuration in accordance with the specifications in a cooperative agreement or needs of a pilot project. The EITS Network Operations Center (NOC) will provide regular monitoring of the organization's connection to the campus network. In addition, the EITS Network Information Center (NIC) will serve as the focal point for name and address coordination functions.
Each non-UGA organization is expected to identify a network liaison who can serve as a point of contact with the EITS NOC and NIC. The network liaison is expected to provide name and address coordination functions such as requesting IP network advertisements. That individual will also serve as an initial point of contact for resolving network problems involving their attached network.
Only one communications protocol (IP) will be permitted between UGA and non-UGA networks. This protocol *must* be routed rather than bridged between the networks. For WAN point-to-point connections, two routing devices supporting IP will be connected together via suitable interfaces, with one device directly connected to the UGA network and the other to the non-UGA network. If the organization attaches their network infrastructure via a direct LAN connection, one router (at most) will be involved. The physical connection of the router on the UGA network will be via some form of Ethernet (10BaseT, 10BaseFL, 100BaseT, 100BaseFX, 1000BaseT, 1000BaseSX or 1000BaseLX) depending on the attachment available in the building where the router resides. The physical attachment of the non-UGA router will be specified by that organization.
The following subsections describe specific requirements for the IP protocol, including name and address requirements, acceptable frame formats, routing protocols, and filtering and management capabilities.
Non-UGA organizations must obtain and manage their own IP address space (typically one or more class C IP networks) and must obtain their own domain name service through non-UGA providers. The routing devices, especially the one connected to the UGA network, must adhere to the following specifications:
All routers must provide SNMP V1 management support, minimally supporting MIB II database information. The EITS NOC will minimally configure and manage the UGA-attached router and will be provided with an SNMP read community name for the non-UGA router to enable them to monitor that device. They also will have the authority to disconnect the organization's network from the UGA campus network if they determine that this device is causing any loss of service to the UGA community.