A NEW WAY OF THINKING  

Where is ChatNet Going and Why?

That is a fair question. Over the last 4 years, ChatNet has slowly decomposed into just another network with no future vision. This is both a result of the clientele and the staff putting very little time and effort into the growth and marketing of the network. The network still runs an IRCD daemon and complimentary services based on a legacy version of the Undernet daemon. There have been small modifications that have been added to help our user base, but these are in reality, face paint, or cosmetic cover ups. The reality is that ChatNet is currently in a rut.

To help ChatNet move in a direction that makes the network far more viable, development of a new IRC daemon based on new technologies has begun. This is not something that will happen over night, however it will be installed and running very soon. To ensure that this development continues, the ChatNet Routing Com and the ChatNet Coder committee have merged into a single Entity that is now referred  to as The ChatNet Development and Support Committee.

This committee will handle Server recruitment, network security, server and service development, and platform migration. It will be two different branches working as a single unit for now. This will change and will be incorporated into a single entity as soon as the kinks are ironed out. 

CHATNET IRCD AND SERVICES DEVELOPMENT
CISD

The director of development is Pyra. In this roll, Pyra will be responsible for setting the ChatNet Coding Standards and recruiting the development staff. In the past, ChatNet's developers each did things their own way, and when they no longer wanted to work on the IRCD, almost  as much time was spent deciphering the methods and structures used as time was put in to actually correct errors in code. His roll will include documenting the base IRCD system and any changes or additions to design, nomenclature or structure. 

There have been many ideas passed along to members of the IRC Operations staff that have to be addressed. For years now, the users have been ignored when their suggestions have been placed before the ChatNet staff. The CISD is charged with exploring these suggestions and analyzing the viability of these additions. Priorities will be assigned by the directors of the committee. All development will be worked on by level of importance. Asthetic additions and similar changes will  most likely be released as patch levels. The priority is to move the ChatNet Daemon forward. 

ChatNet has suffered from a serious lack of  version control. This issue has left ChatNet running three distinctly different IRCD's. The disadvantage to this situation is that enhancements are added to the IRCD and they are not active or even seen on certain servers. This will be the last time that this happens. As it was in June of 99, there will be a move to a single new IRCD. There is no commitment that this will be based on IRCU, Comstud, Hybrid or Bahamut. There are advantages to each and there are serious draw backs as well. It is the duty of the CISD to decide what they feel will be the most logical version to work with. 

Any questions that you have regarding the CISD, please direct them to this address: cidc@routing.chatnet.org

CHATNET ROUTING AND SECURITY
CRC

The director of Routing is Spectre. In this roll, Spectre will be responsible for setting the ChatNet routing and Security standards and the Routing staff. These standards will include the requirements by location for a linking server, the acceptable minimum load for a server, as well as where a server can link from. The CRC will also be executing periodic security and performance checks on the current server population of the ChatNet network.

In the past, ChatNet took a very aggressive linking strategy that created a network that carried between 20 and 30 unpopulated servers. These servers often were slow or lacked any form of server security. To verify the quality of links, we started to make the scanning of each prospective server’s open ports, mandatory. This continued for the better part of a year, at which time things sort of reverted to the old mentality of “there is no need to do anything to the network. It is fine as it is”.

ROUTING DISCLAIMER 
The CRC will be once again implementing security checks on linking servers. The CRC also reserves the right to contact the housing institution of a server to verify that permissions have been granted to run an IRCD. This has become necessary due to the recent influx of exploited servers that have tried to link. The CRC reserves the right to use any of the tools at its disposal to verify the security of an applicant server.

CRC SECURITY STAFF

The CRC security staff executes all security checks from the CRC. This is an inclusive statement regarding new links, as well as current links. This team will handle all auditing of servers on ChatNet. They will publish the results of the audits on the routing website. We are currently deciding if this wil be a public or private posting. Currently this staff is made up of Sh0rty, Basty, and Cam-. Any questions that you have regarding past security checks, an upcoming security check, or any information you require regarding these checks, please direct to security@routing.chatnet.org.

CRC SERVER LINKING  STAFF

