Server routing

All global IRC Operators are expected to help with routing and recovering from network disruption. If server rerouting is required, an IRC Operator must first warn fellow staff:
/chatops I'm about to reroute neo, scream now if this is bad
(wait 10 seconds or so)
Then users due to be affected by the upcoming split MUST be warned via services global notice or a mass-notice:
/notice $neo.*KDFSnet.net users, the server you are using is shortly going to be rerouted to reduce lag. Please bear with us.
And finally the reroute takes place.

Please note that servers normally recover from netsplits themselves due to autoconnects defined in their configs. There should be no need to intervene unless there is a problem. For example, a server may be able to connect to its primary hub but packet loss on that link may be unacceptable, therefore requiring a reroute to its secondary hub.

Unnecessary rerouting of client servers is frowned upon - a few hundred milliseconds extra lag is not normally noticeable for users, unlike a netsplit.

The current optimal routing plan for the network is decided and documented by The Admin team.

Emergency Action

Any admin or services admin may take emergency action to immediately resolve or mitigate network problems. This includes actions that would normally require a full admin vote.

This can include immediate delink of servers or linking of new servers without the normal test-link procedure being followed.

The staff member is required to explain their actions in full to the Admin Team ASAP. Obviously, these actions should not be taken lightly and staff causing unnecessary damage to the network should expect to be reprimanded once the dust has settled.

Change of Server Details

Admins are permitted to alter their server's details such as operating system, hardware, and/or bandwidth. The Admin Team should be informed of any such changes.

Should a server need to move location net-wise from its current local network, then the server may need to reapply for a test-link period. This, of course, will be approved/denied at the discretion of the Routing Team.

The Admin Team must be informed by email to staff(at)kdfs.net at least 48 hours prior to the change of a server Admin so that any possible objections can be made clear. Should any objections not be resolved in discussion by the Admin Team then an admin vote will be called to decide whether the server should go through a new test link period, continue to be permanently linked with the new Admin or be delinked.