helldive premium irc network document

helldive linking policy - written 02/02/08 inkydropz_

SECTION I - SERVER REQUIREMENTS
all servers requesting a link to helldive have to correspond to the following requirements:

shell access for network admins
some form of ddos mitigation, or at least a 100mbit port (so the little skiddies dont get us)
the latest version of unrealircd (3.2.7 at the time of writing)
ircd setup properly (preferrably in the clean method)
no more than two netadmins per server, no more than two services admins per server
no more than 8 opers
matching network name, cloak keys, and u:lines
o:lines for other netadmins
server must support 300+ users 
maxfd of 1024 or above
ssl and gzipped link (requires latest openssl and zlib on server)
entirely devoid of botnets, drones, and other undesireable material 
server must listen on 6666, 6667 (plain clientsonly) and 6697 for ssl
server must be able to ping sub-hubs in case of main hub firewalling

all servers must be connected 24/7 and keep a stable connection during the trial
link period (see section II), and netsplits must be minimal after that period. firewalling
and ddos does not apply to this requirement.

SECTION II - TRIAL LINK PERIOD
all incoming servers are required to meet the requirements stated in section I, as well as 
to comply during the 30 day trial link period, as current staff will view user interaction 
and ircop compliance. your link may be terminated at any time during this period if requirements
are not met, or excessive ircop abuse is noted. the trial period may end early if all opers
vote and a majority is reached.

SECTION III - LINK MERGE ISSUES
issues such as services databases being merged will be handled after the trial link period has 
ended. our services are anope latest unstable, using no encryption. we use the bs_fantasy_ext
module. 

SECTION IV - IRCD CONFIGURATION
ircds must support ssl and gzip links. oper passwords should be hashed (md5 or sha1)
for extra security, and in the future we may require ssl certs for linking. servers should be
(this is a recommendation for easy configuration and maintainence) configured using inky's
clean unrealircd setup. if you do not wish to set it up like this then you are responsible for
fixing any network issues caused by your server, which may even lead to your server being
delinked from the network if it is not fixed within a certain period of time (usually 24hr 
not allowing extended absences due to vacation, etc) either squit'd and/or link block
removed.

SECTION V - SECURITY AND ABUSE
if a password is leaked or security breached in any way, your server will be immediately
removed from the network, and relink will require the ircd to be managed by a trusted
network official. your netadmin positions will also be revoked to services admin until
further notice. if security is breached once more, your server will be blacklisted and 
delinked for good. 
if multiple abuse complaints (4 or more) are recieved for a particular ircop, it is up to the
server admin to reprimand the abusee. if the situation is not resolved within a set period
(usually 24hr non-withstanding extended absence)  your server will be squit and/or 
link block file removed. if the head admin of the server is the abusee, the server will be
delinked and relink requests will only be accepted if the abusee re-enters a trial link
period. 

SECTION VI - MISC. INFO AND STATEMENTS
the official network channel is #spk.
your server should restrict the setting/removing of usermodes +iwxs
we do not use host-on-oper-up
we do not care if you keep your server name, as long as all other info is acceptable
your server has to have an oper on at least every 12hr
your server has to have at least 70 users on average

note: this document is in an alpha stage. contents may change at any time.