The CRC Server Linking staff will review all applications submitted from the Routing Website. This staff is made up of the following members.  Vampire and Sh0rty will handle links that are based in the United States and Canada. Links that originate from Austral-Asia, Eastern Continental Asia, or the Greater Pacific Islands will be handled by Cam-. Links that originate in Europe, including both the North Islands and Mediterranean Sea will be reviewed by Basty. Links that originate in central or western Asia, Africa, Latin or South America including Mexico will be review by Spectre. Any application that is received will be reviewed by the regional contact. If the load on the defined CRC member becomes too much to bear, Labattz will handle the over flow.

CHATNET AND THE INTERNET IN A NUT SHELL

The following is a simple review of the ideology that is being used in creating the infrastructure of the ChatNet Network. What I have tried to compile below, is a collection of graphs, maps, and documentation that describes the philosophy we are implementing into the current Routing Schema. Most of the routing model is based on the Above Net international backbone model. Above net is an industry leader in the installation and maintenance of an International fiber based network. ChatNet has been lucky enough to slowly aquire servers that are either directly connected to Above Net or to its primary peering partners. 

The Internet has become a conglomerate of ½ baked internet provision and over saturated lines. This has been expected because the core of service with in the US alone, is still run by the "Good Ole Boy" networks. This includes  AT&T, MCI, Cable and Wireless, and Sprint. The actions of these providers over the past few years explains what has happened to the Internet as a whole very clearly. 

In May of 1998, MCI, America's number 2 long distance carrier decided that the back bone they built for the Internet was not as viable as a profit source. They sold their back bone infrastructure to a British company called Cable and Wireless. This action was a ruse to allow the MCI corporation to merge with a growing company called World Com. This was the first major change in the Internet structure in the United States. The merger of MCI and World Com created the company that would act as the primary backbone providers for the next 2 years. 

As recently as the year 2000, MCI World Com (UUnet or Alter Net) the United States' second largest Long distance carrier tried to merge with Sprint the United States' third largest carrier. This would have placed a majority of companies on one network back bone. To understand the gravity of that situation, one has to read the comments made by AT&T the largest Long distance carrier in the world. The following is from the AT&T website and is the property of the AT&T corporation:

MCI WorldCom-Sprint Merger Requires Divestiture of Sprint's Internet Backbone Assets, AT&T Says

WASHINGTON -- The merger between MCI WorldCom and Sprint must be denied unless Sprint is required to divest its Internet assets, AT&T said today.

In a filing with the FCC, AT&T noted that the combined entity would be by far the largest single nationwide Internet backbone provider with so much control over Internet traffic that it would discriminate against competitors that need to connect to its network.

The combination of MCI WorldCom and Sprint, the nation’s first- and second-largest Internet backbone providers, respectively, would effectively monopolize the market for peering, the exchange of data between networks, AT&T said. The entity could discriminate against competitors that need to connect to its network by either raising its rivals’ costs or by degrading the quality of the connections, AT&T said, adding that under these circumstances customers are likely to abandon the rivals altogether.

A similar issue arose in 1998 when MCI merged with WorldCom, AT&T said, noting that the FCC only approved the merger because MCI agreed to transfer its Internet assets to Cable and Wireless.

AT&T called this merger even more insidious. AT&T explained that while the merger is pending, there is a substantial risk that Sprint’s customers, aware of the prior merger divestiture order, will begin to shift their traffic to the network they believe will survive -- MCI WorldCom’s -- so that they will not be affected by a divestiture. In order to be effective, any remedy imposed by the FCC, therefore, must assure that the spun off network retains the same customers it had before the merger was announced. In addition, the FCC should impose conditions to assure that the merged entity continues to peer on a non-discriminatory basis, AT&T said.

As the statement above points out, AT&T was not worried about competition in regard to their long distance provision, but they were strictly worried about the Internet portion of this merger. This is an issue for AT&T because they as well as companies such as GTE and other providers,  do a large portion of their Internet provision on leased lines. 

