ŪŪŪ» ŪŪ» ŪŪŪŪŪŪ» ŪŪŪ» ŪŪ» ŪŪŪŪŪŪŪ» ŪŪŪŪŪŪŪŪ» ŪŪŪŪ» ŪŪŗ ŪŪÉĶĶĶĶ¼ ŪŪŪŪ» ŪŪŗ ŪŪÉĶĶĶĶ¼ ČĶĶŪŪÉĶĶ¼ ŪŪÉŪŪ» ŪŪŗ ŪŪŗ ŪŪÉŪŪ» ŪŪŗ ŪŪŪŪŪ» ŪŪŗ ŪŪŗČŪŪ»ŪŪŗ ŪŪŗ ŪŪŗČŪŪ»ŪŪŗ ŪŪÉĶĶ¼ ŪŪŗ ŪŪŗ ČŪŪŪŪŗ ČŪŪŪŪŪŪ» ŪŪŗ ČŪŪŪŪŗ ŪŪŪŪŪŪŪ» ŪŪŗ ČĶ¼ ČĶĶĶ¼ ČĶĶĶĶĶ¼ ČĶ¼ ČĶĶĶ¼ ČĶĶĶĶĶĶ¼ ČĶ¼ (TM) (New Connections Network) Net 82 Echomail Policy Established February 1994 Version 4.5 Updated: February, 1996 GENERAL ÄÄÄÄÄÄÄ This document contains Policy information for Net 82, herein refered to as NCNet, and which establishes the policy for Sysops who are members of NCNet as listed in the most current NCNet Nodelist issued by the Zone or Administrative Zone Coordinator. In cases of conflict, the most stringent NCNet policy shall apply. This policy is to define a course or methods of action selected to guide and determine present and future decisions, operation and function for NCNet. The ZC reserves the right to modify the Policy's wording as s/he see's fit so that they may be kept up-to-date as the need arises. Major changes to the Policy will be posted in NC.ADMIN/NC.SYSOP for all to view and comment upon prior to the changes becoming "policy". ĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶ NOTICE TO SYSOPS WISHING TO JOIN NCNet ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Sysops wishing to apply for a NCNet node number MUST read this policy in full and be aware of it's requirements agreeing to them. They are then "required" to fill out "Area D" of this policy and then Netmail this application to your local Hub as defined in the current NCNet nodelist using the "temporary" NCNet node number of 82:1000/999 ĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶĶ Table of Contents ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ A) Definitions B) Responsibilities C) General Echomail Policy D) New Node Policy and Procedures E) Appointments to Administrative Positions F) Annoying Behavior G) Network Use H) Sysop Procedures I) Down Nodes J) Node Number Appointments A) DEFINITIONS ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ž Zone Coordinator ......... ZC The Zone Coordinator is the main authority(Owner) and node for NCNet and is assigned the Main node number of 82:82/0 ž Administrative Zone Coordinator...AZC Aid ZC in all Administrative duties. Coordinates all echo moderators. ž Regional Coordinator ..... RC The Regional Coordinator(s) are the main echo mail distribution centers for their given region ž Net Coordinator........... HOST The Echo Host ensures distribution of echo mail to all Echo Hubs in his/her area (May also act as an EH) ž Echo Hub ................. EH The Echo Hub distributes echo mail to those "Bulletin Board Systems" (known hereafter as a 'BBS') designated in his/her Node(s) ž Echo Moderator ........... EM The Authourity who ensures that a particular echo area is kept on topic ž Sysop .................... A person or persons who runs a BBS ž User ..................... A person who is a member of a BBS ž News Editor .............. NE A person assigned to produce a Newsletter ž Zone ..................... A large geographical area (ie: N. America) ž Region ................... A smaller geopgraphical area such as a Country or a part of a (large) Country (ie: B.C.) ž Net ...................... A collection of systems local to each other (such as a city or suburbs) ž Node ..................... A single system within a net ž Point .................... A single system belonging to a node B) RESPONSIBILITIES ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ž The Zone Coordinator has the following responsibilities: ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. To coordinate the flow of NCNet Echo mail and nodelist distribution. 2. To assign positions for RCs, 'administrative' positions and Nodelist maintainance. 3. To remove 'administrative' positions assigned to nodes when necessary or if it decided by the ZC that this action benifits NCNet. 4. Assume the titles of RC and NC, until such time as these positions are deemed needed and thier positions assigned. 5. Be responsible for being the Main Echo Coordinator and send/receive all of NCNet's echo mail to each of the RCs. The ZC should arrange with all LD Echo Hubs designated times and days in which to help ensure a successful session connection. ž An Administrative Zone Cooridnator has the following responsibilities: ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. To coordinate the flow of NCNet general messages or information (ie: Newsletter, Notices to specific regions). 2. Assigns or changes the Echo Moderators, and is responsible for Echo policy and guidelines. 3. To assist in assigning positions for RCs, and other such 'administrative' positions as the ZC see's fit. 4. To remove 'administrative' positions assigned to nodes when necessary or if it decided by the ZC that this action benifits NCNet. 5. To preform various other duties as assigned by the ZC. ž The Regional Coordinator has the following responsibilities: ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. To coordinate the flow of NCNet Echo mail and nodelist distribution to all Hosts. 2. To assign Host (NC) positions within the designated region as well as assigning node numbers to all new nodes, in keeping with the guidelines for node number assignment within NCNet. 3. To maintain a Regional nodelist segment and forward all changes to the ZC by Thursday of each week. 4. Advises the ZC of net-related problems within their region, and handling policy complaints within their region, unless referred to the ZC for final decision or policy interpretation 4. Forwards all applications for node numbers to the ZC for reference. ž NC - Net Coordinator (Host) ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. To coordinate the flow of NCNet Echo mail and nodelist distribution to all Hubs or individual Nodes. 2. Advises the RC of network related problems within their Host area. 3. Forwards all Applications for Node numbers to the RC for Node number assignment. An NC administrates the network at the local state, province, or area level. Their responsibilities include the timely transfer of echomail, routed netmail, and NCNet administrative files to their dowlinks, adding new nodes within their local net, assigning node numbers to those new nodes, forwarding weekly net nodelist segments to their RC on a regular and timely basis, attempting to resolve inter-Sysop disputes within their net, and promoting NCNet whenever possible. The NC must also make sure each person to which they assign a node number is of the legal age of majority in the area in which they reside. The NC must also agree to make available to all member nodes in their net, routed netmail and NCNet administrative files, including the weekly nodelist and nodediff. The NC must poll their RC at least once weekly for any routed mail which the RC may have on hold for them. ž An Echo Moderator has the following esponsibilities: ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. Receive All of the NCNet Echo area(s) he/she has been assigned to or has volunteered to be the moderator of. 2. Monitor the contents of "each" new message in those echo area(s) to ensure that they are conforming to the Echo "topic" in general. Encourage messaging within the echo by posting messages and answering any questions that may arise. 3. Upon a violation of off-topic messages, inform the offending person(s) "politely" of the fact that they are not adhering to the Echo topic (one or two off-topic messages can be tolerated but consistent off-topic messages should be redirected back to the Echo topic). 4. Post "Rules" for the Echo on a periodical basis as the Moderator feels the need. *Note An Echo Moderator "DOES" have the power to revoke an offending User's priveledges for a determined length of time for failure to adhere to echo rules. ž An Echo Hub shall have the following responsibilities: ÄÄÄÄÄÄÄÄ 1. Sysops who are Echo Hubs shall be capable of distributing all of NCNet echo areas to their assigned nodes, at no costs to the node(s), upon request by the node(s) by either Netmail requests or by Areafix or other similar means (the prefered method is to Areafix). 2. Echo Hubs are not administrative positions. Their main function is to distribute NCNet Echo mail and other information to designated nodes. 3. The Hub position usually is determined by geographical rather than modem capabilities. However, while the higher speed connection is prefered, it is not necessarily a must. 4. Advise the ZC of any potential new Member and the gathering of and the passing on of information of the new member (as later stated within this document) for the ZC or NLC to assign a Node number. 5. Pass on all new Nodelists and Newsletters received from the ZC to their assigned nodes as soon as possible. 6. Pass on all NCNet administrative Netmail messages to their assigned nodes as soon as possible. 7. Have the latest NCNet Nodelist and Policy available for all NCNet nodes for File REQuesting (FREQ) (if possible). 8. Advise the ZC or NLC of any existing NCNet nodes that are either 'down' or who they are unable to establish daily sessions with. C) GENERAL ECHOMAIL POLICY ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. The receiving of a NCNet Nodenumber and Echomail is a privilege not a right. 2. All Sysops in NCNet must be set up to receive the Sysop Chatter Echo (known as NC.SYSOP-CHAT) even if no other Echo mail areas are to be received by the node. This is a "mandatory" NCNet echo and must be received by all current members. 3. NCNet has a Mail Hour (refer to the appropriate section of this document) for every day of the week throughout the calander year. This is to establish a time during the day where at least ONE session connection can be achived for those systems who are very busy during the day or are Private. What is perfered is for "each" Sysop to set aside an Event where no Users are allowed to call during this Mail Hour. Other mail hours times may be used providing that both Sysops agree. 4. At this time there are no costs for receiving NCNet Echos for all current NCNet nodes. In future, costs may be introduced but only upon a vote and agreement by the majority of NCNet members. 5. Violations of echo mail policies may be sufficient grounds to prevent access to selected or all EchoMail for an offending Node. Appeals shall be made to the ZC for review of appeals. All NCNet Sysops are fully responsible for all echo mail being writen on their BBS by any of their Users in all NCNet echos that they receive. 6. No NCNet echo mail shall be transferred to any other network or non-NCNet member(s) without the permission of the ZC. Points off NCNet Sysops are not permitted at this time. 7. The ZC may refuse service to a node (new or existing) if that node is in a difficult or inconvenient location, a long distance connection, or is excessively annoying (refer to following sections for definitions of what is considered to be excessively annoying). 8. A node wishing echo mail (other than the mandatory Sysop echo) should contact their local Echo Hub to request this service via Areafix. 9. It is suggested that Sysops receive as many of NCNet's Echo areas as available and that they allow Users access to these areas to help facilitate greater participation to NCNet's echo's (the exception of which shall be those echo's noted in paragraph #12 below) of which normal Users nor Non-NCNet Sysops shall not have access to either of these areas under any circumstance). However, co-sysops identified either at the time of application or through netmail to the NC, RC or ZC may participate in these echo areas. The Boss node "must" use discretion and good judgement in determining if their co-sysop may have access to these two echos. The ZC shall reserve the right to decide IF a co-sysop shall have access to any of these echos. 10. Nodes found to be "Pirate" boards (BBS's) shall have their node numbers removed immediately from the nodelist and their feeds cut permanently upon the disclosure of firm proof of their 'illegal' activities. A pirate board is one who 'knowingly' has "commercial" software available to the public (either openly or via 'special' access). 11. Nodes found to be "Hacker" boards (BBS's) shall have their node numbers removed immediately from the nodelist and their feeds cut permanently upon the disclosure of firm proof of their 'illegal' activities. 12. The following echo's are NOT to be made available on any BBS (public or private) to any User or Non-NCNet Sysops without the ZC's prior know- ledge and permission (this is because these echo's are either designated Sysop only or are of such nature as not to be intended for User viewing: NC.ADMIN Administration Area NC.SYSOP-CHAT Sysop Chatter Area NC.BADUSER Discussion on/about Bad Users on BBS's D) NEW NODE POLICY AND PROCEDURES ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. All New nodes wishing a NCNet node number must advise the ZC, AZC or NC directly (or via another NCNet Sysop if convienient) of their required information before a node number will be issued. The file titled NCAPP.TXT must be completed in full and forwarded to the appropriate party. 2. Sysops applying for a node number MUST provide their real name in order to be accepted for inclusion in NCNet. Sysops may choose to use handles or real names in the Administrative areas. 3. All new Sysops should use the "temporary" NCNet node number of 82:1000/999 to send their NCNet Application form and to maintain this number until such time as a permanent NCNet node number is assigned to them. 4. New Sysops must familiarize themselves with NCNet's policy prior to submitting their application for receiving a nodenumber. 5. All NCNet Sysops must update this information and send it to the ZC, AZC or NC whenever a change to the above information occurs for their system. 6. All Sysops wishing to carry the Adult echos of NCNet must be 18 years of age or older. Verification of this will be required. 7. Upon receipt of a node number new sysops may post test messages in the NC.SYSOP-CHAT echo only for confirmation of setup, distribution, and origin lines. E) APPOINTMENTS TO ADMINISTRATIVE POSITIONS ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. All Administrative positions in NCNet are appointed by the ZC & AZC and can be replaced, and/or changed at any time at the discretion of the ZC. 2. All Administrative positions shall report directly to the ZC/AZC. 3. Any full NCNet node may assume several Administrative positions in NCNet. F) ANNOYING BEHAVIOR ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. There are references throughout this policy to "annoying behavior" or "excessively annoying" behavior. It is defined as a term (based upon the final judgement of the ZC) where, generally speaking, annoying behavior irritates, bothers, or causes physical or emotional harm to other persons within NCNet via the use of Echo mail or Netmail under the NCNet mail distribution system (ie: Echomail, Netmail). 2. All participants of NCNet (Users of BBS's and Sysop's of NCNet) shall refrain from being obnoxious or abusive to other participants. The ZC and Echo Moderators shall be the judges of what is considered to be "annoying" with the ZC having the final judgement. 3. Any problems relating to messages and Users shall be forwarded to the related echo moderators via netmail for the Moderator to handle if the Sysop of the board where the originating "annoying" message(s) was made has not delt with the offender (if it is a User) promptly. Sysops who do not deal with the offenders may have their echo feed cut off for that echo area until such time as the ZC and Moderator(s) feel satisfied that no further problems will be forth coming from the offending system. 4. The ZC shall deal directly with offending Sysop(s). 5. Excessive swearing, anti-racist, hate, sexist or lewd comments in all message areas is to be considered "excessively annoying" behavior. G) NETWORK USE ÄÄÄÄÄÄÄÄÄÄÄ 1. NCNet is an amateur network. Participants spend their own time and money to make it work for the good of all the Users. It shall not be permitted for any commercial enterprise or person(s) to take advantage of these volunteer efforts to further their own business interests. 2. It shall be NCNet's policy that all commercial mail shall not be routed via NCNet's mail distribution system (ie: Echomail, Netmail). "Commercial mail" includes mail which furthers specific business or of person(s) interests without being of benefit to the net as a whole. Examples include company-internal mail, inter-corporate mail, specific product pricing inquiries/quotes, orders and their follow-ups, and all other subjects specifically related to commercial business. 3. The NCNet Buy and Sell echo area (NC.BUY-SELL) is not considered to be for commercial use. However, the rules above concerning commercial use and specific mail, pricing, quotes, etc. shall apply. 4. The use of NCNet as a way to communicate the means, methods (by either netmail or transfering of files) of pirating or hacking purposes of any commercial software shall be cause to have the offending node(s) removed from the net. H) SYSOP PROCEDURES ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. As the Sysop of an BBS node, you can generally do as you please, as long as you are not excessively annoying to other nodes in NCNet, and do not promote or participate in the distribution of pirated or copyrighted software or other illegal behavior via NCNet. 2. Sysops should familiarize themselves with NCNet's policy on a regular basis. Having read the policy and requested a node number, the ZC/AZC will assume that the Sysop has read the policy and will be expected to uphold the mandate of NCNet. 3. The Sysop listed in the nodelist entry is responsible for ALL traffic entering NCNet via their system. This includes (but is not limited to) traffic entered by users and any other networks for which the Sysop act's as a gateway. I) DOWN NODES ÄÄÄÄÄÄÄÄÄÄ 1. If it is known that your system will be down for an extended period (ie: more than three days), inform the ZC or your Echo Hub AS SOON AS POSSIBLE prior to or after the down time of your system. It is not the ZC or your Echo Hub's responsibility to chase you down for a status report. Any Node not receiving echo mail from their Hub on a daily basis may be considered to be 'down'. 2. Typically, any node that has not had a mail session made within 3 days of being down shall be placed upon HOLD and any waiting mail after that period may be deleted on a weekly basis (or at the Hubs discretion). After a resonable period of time, the node who is down may be deleted from the NCNet node in their entirety at the discretion of the ZC. 3. If your system is down never put an answering machine or any other device which answers the phone on your BBS phone line while you are down. If you do then systems calling will get the machine repeatedly. This constitutes annoying behaviour. 4. If you will be leaving your system unattended for an extended period of time (such as while you are on vacation), you must notify your Echo Hub. As Systems have a tendency to "crash" now and then, you may want your Echo Hub to know that it is a temporary condition if it happens while you are away. J) NODE NUMBER APPOINTMENTS ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. Node numbers for NCNet will only be provided to those who run a fully functional public or private BBS. Anyone running a BBS or Mailer for their own personal use will NOT be assigned a NCNet node number. The reason for this policy is to further the availability of NCNet Echo areas to Users. A single User system is not considered a means to which NCNet echos are available to the general public. Those systems should ask a NCNet Sysop of a BBS that they call frequently and see if they can become a Point off that BBS. In this way, they can then receive NCNet echo's. The ZC may, if they wish, over-ride this if they feel that the requesting Sysop is of potential benifit to NCNet. 2. Node numbers will be assigned in proper numerical order (ie: 101, 102, 103) in single digit increments. Regional Coordinators should refer to the current NCNet nodelist for reference or contact the ZC/AZC should they require further explanation. Dwayne Deschaine Owner & Zone Coordinator 82:82/1 - 82:1000/0 Fido: 1:153/8001 E-mail: ddeschai@direct.ca Jana Deschaine Administrative Zone Coordinator 82:82/1 - 82:1000/101 Fido: 1:153/223 Tammy Wilson Assistant Net Coordinator 82:82/2 - 82:1000/116 Fido: 1:153/7019 (C) 1994-1996