• Policy 4 Ingles (3/3)

    From Enric Lleal Serra@2:343/107.1 to All on Thu Jul 19 14:25:00 2007
    Hola All!

    9.4 Problems with Other Coordinators

    Complaints concerning annoying behavior on the part of any coordinator are treated as in section 9.2 and should be filed with the next level of coordi- nator. For example, if you feel that your Regional Coordinator is guilty of annoying behavior (as opposed to a failure to perform duties as a coordina- tor) you should file your complaint with the Zone Coordinator.

    Complaints concerning the performance of a coordinator in carrying out the duties mandated by policy are accepted only from the level immediately below. For example, complaints concerning the performance of Regional Coordinators would be accepted from Network Coordinators and independents in that region. Such complaints should be addressed to the Zone Coordinator after an appro- priate attempt to work them out by direct communications.


    9.5 Appeal Process

    A decision made by a coordinator may be appealed to the next level. Appeals must be made within two weeks of the decision which is being appealed. All appeals must follow the chain of command; if levels are skipped the appeal
    will be dismissed out of hand.

    An appeal will not result in a full investigation, but will be based upon the documentation supplied by the parties at the lower level. For example, an appeal of a Network Coordinator's decision will be decided by the Regional Coordinator based upon information provided by the coordinator and the sysop involved; the Regional Coordinator is not expected to make an independent attempt to gather information.

    The appeal structure is as follows:

    Network Coordinator decisions may be appealed to the appropriate Region-
    al Coordinator.

    Regional Coordinator decisions may be appealed to the appropriate Zone
    Coordinator. At this point, the Zone Coordinator will make a decision
    and communicate it to the Regional Coordinators in that zone. This
    decision may be reversed by a majority vote of the Regional Coordina-
    tors.

    Zone Coordinator decisions may be appealed to the International Coordi-
    nator. The International Coordinator will make a decision and communi-
    cate it to the Zone Coordinator Council, which may reverse it by majori-
    ty vote.

    If your problem is with a Zone Coordinator per se, that is, a Zone Coordina- tor has committed a Policy violation against you, your complaint should be filed with the International Coordinator, who will make a decision and submit it to the Zone Coordinator Council for possible reversal, as described above.


    9.6 Statute of Limitations

    A complaint may not be filed more than 60 days after the date of discovery of the source of the infraction, either by admission or technical evidence. Complaints may not be filed more than 120 days after the incident unless they involve explicitly illegal behavior.


    9.7 Right to a Speedy Decision

    A coordinator is required to render a final decision and notify the parties involved within 30 days of the receipt of the complaint or appeal.


    9.8 Return to Original Network

    Once a policy dispute is resolved, any nodes reinstated on appeal are re- turned to the local network or region to which they geographically or techni- cally belong.


    9.9 Echomail

    Echomail is an important and powerful force in FidoNet. For the purposes of Policy Disputes, echomail is simply a different flavor of netmail, and is therefore covered by Policy. By its nature, echomail places unique technical and social demands on the net over and above those covered by this version of Policy. In recognition of this, an echomail policy which extends (and does
    not contradict) general Policy, maintained by the Echomail Coordinators, and ratified by a process similar to that of this document, is recognized by the FidoNet Coordinators as a valid structure for dispute resolution on matters pertaining to echomail. At some future date the echomail policy document may be merged with this one.


    9.10 Case Histories

    Most of FidoNet Policy is interpretive in nature. No one can see what is to come in our rapidly changing environment. Policy itself is only a part of
    what is used as the ground rules for mediating disputes -- as or more impor- tant are the precedents.

    In order to accommodate this process, case histories may be added to or
    removed from this document by the International Coordinator, with such a revision subject to reversal by the Zone Coordinator Council. Should Policy
    be amended in such a way to invalidate a precedent, Policy supersedes said precedent. (A carefully prepared amendment would address this by removing
    the precedent reference as a part of the amendment.)

    Although a case may be removed, the text of a case history may not be modi- fied by any mechanism. Case history is written close to the time of the decision, by those involved with it. Amending the text of a case history is the same as revising history, something quite inappropriate in an organiza- tion dedicated to moving information.



    10 Appendices

    10.1 General

    The Appendices of this document are exceptions to the normal ratification process. Section 10.2 can be changed by the appropriate Zone Coordinator,
    and section 10.3 may be modified by the International Coordinator (see
    Section 9.10).


    10.2 Timing of Zone Mail Hour

    Zone Mail Hour is observed each day, including weekends and holidays. The
    time is based upon Universal Coordinated Time (UTC), also known as Greenwich Mean time (GMT). In areas which observe Daylight Savings Time during part of the year, the local time of zone mail hour will change because FidoNet does
    not observe Daylight Savings Time. The exact timing of Zone Mail Hour is set for each zone by the Zone Coordinator.

    In FidoNet Zone 1, Zone Mail Hour is observed from 0900 to 1000 UTC. In each of the time zones, this is:

    Eastern Standard Time 4 AM to 5 AM
    Central Standard Time 3 AM to 4 AM
    Mountain Standard Time 2 AM to 3 AM
    Pacific Standard Time 1 AM to 2 AM
    Hawaii Standard Time 11 PM to Midnight

    In FidoNet Zone 2, Zone Mail Hour is observed from 0230 to 0330 UTC.

    In Fidonet Zone 3, Zone Mail Hour is observed from 1800 to 1900 UTC. In each of the time Zones involved this is:


    GMT +12 Zone 6:00 AM to 7:00 AM
    (New Zealand)

    GMT +10 Zone 4:00 AM to 5:00 AM
    (East Australia)
    (Papua New Guinea)
    (Micronesia)

    GMT +9.5 Zone 3:30 AM to 4:30 AM
    (Central Australia)

    GMT +9 Zone 3:00 AM to 4:00 AM
    (Japan)
    (Korea)
    (Eastern Indonesia)

    GMT +8 Zone 2:00 AM to 3:00 AM
    (Hong Kong)
    (Taiwan)
    (Central Indonesia)
    (Philippines)
    (Western Australia)

    GMT +7 Zone 1:00 AM to 2:00 AM
    (Malaysia)
    (Singapore)
    (Thailand)
    (Western Indonesia)


    10.3 Case Histories


    Case histories of past disputes are instructive to show general procedures
    and methods. Any decision may be included in this document by a majority
    vote of either the Zone Coordinator Council or the Regional Coordinators.

    Policy4 significantly changes the functions of the Zone and International Coordinators. In the following cases which were decided using Policy3, substitute "Zone Coordinator" for all occurrences of "International Coordina- tor(*)".


    10.3.1 The Case of the Crooked Node

    A sysop of a local node was using network mail to engage in unethical busi- ness practices. The Network Coordinator became very annoyed at this, and dropped the local from the nodelist.

    The local appealed to the Regional Coordinator for assignment as an indepen- dent node. The Regional Coordinator, after checking with the Network Coordi- nator, decided that the Network Coordinator was right to be annoyed. Inde- pendent status was denied.

    The International Coordinator(*) did not intervene.


    10.3.2 The Case of the Hacker Mailer

    A sysop of a local node made use of file attaches for extra users to mail himself the USER.BBS file from several local boards. The sysops of these boards felt annoyed at this, and appealed to their Network Coordinator, who agreed and dropped the offending node from the nodelist.

    The Regional Coordinator was not consulted.

    The International Coordinator(*) did not intervene.


    10.3.3 The Case of the Bothered Barker

    A local node became annoyed with the Network Coordinator for failing to
    provide services. Repeated complaints to the Network Coordinator did not satisfy him, so he appealed to the International Coordinator(*).

    The International Coordinator(*) dismissed the complaint because the Regional Coordinator had not been consulted.

    The local node submitted the complaint to his Regional Coordinator, who investigated the case and discovered that there was some justice to the complaint. He advised and assisted the Network Coordinator in configuring
    his system to provide an improved level of service to the local nodes.

    The Regional Coordinator also decided that the local node was being too
    easily annoyed, in that he was expecting services not normally required of a Network Coordinator. The local node was informed as to the true duties of a Network Coordinator, and was advised to lower his expectations.


    10.3.4 The Case of the Busy Beaver

    A local node which was operated by a retail establishment was engaged in
    making "bombing runs" to mail advertisements over FidoNet. The Network Coordinator felt annoyed and handling the outgoing traffic for a commercial operation, and asked the local node to leave the network.

    The local node applied to the Regional Coordinator, and was granted status as an independent node in the region.


    10.3.5 The Mark of the Devil

    A local sysop whose board was used in conjunction with voodoo rites, hacking, phreaking, and obscene material applied to a Network Coordinator for a node number. The Network Coordinator deemed that this board was exceptionally annoying, and denied the request.

    The Regional Coordinator was not consulted.

    The International Coordinator(*), on seeing that the Regional Coordinator had not been consulted, dismissed the case out of hand. No further appeals were made.


    10.3.6 The Case of the Sysop Twit

    A patron of various local nodes had been roundly recognized by all sysops as
    a twit. The user obtained his own system, became a sysop, and applied for a node number. The Network Coordinator denied the request. No appeals were made.


    10.3.7 The Case of the Echomail Junkie

    A local node became enamored with echomail and joined several conferences, routing mail through his network. He then started an echomail conference of his own and began relaying echomail between several systems, again routing it all through the network.

    His Network Coordinator observed that network performance was becoming seriously impaired. The offending node was told to hold it down. A compro- mise was reached whereby much of the echomail traffic was no longer routed through the network, and routed echomail was limited to twenty messages per night. No appeals were made.


    10.3.8 The Case of the Bouncing Board

    A local user decided to establish a node to promote a worthy charity. The machine being used was also used for various other activities during the day, and the sysop was often called away. His coworkers would often forget to
    bring the board up at the end of the day while he was away, so the node was often down for extended periods. The Network Coordinator, finding the node unable to receive mail, would mark it down. The sysop would return, restart the board, and ask to be reinstated.

    The Network Coordinator eventually decided that the sysop was not able to maintain a reliable system, and removed him from the nodelist completely. Subsequent requests for a node number from the same sysop were turned down.
    No appeals were made.


    10.5 Credits, acknowledgments, etc.

    Fido and FidoNet are registered trademarks of Fido Software, Inc.




    Index

    -1/-1, 2.3
    Additional mail events in local network 2.1.8
    Address in message to request node 2.2
    Administrative Region 6.1
    Advantages to network membership 2.2
    Alteration of mail 2.1.5
    Answering machine 2.3
    Announcement of voting results 8.2
    Annoying behavior 1.3.5, 1.4.8, 2.1.1, 2.1.2, 2.1.4, 2.1.6, 2.1.7, 2.1.8,
    2.1.11, 2.3, 4.2, 4.3, 5.2, 9, 10
    Appeal chain 9.5
    Appointment of coordinators 1.2.3, 1.2.4, 5.7, 6.1
    Availability of NodeList 1.3.4
    Balloting Period 8.4
    Bombing run 4.2
    BossNode 1.2.1.2
    Boundaries 1.3.2
    Business use of FidoNet 1.3.6
    Calling areas 1.3.2, 5.6, 5.7
    Case histories 9.10, 10.3
    Chain of command 1.2.8
    Changing node numbers 4.3, 5.2
    Checks and balances 1.2.8
    Commercial messages 1.3.6, 2.1.4, 4.2
    Complaint (policy) 2.1.6.1, 9
    Contributions to FidoNews 1.3.1
    Current nodelist 2.1.11
    Daylight Savings Time 2.1.14
    Difference file 4.5, 5.8, 8.2
    Disclosing private mail 2.1.6
    Discussion period 8.2
    Disputes 9
    Distribution of ballots 8.2
    Down 2.3, 4.4, 5.5
    Downloading by users 3.6, 4.5, 5.8
    EchoMail 4.2, 9.9
    Effective date (policy change) 8.2
    Election of coordinators 1.2.5, 6.2, 7.2
    Eligibility to vote 8.3
    Encryption 2.1.4, 4.2
    Exceptions 5.6
    Excessively annoying behavior 1.2.1.1, 1.3.5, 2.1.1, 2.1.2, 2.1.4, 2.1.6,
    2.1.7, 2.1.8, 2.1.11, 2.3, 4.2, 4.3, 5.2, 9, 10
    Exclusivity of Zone Mail Hour 2.1.8
    Excommunication 2.1.12, 4.3, 5.2, 9
    Exemptions, node location 1.3.2, 5.6
    Familiarity with policy 2.1.2, 2.2
    FidoNews 1.3.1
    availability 3.1, 4.5, 5.8
    FTSC 2.1.8, 2.1.9, 2.4
    Gateway 2.1.3
    Geography 1.3.2, 5.6
    Glue 4.5
    Guarantee of mail delivery 1.3.6
    Hats 3.4
    Host-routed mail 4.2
    How to obtain a node number 2.2
    Hub 1.2.3.1, 4.4
    Illegal behavior 2.1.1, 9.6
    Illegal mail 4.2
    Impeachment 8.7
    In-transit mail 2.1.6.1
    Independent node 4.2, 5.2
    Inter-zonal questions 1.2.6
    International Coordinator 1.4.1, 1.4.9, 7
    Justification of private nodes 2.1.9
    Language 1.0
    Levels of FidoNet 1.2, 1.4
    Local calling areas 1.3.2
    Local policies 1.2, 3.3
    Mail 1.2.3, 4.2
    Mailer 2.2
    Majority 8.6, 8.7.2
    Member of area administrated 3.5
    Modem 2.2
    Modification of mail 2.1.5
    National Mail Hour see Zone Mail Hour
    Network
    advantages 2.2
    boundaries 1.3.2, 5.4
    definition 1.2.3
    forming 2.4, 5.3
    hub 1.2.3.1, 4.4
    numbers 2.2, 5.4
    Network Coordinator 1.2.3
    procedures 4
    replacement 5.7, 9.3
    Network Mail Hour see Zone Mail Hour
    New sysops 2.1.2, 3.6
    Node numbers 4.3, 5.2
    obtaining 2.2
    Nodelist 1.3.4, 2.2, 4.4, 5.5
    availability 3.1, 4.5, 5.8
    changes 4.4, 5.2
    current 2.1.11
    definition 1.3.4
    format 10.3
    official 1.3.4
    Nodes
    definition 1.2.1
    down 2.3
    Observing mail events 2.1.8, 2.1.10
    Obtaining a node number 2.2
    Offensive messages 2.1.5
    Orders (commercial) 1.3.6
    Partial nodelist 1.3.4
    Pirated software 2.1.1
    Point of origin 2.1.3
    Points 1.2.1.2, 2.1.3
    Policy 3.1, 3.3, 4.5, 5.8
    changing 8
    complaint 2.1.6.1, 9
    familiarity with 2.1.2, 2.2
    local 1.2, 3.3
    Precedent 3.7, 9.10, 10.3
    Private messsages 2.1.6
    Private network 1.2.1.2
    Private nodes 2.1.9
    Problem resolution 9
    Protocol 2.1.8
    Public BBS 3.6
    Ratification 7.1
    Redundant nodes 2.1.9
    Referendum 1.2.7, 8
    Regional Coordinator 1.2.4
    procedures 5
    replacement 6.1, 9.4
    Regions 1.2.4
    Replacement of coordinators 1.2.8
    Replacing services 3.4
    Requirements to be in NodeList 1.3.4, 2.1.2, 2.2
    Resignation of ZC 8.7.4
    Resolution of disputes 9
    Results Announcement 8.2
    Review of decisions 3.7
    Review of routed traffic 2.1.4
    Routing 2.1.4 - 2.1.7, 4.2
    Routing Hub 1.2.3.1, 4.4
    Rules 9.1
    Speedy decision 9.7
    Standards (FTSC) 2.1.8, 2.4
    Statute of limitations 9.6
    Submissions to FidoNews 1.3.1
    Sysop procedures 2
    System operator (sysop) 1.2.1
    Three-tiered networks 1.2.3.1
    Time limit on decision 9.7
    Timing of Zone Mail Hour 2.1.13, 2.1.14, 10.2
    Top-down 1.4.9
    Tradition 3.7
    Trivial network 5.3
    Unattended systems 2.3
    Updates to nodelist 3.2
    User 1.2.1.1
    User access during ZMH 2.1.8
    Vacation 2.3
    Voice telephone number 2.2
    Vote 8
    eligibility 8.3, 8.7.2
    ZMH see Zone Mail Hour
    Zone Coordinator 1.2.5, 6
    election 6.2
    impeachment 8.7
    procedures 6
    removal 6.2
    resignation during impeachment 8.7.4
    Zone Coordinator Council 1.2.6, 7.1
    Zone Mail Hour 1.3.3, 2.1.8
    timing 2.1.13, 2.1.14, 10.2
    Zones 1.2.5, 1.3.2

    -
    A reveure!!
    Enric

    --- FMail/Win32 1.60
    * Origin: El camino mas corto entre A y B es la teleportacion. (2:343/107.1)
  • From Felipe T. Dorado@2:345/702 to Enric Lleal Serra on Fri Aug 10 13:09:12 2001
    Hola Enric :)

    Jueves 19 Julio 2007 14:25, Enric Lleal Serra escribió a All:


    9.9 Echomail

    Echomail is an important and powerful force in FidoNet. For the purposes of Policy Disputes, echomail is simply a different flavor of netmail, and is therefore covered by Policy. By its nature, echomail places unique technical and social demands on the net over and above those covered by this version of Policy. In recognition of this, an echomail policy which extends (and does not contradict) general Policy, maintained by the Echomail Coordinators, and ratified by a process similar to that of this document, is recognized by the FidoNet Coordinators as a valid structure for dispute resolution on matters pertaining to echomail. At some future date the echomail policy document may be merged with this one.


    ¿Tienes por favor una copia de la Echomail vigente en Español?

    ¿La pones por aquí como has puesto la Policy, por partes o fascículos? Please.


    Felipe :)

    --- GoldED+/LNX 1.1.5
    * Origin: El Zoco BBS, COrdoba, Espa-na, UE, Tierra, Sol, VL. (2:3 (2:345/702)
  • From Enric Lleal Serra@2:343/107.1 to Felipe T. Dorado on Tue Aug 28 10:07:10 2007
    ­Hola Felipe!

    El Viernes 10 Agosto 2001 a las 13:09, Felipe T. Dorado escribi¢ a Enric Lleal Serra:

    ¿Tienes por favor una copia de la Echomail vigente en Español?

    Pues no, tengo la 1 en ingl‚s, y varias versiones/propuestas de la 2, pero todas en ingl‚s... :-(


    -
    A reveure!!
    Enric

    --- FMail/Win32 1.60
    * Origin: This is FidoNet! FIDOers, tonight we'll write in Hell! (2:343/107.1)