Fidonet Region 18 Policy
Version 1.06
2 July 1993

This policy was ratified by a vote of the sysops of Region 18, and is 
the current Fidonet Region 18 policy until superceded. There are no 
differences between this version and 1.05 except this statement.

1. Introduction

This document is intended to describe the various policies and 
procedures which are specific to Fidonet operations in Zone 1, Region 
18. It is an extension of the overall Fidonet policy containing 
information related to the individual procedures and methods of Region 
18, and should not be considered a replacement for that policy.

2. Nodelist Entries

FidoNet association is indicated by inclusion in a weekly listing of 
computer systems. It is the responsibility of the individual system 
operator to request the appropriate listing from the local Net 
Coordinator. It is the responsibility of the local Net Coordinator to 
determine that the requested listing is proper and include the listing 
in the nodelist segment submitted for inclusion in the FidoNet nodelist.

Any system operator (sysop) maintaining a FTS-0001 compatible mailer 
available to establish a mail session with all FidoNet Nodes during Zone 
Mail Hour and agreeing to abide by Fidonet policies is entitled to a 
FidoNet nodelist listing. This listing may be removed without request 
only through the system failing to maintain minimum technical compliance 
or as the result of a formal policy complaint. Technical compliance 
shall be the decision of the local Net Coordinator, subject to appeal.

The sysop listed in the nodelist has sole responsibility for maintaining 
the compliance of that system with both technical standards and Fidonet 
policies. If more than one person is listed as sysop, they shall be 
considered to be a single entity for the purposes of this policy. The 
actions of one are considered the actions of all and official 
communication to or from one shall be considered communication to or 
from all. The penalties of any policy complaint arising from the actions 
of one will be assessed against all.

2.1 Extended Operating Hours

Any system maintaining a FTS-0001 compatible mailer available for a mail 
session with all FidoNet nodes any time the phone is answered is 
entitled to be listed for such operation. A system displaying this flag 
(CM) must be capable of a reasonable expectation of a minimum of a 
FTS-0001 mail session with any FidoNet caller at any time the phone is 
answered.

2.2 Mail Only

Any system not operating a public BBS may be listed with a flag to 
indicate this status in the Nodelist (MO).

2.3 Limited Access

Any system may restrict the ability of non-FidoNet systems to establish 
a mail session at the discretion of the operator. It is requested that 
any system operating in this manner request the appropriate LO flag 
(Listed Only) from the local Net Coordinator. Mail sessions with any 
FidoNet system may not be restricted without notification to the 
restricted system.

2.4 Multiple Node Listings

A system may be granted multiple listings in the FidoNet nodelist if:

2.4.1 Mail Sessions with the two listed numbers access separate message 
databases, or;

2.4.2 The separate listings show connection capabilities that are 
incompatible at any level, such as ISDN equipment and Asyncronous 
modems, or;

2.4.3 The number of inbound mail calls is greater than a single 
telephone line can handle. This decision shall be made by the local Net 
Coordinator with the agreement of the Regional coordinator.

2.4.4 Administrative address prefixed by 'Region', 'Host' or 'Hub' are 
permitted. Any listing prefixed by 'Hub' must be a redundant listing for 
a node within its following group. A 'Host' listing should not be 
duplicated by a 'Hub' listing.

Administrative addresses shall not be used as a primary address.

2.5 Hold Nodes

Nodes may be marked as Hold in the Nodelist to indicate the system is 
unavailable for a period of time. No node shall be marked as Hold for 
longer than four weeks. This flag is to accommodate unusual situations 
and FTN mailers route the addressed to a Hold listing to the local Net 
Coordinator.

2.6 Down Nodes

Systems may be marked as Down by the local Net Coordinator as a 
preliminary step to removal from the nodelist for either technical 
non-compliance or the result of a Policy Complaint.  As technical 
non-compliance may restrict the ability of the local Net Coordinator to 
communicate with the system, this may be the only notice provided for 
removal from the nodelist. No system shall be listed as down for longer 
than two weeks.

