Chatnet Routing Committee (CRC) Policies 

The Routing Charter

It is the responsibility of the Routing Committee to represent the ChatNet server administrators
(CADMIN) in regard to ChatNet network administration. The Routing Committee is a separate entity 
that consists of volunteers from the ChatNet staff. CADMIN will pick a single person to chair the 
committee. This candidate will be a person that CADMIN feels has the best ability to both understand 
routing and effectively lead a group. That person will pick his or her team and proceed on 
accomplishing the tasks and goals of The Routing Committee. The Routing Committee chair will 
serve an annual term. There are no term limits defined for this position. 

New Applications

All applications will be responded to (initial contact) in 10 working days except during holidays. 
Upon receipt of an application via the CRC web site, a routing member will review the application 
for legitimacy and for any missing information. If said member finds something missing, the member 
has the choice to deny the application or to try to discover why this application is incomplete. 
If there is no reply from the applicant in 48 hours, CRC will remove the application. Once the 
application has been reviewed, and if there is no obvious reason to remove the application, 
the CRC member will begin the server qualification footwork. This includes pings, traces, and 
Name server BIND version checks. The CRC member handling the Application is to request pings 
and traces from applicant only to regional hubs. All pings will be 50 packets by 1024 bytes.

Test-Links

After all of the required information is collected, and reviewed, the reviewing member will begin 
TEST LINK preparation. The CRC will send a standardized listing of rules and requirements for a 
testlink. A new administrator is to know, agree with and understand the requirements set upon he 
and his staff. The CRC will post the following information to the CADMIN mailing list. 

1: ADMINISTRATOR applying for Link
a: Name
b: Nick
c: Email
d: Phone

2: LOCATION of Server applying for link.
a: City
b: State
c: Country

3: Connectivity and representative information
a: Uplink
b: Connectivity - Processor
c: Routing Com Contact to field legitimate questions.
d: Routing's reasons for linking the server.

4: IRC OPERATIONS:
a: OP1
b: OP2
c: OP3

It is highly recommended that CADMIN be introduced to the server administrator.

A TEST NUMERIC will be assigned to the TEST-LINK Server with a Skeleton CONF file submitted from 
the director of CRC. For all test link servers there will be at least 2 up-links assigned for the 
test link. The TEST-LINK server will not have an AUTO CONNECT to any UP-Link initially. It will 
be the responsibility of the TEST-SERVER administrator, his staff, and CRC to maintain the link. 
This process is 3 fold. It will help show the competence of the new server's staff, the server's 
coverage, and will allow for tracking links that are failing. 

The TEST-LINK server administrator will be added as a level 500 in Nuthouse. The server's routing 
representative will do this. At this point, he may add the IRC operators that he has listed on his 
application as level 200. A test link server MAY NOT add new staff members that are not listed on 
the application. This means as either a local or a global operator. This allows for a complete review 
of the server and staff by not only by the ChatNet administrators but the IRC operations staff as well.
The staff of the Test Link server should be aware of and abide by the rules/policies/guidelines set 
forth in the OperFAQ. 


As of January 29, 2001, it is required that a testlink server does not add any additional O:lines 
during its test link. This means do not add backup O:lines.


The only lines that should reside on your server, is your defined staff and the generic Routing 
lines that CRC includes in your CONF File.

Test-links will last 45 days. CRC reserves the right to alter the length of a test-link based on 
server performance, staff performance, or other issues beyond the control of ChatNet, CRC, or the 
test-link server and its representative staff.

The CRC will not link more than 6 servers at a time. This will always leave 2 routing members free 
to field questions and deal with incoming applications.

New Server DNS

It is the responsibility of the CRC representative to send an email to the Executive Council 
requesting a DNS addition for the test server. This should be done with in the first 10 days of a 
test link. The nomenclature for that will be used for all ChatNet servers is based on these models:

USA:

City.State.US.ChatNet.Org

Canada:

City.Province.CA.ChatNet.Org

Provinces 
Alberta AB 
Manitoba MB 
New Brunswick NB 
New Foundland NF 
Northwest Territories NW 
Nova Scotia NS 
Ontario ON 
Quebec QU 
Saskatchewan SK 
Yukon Territory YT 

Mexico, The Carribean, the Pacific Isles & Central America

City.Country.ChatNet.Org

Europe (EU), Asia (AS), Africa (AF), South America (SA)

City.Country.Continent.ChatNet.Org

Australia:

City.State.AU.ChatNet.Org

States 
New South Wales NSW NSW 
Northern Territory NTH NTH 
Queensland QLD QUE 
South Australia SAU SAU 
Tasmania TAS TAS 
Victoria VIC VIC 
Western Australia WAU WAU 


New Zealand:

City.Island.NZ.ChatNet.Org

Island 
North Island NI NI 
South Island SI SI 
Stewart Island ST ST 
Great Barrier Island GB GB 
Chatham Island CI CI 
Pitt Island PI PI 
Auckland Island AI AI 
Cambell Island CB CB 
Macquarie Island MI MI