Both UUnet and Sprint are fully saturated back bones. This is the result of years of sales and a lack or progression into larger pipes. This information is not new . In the past there was of the lack of alternatives to these giants. They used their size and economic strength to leverage out smaller companies, they have maintained a majority hold on the Internet infrastructure for years. 

Even though ChatNet is basing its routing schema on the Above Net network, this does not mean that these more mature network connections are looked down upon. These older patrons of the Internet are the companies that the new companies use for peering and architectural standards. This is a fact of life on the Internet and companies such as MCI Worldcom, Sprint, PSInet, GTE, and Cable & Wireless should not be discarded as old or by any means considered ineffectual. 

A lot has been said about the other players, now it is time to explain why Above Net is being given special treatment. The internet routing philosophy that Metromedia Fiber Networks Inc. maintains is to keep traffic on their own network as long as possible. This insures that traffic running on Above Net remains on Above Net. Because of this, we currently have the ability to push traffic directly from London, England, to Cupertino, California using nothing but an OC-48 (2.2Gb) connection. Our average travel times on this connection are in the area of 110ms with out packet loss.  The eastern US  connection is faster and just as stable producing times in the low and mid 70ms second range. For this reason, and the fact that Above net peers very well with most Internet providers internationally, we have based our routing schema on their network. 

What is ChatNet looking for in the United States and Canada?

The following map describes merely one of a myriad of possibilities for good coverage throughout North America. The servers that are in WHITE are Above Net servers or their tier one partners. Servers that are colored in GREEN are servers representing the Primary Back bone providers (UUnet, C&W, Sprint, PSI). Servers that are colored in YELLOW are marked by the provider that they represent.

Wessyde.Hub.US.CHatNet.Org
 |-LosAngeles.CA.US.ChatNet.Org
 |-SF.CA.US.ChatNet.Org
 |-Portland.OR.US.ChatNet.Org - Verio
 |-Phoenix.AZ.US.ChatNet.Org
 |-Honolulu.HA.US.ChatNet.Org
 |-PrinceGeorge.BC.CA.ChatNet.Org - BCtel /UUnet
 |-Winnipeg.MB.CA.ChatNet.Org
 |-OKC.OK.US.ChatNet.Org
 |-SLC.UT.US.ChatNet.Org - Verio
 `-Eassyde.Hub.US.ChatNet.Org
    |-Detroit.MI.US.ChatNet.Org
    |-Lexington.KY.US.ChatNet.Org
    |-Montreal.QU.CA.ChatNet.Org
    |-Columbia.S C.US.ChatNet.Org
    |-NYC.NY.US.ChatNet.Org
    |-Boston.MA.US.ChatNet.Org
    |-Miami.FL.US.Chat Net.Org - BellSouth
    |-KansasCity.MO.US.ChatNet.Org
    `-StJohns.NF.CA.ChatNet.Org

What is ChatNet looking for in Europe and Western Asia?

ChatNet's historical presence  has been localized to the British isles and Scandinavia. over the past year, we have tried to sway this perception and increase our presence in Europe. As our user base increases internationally, we intend to give these new users a regional server that fortifies them with a fast and stable connection to ChatNet. 

EuroTrash.Hub.EU.ChatNet.Org
 |-Frogn.NO.EU.ChatNet.Org - Chello Networks
 |-Moscow.RU.EU.ChatNet.Org - Relcom
 |-Copenhagen.DK.EU.ChatNet.Org - Euroconnect Net
 |-Amsterdam.NL.EU.ChatNet.Org
 |-MONTECARLO.MC.EU.ChatNet.Org - UUnet HUB
 | |-MILAN.IT.EU.Chatnet.Org - Libero Italy
 | |-ATHENS.GR.EU.ChatNet.Org - PSI net
 | |-Madrid.ES.EU.ChatNet.Org - UUnet
 | `-Istanbul.TR.AS.ChatNet.Org - SDN net
 |-KUWAITCITY.KW.AS.ChatNet.Org - UUnet
 `-MECCA.SA.AS.ChatNet.Org - Cable & Wireless

LATIN MAP Future

