Server Linking Policy

Author: Ben

Generally speaking, link applications are not open most of the time and based on need. There is no queue or waiting list. If you are denied, it’s not personal. There is also a possibility a user may be asked to consider a link, though even that is not a guarantee. The primary purpose of this document is to indicate minimum requirements every server must meet.

As every server administrator is expected to be a services operator (and then some), do not apply if you don’t believe you will be granted the position.

Any link must follow this policy and the stated requirements and expectations.

Technical Requirements

  1. The server must be either a dedicated server, or a VPS (virtual private server). Cable/DSL connections and shell accounts will not be accepted.
  2. The hosting company must be well established and have a good reputation.
  3. The server must be hosted at a datacenter.
  4. Reliability must normally be at least 99.5% overall.
  5. 256MB of RAM (512MB+ is recommended)
  6. RAID storage is highly recommended.
  7. Multiple IPs is highly recommended.
  8. Native IPv6 support is required.
  9. Server load must not normally exceed 0.5 * number of cores.
  10. The server must use Linux or *BSD. Other UNIX-like OSes such as Solaris may be permitted.
  11. The server must be capable of compiling and running ChatIRCd, including maintaining the appropriate build environment.
  12. On the IRC server listening IPs (v4 and v6), ports 6665-6669, 6697, and 9999 must be unblocked and unrestricted (except for hub servers).
  13. The server does not have to be dedicated to being an IRC client server, but it must listen to the standard port numbers on the listening IPs. If the server has other purposes, you may be asked to explain what those purposes are. Other purposes will not necessarily result in an automatic disqualification.

Administration Requirements

  1. As security patches are often released, server administrators are expected to perform updates and install patches weekly.
  2. In addition to being responsible for your servers, the server administrator is expected to engage in moderation tasks to enforce the Acceptable Use Policy.

Other Requirements

  1. The potential server administrator must have root access on the server.
  2. While granting other network staff root access to the server is not required, be mindful of the requirement to keep the server updated with security patches.
  3. Aside from the server administrator, authorized network staff, and/or hosting company employees, no one is to have root access.
  4. Members of the Routing Committee must have shell access to the user account(s) the IRC server and HOPM are running under, for the purposes of possible upgrade/reconfiguration.
  5. Server administrators may not link other servers through their server without prior consent.
  6. Server administrators agree not to set up file permissions in such a way to prevent those with shell access from editing the configuration files. (i.e. setting the files as owned by ‘root’)
  7. DDOS is unfortunately always a possibility, so the provider must not cancel in the event of an attack.
  8. The hosting company must permit IRC software.
  9. A HOPM instance must be operated and maintained on each client server. Hub servers must not run HOPM.
  10. Applicants are not permitted to appoint other individuals to the Staff positions without prior approval.
  11. All Staff are expected to be able to oper on any client server. This includes the applicant, if approved.
  12. There must be a means to contact the server administrator outside of the network, in the event contact is necessary.
  13. Any servers must have the same modules loaded as the other servers, and be similarly configured to have matching nickname lengths and channel limits. Loaded modules are at the discretion of the Founder and Network Administrators.
  14. Server configuration is centrally managed, and up to the discretion of the Founder and Network Administrators. Acceptance of this is a requirement of being approved.
  15. Sponsoring a server doesn’t imply, or provide the right to add additional opers without prior consent from the Administration.
  16. Only the Founder and Network Administrators are eligible to sponsor hub servers.