2.7 Private Nodes

A Private node number will be issued only when it can be shown to 
represent a benefit to the node's local net, Region 18 or to Fidonet as 
a whole. The justification for a Private node listing shall be provided 
in writing to the local Net Coordinator and filed with the Regional 
Coordinator for approval. Such approval should not be considered 
permanent, and may be reviewed and re-evaluated by the Net Coordinator 
or Regional Coordinator at a later time.

2.8 Modem Capability Flags

Modem capabilities are indicated with a series of flags approved by the 
International Coordinator and listed at the end of the FidoNet Nodelist. 
Additional modem capability flags should not be used. Flags which 
indicate capability shown by other flags in the listing should not be 
used.

2.9 User Flags

The user flag (Uxxx...) was originally proposed as a means of fostering 
development of Fidonet technology by identifying systems with common 
characteristics or participation for the purposes of enhancing the basic 
Fidonet goal of communication. Experimentation with new integrated 
technologies is encouraged. These are never used for advertisement or 
for announcing non-Fidonet accesses of particular BBS's, but are for the 
advancement of Fidonet as a whole. They should never duplicate 
information that could otherwise be found in the nodelist (such as NC 
status).

By standardizing certain User Flags, it may be possible for software 
developers to put these flags to beneficial use for all Fidonet members. 
For this reason, all new user flag types not authorized by the Fidonet 
Technical Standards Committee must be approved by the Regional 
Coordinator.

3. Freedom of Operation

3.1 FidoNet exists for the exchange of information between computer 
systems. No one may limit the exchange of information between nodes, 
except where the exchange is:

3.1.1 Causing the information to be duplicated at other nodes.

3.1.1.2 The coordinator structure can request that automated links be 
cut to eliminate the duplication. Nodes must honor the request.

3.1.2 Routed through other nodes.

3.1.2.1 Any non-administrative node has total control over any and all 
information routed through the node.

3.1.2.2 Administrative nodes must provide the routing defined in the 
description of their duties.  No administrative node is required to 
provide routing for information that is illegal to transfer, or that is 
deliberately sent in a manner the routing node is unable to review.

3.1.3 Covered by a voluntary agreement which limits redistribution of 
the information.

3.2 With automated transfer systems the originator of information shall 
have control over where information is sent. The Moderator of an 
EchoMail area is considered the originator of the Echo. The 
administrator of a file distribution system is considered the originator 
of the distribution system. Requests to modify automated routing of 
information by the originator must be followed.

False claims to be the originator of information in an effort to control 
the distribution of information shall be considered excessively 
annoying.

4. Net Service Areas

A three level definition of Net Service Areas will be used.

The Primary Service Area for a net will be the local (toll free) dialing 
area central to the net. This central area is defined as that telephone 
exchange area within the net whose local calling area includes the 
largest number of nodes. No other net will be formed or expanded to 
provide service to this area.

The Secondary Service Area for a net includes the areas which may have 
toll free access to the central area of the net by paying an extra 
monthly fee to the local phone company (Metro Calling Area) and the area 
in which a node is local to a hub in the Primary Service Area of the 
net. These areas may form nets.

If a second net forms or exists so that its local calling area overlaps 
the Primary Service Area of another net, the older of the nets will 
provide service to that area unless an agreement between the NCs of the 
two nets concludes cost effective service would be best implemented 
through other assignments. The Network Coordinators of the two nets will 
form a working agreement based primarily on cost effective service and 
secondly on logical boundaries. All local telephone exchanges between 
the nets should be defined. The process will be repeated with the 
formation of each additional net. This working agreement will be 
submitted to the Regional Coordinator for approval.

The Tertiary Service Area is a temporary assignment of an expanded 
Service Area to provide service to adjoining areas not covered by an 
existing net. All local telephone exchanges between nets should be 
defined to give Network Coordinators guidance on the proper handling of 
applications for Fidonet Membership. These areas should be encouraged to 
form independent nets.

