Google Groups Home
Help | Sign in
Message from discussion New IRC Network forming
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Karl Denninger  
View profile  
 More options Nov 5 1995, 3:00 am
Newsgroups: chi.internet
From: k...@Mcs.Net (Karl Denninger)
Date: 1995/11/05
Subject: New IRC Network forming

There is a new IRC network forming -- here's the constitution, if any of the
users and operators of servers here would like to join in.

*****************************************************************
*                                                               *
*               Constitutional Document for CIRC                *
*               Commercial IRC Network Operators                *
*                       November 5, 1995                        *
*                                                               *
*****************************************************************

DRAFT NOTICE:   The following is a draft copy of the Consitution for the
                CIRC Network.  This document is subject to amendment by the
                procedures outlined herein.

Preamble:       Recognizing that Internet users desire a place to hold
                conversations in and among themselves without interferance;
                that the existing EFNet structure of power is unsuitable to
                that task and has demonstrated itself to be arbitrary and
                capricious, and finally that site administrators are
                soverign over their own infrastructure and components,
                we band together as ISPs and other system administrators
                to provide a better and easier-to-use IRC Network.

Article I:      Purpose

        CIRC is a network of commercial-AUP IRC servers interconnected for
        the purpose of providing interactive keyboard-based chat for the
        general public on the Internet.

Article II:     Governance and holding of office

        A: CIRC shall be governed by a Constitutional document, as amended
           from time to time.

        B: The server administrator(s) (declared by the "A" line) shall be
           the governing authority for a given site.   Operators shall have
           no power of vote by virtue of their operator status.

        C: Each legal entity operating server(s) shall be entitled to one
           vote.  (IE: If MCSNet operates three servers, it is entitled to
           one vote on the governing committee).  The voting member shall be
           selected by the legal entity (company, etc) from those listed in
           the "A" line.  That person shall be identified clearly in the "A"
           lines of the server.

        D: Each voting person shall be reachable by electronic mail on the
           Internet.

        E: A site may name a "proxy", who shall be an operator of the site
           in question, to vote in the absence of the names server
           administrator.

        F: There shall be no "officers" of this association, as its purpose
           is the preservation of this constitution and an effective medium
           for communications on CIRC.

Article III:    AUP

        A: CIRC shall have an AUP for use of the Commercial IRC Network,
           which shall include sanctions for violations.

        B: The following are prohibited on CIRC at all times:
                1. War, clone, or flood bots.
                2. Any bot which operates on more than one channel or
                   coordinates more than one instantiation of itself (as
                   defined by "connections" and "nicks") at a given time.
                3. Any bot running with operator privileges (with the
                   exception of the enforcement-bot defined below.)
                4. Riding netsplits and other natural and unnatural server
                   activity with the purpose of disrupting operation of a
                   channel, removing existing channel operators, or becoming
                   a channel operator.
                5. Actively causing disruptions (netsplits, server quits,
                   etc) to the user base of the CIRC network.

        C: The following server operator actions are prohibited:
                1. Use of /kill on a remote server for other than purely
                   technical reasons.  (Ie: a client program which has gone
                   insane,  is sending tens of kilobytes to a channel, and
                   the user cannot be otherwise contacted quickly is a
                   technical reason for a /kill).
                2. Use of /squit without the consent of the server
                   ADMINISTRATOR being /squit.
                3. Juping a server for other than purely technical reasons
                   (ie: a server which is being actively NUKEd and is not
                   patched to prevent this from being effective).  Any Jupe
                   placed for technical reasons must be announced
                   immediately to "circ-operat...@mcs.net" (the CIRC
                   operators mailing list) along with the reason and
                   conditions for removal.
                4. Intentional disruption of channels or servers, or
                   exploiting accidental disruptions in any fashion.

        D: No server may run code which (1) permits any person abilities of
           data inspection which are not granted to a user of ordinary
           permission on any other server, (2) is hacked to hide or
           obfuscate the identities of users of the network, (3) does not
           log and use identd returns, and (4) otherwise is "hacked" in
           violation of community standards as defined by the Jurists
           currently sitting.

        E: All servers shall have this Constitution, as amended from time
           to time, referenced to in HTTP or FTP format.  Pointing to the
           canonical source at http://www.circ.net constitutes sufficient
           notice to users of each server.

