You have reached the ChatNet Development and Routing Committee

The ChatNet Development and Routing Committee (CD&R) is tasked with maintaining the ChatNet Internet Relay Chat daemon and the network as a whole. The two divisions of this committee work together to create a seamless fabric integrating network stability, IRCD functionality, and client services. This committee is made up of ChatNet operations staff members. Each member is hand selected by the director of the CD&R who in turn is selected annually by the ChatNet server administration.

The responsibilities of the CD&R include the day-to-day operations and administration of the network. In this roll, the CD&R is charged with network stability, Daemon usability, User and Operations services, and DNS maintenance.

Effective 01 February, 2003, all applications will be reviewed and notification regarding test linking or denial will be received with in 10 working days. The CD&R reserves the right to make exceptions for holidays and personal or network emergencies. Upon receipt of an application via the Routing website, a routing member will review the application for legitimacy and for any missing information. If the application is complete, this member will send his views on the server to the routing committee. If at least one more member agrees with the assessment of the initial application, notification will be sent to the applicant. If at this time, the reply bounces, or we do not hear back from the applicant with in 3 days, we will discard the application. Prior to this notification, a routing member will post as much information as possible. This includes pings, traces, and Name server BIND version checks. The routing member handling the Application may request pings and traces from applicant only to routers or servers that apply to the overall network structure. All pings that are requested should be at least 50 packets ranging from 1024 to 1505 bytes in size.

After all of the required information is collected, and reviewed, the reviewing member will begin TEST LINK preparation. The ChatNet Routing Committee will send a standardized listing of rules, requirements and the standardized ChatNet Non-Disclosure statement the the test link administrator. A new administrator is to know, agree with and understand the requirements set upon he and his staff. The ChatNet Routing Committee will post the following information to the ChatNet Administration 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 ChatNet Administration be introduced to the server administrator.

If a server does not have a resolvable name in the format of irc.company.TLD or irc-#.company.TLD, a name will be assigned to it using one of the following formats:

A test link name will be assigned to the TEST-LINK Server with a Skeleton CONF file submitted from the director of ChatNet Routing Committee. 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. It will be the responsibility of the TEST-SERVER administrator, his staff, and ChatNet Routing Committee 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 either himself, or via written request to ChatNet Channel Services. At this point, he may add the IRC operations staff 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.

That TEST LINK server will not add backup O:LINES with out the expressed written consent of the Routing Committee. Modifications to the configuration of the server regarding uplinks and services that are made with out prior Routing Committee consent will terminate the test link. With this said, the only operations lines that should reside on your server, is your defined staff and the generic Routing lines that ChatNet Routing Committee includes in your CONF File.

Test-links will last 45 days. ChatNet Routing Committee 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, ChatNet Routing Committee, or the test-link server and its representative staff.

New Server DNS
After 30 days of the test link, it is the responsibility of the ChatNet Routing Committee representative to send notification via email to the CD&R DNS administrator requesting a DNS addition for the test server. The nomenclature for that will be used for all ChatNet servers is based on these models:

Provinces
Alberta	AB
British Columbia	BC
Manitoba	MB
New Brunswick	NK
New Foundland	NF
Northwest Territories	NT
Nova Scotia	NS
Ontario	ON
Prince Edward Island	PI
Quebec	QU
Saskatchewan	SN
Yukon Territory	YK

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