philippelh/ircu2.9.32
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

init

Browse Source
This commit is contained in:
Philippe L'Heureux
2023-12-26 16:40:53 -05:00
commit ab64084f63
93 changed files with 40857 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

63
doc/Europe/CoordEBIC Normal file
View File

@@ -0,0 +1,63 @@
############################################################################
If you like in future to establish a link inside the EBIC area,
please contact the coordinator of the affected toplevel domain.
This coordinator will discuss the link with affected local server
admins and inform other EBIC members about new links. Also a good
idea is to join #EU-Opers and discuss the new link there.
############################################################################
These toplevel domains are currently participating EBIC:
############################################################################
*.at *.ch *.de *.dk *.fi *.fr *.it *.nl *.no *.pl *.se *.uk
############################################################################
The following national coordinators have been choosen for 92/93:
############################################################################
*.at EASINET, ACONET
1. Tom Tom Kovar <Tom.Kovar@rcvie.co.at>
*.ch SWITCH, EUNET/CH
1. StarNet Karim Saouli <Karim.Saouli@epfl.ch>
2. Maxim Maxim Samo <samo@nessie.cs.id.ethz.ch>
*.de WIN, BelWue
1. YeggMan Volker Paulsen <Volker.Paulsen@gmd.de>
2. Haegar Thomas Thissen <tici@uni-paderborn.de>
*.dk DENET, DKNET
1. karthy Karsten Thygesen <karthy@iesd.auc.dk>
2. MAGNA Jens Fallesen <fallesen@login.dkuug.dk>
*.fi FUNET
1. Vesa Vesa Ruokonen <Vesa.Ruokonen@lut.fi>
2. Visti Hannu Visti <visti@sauna.cs.hut.fi>
*.fr EASINET/ROCAD, RENATER
1. Nono Arnaud Girsch <Arnaud.Girsch@insa-lyon.fr>
2. Le_Chat Laurent Montaron <irc@eurecom.fr>
*.it CILEA
1. Allanon Riccardo Facchetti <riccardo@cdc835.cdc.polimi.it>
2. mAu Maurizio Paoluzi <paoluzi@mercurio.dm.unirm1.it>
*.nl SURFNET/NLNET
1. scorpio Cor Bosman <bosman@gene.fwi.uva.nl>
2. Erwin Erwin Bolwidt <erwin@mars.let.uva.nl>
*.no UNINETT
1. Veggen Vegard Engen <vegard@bih.no>
*.pl POLIP
1. Artur Artur Jaroszek <artur@vulcan.mimuw.edu.pl>
*.se SUNET
1. Black Christer H. Jansson <svarten@solace.hsh.se>
2. Sorg Owe A Rasmussen <d1rasmus@dtek.chalmers.se>
*.uk JANET, JIPS
1. ScottM Scott A. McIntyre <scott@shrug.dur.ac.uk>

171
doc/Europe/IRCNO Normal file
View File