Article IV:     Complience

        The following set out minimum complience measures that are agreed to
        be undertaken by the administrative community on CIRC.  Nothing
        in this section shall prohibit stronger enforcement actions than
        called for here by any individual server administrator for their
        local server.

        A: For the purpose of enforcement, a "user" is a person without
           ANY "O" lines on any server.  An "operator" is a person who
           has "O" or "o" lines on any CIRC server, regardless of whether
           or not privileges are being used at the point in time under
           consideration.

        B: Allegation of violations by a user of Articles III-B2, B3, and
           B4 shall be deemed "misdemeanor" violations when proven.
           1. A user violating these terms shall be warned *once* by an
              operator via email (with copies to circ-operat...@mcs.net)
              and pointed to the Constitution.
           2. Second violations shall cause the user to be "Klined" at the
              originating server for a period of the server operator's
              choosing, but not less than 24 hours.
           3. A third violation shall cause the user to be entered in the
              "kill bot" cache for a period of 7 days.
           4. Subsequent violations shall double the disabled period for
              each subsequent violation.

        C: Allegations of all other violations, and any violation of the AUP
           by an operator, shall be deemed "felony" violations when proven.
           1. Any user violating Articles III-B1 or B5 shall be placed
              on the "kill bot" cache for 48 hours.
           2. Subsequent offenses will double the time quarrantined for
              each offense (4 days, then 8 days, etc).
           3. Any *operator* violating any of Articles III-C shall have
              the penalty applied to their operator privileges by the server
              administration, with the exception that after three offenses
              the Operator shall be permanently removed.

        D: Should any server administrator refuse to comply at a minimum level
           with these enforcement measures their server shall be removed.

        E: Any server refusing to delink a server for violation of IV-D
           shall itself be removed or permanently juped.

Article V:      Adjudication

        A: Each server administrator shall be elegible for random lottery
           to serve on a tribunal to adjudicate disputes and judge evidence
           of procedings brought under Articles III and IV.  This shall be
           known as the "CIRC Jury".

        B: The term of jury service shall be one month.

        C: The jurists shall be maintained on a list at "circ-j...@mcs.net".
           Disputes shall be submitted to "circ-disp...@mcs.net", which
           shall reflect to the server operator list and the jury list.

        D: The names and network addresses of the current jurists shall be
           retrievable from majordomo at the mailing list processing site at
           all times.

        E: Conviction for violations under Articles III and IV shall be by
           vote of all jurists; all responding jurists shall be required to
           agree for conviction.  Convictions for offenses shall be public
           knowledge and be posted during the term of the sentence as
           defined above.

        F: All judgements by the jurists are final.

        G: All server admins must have "jury duty" in a given round before
           any admin may sit twice, with the same holding true for each
           subsequent round of jury service.

        H: The number of jurists shall number 7 once there are at least
           seven servers linked.  Until that time the number of jurists shall
           equal the number of administrators, and no lottery is necessary.

        I: The jurists are allowed to request evidence sufficient to draw
           conclusions about the charge(s) being made.

Article VI:     Linkage policy

        It is the general policy of CIRC to link servers where the
        following conditions exist:

        A: There is a significant existing or projected user base for the
           server which is to be linked.

        B: The server is able to technically support the userbase and load
           intended to exist, and sufficient bandwidth exists between it and
           its uplinks to permit stable and efficient operation.

        C: The server admins are willing to abide by the Constitution for
           CIRC as amended from time to time.

        D: The server is connected by at least a T1 connection to the
           Internet.

        E: Hubbing and other linkage disputes may be submitted to the
           sitting jurists - unanamous consent is required for a dispute
           to be resolved by these jurists.

        F: All servers linked to CIRC shall be maintained in a file
           retrievable from the circ-operators mailing list.  These entires
           shall name the legal entity responsible for the operation of the
           server, email contact for requests and inquiries, physical
           location and address, and telephone number for the NOC (network
           operations center) responsible for the physical machine on which
           the server operates.

Article VII:    Amendment of Constitution

        This Constitutional document may be amended by vote of the
        administrators of the servers connected to CIRC as follows:

        A: The proposed amendment must be submitted to
           "circ-operat...@mcs.net" and clearly noted as a Constitutional
           Amendment.

        B: At least one calendar week of discussion shall take place.

        C: An Administrator vote shall then be taken.  The requirements for
           passage of amendments are as follows:

           1. Until CIRC reaches 20 servers operating: 100% assent.
           2. From 20 - 50 servers operating: 90% assent.
           3. 50+ servers operating: 75% assent.

        D: The number of ballots "outstanding" which must be cast in assent
           for a Constitutional change shall be determined from the total
           number of servers defined as linked to CIRC (as in Article VI-F).

Signatories:    Server Administrators in Complience

We, the undersigned, pledge to uphold this Constitution and abide its terms
during the period we are CIRC members and operate servers on this IRC
Network.

Signed                  Email Address                   Server:port
Karl S. Denninger       k...@mcs.net                    irc.mcs.net:3333

--
--
Karl Denninger (k...@MCS.Net)| MCSNet - The Finest Internet Connectivity
Modem: [+1 312 248-0900]     | (shell, PPP, SLIP, leased) in Chicagoland
Voice: [+1 312 803-MCS1]     | 7 Chicagoland POPs, ISDN, 28.8, much more
Fax: [+1 312 248-9865]       | Email to "i...@mcs.net" WWW: http://www.mcs.net
ISDN - Get it here TODAY!    | Home of Chicago's *Three STAR A* Clarinet feed!


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google