----------------------------------------- New England Network Policy Guidelines ----------------------------------------- [Formerly known as RI-Net since 1988] Revision 1.05 - As of 10/1/92 I Network Overview ================ New England Net (NE-Net) is a co-operative effort of many high quality bulletin board systems and users. The network welcomes any computer type or bbs software which is capable of exchanging net mail with other systems. We currently support the following networking technologies: Postlink, Fido echomail, Qnet/QWK(Rnet, Tnet, Cnet, etc). We are a small general interest network serving the New England area. Boards outside of the NE area are also welcomed to join. Our goal is simple: To transfer messages for our users Network Motto : "It's ONLY A Hobby!" Our goal is to provide an environment where users can discuss social and technical related topics. The network is divided into Special Interest Group conferences (SIGs), and each area is managed by a worthy Conference Host. The network is privately managed as if it was a BIG BBS, with member systems subscribing for their echomail feeds(free). We feel that this structure provides a minimum of politics, while simply getting the mail through. Sysop feedback is VERY important and will help to guide the network - however, we are NOT and do not claim to be democratic or political. There are no fees to participate in NE-Net, except possibly toll charges that you may incurr. II Operational Concept and Definition ================================== -NETHUB- / | \ \ / | \ \ / | \ \ HUB NODE HUB NODE / \ / \ NODE NODE NODE NODE HUB - A hub is any board that distributes mail to other systems. Hubs are established in new calling areas to distribute mail to other local boards. This method minimizes toll charges. NODE - A node is any participating BBS. Nodes can call a regional hub, or directly into the NETHUB as long as arrangements are made in advance. Nodes are not called by any other systems in the net. NET HUB - The nethub is where the network originates, and does not make outgoing calls for mail. The nethub sysop will be responsible for overall network operation and direction. The nethub supports multiple networking technologies, and is responsible for moving the mail between the various packet formats and to keep it flowing properly without duplicates. The NE-Net nethub system is Eagles Nest Communications, and presently supports v32/bis, v42/bis, HST, and CompuCom high speed connections. III Conference Hosts ================ Each special interest group is GUIDED by a dedicated volunteer who is responsible to assure that net guidelines are being used, topic information is posted approximately monthly to define the goals of the base, bashing is prevented, and to keep the mail flowing by introducing new topics and suggestions in the area of interest. Conference hosts on NE-Net are present to encourage friendly discussion and topics -- but NOT for heavy handedness or strong moderation/enforcement. Problems with users may sometimes arise in the SIGS, and hosts are asked to contact the network coordinators if a situation cannot be remedied by a friendly reminder to the user. In those rare cases, the NCs will handle the situation according to their discretion which may include contacting the sysop(s) of that board and asking them to address the situation discreetly and personally. We feel that over-moderation is the key to an unpleasant networking experience, and watch this carefully. One person may host up to two NE-Net conferences. A current list of conferences can be found on the nethub, or in the latest NENETxxx.ZIP "Information Pack". Conference suggestions and host volunteers are heartily welcomed, and can be directed to NE-Net Common. IV New England Net Policies ======================== Although we are a non-politically intense/social type of network, some "common sense guidelines" are required. They have been spelled out here to hopefully head off most problems before they happen, and to answer questions. Some conferences have additional guidelines, and those are defined in the NENET.CNF document. a) Private and/or confidential mail is NOT supported via the network, persuant to the Electronic Communications Privacy Act of 1986. 18 USC 2510, et al. All systems operators participating in the network have access to any mail which is sent with the R/O flag. Although the messages will be passed, this is discouraged except for sysop communications. b) Quality Assurance: All users are to be verified, either by call- back door, voice, post card, etc, prior to being granting "post" access in the NE-NET bases. This has always been our policy, and protects us somewhat from abusers who would post abusive messages under an assumed name. c) ANSI messages and signatures are limited to the BBS ADS conference. Some users and participating systems have equipment which is not compatable with ANSI, and these messages should be discouraged. d) BBS Ads are limited to the BBS ADS conference. Sysops are encouraged to post ads for their bbs in this base, but no more than once in 14 days. e) Profanity, abusive language, personal attacks, or BASHING will not be tolerated under any circumstances. It is the responsibility of the conference host, the NC's, and the node sysop to properly and privately deal with offenders of this policy in a professional and timely manner. If all parties are not satisfied with the resolution, the NC's may, at their discretion, have the user's access to the network suspended for an undetermined period of time. The NC will send a note to the sysop informing them of the trouble user, and if the sysop does not address the problem in 36 hours, that system will be temporarily syspended until the situation is remedied. f) Handles and aliases are not permitted in message headers, but are welcomed within messages and tag lines. 1) Handles ARE allowed in certain bases. See NE-NET.CNF for details. g) All member boards must carry the NE-NET COMMON message base. This conference will contain network announcements and information. h) System operators are responsible to inform their users of the NE-NET guidelines and are encouraged to extract any portion of this file or the conference description file for public posting/bulletins/news files. Sysops are responsible for messages leaving their system and are asked to post this file for public download (NENET???.ZIP). i) Distribution and exchange of NE-NET messages with other systems is strictly prohibited, unless system has been admitted by the NCs. All gateways with other networks must be under direction of the nethub. We will make every effort to verify a recommended board within 24 hours. j) Any commercial use of the network is strictly prohibited. 1) Vendors may post a sale message no more than once in a two week period. These messages are allowable in the FOR SALE section only. See NE-NET.CNF for more information on this policy. k) All nodes and regional hubs are expected to transfer mail no less than 3 times per week with approved and tested net software. A DAILY event would be perfect for this purpose. If a system is unable to meet this requirement due to sysop vacation or technical problems, we would appreciate notification. l) System tag lines should be in a standard format. For Example: "NE-Net * Eagles Nest Communications * Providence, RI * (401)732-5290" m) These policies may be ammended at any time without prior notice. All member sysops are encouraged to give their input and these discussions should take place in the NE-Net Sysops' conference. Management reserves the right to suspend transfers with any system on the network whenever it deems necessary to ensure that the goals of the network are met. ------------------------------------------------------------------------------ NE-Net: "The Network for the USERS" Please Refer All Inquiries To: Mike Labbe or Lea Walsh, NE-Net Coordinators C/O Eagles Nest Communications BBS PO Box 23392 Providence, RI 02903 BBS: (401) 732-5290 Fido 1:323/126