@@ -0,0 +1,171 @@
European Board of IRC Coordinators - Norway
Email: op-no@nvg.unit.no
Versjon: 1.01-001
Dokument: IRCNO-ORRO 06.07.93 - 03:51
File: flode.nvg.unit.no:/pub/irc/ircno/english
--------------------------------------------------------------------------------
IRCNO in English.
IRCNO is the Norwegian name for EBIC - Norway.
Introduction
~~~~~~~~~~~
The purpose of IRCNO is to make IRC in Norway as effective as
possible. To achieve this, it has to seperate components, an
administrative and a techincal.
The administrative component enforces compliance with the IRC rules in
Norway. The purpose of the rules is not to make operators net-police,
but action must nonetheless be taken when rules are not complied with.
Furthermore, we create national statistics on servers and users
connection time. (This info is however only available to the operators).
We also document IRC in Norway, and keep information files updated.
Finally, we give heavy user-support. All documentation, information
files, and user-support files are in the Norwegian language.
The technical component consist mainly of ensuring the proper and
reliable functioning of Norwegian servers and links, so that IRC in
Norway is compatible with the rest of the EBIC IRC Net.
IRCNO also has its own email adress for any inquiries: op-no@nvg.unit.no
IRCNO has official support from the Norwegian academic network provider
- UNINETT.
IRCNO tasks
~~~~~~~~~~
Here is a list that defines IRCNO's tasks.
1) Take care of the Norwegian IRC servers.
2) Enforce the rules for IRC use in Norway.
3) Be responsible toward UNINETT.
4) Make statistics.
5) Document IRC in Norway.
6) User support.
Rules of IRC use in Norway
~~~~~~~~~~~~~~~~~~~~~~~~~
We have 3 kinds of rules, user-bot, operator and server-admin.
Here is a short translation of the rules
USER-RULES - The following is not allowed:
1) Fake userids, or trying to hide the real user-id.
2) Being intentionally offensive to another user.
3) Dumping a lot of text to a public channel.
4) Constant beeping on a channel.
5) Anything that will reduce the techincal functionality of IRC.
6) Harrasement defined by Norwegian Civil Law.
7) Using offencive words in channel topics on public channels.
8) Destroys the integrity of information.
9) Compromise private communication.
BOT-RULES - The following guidelines must be followed:
1) Bots must not have fake userid unless given permission.
2) Bots must not send a message to a user not activating it.
3) Bots must be invisible unless they perform a good "irc-deed".
4) Bots must only answer to PRIVMSG by using NOTICE.
Dispensation from some of the bot-rules may be given under certain
circumstances.
OPERATOR RULES
This guide gives guidelines on what is not good and what is good.
Stuff that is not allowed:
- Using SQUIT / CONNECT to gain channel-operator-status.
- Mindless use of KILL.
- Using TRACE to find invisible users.
Stuff that is allowed:
- Using SQUIT / CONNECT to "fix" the net. This is normally not
allowed and should be used with care. The IRCNO tries to make
efficient use of automatic routing.
- KILL should only be used when a user ask to be killed. KILL can
also be used if it's based in a certain paragraph of the USER
rule file.
SERVER RULES
Following is the EBIC-Rules conserning linking. For domestic
linking we have our own rules.
1) To get a server connect to the Norwegian IRC-net:
a. New servers must only be leafs.
b. New servers must have one primary- and one secondary link.
c. New servers should only have one active link at a time.
d. The new server must have enough users.
2) New server connections should be discussed among the existing oper/admins.
3) Any link should follow the physical net-topology.
4) A server that is not close to a regional UNINETT net center should not
perform as a HUB server.
5) Every server in Norway takes part in the national user-staistic.
6) If hostmasking is to be used, every server behind a mask must be able
to connect to the up-host.
ADMIN RULES
1) An irc-admin must be available by email, unless he/she notifies IRCNO
about any longer planned absence.
2) A server-admin's duty is to have his/her server perform well for
the end-users and other servers on the irc-net.
3) An irc-admin must upgrade his/her server and tune it according to
something suitable as soon as a server-release is known to be
relatively stable.
4) An irc-admin that is not following these rules can loose his/her links
if 100% of IRCNO agrees.
Persons in IRCNO
~~~~~~~~~~~~~~~
We do not have any leader or jobs, but we do preform certain tasks.
Every decision is taken by discussion and voting. We do not have any
problem with this, and no nasty disagreements occur. This we belive
is because of our Norwegian Nature :-)
Who is Who is documentet in the file called irc-no. Norwegian titles
in paranthesis.
IRCNO secretary (IRCNO sekret{r)
Keeps track and system of all docs that are produced within IRCNO.
The updating of the various documents is left to the one who has
the administrative job with the document.
Filearchive (Filarkiv)
Keeps the anonymous FTP archie at flode.nvg.unit.no up-to date.
The archive is also accessible by FSP. The archive consist of
IRCNO docs, IRC docs in general, and IRC software.
This person also administrate the two mailinglists that exist (IRCNO
and a IRC-user list)
Statistics: (Statistikk)
Does the monthly stats of IRC-use in Norway.
EBIC contact (EBIC kontakt)
This task is defined in the EBIC-rules.
Link master (Link ansvarlig)
Job is to find the best links for Norwegian servers, and how they
should connect to each other. In link-matters this person often
has the last word. The link master write a link-report from time
to time (found on the archive as "links"). This report is the only
english document beside this one. This person must have good
knowlege on net-structure in Norway and how the server-linking works.
UNINETT contact (UNINETT kontakt)
UNINETT want one contact person. This person will likely aslo be
known as the one who is "responsible for IRC in Norway".
Other stuff
~~~~~~~~~~~
For a list of servers and their associated persons, see the file irc-no
under "servere in IRCNO".
This document is proof-read by Espen Anneling (anneling@uiowa.edu)

90
doc/Europe/RulesEBIC Normal file
View File

@@ -0,0 +1,90 @@
########################################################################
##### RULES FOR ESTABLISHING NEW IRC SERVERS IN EUROPE (v1.1) #####
########################################################################
1.) Establishing a new server and inner domain linking should be
a local toplevel domain (country) decision.
Guidelines:
+ New servers should be leafed until their admin(s)
have sufficient experience to handle their server
responsibly. (This avoids routing disasters).
+ 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 hierachy).
+ Be sure that if a toplevel domain hostmask link is given,
all hubs of that domain can connect the masked server!
(this should avoid disagreement between serveral hub
admins in one domain).
2.) All other links between toplevel domains (countries) should be
dicussed between the major link coordinators of each toplevel
domain (country). These coordinators are called European Board
of IRC Coordinators (EBIC).
Guidelines:
+ Major link coordinators of each toplevel domain (country)
should be published with the server sourcecode in
directory ./doc/Europe
+ Each toplevel domain (country) participating in the
European IRC net must have a coordinator, who is
responsible for country-internal connections AND
represents the country in contacts with the rest of the
world. This person(s) is (are) chosen by their domain,
but must be approved by the EBIC.
+ The EBIC is the only executive in charge of European
interconnections and of connections from Europe to the
rest of the world. They will decide linking issues
WITH the affected local admins.
+ For establishing new links between several toplevel
domains the affected EBIC coordinators should be
consulted. If further coordination is needed it should
be discussed within the EBIC.
+ Additional note: International links should also take
care of the network topology, so even if several national
opers agree on a same international link, they might be
wrong and use unecessary network ressources. The EBIC
should avoid such linking.
+ Any major linking change should be announced in the
european mailing list:
IRC-Operators Europe <irc-eu@grasp.insa-lyon.fr>
3.) Cracked servers are the concern of EBIC, overiding 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) EBIC will take action.
+ The recommended action is permanent withdrawl of the
server from the IRC-net by removal from all its uplinks
configuration files.
4.) A prerequisite for getting a NEW server connection within
Europe is an understanding of and compliance to the above
rules.
Guideline:
+ All new admins should get a copy of these rules.
############################################################################