5. Formation of new nets

Any group of nodes in a local calling area outside the primary service 
area of any existing net may form a new Net if:

5.1 The majority of nodes listed in the Fidonet nodelist in that area 
agree to the formation of the net. This majority must consist of a 
minimum of four (4) nodes.

5.2 The nodes requesting net status select a Net Coordinator who:

5.2.1 Submits a nodelist segment to the Regional Coordinator. This 
segment should be without any error that would prohibit its inclusion in 
the Fidonet nodelist.

5.2.2 Submits a netmail message to the Regional Coordinator describing 
the area to be provided service by the new net. This should be of 
sufficient detail to allow the Regional Coordinator to discuss the new 
service area with the Net Coordinators of existing networks and should 
include a list of all Fidonet nodes in the affected area.  Copies must 
be sent to the Net Coordinator of all nets whose nodes are involved.

5.2.3 Submit a statement of the procedure for future Net Coordinator 
selection to the Regional Coordinator.

5.3 All nodes in the Primary Service area of a new net and outside the 
Primary Service area of an existing net shall be assigned to the new 
net.

5.4 Additional areas may be temporarily assigned to the new net by the 
Regional Coordinator if the RC determines the areas can be provided more 
cost effective service by the new net.

5.5 Formation of a new net may be postponed if a majority of the 
applicant nodes have been members of Fidonet for less than one month.

6. Merging of Existing nets

As the reason for local nets is cost effective mail routing, changes in 
the telephone company billing topography or development of areas 
previously unpopulated by Fidonet nodes may make merging of existing 
local nets advantageous to the whole of Fidonet.

If one net is entirely within the Primary Service Area of another 
existing net, or if two nets are entirely local to a common area with a 
significant number of established nodes, the Regional Coordinator may 
determine that cost effective service is best provided by the merging of 
the local nets.

Mergers may also be requested by the Net Coordinators of adjacent nets 
to enhance the efficiency of communication. Such merged nets must be 
consistent with the definitions under Net Service Areas (section 4) and 
must not create new Tertiary Service Areas as defined in that section.

The Regional Coordinator shall call for the two nets to be merged by:

6.1 Notifying the Net Coordinators of the nets involved of his intention 
to merge the nets and requesting comments from them. The NCs will be 
given a minimum of two weeks to submit comments on or objections to the 
planned merger.

6.2 Requesting that the nets select a Net Coordinator by a procedure 
agreed to by the membership of the nets. If there is no agreement 
reached on a method, the RC may request that the Net Coordinator be 
selected by the procedures established by one of the nets, with the 
membership of both nets participating. The new Net Coordinator shall 
follow the procedures for establishing a new network.

6.3 Permitting any removed net nodelist segment to remain in the 
nodelist for a minimum of two weeks after the inclusion of the new net 
segment.

7. Dissolution of Trivial Nets

Any local net with less than three members may be considered trivial by 
the Regional Coordinator and the listing ended by:

7.1 Requesting an adjoining net to provide service to the area, or;

7.2 Placing the nodes in the nodelist as Regional Independents.

7.3 Permitting any removed net nodelist segment to remain in the 
nodelist for a minimum of two weeks after inclusion of the new net 
segment.

8. Local Net Policies

In order to facilitate regional coordination, copies of all current 
local net policies must be filed with the Regional Coordinator.

9. Installation of Net Coordinators

The Regional Coordinator will recognize as Net Coordinator that member 
of a net selected by procedure defined in the net's local policy, if 
such a policy exists. If the net does not have a local policy, the 
Regional Coordinator will follow the wishes of the majority of the net's 
members. In the absence of a local net policy on file with the Regional 
Coordinator, or in the event of a challenge to the installation of a new 
Net Coordinator, it is the responsibility of that new Net Coordinator to 
demonstrate to the Regional Coordinator that his selection represents a 
majority decision of the net before such changes will be accepted for 
placement in the nodelist.

