From: Esemi@polaris.utu.fi (Sami-Pekka Hallikas)
Newsgroups: alt.bbs.ads
Subject: Cabinet (Fidonet (tm) type network)
Date: 3 Jan 93 02:24:57 GMT
Organization: University of Turku, Finland

I'm not sure if this MAY not be right area, but I post this anyway. And please
not any flames, But if you REALLY like to send flames, send those in /dev/null
 
 
 
    CCCCCC   AAAAAA   BBBBB        ii        N    NN   EEEEE  TTTTTTT
     CC       AA  AA   BB  BB               NNN  NN   EE        TT
      CC       AAAAAA   BBBBB     iii      NN N NN   EEEE      TT
       CC       AA  AA   BB  BB    ii     NN  NNN   EE        TT
        CC       AA  AA   BB  BB   ii    NN   NN   EE        TT
         CCCCCC   AA  AA   BBBBB  iiii  NN    N   EEEEEE    TT
 
 
             Computers And Bulletinboards in NETwork.
 
 
    TITLE:      CABiNET official document
 
    SUBJECT:    CABiNET RULES AND ORGANIZATION
 
    REVISION:   1.02
 
    Approved by the CABiNET official informant at 112:911/170 on 21Dec92.
 
 
============================================================================
 
DESCRIPTION OF CABiNET:
=======================
 
         CABiNET is a BBS (Bulletin Board System) network that intends
         to make electronic communication easier and swiftier than ever.
 
         CABiNET is based on the standards created by the Fidonet<tm>
         Standards Committee. For more information on those standards,
         please consult the FSC*.* and FTS*.* documents found on many
         public bulletin board systems.
 
         In addition to the FSC standards, CABiNET follows these rules:
             ~ 8 bit characters may be used and are recommended.
               (International areas are yet under construction)
             ~ Encouragement towards 4D systems. (points are welcome)
             ~ Default packing used is .ZIP (using Phil Katz's PkZip 1.10)
 
             ~ POLLing optimization. The CABiNET organization tries to
               optimize node-to-hub and hub-to-host polling in a way that
               leads to as fast mail as possible but still at a reasonable
               cost.
 
             ~ NodeList format:
               In Finland there are currently two different companies
               organizing long distance calls. And there are three ways to
               make a LD call. First, there is the conventional TELE, whose
               LD-prefix is always 9-. This is the most expensive method
               to call. Nowadays MOST (but not all :() local telephone
               companies have joined to a commercial service system called
               DIANA. When you call to a Diana number, you select the prefix
               9102-. DIANA has also another service -- you may have Diana
               installed to your number, and then you can call to numbers
               that do not have Diana installed. The prefix is 9103-.
 
               But then... if a telephone number is in a calling area there
               there is no local company but only the TELE, you cannot use
               the 9103 Diana service.
 
               This is why CABiNET uses a different format in the telephone
               numbers in the nodelist. Examples follow:
 
                  +358-17-533621
 
                  This is a normal number at a local telephone company.
                  No 9102-service, but you may use 9103-service if you have
                  it installed.
 
                  +358D-17-533621
 
                  Local telephone company's number with Diana 9102-service
                  installed. You may dial 9102- even if you don't have 9103
                  installed. If your phone is in TELE's district, you may not
                  use the 9102 service.
 
                  +358T-37-49007
 
                  Telephone number under TELE's control. DON'T CALL with
                  9103- nor 9102 -- they won't work.
 
         CABiNET will try to serve as many users' needs as possible. Thus,
         end-user comments are warmly welcomed to the CN.COMMENTS conference.
         The organization reads this conference and respects the views
         expressed by the users. However, every comment will be considered
         carefully before acting upon.
 
 
THE CABiNET ORGANIZATION
========================
 
         CABiNET main organization consists of:
 
           ~ HOST
             This is the main node that distributes mail to all hubs in
             a net. Currently CABiNET is in only one net, so there's only
             one HOST, 112:911/0, a.k.a. 112:911/370.
             The HOST's SysOp is called the Network Coordinator, NC.
             The NC of CABiNET is Petri Kultaranta.
 
           ~ HUBs
             HUBs are bigger nodes that distribute mail to their closest
             nodes. In CABiNET there will be one HUB per one local calling-
             area, so only one system in the area will have to make LD
             calls to get the mail.
 
           ~ NODEs
             A NODE is one system with a SysOp and all of its users.
 
           ~ POINTs
             A POINT is one end-user who subscribes the mail from his/her
             BOSS node directly to his/her system.
 
           ! CABiNET ORGANIZING COMMITTEE, COC
             COC consists of several important CABiNET SysOps.
             The director of COC is Jaakko Kivela @ 112:911/170.
 
           The NC and the COC director together always have the final word
           on any matter considering the net.
 
           CABiNET nodelist is the responsibility of the NC.
 
           All other official cabinet files are the responsibility of
           the COC. Also, the COC director is the one who finally decides
           all changes done in the network system by adding the changes
           in the official documents. No change takes place before it is
           officially noted in one of the CiN-*.* documents. All of the
           official documentation packets have a .ZIP verification from
           Jackal Computing.
 
           The newest nodelist can be FileRequested from 112:911/370 and
           112:911/170 anytime with tag 'CABiNODE'. The filename for the
           nodelist is 'CABNODE.???', where ??? is the number of the day
           of the year.
 
           The latest update on other CABiNET files may be requested
           from 112:911/170 anytime with tag 'CABiNET'. With this tag
           you will get a packet, CABiNET.ZIP, which contains some or all
           of the official CABiNET documents.
 
 
A CABiNET NODE -- how to become one?
====================================
 
         Rules for a node:
 
           ~ CABiNET is not a commercial network, so you may not charge
             any extra fee from the users for reading/writing CABiNET
             messages. It's OK for you to charge for the use of your system,
             but you may not charge EXTRA for CABiNET.
 
           ~ You may choose whatever areas you want from the CABiNET.
             However, the following areas are OBLIGATORY for any node:
             CN.NEWS, CN.COMMENTS.
 
             The CN.NEWS conference is for CABiNET official information
             only. You will have to mark it read-only for the users.
             The only persons having right access to this conference are:
             NC, members of COC, and moderators.
 
             The CN.COMMENTS conference is for end-user comments on the
             CABiNET. This conference should be marked write-only for the
             users, so that other users cannot read one user's comments to
             the organization. The NC, COC members, moderators and SysOps
             will answer to the messages in this conference; and the COC
             will consider any given ideas.
 
           ~ As swiftness is one of CABiNETs main principles, the nodes
             must poll their feeds regularly and frequent enough. A node
             will always poll its hub. Node-to-node polling is not allowed,
             because it would make the mail routing complicated and slow.
 
             If a node is considered too 'quiet' by the COC and the NC,
             the node will be rejected. (Quiet means there are few messages
             from that node.)
 
           ~ Any message in a given conference must match the subject
             of that conference. It is the SysOp's responsibility to
             make his/her users understand this. Also, the messages must
             be of acceptable language (no screaming, swearing, etc.) and
             of good grammatic (correct spelling, capital letters after
             periods, etc.).
 
             On the request from the NC, the COC director or a moderator,
             the SysOp of a node will have to remove write-privileges from
             a user to a CABiNET conference.
 
           ~ Any system continuously sending illegal messages will be
             warned by the COC. If this continues, the system will
             be marked read-only for the specified area for two weeks.
             After that, if this doesn't help, the system's feed will
             be cut off for a time considered by the NC and the COC.
 
         Joining in Cabinet:
 
           ~ Take contact to Dream World BBS and write message to sysop.
             Or write E-Mail to Esemi@utu.fi.
             (Dream World BBS, Phone: international code+358-21-811024,
              Open: 24 Hours, Speed: 9600 Baud)
 
 
A CABiNET HUB -- how to become one?
===================================
 
         Rules for a HUB: (in addition to those for a node)
 
           ~ If a hub doesn't poll its feed regularly enough or is
             quiet for more than seven days without notice; the hub of
             that area will be changed by the COC.
 
           ~ If one area needs more than one hub, then hub-to-hub polling
             may be arranged. These special cases are always decided by
             the COC.
 
         Application:
 
           ~ CABiNET HUBs are selected by the NC and COC.
 
 
QUESTIONS on CABiNET?
=====================
 
         ~ Contact:
 
        NC, Petri Kultaranta @ 112:911/370, +358-37-49007, 24H
                                (Valkeakoski, Finland)
        COC Director, Jaakko Kivela @ 112:911/170, +358-17-533621, 24H
                                (Hameenlinna, Finland)