The following is a listing of the various positions in the chain which makes
up RC-Net, along with the basic responsibilities of each position.

The criteria for maintaining these positions should be followed by those 
systems holding the position in question. Any questions concerning these
responsibilities should be directed to the next higher link in the "chain".
If the problem cannot be resolved at that level, work it up the chain to end
with the Zone Coordinator.


                              Zone Coordinator
                                    |
      ______________________________|________________________________
      |            |                |               |               |
      |            |                |               |               |
   Regional     Regional         Regional        Regional        Regional
    Coord.       Coord.           Coord.          Coord.          Coord.
      |            |                |               |               |
  ____|____    ____|____        ____|____       ____|____       ____|____
  |       |    |       |        |       |       |       |       |       |
 State Hosts  State Hosts      State Hosts     State Hosts     State Hosts
  |       |    |       |        |       |       |       |       |       |
  |       |    |       |        |       |       |       |       |       |
 Hub     Hub  Hub     Hub      Hub     Hub     Hub     Hub     Hub     Hub
  |       |    |       |        |       |       |       |       |       |
__|__   __|__ _|__   __|__    __|__   __|__   __|__   __|__   __|__   __|__
|   |   |   | |   |  |   |    |   |   |   |   |   |   |   |   |   |   |   |
Nodes   Nodes Nodes  Nodes    Nodes   Nodes   Nodes   Nodes   Nodes   Nodes


Position                 Responsibilties
___________________________________________________________________________

Zone Coordinator         Overall Control of the Net. Also, update and hatch
                         the weekly zone nodelist (RCLIST.###). The ZC will
                         hatch the new nodelist on each Sunday, and send it
                         (when possible) to each Regional Coordinator.

Regional Coordinator     Overall control of his/her individual Region. The 
                         RC is responsible for keeping a regional nodelist
                         which will be sent to the ZC whenever an addition
                         or deletion is made. The RC is responsible for the
                         regular polling of the ZC for mail packets (Mon, 
                         Wed, and Fri) and transfer of waiting mail packets
                         to the ZC. The RC is also responsible for ensuring
                         that the new zone nodelist, when received, is 
                         distributed to the Hosts within his region. If the 
                         RC has no Hosts, he will ensure that the nodelist is
                         sent to any Hubs within his domain, or even nodes,
                         as the case may be. The same shall hold true for any
                         echo-files received by the RC. Forwards all received
                         applications from new nodes, hubs, hosts to the ZC.

State Host               Overall control of his state, under the direction
                         of that Host's RC. The SH may assign node numbers to
                         new Hubs/Nodes within his state, provided he notifies
                         his RC of the number assigned (for entry into the 
                         regional nodelist, and also forwards a copy of the new
                         node's application to the RC. Responsible for ensuring
                         that the new nodelist, when received, is distributed
                         to all Hubs within his state. If no Hubs are present,
                         he will ensure that any nodes within his state receive
                         the new nodelsit each week. The same shall hold true
                         for any echo-files received by the SH.

Hub                      Overall control of his City/County, as directed by
                         that Hub's SH. The Hub may assign node numbers to new
                         nodes within his jurisdiction, provided he notifies 
                         his SH, and forwards any copies of any applications
                         to the SH. Responsible for ensuring that the new
                         nodelist, when received, is distributed to all nodes
                         within his domain. The same shall hold true for any
                         echo-files received by the Hub.

Node                     The Node is the last link in the chain. The node is
                         the end-user of any and all information generated 
                         within the chain. The node is responsible for making
                         sure that mail packets are sent to his Hub (or Host,
                         if no Hub is present) on a regular and timely basis.
                         Also, the node is to ensure that there is no profane
                         language used on his system, and will take adequate 
                         measures to stop it quickly, should it occur.

-------------------------------------------------------------------------------

Echo Moderators:

The ZC is currently holding the position of Moderator for RC_BIG, RC_SYSOP,
and RC_CHAT. 
If you're interested in becoming the moderator for any of the other echoes,
please notify the ZC.
-------------------------------------------------------------------------------
Hopefully, all members of RC-Net are actively seeking new nodes in their
regions. Upload RC-NET.ZIP to any other BBS's you frequent. Post a message
on other nets that you might be involved with. This electronic "word-of-mouth"
is the best way to help us grow and become more successful.

Thanks to all, for the work done thus far. Hoefully, as time goes on, we'll 
continue to grow.


Ed