Effective Date

TSO maintains a range of IP network addresses, referred to as OutLANd, that may be used for non-TSO-managed systems. The purpose of OutLANd is to provide a network for systems that require a fixed IP address (and associated DNS name) but are not managed by TSO OutLANd is intended for those with special and compelling computing needs and is not intended as a convenience for users who simply want to administer their own system. Using wired LAWN network ports is an alternative for users who prefer to administer their own machine.

  1. Each OutLANd IP address (and associated DNS name) requires a faculty sponsor. Non-faculty may request, but faculty must sponsor. This provides continuity in the responsibility of maintaining the device.
  2. OutLANd System Administrators must comply with all Georgia Tech computing and networking policies and, in particular, the GIT Computing & Networking Usage and Security Policy (CNUSP) and the CoC Computing & Networking Security Procedures
  3. In keeping with section 2.2.1 of the CoC Computing & Networking Security Procedures, OutLANd System administrators have sole responsibility for their systems. By requesting an OutLANd IP address, you are accepting responsibility for that machine. Your sponsor also shares the responsibility of knowning the nature of the system, the type of data present, and who has access to the system.
  4. In keeping with section 2.2.2 of the CoC Computing & Networking Security Procedures, OutLANd systems should not provide any unapproved services. Examples of services include: FTP, Telnet, IRC, VNC, Active Directory, SQL server, SMTP, DNS, web servers (ie. IIS, and Apache). This also applies to peer-to-peer (P2P) software such as winmx, napster, kazaa, and morpheus. Procedures for requesting new or extended network service can be found in section 2.2.8 and 2.2.9 of the CoC Computing & Networking Security Procedures. 
  5. TSO does not back up filesystems on outLANd machines and is not responsible for any data loss. It is strongly recommended that critical user or project data be stored on InLANd machines (e.g. in the user's network home directory or research group project directory).