Rules for IRC networking
                                      
    1. The establishment of new servers and intra-domain linking should
       be a local toplevel domain (IE: country) decision.
       
    Guidelines:
       * Only a link for ONE server should be given to the new server
       site, that means the new site shouldn't be able to connect
       test-servers to other than its own server. (This avoids confusion
       about linking heirachy).
       * If a toplevel domain hostmask link is given, ensure that all
       hubs of that domain have connect access to the masked server (this
       should avoid disagreements between hub admins within a domain).
       * A previously agreed-upon minimum number of users must exist
       before the server can be granted links.
       * New servers will be L: lined for at least 60 days. An exception
       will be be made for new servers brought up specifically to replace
       an old hub. In most cases, the old hub admin or another trusted
       admin must be admin of the new server for this exception to apply.
       After the 60 days, the L: line will be removed only if the server
       is in an exceptionally good position to hub.
    2. Hacked or cracked servers (and the machines they run on) are the
       concern of all Admins, and override all local interests.
       
    Guidelines:
       * In a server with non-standard source code which breaks the
       current irc protocol (especially the incorrect manipulation of
       channel modes and user/hostname authen- tication) Admins will take
       action, this includes the testing of these patches. [any patches
       for testing should be tested on a seperate network where the
       testing will not disrupt the users].
       * The recommended action is permanent withdrawl of the server from
       the IRC-net by removal from all its uplinks configuration files.
    3. The Admins are responsible for all operator access. IRC
       Administrators should therefore be approved by the machine and
       network admins for the site in question.
    4. Operator power may be used only on server and network maintenance
       purposes. KILL may be used only when other methods to fix a
       problem don't exist. KILL or SQUIT should never be used to fix
       channel or nickname problems. (the only exception being the
       KILLing of a "real ghost").
    5. Server administrators should take care to manage their server
       properly. All server administrators (especially servers that are
       open to non-local-site clients) are encouraged to keep 2 weeks of
       userlog files. This will make abuses easier to track (if a server
       administrator gets email complaining about a certain problem user,
       the administrator can search through the userlog to see if there
       is evidence of the abuse).
         _____________________________________________________________
       
       Infringement of the rules as outlined above should lead to
       operator and/or admin changes on the offending server.
       Responsibility for these changes is primarily that of the uplink
       server administrators.
       In the event of continued transgression, further action may be
       taken by remote IRC Administrators 24 hours after the problem has
       been identified and all responsible parties have been notified.
       All intended additions to this document must be announced to IRC
       Administrators for at least one week prior to ratification.