As the result of Policy Complaint or determination of non- performance, 
the Regional Coordinator may remove a Net Coordinator and appoint an 
interim coordinator until local policy can be followed to select a 
replacement.

10. Independent Nodes

One responsibility of the Regional Coordinator is to serve as a "net" 
coordinator for all nodes in the region who are not members of local 
nets. In most instances, these nodes represent systems that are 
geographically isolated from each other and from any existing net.

Requests for independent node numbers must be made to the Regional 
Coordinator. Such assignments are not automatically granted. The 
Regional Coordinator may assign geographically isolated nodes to the 
nearest local net as an alternative to a regional independent listing 
with the consent of the Net Coordinator of that net.

Sysops who receive large volumes of inbound netmail may request 
assignment of an independent node number even if they are within the 
boundaries of an existing local net. A Net Coordinator may request that 
a node in his net apply for a regional independent node number if the 
volume of inbound host-routed netmail to that node becomes a burden. 
Assignment of independent node numbers under these circumstances will be 
granted at the discretion of the Regional Coordinator.

11. Regional Coordinator Election

11.1 Qualifications and Terms

The Regional Coordinator serves a term of one year and may serve any 
number of consecutive terms. Any sysop listed in the Region 18 segment 
of the Fidonet Nodelist at the time nominations are opened is eligible 
to run. A simple majority (50% + 1) of votes cast is required to elect a 
Regional Coordinator. In the event that no candidate received a majority 
of votes, a run off election will be held between the two candidates 
with the greatest number of votes.

11.2 Nominations

Nominations may be made either in the R18ELECT echo or by netmail to the 
election coordinator. Any netmail nominations received by the election 
coordinator will be cross-posted by him into the R18ELECT echo. Any 
sysop listed in the Region 18 segment of the Fidonet nodelist may 
nominate any other eligible sysop for the position of Regional 
Coordinator.  Nominations must be seconded by a sysop from a net other 
than that of the person placing the nomination. For the purposes of this 
section, all regional independents will be considered as members of a 
single "net".

Nominees must announce their consent to serve in order to be considered 
candidates in the election, and are encouraged to be available in the 
R18ELECT echo for discussion during the election process.

A minimum of two weeks will be allotted for the nominating process.

11.3 Election Coordinator

At the start of the election process, the Regional Coordinator will 
appoint a non-candidate sysop as Election Coordinator. This sysop will 
have several responsibilities:

11.3.1 Collecting nominations, seconds and statements of consent to 
serve from the R18ELECT echo and finalizing the election slate.

11.3.2 Posting the slate of candidates and the voting format 
instructions in the R18ELECT echo at the close of nominations.

11.3.3 Submitting the slate of candidates and the voting format 
instructions to the Regional Coordinator for distribution via netmail to 
all Net Coordinators.

11.3.4 Collecting and tabulating votes submitted.

11.3.5 Notifying the Regional Coordinator of the election results and 
posting the election results in the R18ELECT echo.

11.4 Discussion Period

Following the close of nominations and presentation of the slate of 
candidates, a minimum of two weeks will be allotted for discussion 
before voting begins.

11.5 Voting Procedures

11.5.1 Net Coordinators in each net will distribute the slate of 
candidates, voting instructions and voting schedule to all members of 
their nets.

11.5.2 Votes must be cast by the node sysops via netmail to the Election 
Coordinator. Due to changing technology, the exact format and mechanism 
of placing these votes will be determined by the Election Coordinator at 
the time of each election. Once a vote has been received and validated, 
it may not be changed.

11.5.3 The Election Coordinator will announce the final counts within 
seven days of the close of voting.

11.5.4 Challenges to the accuracy or completeness of the announced 
results must be placed via netmail to the Election Coordinator within 
seven days of the announcement of the results.

11.6 Installation of New Regional Coordinator

