Difference between revisions of "Network Policy"
|Line 20:||Line 20:|
== Delinking Procedure ==
== Delinking Procedure ==
== Voting Procedure ==
== Voting Procedure ==
Revision as of 12:36, 9 January 2020
- 1 Introduction
- 2 Precedence of Network Policy
- 3 Delinking Procedure
- 4 Voting Procedure
- 5 Changing Network Policy
- 6 Nodes
OshaberiNet is a collaborative effort between volunteers. This document describes the day-to-day procedures for operating the network.
Global operators own and maintain a hub node. This type of operator may take action on the entire network such as banning a user from all servers. They may also appoint a single local operator to assist with the operation of their node.
Local operators may own a leaf node or be appointed by a global operator. This type of operator may take action on single node in the network.
All global operators are services operators. Services operators are able to take action on the services system.
Precedence of Network Policy
Network Policy as described in this document shall override local node policy in all cases. All nodes and operators must abide by network policy.
Should a node fail to fully implement network policy a thirty day grace period will be extended to allow for its owner to make necessary changes. If at the end of the grace period the node owner has not complied the node will be delinked in accordance with the Delinking Procedure described in this document.
It is necessary to delink nodes during the normal operation of the network. A node may be delinked on a temporary of permanent basis.
Global operators may temporarily delink any node should it adversely impact the regular operation of the network.
The following must occur before executing a temporary delink:
- A best-effort should be made to contact the operators of a node so that they may resolve the problem.
- The intent to temporarily delink and justification must be posted to the operators channel.
- A WALLOP must be sent notifying users of the impending delink action.
A temporarily delinked server will remain delinked for 12 hours or until the operators of the node have resolved the problem that resulted in the delink.
Votes must be cast as part of governing the network. Voting should be carried out as follows:
- All operators must vote yea/nay or abstain.
- Votes from Global Operators shall be counted on a 1-to-1 basis.
- The simple majority result from the Local Operators shall count as 1.
- Votes from Global Operators and simple majority result from Local operators shall be summed for the final result.
Should a voting action result in a tie, the voting action defaults to nay.
Changing Network Policy
Network policy may be changed to better suit the needs of the network and its users.
Changing the Network Policy requires that:
- The change be sponsored by a Global Operator.
- The change shall have a scheduled discussion period in the operators channel.
- The voting procedure described in this document shall be carried out to confirm (yea) or reject (nay) the proposed change.
- All nodes must have a regularly scheduled maintenance period that is posted on the Oshaberi wiki and included in the message of the day.
- Changes that may interrupt service should be completed during the regularly scheduled maintenance period for the node.
- Node owners should send a WALLOP before commencing and after completing maintenance on a node.
- Nodes must be regularly patched according to the recommendations of the operating system vendor.
Should a problem be identified with a node that impacts the day to day operation of the network, the node owner will be notified and given 30 days to correct the issue or take appropriate mitigating action.
- All nodes must adhere to the baseline configuration stored in GIT_REPO to ensure interoperation and consistent experience for end users.
- All nodes must have an always-on internet connection with a dedicated static IP address.
- All nodes must have matching forward and reverse DNS records.
- The public IP address of a node must only accept connections necessary for operation of the network.
Procedure For Adding A New Node
As nodes are retired or the network grows it may become necessary to add nodes to the network. Any person may apply to run a node, subject to the following procedure.
Apply To Host A Node
- A current Global Operator must sponsor the application.
- The Voting Procedure described in this document shall be carried out.
Should the vote not be found in favor of the applicant their application shall be rejected.
Should the vote be found in favor of the applicant a provisional period of 60 days shall be established.
The Provisional Period
The sponsoring Global Operator (sponsor) shall be responsible for guiding the applicant, providing feedback, and acting as a primary point of contact during the provisional period.
New nodes in the provisional period shall be linked to the sponsoring Global Operator's hub server as a leaf node only.
Operators of a provisional node may not participate in a Voting Procedure.
At the end of the provisional period the Voting Procedure shall be carried out to determine final acceptance of the node.
Should the vote not be found in favor of accepting the node it shall be delinked according to the Delinking Procedure as described in this document.
Should the vote be found in favor of accepting the node it shall be added to the round robin DNS record and its operators will gain voting privileges, joining the network as a permanent node.