Shareware Grab Bag

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Grab Bag / Shareware Grab Bag.iso / 096 / rbbs_net.arc / RBBS-NET.DOC next >

Wrap

Text File | 1988-06-12 | 29.9 KB | 1,025 lines

R B B S - N E T Policy and Procedures Guide Draft 1.0 12 June 1988 Section Page ------- ---- 1 Overview ...................................................... 3 1.1 Objectives ................................................ 3 1.2 Background ................................................ 3 1.3 Definitions ............................................... 3 1.4 The Levels of RBBS-Net .................................... 4 2 Sysop Procedures .............................................. 6 2.1 How to get a node number .................................. 6 2.2 If you are going down ..................................... 7 2.3 How to join a network ..................................... 7 2.4 How to form a network ..................................... 8 3 Network Coordinator Procedures ................................ 10 3.1 Routing inbound mail ...................................... 10 3.2 Assigning node numbers .................................... 10 3.3 Maintaining the Node List ................................. 10 3.4 Passing along Node Lists and RBBS-Net News ................ 11 4 Regional Coordinator Procedures ............................... 12 4.1 Assigning node numbers .................................... 12 4.2 Encouraging the formation and growth of networks .......... 12 4.3 Assigning network numbers ................................. 13 4.4 Maintaining the Node List ................................. 13 4.5 Overseeing network operations ............................. 14 4.6 Passing along Node Lists and RBBS-Net News ................ 14 5 International Coordinator Procedures .......................... 15 6 RBBS-PC Network Contact People ................................ 16 7 Acknowledgment ................................................ 17 Chapter 1 OVERVIEW 1.1 Objective To connect RBBS-PC System across the Nation into a FidoNet Compatible Network for the "Free Exchange of Information." We (The RBBS-PC Network) have no intentions of trying to replace or compete with the existing FidoNet Network. We (The RBBS-PC Network) only want a means of communicating directly with other RBBS-PC SysOps across the nation and to enhance the existing FidoNet and other FidoNet Compatible Networks that are already in place today. This document is an attempt to describe the procedures which have been developed to manage a network. 1.2 Background FidoNet is an amateur electronic mail system. From its early beginnings as a few friends swapping messages back and forth, it has now grown to (October 1986) over 1000 different systems on four continents. RBBS-Net is going to provide the resources to a RBBS-PC System Operator (SysOp) with the tools to connect into a Network of other Bulletin Board (BBS) SysOps across the nation. We hope to be able to provide international connectivity also. RBBS-Net will not try to re-invent the wheel. We will adopt most of most of the standards that International FidoNet Association has already adopted into their network. 1.3 Definitions RBBS-Net nodes are grouped on several levels. These are as follows: Nodes: A node is a single Net address, and is the smallest recognized unit of the Net. Networks: A network is a collection of nodes, usually in a relatively small geographic area. Networks coordinate their mail activity to decrease cost and increase mail throughput. Regions: A region is a well defined geographic area containing nodes which may or may not be combined into networks. A typical region will contain many nodes in networks, and a few independent nodes, which are not a part of any network. Zones: A zone is a large geographic area containing many regions, and covering one or more countries and/or continents. RBBS-PC Network Policy and Procedures Page 3 RBBS-Net: This indicates the entire mail network, as designed by the RBBS-PC Network Coordinators and as defined by the weekly Node List. 1.4 The Levels of RBBS-Net With the introduction of The RBBS-PC Network, RBBS-Net has developed the following levels of organization: The International Coordinator The International Coordinator compiles all of the Node Lists from all of the regions and creates the master Node List, which is then distributed over The RBBS-PC Network. The Zone Coordinator In some cases the International Coordinator will appoint a Zone Coordinator to oversee the operations in a given zone. The exact duties and responsibilities of any given Zone Coordinator are assigned by the International Coordinator, and will not be discussed here. The Regional Coordinator The Regional Coordinator maintains the list of independent nodes in his region and accepts Node Lists from the Network Coordinators in his region. He compiles these lists to create a regional Node List for his region, which he then sends to the International Coordinator. A Regional Coordinator does not perform routing services for any nodes in his region. The Network Coordinator The Network Coordinator is responsible for maintaining the list of nodes for his network, and for receiving and forwarding any mail coming to the network from outside. The Network Routing Hub Network Routing Hubs exist only in three-tiered networks. They generally share some or all of the duties of the Network Coordinator, in order to ease the management of a large network. The exact duties and procedures are a matter for the Network Coordinator and his hubs to settle, and will not be discussed here. The Network Coordinator is still responsible for the maintenance of the network. The System Operator (SysOp) The SysOp formulates his own policy for running his board and dealing with his users, so that will not be discussed in this document. However, the sysop must also mesh with the rest of the FidoNet system if he is to send and receive mail, and that will be discussed here. RBBS-PC Network Policy and Procedures Page 4 The User Policy and procedures for the individual user on any given board is determined by the system operator of that board, and will not be considered in this document. These levels act to distribute the administration and control of RBBS-Net to the lowest possible level, while still allowing for coordinated action over the entire mail system. For example, a Regional Coordinator is solely responsible to the International Coordinator for anything that may or may not happen in his region. From the point of view of the International Coordinator, the Regional Coordinator is totally and completely responsible for the smooth operation of his region. Likewise, from the point of view of the Regional Coordinator, the Network Coordinators are totally and completely responsible for the smooth operation of their networks. If a person at any level above SysOp is unable for any reason to properly perform his duties, then that person can take is problem to the next level up. RBBS-PC Network Policy and Procedures Page 5 Chapter 2 SYSOP PROCEDURES A sysop of an individual node can pretty much do as he pleases, as long as he observes the mail events, is not excessively annoying to other nodes on RBBS-Net, FidoNet or any other FidoNet Compatible Network and does not promote the distribution of pirated copyrighted software. National Mail Hour is the heart of of any NetMail Network, as this is when the network mail is passed between systems. Any system which wishes to be a part of a NetMail Network must be able to receive mail at this time. A system which is a member of a network may also be required to observe additional mail events, as defined by his Network Coordinator. Network mail systems generally operate unattended, and place calls at odd hours of the night. If a system tries to call an incorrect or out of date number, it could cause some poor citizen's phone to ring in the wee hours of the morning, much to the annoyance of innocent bystanders and civil authorities. For this reason, a SysOp who sends mail is obligated to obtain and use the most recent edition of the Node List as is practical. The exact timing of National Mail Hour is set for each zone by the International Coordinator, or by his designated Zone Coordinator. In the United States, National Mail Hour is observed from 0900 to 1000 GMT every day, weekends included. In each of the United States time zones, this would be as follows: Eastern Standard Time 4 AM to 5 AM Central Standard Time 3 AM to 4 AM Mountain Standard Time 2 AM to 3 AM Pacific Standard Time 1 AM to 2 AM Hawaii Standard Time 11 PM to Midnight Networks do not observe daylight savings time. In areas which observe daylight savings time the FidoNet mail schedules must be adjusted in the same direction as the clock change. Alternatively, you can simply leave your system on standard time. 2.1 How to get a node number You must first obtain a current Node List so that you can send mail. You do not need a node number to send mail, but you must have one in order for others to send mail to you. The first step in obtaining a current Node List is to locate the closest RBBS-Net Bulletin Board System to you. If the SysOp of any RBBS-Net system does not have a Node List available for downloading, then he can probably tell you where to get one. RBBS-PC Network Policy and Procedures Page 6 Once you have a Node List, you must determine which network or region covers your area. Once you have located the network or region in your area, send a request for a node number to node zero of that network or region. The request must be sent by FidoNet mail, and must include at least the following: 1) Your name. 2) The name of your system. 3) The city and state where your system is located. 4) The phone number to be used when calling your system. 5) Your hours of operation. 6) The maximum baud rate you can support. 7) BBS Software Version. 8) NetMail Interface Program. Your coordinator may want additional information. If so, he will contact you. Please allow at least five days for a node number request to be processed. If you send your request to a Regional Coordinator, then he may forward your request to the Network Coordinator who covers your area (if any), which may take longer. 2.2 If you are going down If your node will be down for an extended period (more than a day or two), then you should inform your coordinator as soon as possible. If you do not do this, then other systems will still try to reach you while you are down, much to the annoyance of everyone. Do not under any circumstances put an answering machine or similar device on your phone line while you are down. If you do, then calling systems will get the machine repeatedly, racking up large phone bills, which is very annoying. If you will be leaving your system unattended for an extended period of time (such as while you are on vacation), you should notify your coordinator. Systems do have a tendency to "crash" now and then, so you will probably want your coordinator to know that it is a temporary condition if it happens while you are away. 2.3 How to join a network If you are an independent node and would like to join a network in your area, you must contact the Network Coordinator. He can be reached by sending RBBS-Net mail to node zero of the network. He will inform you of any special mail schedules and/or routing required by the network. Your Regional Coordinator will contact you to confirm that you wish to join the network. Once you have been placed in the network, you will be informed by the Network Coordinator. RBBS-PC Network Policy and Procedures Page 7 There are many advantages to being in a network. First and foremost is that it helps reduce congestion of RBBS-Net during National Mail Hour. Also, many networks are "outbound" as well as "inbound", which can substantially reduce your phone bills. In addition, network members receive regular updates of the Node List, while an independent node may not. 2.4 How to form a network If there are several nodes in your area, but no network, then you may wish to form your own. Again, this has several advantages as outlined above. Your first step is to contact the other SysOps in your area. You must decide which nodes will comprise the network, and which of those nodes is going to be the Network Coordinator. Your next step is to inform your Regional Coordinator. You must send him a NetMail message with the following information: 1) The region number(s), or network number(s) if a network is splitting up, that are affected by the formation of your network. The Regional Coordinator will inform the International Coordinator and the coordinators of any affected networks that a new network is in formation. 2) The name that you wish to call your network. Please try to select a name that relates to your grouping. For example, SoCalNet for nodes in the Southern California Area and MassNet for Massachusetts Area. Remember if you call yourself DOGNET it doesn't help others know what area of the country (or even what country) your group is in. 3) A copy of the proposed network's Node List. The Node List file should be named Rrrr-nnn.NET where rrr is the proposed host's current region or network number and nnn is his current node number. For example, if the proposed host is currently listed as node 5 in region 13, then you would name the file R013-005.NET! This file should be sent attached to the message of Application for a Network Number. SAMPLE FORMAT OF A Rrrr-nnn.NET FILE Host,911,Inland_Empire_Net,Alta_Loma_CA,Rod_Bowman,1-714-945-2612,9600,XP:#CM: ,1,The_'PC'_Spectrum_(tm)_RBBS-PC,Alta_Loma_CA,Rod_Bowman,1-714-945-2612,9600,XP:#CM: ,2,Chips_Unlimited_RBBS,-PC,Rancho_Cucamonga_CA,Phil_Rheinecker,1-714-989-2603,9600,RE:WK:1600-0800WE:24 ,3,Tri_Clone_RBBS-PC,Riverside_CA,Dan_Shue,1-714-689-3850,2400,XP:#CM: ; RBBS-PC Network Policy and Procedures Page 8 Granting of a network number is not automatic. Your Regional Coordinator will review your application and inform you of his decision. Do not send a network number request to the International Coordinator. All network number requests must be processed by the Regional Coordinator. RBBS-PC Network Policy and Procedures Page 9 Chapter 3 NETWORK COORDINATOR PROCEDURES A Network Coordinator has the following responsibilities: 1) To receive incoming mail for nodes in his network, and to deliver it to its recipients. This mean you have to poll the Mail Distribution System to receive your mail. 2) To assign node numbers to nodes in his network. 3) To maintain the Node List for his network, and to send a copy of it to his Regional Coordinator whenever it changes. 4) To pass along to his nodes the new Node List, Node List updates and new issues of RBBS-Net as they are received. 3.1 Routing inbound mail It is your responsibility as Network Coordinator to receive all inbound mail for nodes in your network and to forward it to its recipients. You are left to your own discretion as to how best to accomplish this. If a node in your network is routing large volumes of EchoMail, you can ask him to either limit the amount of EchoMail, or even to stop routing his EchoMail completely. The design of EchoMail is such that it is a simple matter to do either of these. Or they can break off out of your network. 3.2 Assigning node numbers It is your responsibility to assign node numbers to new nodes in your network. You may also change the numbers of existing nodes in your network, though you should check with your member nodes before doing so. You may assign any numbers you wish, so long as each node has a unique number within your network. 3.3 Maintaining the Node List You should attempt to implement name changes, phone number changes, et cetera in your Node List as soon as possible, and to forward the revised Node List to your Regional Coordinator whenever a change occurs. You should also on occasion send a message to every node in your network to ensure that they are still operational. If a node turns out to be "off the air" with no prior warning given to you, then you can either mark the node as down, place it in the dog house, or remove it from the Node List completely, at your own discretion. RBBS-PC Network Policy and Procedures Page 10 3.4 Passing along Node Lists and RBBS-Net News As a Network Coordinator you should obtain a new Node List update every week. The Node List update is posted weekly on Sundays. The list will be made available to you by your Regional Coordinator. You should pass both of these along to your member nodes as soon as is practical after you receive them. It is also desirable that you make them both available for downloading by the general user, but this is not required. The Node Lists are the glue that holds us together. Without them, we cease to be a community, and become just another random collection of bulletin boards. RBBS-PC Network Policy and Procedures Page 11 Chapter 4 REGIONAL COORDINATOR PROCEDURES A Regional Coordinator has the following responsibilities: 1) To assign node numbers to independent nodes in his region. 2) To encourage independent nodes in his region to join existing networks, or to form new networks. 3) To assign network numbers to networks in his region. 4) To compile a Node List of all of the networks and independents in his region, and to send a copy of it to the International Coordinator whenever it changes. 5) To ensure the smooth operation of networks within his region. 6) To make new international Node List updates and new issues of RBBS-Net available to the Network Coordinators in his region as soon as is practical. 4.1 Assigning Node numbers It is your responsibility to assign node numbers to new nodes in your region. You may also change the numbers of existing nodes in your region, though you should check with the respective nodes before doing so. You may assign any numbers you wish, so long as each node has a unique number within your region. You should use network mail to inform a new node of his node number, as this helps to insure that he is capable of receiving network mail. If you receive a node number request from a new node that is in an area covered by an existing network, then you should forward the request to the Coordinator of that network instead of assigning a number yourself. 4.2 Encouraging the formation and growth of networks One of your main duties as a Regional Coordinator is to promote the growth of networks in your region. You should try to avoid having independent nodes in your region which are within the coverage area of a network. There are, however, certain cases where a node should not be a member of a network, such as a commercial system with a large volume of traffic which would clog the network. The resolution of such special cases is left to your own discretion. RBBS-PC Network Policy and Procedures Page 12 If several independent nodes in your region are in a "clump", then you should encourage them to form a network. Refer to the SysOp procedure forming a network on forming a network for details of what information you should get. Note that this does not mean to encourage the formation of trivial networks. Obviously, one node does not make a network. The exact number of nodes required for an effective network must be judged according to the circumstances of the situation, and is left to your own discretion. 4.3 Assigning network numbers It is your responsibility to assign network numbers to new networks forming within your region. You are assigned a pool of network numbers to use for this purpose. This pool consists of ten numbers starting at your region number plus ten, times ten. For example, if you are the Regional Coordinator for region 13, then your network number pool consists of the numbers 230 through 239. If you need more numbers than this, then you should ask the International Coordinator for additional numbers as they are needed. 4.4 Maintaining the Node List As a Regional Coordinator, you have a dual role in maintaining the Node List for your region. First, you must maintain the list of independent nodes in your region. You should attempt to implement name changes, phone number changes, and so forth in this Node List as soon as possible. You should also on occasion send a message to every independent node in your region to ensure that they are still operational. If a node turns out to be "off the air" with no prior warning given to you, then you can either mark the node as down, place it in the dog house, or remove it from the Node List completely, at your own discretion. Second, you must receive the Node Lists from the Network Coordinators within your region. You should assemble a master Node List for your region every week and send it to the International Coordinator no later than National Mail Hour on Saturday morning. It is suggested that you do this as late as is practical, so as to accommodate any late changes. You will need to maintain a set of Node Lists for each network within your region, since you cannot count on getting an update from each Network Coordinator every week. RBBS-PC Network Policy and Procedures Page 13 4.5 Overseeing network operations It is your responsibility as Regional Coordinator to ensure that the networks within your region are operating in an acceptable manner. This does not mean that you are required to operate those networks; that is the responsibility of the Network Coordinators. It means that you are responsible for seeing to it that the Network Coordinators within your region are acting responsibly. It is your obligation as Regional Coordinator to maintain direct and reasonably frequent contact with the networks in your region. The exact method of accomplishing this is left to your discretion. 4.6 Passing along Node Lists and RBBS-Net News As a Regional Coordinator, it is your responsibility to obtain the latest RBBS-Net Node List updates and any RBBS-Net News issues as they are published, and to make them available to the Network Coordinators within your region. The Node List is posted weekly on Sunday's by node 8/1. It is your responsibility to distribute these to any Network Coordinators in your region as soon as is practical after you receive them. The method of distribution is left to your discretion. You are not required to distribute them to any independent nodes in your region, though you may if you wish. It is also desirable that you make them both available for downloading by the general user, but this is not required. RBBS-PC Network Policy and Procedures Page 14 Chapter 5 INTERNATIONAL COORDINATOR PROCEDURES The International Coordinator for RBBS-Net has the primary task of maintaining the master Node List. The International Coordinator is responsible for the weekly creation of the master Node List, and the creation of a weekly update file. This master list and weekly update file are to be made available to the various Regional Coordinators during National Mail Hour on Sunday mornings. The International Coordinator is charged with the task of ensuring the smooth operation of the entire network. He does this by overseeing the operation of the various Regional Coordinators. RBBS-PC Network Policy and Procedures Page 15 Chapter 6 RBBS-PC NETWORK CONTACTS 8/0 RBBS-Net Palmdale, CA Michael White 1-805-947-8499 9600 8/1 Membership Services Alta Loma, CA Rod Bowman 1-714-945-2612 9600 Michael White Voice Phone Palmdale, CA 1-800-336-3026 1-805-273-3351 RBBS-PC Network Policy and Procedures Page 16 Chapter 7 ACKNOWLEDGMENTS IFNA The International FidoNet Association for creating standards for Packet Mail to be transmitted across the nation. RBBS-PC Remote Bulletin Board Service Program written by Tom Mack, Jon Martin and Ken Goosens. NetMail DOORWARE Program written by Bob Westcott and Rod Bowman which make RBBS-Net all possible for RBBS-PC Systems. BinkleyTerm The Front End Program for the Interface to a FidoNet Compatible Network written by Bob Hartman. RBBS-Net The RBBS-PC Network created by Michael White and Rod Bowman. AlterNet For the help with Gateways to other Network Systems. EggNet Michael White For his help in providing a BackBone Network for the RBBS-Net and his help in creating a Network for RBBS-PC Systems. Rod Bowman For all of his work on RBBS-PC, DOORWARE Programs and his help in creating a Network of RBBS-PC Systems. Bob Westcott For all of his work on the DOORWARE Programs. RBBS-PC Network Policy and Procedures Page 17