Network Protocol Guideline
The Carnegie Mellon Computing Policy establishes a general policy for the use of computing, telephone and information resources. The purpose of this guideline is to establish acceptable practices that support the policy as it applies to network services and protocols.
This guideline was established to ensure that the Carnegie Mellon community has a clear understanding of the network services and protocols that may cause network problems. In some cases, the protocol or service has potential to be so harmful that it has been banned from use on campus.
Computing Services reserves the right to modify this guideline as necessary. Any changes to this guideline will be posted to official.computing-news and will be reflected on this web page.
This guideline applies to all campus affiliates. This includes students, faculty and staff members as well as guest account holders.
- Dynamic Host Configuration Protocol
- Internet Protocol
- Service Advertising Protocol
Users are responsible for adhering to the Network Protocol Guidelines and the Carnegie Mellon Computing Policy. Any violation of the Network Protocol Guidelines will result in loss of connectivity for the system being used in the violation. If the system is attached via a hub or switch to the network, it may be necessary to disable the outlet to which it is attached. This may result in loss of connectivity for other systems.
In most cases, services will be restored once the system is reconfiguring to adhere to the guidelines. However, repeat offenders may lose connectivity for an extended period of time and may have disciplinary charges filed against them. (Charges are appropriate to the status of the person responsible for the violations.)
User Responsibilities and Procedures
The protocols and services that are banned from use on campus are listed below. To assure that your machine does not inadvertently perform one of these functions, see the Protocol Definitions List.
While we provide this information for most out-of-the-box applications that may cause problems, we do list every possible situation.
Last Updated: December 14, 2005
Established: June 6, 2003