This map represents possible Latin American coverage. ChatNet has been a notoriously Anglo-American network for a long time. This is a stigma we wish to break, by bringing on representation of our southern neighbors. The user load from Central and South America as well as Mexico has grown steadily on ChatNet for the past few years. we have tried to provide coverage via a Latino server but we are yet to find one that will remain linked. Although we intend to start with either a single server or perhaps a pair of server, as the user load from Latin America increases, the number of representative servers will increase as well. South America represents the biggest challenge in these server acquisitions. The continental back bone system is unlike any where else in the world. In most situations, the national backbone has a direct uplink to the US. This causes, in many of the South American countries, horrid routing from country to country. In the case of Colombia, the national backbone runs to the US in Miami via a 300MB ATM via a major US carrier. This connection represents almost 100% of the entire country's external connectivity. The trick to routing South America begins in knowing that there is a second player from the US represented in Colombia. The route that they use makes our map below possible. The same can be said of countries such as Argentina and Uruguay. These countries are also very heavily involved in satellite communication. The colored selections represent servers we would like to see in the future.

MX FUTURE -- SA FUTURE -- Central America & Carrib FUTURE

Wessyde.Hub.US.ChatNet.Org (US Uplink West)
 |-Monterrey.MX.ChatNet.Org
 |-MexicoCity.MX.ChatNet.Org
 | |-Cancun.MX.ChatNet.Org
 | `-Tegucigalpa.NI.ChatNet.Org
 `-Bogata.CO.SA.ChatNet.Org
   `-BuenosAres.AR.SA.ChatNet.Org

Eassyde.Hub.US.ChatNet.Org (US Uplink East)
 |-SanJuan.PR.US.ChatNet.Org
 `-PortOfSpain.TT.ChatNet.Org

AFRICA Future

The Internet standards on the continent of Africa are far behind Europe and the Americas. There are islands of Internet connectivity, that represent the only connections for 1000's of miles. These notable exceptions are the areas of heavy European and American influence. South Africa and Egypt are by far the leaders in technology of the continent. This does not mean that other countries are not moving forward. As Africa moves into the Internet era, ChatNet is poised to welcome them to the Network. Africa is another continent that is heavily based in Satellite traffic. This is because of the enormous costs of laying cable around a continent the size of Africa. Due to the dynamics of international politics, the continental routing for Africa is largely single point routing. With the exception of Egypt, it is very rare to find 2 countries that are sharing a backbone. This is why you see below a map that is represented by single end-point servers instead of a hub structure.

East Africa Future -- West Africa Future -- South Africa Future

US/EU Uplink
|
|-Cairo.EG.AF.ChatNet.Org
|-AddisAbaba.ET.AF.ChatNet.Org
|-Algiers.DZ.AF.ChatNet.Org
|-Dakar.SN.AF.ChatNet.Org
|-Harare.ZW.AF.ChatNet.Org
`-Johannesburg.ZA.AF.ChatNet.Org

OCEANIA & WEST ASIA Future

ChatNet is actively pursuing a Pacific rim sub network. It is important to our routing philosophy to represent the globe. 

AU Future -- ASIA Future -- PAC ISLES Future

Singapore.SG.AS.ChatNet.Org - Hong Kong Tel
 |-Melbourne.Vic.AU.ChatNet.Org - Connect Com Australia
 |-Manila.LU.PH.ChatNet.Org
 |-Taipei.TW.AS.ChatNet.Org
  |-Sydney.NSW.AU.ChatNet.Org - Connect Com Australia 
 | `-Wellington.NI.NZ.ChatNet.Org
  |-Tokyo.JP.AS.ChatNet.Org
 `-Perth.WA.AU.ChatNet.Org
    |-Singapore.SG.AS.ChatNet.Org
    |-NewDelhi.IN.AS.ChatNet.Org
    `-Karachi.PK.ChatNet.Org

This is a global map that reflects the routing schema we would like to see in ChatNet's future. The servers that are reflected here are based on servers that have been linked in the past as well as servers that we are looking to get in the future. They are included more to represent a region then a specific city. If you are considering linking to ChatNet and you do not see your city represented in this map, do not fret. This is a pipe dream and will probably never happen, however, we can always wish :)
Future Servers