S T O R M N E T F l e x i b i l i t y i s o u r m i d d l e n a m e Official StormNet Policy Document (SNPol) Version 2.00 Effective Tuesday, December 20, 1994 StormNet - Flexibility is our middle name. 1. Introduction Welcome to StormNet, the flexible and fast-growing mail network! This policy document must be read by everyone before applying to join StormNet. We won't go into a two-page dissertation, but for simplicity's sake, 'his' will be used instead of 'his/her'. 2. StormNet Structure 2-a. Node Number A node number is your means of identifying yourself when communicating in StormNet. You must present this node number when sending messages or exchanging any files with other systems. The format of a node number is :/[.]. Some examples of StormNet node numbers are 181:292/1, 182:182/1, 181:192/201, 181:1813/0, 183:1830/1 and 181:192/104.1. 2-b. Coordinators and Support Nodes In a multi-zone network such as StormNet, there are many coordinator positions and nodes. These are outlined in this section. 2-b1. International Coordinator (IC) The International StormNet Coordinator is the head of StormNet. His duties are to monitor office holders at the International level, act as the president of the SNAC and generally ensure the smooth operation of StormNet. He moderates the sysop echo (SN_SYSOP), the *C echo (SN_STAR-C), the StormNet Advisory Council (SNAC) echo (SN_SNAC) and the questions and answers echo (SN_Q-A). 2-b2. International Echomail Coordinator (IEC) The International Echomail Coordinator is in charge of the moderation and distribution of echomail. His duties are to approve changes to the echomail backbone (additions and deletions of areas) and release a weekly file "STORMNET.EBB" listing all areas on the current backbone. He appoints echo moderators, acts as an echo co-moderator for all areas and moderates all echos that do not have a full-time moderator. He also moderates the general chat echo (SN_CHAT), echo request echo (SN_ECHOREQ), moderator echo (SN_MODERATOR), and war zone echo (WAR_ZONE). 2-b3. International Nodelist Coordinator (INC) The International Nodelist Coordinator is the head of the StormNet nodelist (SNETLIST) and node difference file (SNETDIFF). His duties are to assign zone numbers to new areas and compile the zone segments from the international positions to form the weekly nodelist and difference files. 2-b4. International Literature Coordinator (ILC) The International Literature Coordinator is the head of the StormNet Policy, StormNews, and other StormNet related documents. Duties include ongoing policy maintenance in addition to creating and editing the StormNews. He also moderates the news echo (SN_NEWS) and the policy discussions echo (SN_POLICY). 2-b5. International InterNet Coordinator (IIC) The International InterNet Coordinator is responsible for the interchange of mail between StormNet and the InterNet. The IIC operates the primary gateway between StormNet and the InterNet (181:181/10), manages which other systems in StormNet may carry the GUUCP flag, and maintains proper operation of the StormNet DNS domain (storm.net). The IIC also acts as the liaison between the members of the StormNet administration and the Internet administration. 2-b6. StormNet Advisory Council (SNAC) The StormNet Advisory Council consists of the current I*Cs, Z*Cs and RCs of StormNet; the IC acts as president of the SNAC. This council votes on specific issues as needed. This includes appeals, excommunications and reapplications following excommunication. For additional information on the SNAC, see section 6-a. 2-b7. Zone Gate The Zone Gates are those systems which gate netmail, echomail and files between their zone and other StormNet zones. 2-b8. Support Nodes A sysop who considers himself proficient in a specific field or application may request the SNAC to designate him as a support node. 2-b8a. Duties A support node is considered an expert in the field which he was designated. He can be called upon through echomail or netmail by anyone needing assistance. The moderation of an echo may also be included as part of his duties. 2-b8b. Nodelist Indication A support node is identified in the nodelist by means of a flag. The flag is the prefix "S-" followed by the name of the program (or an abbreviation thereof). For example, the support node for the T.A.G. BBS software has the flag S-TAG; while the support node for the BinkleyTerm software has the flag S-BINK. If a person is a support node for two or more items, both flags are listed separately. For example, if a node is a support node for both BinkleyTerm and Maximus, he would have the flags S-BINK and S-MAX. 2-c. Zone A zone is a large geographic area such as a continent or a large country. The zone number occupies the first field of the node number before the colon. At the time of this policy, StormNet occupies zones 181, 182, 183, and 184, meaning all StormNet node numbers begin with one of these four numbers (for example 181:181/0 or 183:183/0). StormNet has reserved zones 185 through 189 for future expansion. 2-c1. Zone Coordinator (ZC) The duties of the zone coordinator are to compile their zone nodelist segment and send it to the INC, monitor office holders at the zone and regional levels, and act as president of the Zone Advisory Council (ZAC) of his zone. 2-c2. Zone Advisory Council (ZAC) The Zone Advisory Council consists of the current R*Cs and Z*Cs of that zone, with the zone coordinator (ZC) acting as president. This group functions similar to the SNAC, but focuses on zone specific issues. 2-d. Region A region is an area occupying a portion of a zone. This normally consists of a group of states/provinces or a small nation. 2-d1. Regional Coordinator (RC) The Regional Coordinator's duties include assigning net numbers for new networks, monitoring office holders at the regional and network levels and compiling the regional nodelist segment and sending it to the zone coordinator. 2-d2. Regional Echomail Coordinator (REC) The Regional Echomail Coordinator's duties include supervision of echomail in that particular region. His duties are to transfer echomail with the NEC's in his area. 2-d3. Independent Systems A system which is not in the vicinity of an existing network, and is not able to become an NC for whatever reason, can request to be an independent system in the region which they were assigned to. Independent systems are treated in the same way as any normal node. 2-e. Networks A network (a.k.a. net) is a collection of systems in an area forming part of a region. A network is a less expensive and more efficient method of mail transfer when there are several systems in the same area. 2-e1. Network Coordinator (NC) The Network Coordinator's responsibilities include ensuring the smooth operation of their individual network. The NC's duties are to assign node numbers for sysops joining the StormNet, handle sysop applications, and maintain the nodelist segment for their individual network. The NC may also moderate an echo for network information such as net 181:192's "NET192" echo. 2-e2. Network Echomail Coordinator (NEC) The Network Echomail Coordinator distributes echomail and files to the NC, HCs, and/or nodes in the net. 2-e3. Hubs and Hub Coordinators (HC) The Network Coordinator may require assistance in the distribution of echomail to the systems within the net. In this case they can appoint systems to be echomail hubs in order to aid in the distribution of echomail. The duties of a Hub Coordinator are to simply distribute the echomail sent to him by the Net Coordinator. The method of designation to be used for a hub is decided by the HC and NC in the area. 2-f. Systems A system is a BBS run by a single SysOp (system operator) using Fido-Technology or QWK-Compatible mail software. The BBS receives mail from another system the StormNet network (called an uplink or feed) and may send mail to other StormNet systems (called downlinks). 2-f1. Users A user is a single person who calls a system and reads and/or replies to messages in StormNet echos with his terminal program and/or offline reader. In doing this, his actions are the sole responsibility of the sysop. 2-f2. Points A point is a more advanced form of a user who uses an offline mail reader. A point is like another system in the net using a FidoNet technology mailer, but whose interactions in the network are handled through a bossnode (another StormNet node from which the point transfers mail). Points may use echomail or netmail, but must receive them and route them through their bossnode only. Interactions between points and other systems are not prohibited unless you have been instructed not to interact to with specific system by the operator of that system. These requests will be enforced by the net. Like a user, the bossnode is responsible for the actions of his points. 3. General Policies 3-a. General Policy Be nice and use common sense. The only time this can fail is if someone is unwilling to use common sense, in which case, the rest of the nonsense found in this extraordinarily long policy document applies. 3-b. Netmail Policy Use of encryption programs or devices in hub-routed mail is permitted, unless your zone/region/net has a separate policy stating that you may not encrypt mail. If encryption is allowed, you must agree to not discuss topics which are illegal or could cause legal action to be taken against yourself or any sysop along the routing chain. StormNet and its mail hubs are not responsible for any illegal activities discussed in netmail. 3-c. Echomail Policy StormNet is a fabulous network in which communication via echomail can be fun. Echomail is a great way to contact a wide variety of people on numerous topics. Since so many people have access to these echos, there is the possibility of starting quarrels and other disputes. Our talented staff of moderators will endeavor to keep things under control in these circumstances. 3-c1. Handles Handles are NOT permitted in any echos unless otherwise stated by the IEC, moderator, or noted so in the echomail backbone listing. 3-c2. Swearing/Vulgar Language Swearing and vulgar language is not permitted in any conference unless otherwise permitted by the IEC. Moderators must receive permission from the IEC if they wish their echo to permit such language. The moderator must netmail a request to the IEC, who will decide if the request should be granted or not; a netmail message with his decision should be returned to the moderator within two (2) weeks time. The moderator may appeal the decision by bringing it to the attention of the StormNet Advisory Council (SNAC). 3-c3. ANSI Graphics in Echomail Areas ANSI graphics are not permitted in any StormNet echomail conference unless the moderator specifically states that they are allowed. This decision is entirely up to the moderator of the echo and any changes should be reported to the IEC. 3-c4. Proper and Improper AKAs Proper AKAs must be appended to echomail messages by your message tosser. Proper AKAs must include the following node numbers: Your individual node number, your *C addresses (if you have any of these), and your zone and international positions. Addresses should go in the order specified above. You may not use improper AKA information in your echomail data for any reason. Accidents will be permitted, but if the problem persists after thirty (30) days (you will be warned), you may face excommunication. These decisions will be made by the SNAC. 3-c5. User/Sysop Compliance If a user can not contain himself and does not follow the rules, they will receive two (2) warnings from the moderator (one through the echo and the second via netmail). If, after the second warning, the user does not get his act together, the moderator will notify the IEC of the infraction, and the IEC will netmail the sysop and the user. If the symptoms still persist, the IEC will notify the sysop to remove the user's access. If the sysop does not do so within a week, the node will simply be excommunicated. If the sysop is the one causing the trouble, he gets two warnings from the moderator, and then the moderator hands it over to the IEC. The IEC will warn him twice, and if the sysop still does not comply, he will be excommunicated. 3-c6. Removal of a Moderator If the moderator does not follow his part in the rules stated above and the IEC receives complaints concerning him, the moderator may be removed from the echo by a decision from the IEC. This may be appealed by discussion with the SNAC. Moderators also have to follow the same rules as sysops and users. 3-c7. Becoming a Moderator If you would like to become a moderator for an echo, you must sent netmail to the IEC requesting the position. The IEC will decide if that echo requires a moderator and then make his decision. The IEC has the right to restrict a person from becoming a moderator. In order to become a moderator, the following basic requirements must be met. First, the applicant must have a valid StormNet address or receive mail directly from a valid StormNet crashmail address. Second, the applicant must be able to receive the echo at least twice a week and have a feed that polls their mail hub at least as often. Third, the applicant or his mail contact must have been a StormNet crashmail system for a minimum of sixty (60) days. 3-c8. Going Beyond the Echomail Policy In some cases, the policy will not cover the a particular problem. In this case, the moderator or a member of the SNAC is to contact the IEC directly and notify him of the problem. The IEC will decide fairly based on the facts. The IEC's decision may be appealed by way of the SNAC. 3-d. Nodelist Policy No modified version of the StormNet Nodelist may be distributed without specific written permission from the current StormNet INC. If you are a coordinator, you MUST make available the new SNetList to all your downlinks. All nodes and points should also try to maintain the latest nodelist. 3-e. Policy Information 3-e1. General Policy Information This policy is an official document. It is understood by the SNAC that you agree to comply with it before applying for your StormNet address. If this is not the case, simply inform your coordinator that you cannot abide by it and you will be removed from the net. It's that simple. This document is long, but we have tried to cover every instance of possible trouble. 3-e2. Policy Distribution Being an important document, it is of utmost importance that you have a fully accurate and up-to-date policy document. Your local mail hub should always have the newest version available. If it is not available for any reason it may be file requested from any international or zone coordinator. It is forbidden for a coordinator or sysop to distribute a policy that is not identical to the policy distributed to them. Anyone discovered doing so will be given one netmail warning immediately. If they are ever discovered doing so again, they will be excommunicated without question. 3-e3. Interpretation The wording contained in this document is not necessarily the wording contained in this document. If there is any confusion as to the wording of this document, the SNAC will decide on its meaning. Many versions were drafted before its released. Note that decisions are not always a precedent; the SNAC may change their interpretation at any time. 3-e4. A Final Paragraph Be nice and use common sense. "Do not be excessively annoying and do not be too easily annoyed." 3-e5. A Final Word Goodbye :-) 3-f. StormNews Policy StormNews is the random "whenever we get to it" electronic newsletter of StormNet. It will be released only if there is reasonable material to publish. If you have any articles that you would like to submit for a future StormNews, please file attach or netmail them to the ILC (181:181/3). 3-g. Mail Distribution Policy In order to keep mail flow current and up-to-date, it is required that you poll your uplink for mail a minimum of once per week. If you cannot meet this requirement, you are to contact your uplink and notify him of this fact. The uplink may choose to remove your mail feed rights from his system if he wishes. This decision can be appealed by way of the SNAC. 3-g1. Coordinator Mail Distribution When you assume a coordinator position and are an uplink for other systems, it is required that you poll your uplink a minimum of three times per week. If you cannot poll a minimum of three times per week, you should contact your uplink and notify him, as well as contact your downlinks. Systems with downlinks that will not be polling their uplinks at least once per day are requested to inform their downlinks of their intended polling schedule. If one of your downlinks is capable of polling the minimum or more often, it would be wise to turn echomail coordinator control to this downlink or allow them to take your position. It is recommended that all systems with downlinks poll their uplink once every day or two, but at least once every three days so that mail can be distributed as quickly as possible. 3-h. Changes to the Policies and Approval Submissions of new policies are subject to a SNAC approval vote. This vote will be taken before the official policy document is modified and released. 4. Policy Complaints, Appeals, and Policing System 4-a. Definition of a Policy Complaint A policy complaint is bringing someone before the SNAC because they have violated some portion of the current policy. Anyone can have a complaint filed against them. If the offense is regarding a sysop's actions or inactions as a sysop (writing an offensive message, distributing an altered policy or a user-based offense) the node filing the complaint should notify the appropriate Regional Coordinator. If there is a problem with this, such as the RC is the sysop being filed against, then the message should be sent to the ZC. If there is a problem with this, then the message should be sent to anyone in SNAC. The SNAC member receiving the complaint should forward it to the SNAC president (the IC) who will call for a vote of the SNAC on the matter. 4-b. Definition of Appeal "ap-peal (e pel')"..."n. (1) a call upon some authority or person for a decision, opinion, etc, n. (2) the skin of a fruit, ie. appeal on an apple." Webster's New World Dictionary. StormNet and the SNAC define appeal in a manner quite similar to Mr. Webster. An appeal is a partial synonym for policy complaint, but can also hold another meaning. For example, if a user is appealed by an NC to the StormNet Advisory Council (SNAC), who says that the user should be excommunicated, then the user has a right to appeal to SNAC for the decision. The decision of the higher council overrides the lower decision, regardless if it helps or hurts the user. Both sides may present evidence and reasons in attempt to persuade the council members to vote in their favor. 5. Coordinator Term Length and Voting 5-a. Term Lengths A StormNet coordinator can remain in office as long as he wishes and as long as he continues to have the support of those under him. This will be proven by a bi-annual election. 5-b. Hub Coordinators Hub coordinators retain their positions until they resign, are removed by the NC or are removed by popular vote. Upon the vacating of the position, a new hub coordinator will be elected by the members of the hub he represents, excluding the net coordinator in cases where the NC resides in the hub in question. In the event of a tie, the net coordinator will cast the tie-breaking vote for a new hub coordinator. 5-c. Network Coordinators Network coordinators retain their positions until they resign, are removed by the RC or are removed by popular net vote. Upon the vacating of the position, a new network coordinator will be elected by the members of the net he represents, excluding the regional coordinator in cases where the RC resides in the network in question. In the event of a tie, the regional coordinator will cast the tie-breaking vote for a new network coordinator. 5-d. Regional Coordinators Regional Coordinators retain their positions until they resign or are removed by the zone coordinator, international coordinator, StormNet Advisory Council, or a popularity vote by the net coordinators of the region, excluding the zone coordinator, or international coordinator in cases where either hold a network coordinator position in the region in question. Upon the vacating of the regional coordinator position, a new regional coordinator will be elected by the network coordinators of the region, excluding the zone coordinator if he also holds an NC position in the region holding the election. In the event of a tie, the ZC will cast the tie-breaking vote for the new regional coordinator. 5-e. Zone Coordinators Zone Coordinators retain their positions until they resign or are removed by the international coordinator, a SNAC committee vote, or by popular vote of all nodes in the zone. Upon the vacating of the position, a new zone coordinator will be elected by the regional and network coordinators of the zone. In the event of a tie, the international coordinator will cast the tie-breaking vote for the new zone coordinator. 5-f. International Coordinator The International Coordinator will retain his position until he resigns, is removed by the StormNet Advisory council, or by popular vote of all *Cs in StormNet. 5-g. Voting Procedures The procedure for an election should be decided by the former or current office holder. If there is no current office holder, the next highest coordinator will decide the procedure. If there is no current office, the procedure is decided by the person creating the position. 6. Judiciary System 6-a. SNAC: The StormNet Advisory Council SNAC is the supreme court of StormNet. It has the highest decision over any issue at hand. 6-b. Members and Location of SNAC The SNAC consists of the following members: I*Cs, Z*Cs, and Rcs. All members of the SNAC have one (1) vote regardless of the number of positions they hold. 7. Appendices 7-a. Mail Hour Similar to other mail networks, StormNet has a mail hour. This is a period of time when all systems except points and private nodes must disallow BBS user access to ensure mail transfer completion. StormNet Mail Hour, by request, coincides with the FidoNet Zone 1 Mail Hour. Therefore, StormNet's mail hour is: UTC DISC [+/-] Area Description Local Time --------------------------------------------------------------- AHST -1000 Alaska-Hawaii Standard Time 23:00 to 00:00 HDT -0900 Hawaii Daylight Time 00:00 to 01:00 PST -0800 Pacific Standard Time 01:00 to 02:00 PDT -0700 Pacific Daylight Time 02:00 to 03:00 MST -0700 Mountain Standard Time 02:00 to 03:00 MDT -0600 Mountain Daylight Time 03:00 to 04:00 CST -0600 Central Standard Time 03:00 to 04:00 CDT -0500 Central Daylight Time 04:00 to 05:00 EST -0500 Eastern Standard Time 04:00 to 05:00 EDT -0400 Eastern Daylight Time 05:00 to 06:00 AST -0400 Atlantic Standard Time 05:00 to 06:00 ADT -0300 Atlantic Daylight Time 06:00 to 07:00 WAT -0100 West Africa Time 08:00 to 09:00 *GMT +0000 Greenwich Mean Time 09:00 to 10:00 *UTC +0000 Universal Time 09:00 to 10:00 CET +0100 Central Europe Time 10:00 to 11:00 BST +0100 British Summer Time 10:00 to 11:00 CEST +0200 Central Europe Summer Time 11:00 to 12:00 EET +0200 Eastern European Time 11:00 to 12:00 WAST +0700 West Australian Time 16:00 to 17:00 WADT +0800 West Australian Daylight Time 17:00 to 18:00 CCT +0800 China Coast Time 17:00 to 18:00 JST +0900 Japan Standard Time 18:00 to 19:00 CAST +0930 Central Australian Standard Time 18:30 to 19:30 EAST +1000 East Australian Standard Time 19:00 to 20:00 CADT +1030 Central Australian Daylight Time 19:30 to 20:30 EADT +1100 East Australian Daylight Time 20:00 to 21:00 NZST +1200 New Zealand Standard Time 21:00 to 22:00 NZDT +1300 New Zealand Daylight Time 22:00 to 23:00 --------------------------------------------------------------- (*) This chart is meant for convenience. If your time zone is not listed above, please add/subtract the appropriate amount of time from the GMT/UTC time. Additions to this list should be submitted to any SNAC member, to be added to the next policy revision. --------------------------------------------------------------- 7-a1. StormNet Mail Hour Exceptions If your system resides at a location where the time of StormNet Mail Hour falls at an inconvenient time (such as during the day), you may follow your zone policy (if one exists) as to when your system is to be available for mail hour. If zone policy or a zone ruling on this matter does not exist in your zone, you should suggest it to the ZAC and attempt to have one passed. Until such time, your system should remain available during the StormNet Mail Hour as defined in this document. It is recommended that your system be available during StormNet Mail Hour if you are on the I*C and/or Z*C chain (including Zone Gates). This is to insure that mail flow between zones continues smoothly. 7-b. Cost Recovery Due to the increasing volume of StormNet mail, it may become necessary to implement a cost recovery plan for your region, net or hub. There will be NO network wide cost recovery plan. The only costs allowed to be recovered from StormNet nodes are those for your telephone bill related to calls for StormNet mail and files. You may only expect StormNet nodes to pay for costs directly related to the distribution of StormNet. Failure to comply with this may result in removal of your *C position and all mail distribution rights. 7-b1. Non-Participation in Cost-Recovery Systems You may not force nodes to participate in a cost recovery system. However, you do not have to provide them with a feed if they choose not to participate. Any node can poll any echomail distributor for mail if he does not wish to poll his *EC for any reason. 7-b2. Starting a Cost-Recovery System If you wish to recover costs relating to StormNet from your downlinks, you must receive approval from the ZC of the zone which this plan will effect. Before implementing a system, we suggest that you ask the opinions of those nodes which will be assisting in the payment of your costs. We hope you will consider their opinions and will adjust your plans accordingly. Implementing a cost-recovery system does not give you the right for a free ride; you should pay the same share as any other node pays. Before applying any cost-recovery system, you must obtain approval from the ZC of the zone that this plan will effect. Reasonable and fair requests will normally be accepted. Anyone affected by the proposed cost-recovery system may appeal this decision by bringing it to the attention of the SNAC. If the ZC wishes to implement a cost-recovery system, he must contact the IC and IEC for approval. 7-b2a. Failure to Seek Approval for a Cost-Recovery System Any system beginning a cost-recovery system without the approval from the ZC of the zone that this plan will effect should be reported immediately to the ZC of the zone which it is occurring in. The ZC will warn the originator of the system to stop all plans immediately. If this still continues without the ZC receiving an application to have the cost-recovery system approved, the originator will simply loose his mail distribution rights. The cost-recovery originator may appeal this decision by bringing it to the attention of the SNAC. If the ZC is the one who implemented the unapproved cost-recovery system, the decision will be made by the IC and IEC. 7-c. Excommunication Excommunication is the termination of all StormNet related communications with a particular system. Violation of these policies may result in excommunication. The terms of excommunication are as follows: You will be removed from the StormNet nodelist. You will be denied reapplication into StormNet for a period of time to be determined by the Advisory Council at the time of excommunication. After such time has passed you may reapply, pending a majority vote in the StormNet Advisory Council.