The newly elected Regional Coordinator will be installed in the nodelist 
as soon as the transfer of control files and other necessary information 
can be coordinated between the incoming and outgoing Coordinators, but 
not later than two weeks from the announcement of final election 
results.

11.7 Eligibility to Vote

Elections are held on a one sysop, one vote, basis. All sysops listed in 
the Region 18 segment of the Fidonet Nodelist at the close of 
nominations are eligible to vote. No more than one vote may be submitted 
by the same individual or the same address. If a vote has been recorded 
from any node on which an individual is listed as sysop, no other votes 
will be accepted from nodes on which that same individual is listed.

11.8 Schedules

Nominations for the position of Regional Coordinator will be open from 1 
November through 15 November each year. The voting period will be from 1 
December through 15 December.

12. Replacement of a Regional Coordinator

12.1 Impeachment

In extreme cases, the Regional Coordinator may be impeached by petition. 
Impeachment of the Regional Coordinator does not require a Policy 
violation. An impeachment proceeding is invoked when a majority (50% + 
1) of the Net Coordinators of the region request the Zone Coordinator to 
institute it.

On receipt of petitions from the required majority of Net Coordinators, 
the Zone Coordinator will notify the Regional Coordinator that a new 
Regional Coordinator election will be held.

An election will be held according to the procedures elsewhere in this 
policy. The incumbent Regional Coordinator may run in this election to 
retain his office if he chooses.

At least one full year must elapse between impeachment petitions.

12.2 Resignation

A replacement election will also be held in the event that the Regional 
Coordinator resigns during his term. The Regional Coordinator will 
announce the election and follow the procedures as specified for the 
scheduled RC elections. At his discretion, the RC may appoint an interim 
RC to serve until the completion of the election process.

12.3 Coordination of terms of office

If a replacement election is started with less than six months remaining 
in the term of the current Regional Coordinator, the person elected will 
serve the next full term of office in addition to the remainder of the 
current term. If more than six months remain in the current term, the 
person elected will serve the remainder of the current term and the next 
election will take place as scheduled.

13. Regional Coordinator Technical Backup

The Regional Coordinator is encouraged to designate a technical backup 
for the purpose of processing nodelist segment updates and distributing 
information notices in the event of a system failure or unexpected 
absence of the Regional Coordinator. If the Regional Coordinator is 
absent from his duties without contact for more than 30 days, a 
replacement election will be called by the technical backup sysop.

14. Dedicated Regional Echo Conferences

Numerous regional echomail conferences are available for distribution 
throughout Region 18. The following conferences are of particular note 
for their role in the distribution of information of regional importance 
to the members of Region 18:

HOST18 - This is a discussion area available to all local Net 
Coordinators and Net Echo Coordinators for the discussion of 
administrative issues. Since this is frequently used for dispersing 
information from the Regional Coordinator to all net administrations and 
for gaining consensus on issues that may affect regional operations, all 
local Net Coordinators are encouraged to participate in this echo. 
Although the minimum information required to conduct any region-wide 
voting will be distributed via netmail, this echo is considered the 
official forum for discussion of regional business.

R18ELECT - This echo is used for discussion of regional elections, 
nominations for Regional Coordinator, candidate discussions during the 
Regional Coordinator elections and any other items related to elections 
within Region 18, including elections within the Echomail Coordinator 
structure or individual nets if desired. It is open to all node sysops 
in Region 18.

SYSOP18 - This is a general discussion area open to all node sysops in 
Region 18. This echo represents the largest open forum for reaching the 
members of the region.

15. Resolution of Disputes

As with any activity in which a large number of people interact, from 
time to time disputes will arise between members of Fidonet. It should 
be the goal of all members involved in disputes to resolve their 
differences through cooperation. The only true penalty that can be 
imposed on a member of Fidonet is the removal of his node number from 
the nodelist ("excommunication").

15.1 Causes of Complaints

Complaints that could result in the "excommunication" of a member fall 
into three categories:

15.1.1 Technical Non-compliance, which includes willful failure to 
operate an FTS-0001 compliant mailer or willful failure to observe Zone 
Mail Hour.

15.1.2 Illegal activity that involves, pertains to, or utilizes Fidonet 
as part of that activity.

15.1.3 Excessively annoying behavior in Fidonet. This includes 
activities that willfully disrupt the operations of one or more Fidonet 
systems; using non- existent or falsified node numbers with the intent 
of disguising the origin of mail traffic or of intercepting mail 
intended for the rightful owner of that node number; willfully 
compromising the integrity of an echomail conference after having direct 
links to that conference severed; threatening or initiating litigation 
against another Fidonet member related to actions taken under this or 
any other Fidonet policy.

15.2 Process of Resolution and Appeal

The process of complaint and appeal available to all Fidonet members is 
delineated in Fidonet policy (Policy 4, sections 9.1 through 9.8, until 
superceded by later policy) and follows a step by step procedure if the 
problem cannot be resolved directly between the involved members:

1. A Fidonet sysop complains via netmail to a Net Coordinator about 
specific annoying activity of a node in that net, and the Net 
Coordinator agrees that such activities are annoying.

2. The Net Coordinator points out this activity to the offender and 
gives him the opportunity to refrain.

3. The Net Coordinator records the response of the offender.

4. If the offender desists, the case is over.

Otherwise;

5. The Net Coordinator issues a final warning to the offender stating 
that he will be removed from the nodelist permanently unless immediate 
cessation of the offense(s) follows this final warning. Repeating at a 
later date an offense for which a warning was previously given may be 
considered refusal to comply.

6. If the offender desists, the case is over.

Otherwise;

7. The Net Coordinator notifies the offender of his removal from the 
nodelist.

8. Net Coordinator records offender's final response (if any) and 
removes offender's node number from the nodelist if no new information 
is received.

9. Net Coordinator advises Regional Coordinator of complete chronology 
with documentation and the case is closed,

or;

10. The offender appeals to the Regional Coordinator and offers other 
information contrary to the Net Coordinator's account and requests 
intervention and/or investigation.

11. If the Regional Coordinator refuses the appeal, the case is over.

Otherwise;

12. The Regional Coordinator agrees to consider the appeal and advises 
the Net Coordinator to refrain from removal pending investigation of the 
appeal.

13. The Regional Coordinator finds appeal has no merit, advises Net 
Coordinator to proceed with node removal, and advises offender of 
finding and of his option to appeal to the Zone Coordinator,

or;

14. The Regional Coordinator finds appeal has merit and advises Net 
Coordinator to retain the node's number and to appeal to the Zone 
Coordinator if unsatisfied.

15. The case is closed.

16. Amendments to Region18 Policy

This policy may be amended in whole or in part by the affirmative vote 
of a majority (50% + 1) of the Region 18 members who cast votes in a 
policy referendum. Such a referendum may be called at any time on the 
request of 25% of the local Net Coordinators or 5% of the node sysops in 
Region 18 presented to the Regional Coordinator. Multiple amendments may 
be considered during a single referendum, but will be voted on 
individually.

Voting in a Region 18 Policy Referendum will be carried out in the same 
manner as a Regional Coordinator election, with the following 
exceptions:

1) The text of any proposed amendment will be posted in the R18ELECT 
echo for discussion weekly for a minimum of three weeks prior to the 
beginning of voting. The drafter(s) of such amendment is encouraged to 
participate in discussing the rationale and merits of the amendment 
during this time.

2) The Regional Coordinator may at his discretion serve as vote counter 
or may designate an alternate to carry out the duties comparable to the 
election coordinator in a Regional Coordinator election.

3) The Regional Coordinator will distribute the text of all amendments 
and the voting format instructions to all Net Coordinators not less than 
two weeks before the beginning of the voting period and will maintain a 
file of this information available for File Request by any member of the 
region until the close of voting.