OPER POLICY:
Behavior:
Opers will not use their IRCop privileges when dealing with non
policy violations in their own private channels.
All kill msgs must clearly state a valid reason for the kill so
it's apparent to all why the person was removed from the net.
This includes kills of other opers which should clearly state
that it is a vanity kill or a congratulations kill.
Opers will NOT kill another oper on the request of a user.
No vanity kills of users. There must be a valid reason (ie: flooding,
spaming, etc...) to kill a user.
Opers are allowed 2 back up O lines on servers other than their
primary server.
The net reserves the right to remove any O line/s for an oper
with a majority vote by server admins, founders, and global opers.
The AokChat IRC Network's IRC Operator Policy - May 18, 2003
============================================================
1. IRC Operator Privileges
--------------------------
Being an IRC Operator is a privilege and not a right.
Do not take IRC Operator Privileges lightly. Abuse of them will
get an
IRC Operator's oper{} block suspended, demoted or removed permanently.
2. IRC Operator Responsibilities
--------------------------------
Network Administrator
- Maintain order and control over the network and its
IRC Operators.
- Create, modify or remove rules which are intended to
maintain a properly running IRC network.
- Schedule monthly IRC Operator meetings.
- Be available at any reasonable time in order to
acess issues and concerns from anyone.
- Enforce rules upon other IRC Operators and their
Server Administrators.
- Also responsible for Server Administrator and IRC
Operator's responsibilities.
Server Administrator
- Maintain a server with current AokChatIRC standards.
- Maintain a stable server uptime and link time.
- Watch over the server's IRC Operators and enforce rules
outlined in this document.
- Also responsible for IRC Operator responsibilites.
IRC Operator
- Spend at least 7 hours a week visiably on IRC.
- Protect the network, and its resources against anyone
wishing to do harm.
- Maintain a routed network.
- Join #AokChatIRC and assist the network.
- Help all users requesting help in any channel.
- Attend IRCop Meetings and provide ideas and suggestions.
- Follow all rules of AokChatIRC.
3. AokChatIRC Standards for a Server
----------------------------------
REQUIRED
- Upgrade the IRCD within 7 days of a new release
- Upgrade the IRCD within 24 hours of a security fix
- Run confsync once a day in crontab
- Manually update unrealircd.conf options within 3 days of a request
- Run a time sync program at least once an hour
- Upgrade third party software when security issues are known
OPTIONAL
- Run a firewall and block all unused ports and secure open ports
Failure to follow the REQUIRED standards will result in a server
being
JUPED or delinked.
4. The AokChat IRC Network's Operator Chain Of Command
----------------------------------------------------
To maximize efficiency on AokChatIRC, the Chain Of Command should
be followed
when dealing with problems that may arise. This Chain of Command
refers to
the IRC Operators on a Server and then to a Network Administrator.
This includes not only problems with users on the Network, but
also
problems with other IRC Operators.
The Chain Of Command is as follows:
Local IRCop -> Global IRCop -> Server Co-Admin -> Server
Admin ->
Co-Network Admin -> Network Admin
Emergencies such as someone attempting to hack one of AokChatIRC's
servers or
services should be immediately reported to a Network Administrator.
5. KILL, GLINE, KLINE and ZLINE
-------------------------------
KILL, KLINE, GLINE and ZLINE are IRC Operator commands that allow
an IRC
Operatorto deal with users who are causing trouble. They are to
be used as
a last resort when normal user commands and common sense procedures
are not
working.
Each IRC Operator is to use their best judgement on when a KILL,
KLINE, GLINE
or ZLINE is necessary. If there are any questions on whether it
is
appropriate, they should be directed to the Server Administrator
or a Network
Administrator.
The use of KILL
---------------
All IRC Operators have access to KILL. Local IRCops can only
KILL on their
local server. Global IRCops, Server and Network Administrators
can KILL
globally on any server.
Before an IRC Operator uses KILL to disconnect a user make sure
it is
absolutely necessary and there is no other way to solve the problem.
Just
because an IRC Operator can use KILL doesn't mean they have to.
The use
of IGNORE or BAN is very useful and usually can solve the problem.
All KILLs should have a clear reason so others will understand
why a user
was disconnected.
Examples of when NOT to use KILL:
1. If a user is harassing and indvidual. (Use /ignore)
2. If a user is harassing a channel (Use /ban)
Examples of when to use KILL:
1. Breaking the rules of The AokChat IRC Network User Policy or
the
rules of a Local Server.
2. When BAN or IGNORE is NOT working and after warning the user
of their
inappropriate behavior.
3. If a user is harassing many channels or users.
The use of GLINE
----------------
Global IRC Operators, Server and Network Administrators may use
GLINE to
solve any problems that KILL has not been able to stop.
Before an IRC Operator uses GLINE to BAN a user from The AokChat
IRC Network,
attempt a KILL first to make them think twice about what they
are doing. If
the user repeatedly continues to abuse the rules, a GLINE may
be appropriate.
The user's ISP should be contacted whenever a GLINE is created
that lasts for
more than 4 days.
All GLINEs should have a clear reason in English so other IRC
Operators will
understand why a user was banned.
Examples of when NOT to use GLINE:
1. Seeing multiple logon and logoff notices from someone. Use
a KLINE if
it is appropriate to ban this user from the server.
2. User should be banned from a single channel.
Examples of when to use GLINE:
1. KILL does not seem to persuade a user to stop.
2. Any attempts on hacking the network is an automatic GLINE.
Also
notify a Network Administrator ASAP.
The use of KLINE and ZLINE
--------------------------
All IRC Operators can use KLINE and ZLINE to ban a user from
the server the
IRC Operator is currently logged on. KLINE and ZLINEs are not
global bans,
instead they ban a user from being able to log on a single server.
The user
may log on any other server that does not have a KLINE or ZLINE
on them and
still access the network.
The difference between KLINE and ZLINE is that ZLINEs are the
most powerful
ban available. They ban an IP address and the server immediately
terminates the connection when it's detected.
It's usually more appropriate to ban using KLINE as it will give
the user a
reason for why they are unable to connect.
All KLINEs and ZLINEs should have a clear reason so others will
understand
why a user was banned.
Example of when NOT to use KLINE or ZLINE:
1. User should be banned from a single channel.
Example of when to use KLINE or ZLINE:
1. A user is abusing a local server's rules.
6. CONNECT and SQUIT
--------------------
CONNECT is used to connect one IRC Server to another. SQUIT is
used to
disconnect an IRC Server from another.
The Use of CONNECT
------------------
All IRC Operators have access to CONNECT. Local IRC Operators
can only
CONNECT their local IRC Server to another. Global IRC Operators,
Server
and Network Administrators can connect remote servers as well
as their
local server. In order for a CONNECT to be successful, both servers
must
be configured properly with link{} blocks according to AokChatIRC
standards
and must have been approved by the Routing Team.
It is the responsibility of all IRC Operators to be aware of
when a server
is disconnected. Disconnected servers are to be reconnected by
its IRC
Operators within 15 minutes or an attempt to CONNECT it remotely
should be
executed if the reason of the disconnect was unplanned.
If after several attempts, over a reasonable period of time,
a server
cannot be relinked, then the server should be considered "dead"
and
further attempts will not be required.
Servers are only to CONNECT to other servers according to the
routing map.
The Use of SQUIT
----------------
All IRC Operators have access to SQUIT. Local IRC Operators can
only
SQUIT their local IRC Server from another. Global IRC Operators,
Server
and Network Administrators can SQUIT remote servers as well as
their local
server.
The use of SQUIT should rarely be used since a disconnected server
serves
no purpose off The AokChat IRC Network.
A SQUIT is most commonly used to reroute a server to another
server on the
Network to help prevent network lag or prepare for a planned network
split.
Before a server is SQUITed, the IRC Operator of that server should
notify
the other IRC Operators, preferably a Network Administrator, for
the
reason of the SQUIT and also perform a Wallop explaining the reason.
This helps prevent another IRC Operator from attempting a reconnect
and
lets everyone know why the server left.
7. OperMode
-----------
OperMode is used automatically when a Global IRC Operator, Server
or Network
Administrator performs a standard IRC command, such as MODE, BAN
or KICK
when they are not a Channel Operator. This IRC Operator privilege
is
discouraged and users should use The AokChat IRC Services to keep
control over
their channels.
Examples of using OperMode:
1. Kicking a user from a room when the IRC Operator is not opped.
2. Oping yourself or someone else in a room when the IRC Operator
is not
opped.
3. Removing BANs from a room when the IRC Operator is not opped.
4. BAN Walking.
An IRC Operator will NOT need to use OperMode without reason.
NickServ and
ChanServ give all the access to the users to handle Oping themselves
in
their own channel, unbanning themselves or for getting their channel
back
after someone maliciously takes it over.
8. IRC Operator Broadcast Messages (Wallops, Locops, Chatops and
Globops)
-------------------------------------------------------------------------
There are times when IRC Operators may be required to provide
warning,
notice or discussion over some Server or Network related issues.
These messages are not ment to be used for general chat, except
for
Chatops.
Wallops
-------
Wallops provide a way of broadcasting messages to the entire
network.
Not only do the IRC Operators receive these messages, but anyone
who has
set UMODE +w can view them as well.
These messages are generally used for notices if a server is
going to be
SQUITed, CONNECTed or any other basic Network Related issues or
problems.
Locops
------
Locops provide a way of broadcasting messages to only the local
server.
Locops are a good way of discussing Server problems that does
not
require the entire network to solve.
Globops
-------
Globops provide a secure way of broadcasting messages to the
entire
network. Globops are different from Wallops in that they can only
be seen
by IRC Operators.
Chatops
-------
Chatops provide a secure was for IRC Operators to participate
in general
discussion.
9. The AokChat IRC Network's Teams
--------------------------------
There are several different teams that run The AokChat IRC Network.
These teams
provide the network with the latest technology, security, configuration,
ect.
Team Meetings
-------------
Each team should have at least one Team Meeting per month. It's
up to the
team when the meeting will occur. Topics discussed should involve
problems,
concerns, updates, ideas, ect.
Team Participation
------------------
Each member of the team must participate in some way to help
the team.
Whenever a request is made to the team to provide an update or
change, it
should be executed as soon as possible.
10. Network Related
------------------
There are many security and privacy issues to contend with. Most
of which
should be brought to the attention of the Administrative Team
when the time
arises.
Abusive IRCops
--------------
Abuse of an IRC Operator's oper{} block will not be taken lightly
and will
result in suspension, demotion or removal of the IRC Operator's
oper{}
block if their actions are determined inappropriate by the Administrative
Team.
Abuse of server realated issues may result in the server being
JUPEd and
its link{} and oper{} blocks being removed from all other servers.
Abuse is considered violating this document, the User Policy
and/or
performing actions found inappropriate by the Administrative Team.
oper{} block
------------
All oper{} blocks on all servers are to be approved by the Administrative
Team before they are added or removed. This is necessary in order
to
prevent excessive IRC Operators on the network.
Each Server may have the following number of oper{} blocks after
they are
approved:
- One Server Administrator
- One Server Co-Administrator
- Two Global IRC Operators
- Three Local IRC Operators
Other oper{} blocks may be added with the approval of the Administrative
Team.
In the case that a server is scheduled to be down for three days
or more,
temporary oper{} blocks on another server may be approved by the
Administrative Team.
New IRC Operators
-----------------
The user must have had their nick registered with ChanServ for
at least
30 days and have been actively participating in network related
issues.
New IRC Operators must attend at least one scheduled IRCop Training
Meeting and pass a test showing they know enough to become an
IRCop.
Before a new IRC Operator is allowed an oper{} block, they must
also be
approved by all Network Administrators.
New IRC Servers
---------------
- The server admin must meet all criteria in linking.txt.
- If approved, the server will be on a 45 day test link period
where it's server admin and ircops are monitored.
- At the end of 45 days, a vote is held by all IRC Operators.
Network Routing
---------------
All Network related configuration lines are to be submitted to
the
Routing Team at routing@AokChatirc.org to be approved before they
are to be
added to the server.
All servers are to stay routed according to the current routing
map at
its Primary Link at all times unless that server is down, in which
case,
the Server Administrator is to link to thier Secondary Link. If
both
servers are down, contact the Routing Team and have a temporary
Link
approved and setup until one of the routed servers returns.
Net Splits
----------
Any available IRC Operator must attempt to reconnect the missing
server
or service immediately.
When a server or service cannot be relinked, it may be rerouted
to its
secondary link until such time that its primary link can be restored.
When a server cannot be relinked or rerouted and attempts have
been made
for no less than 30 minutes, an email must be sent to
routing@AokChatirc.org with the following:
(1) Which server(s) or service(s) are down.
(2) Names of each IRC Operator who participated in
attempting to reconnect the server(s) or service(s).
(3) Procedures that were attempted to relink.
Network Configuration
---------------------
All server configuration files must be up-to-date with the rest
of the
network. They confsync script will do this automatically and should
be run once a day.
Important network configuration can be found on the IRCop's web
page.
Each Server Administrator should keep their configuration files
up-to-date with this page.
Server Software
---------------
The AokChat IRC Network uses Conference Room by Webmaster IRCD
Each server is responsible for keeping up-to-date on which version
of
the IRCd should be used.
Privacy
-------
The use of any program, such as a port sniffer, to intercept
communication between servers or between users is prohibited.
11. Ammendments
---------------
The Administrative Team, which consists of all Network
Administrators, reserves the right to change anything contained
in
this document at any time without prior warning.
