ECHOPOL.R13
Region 13 Echomail Policy
04 April 1998
Blatantly Plagiarized From Region 17's Echomail Policy
This document contains information for the handling and distribution of
ECHOMAIL in Fidonet's Region 13 (Zone 1).
Contents:
1. INTRODUCTION
2. APPOINTMENTS
3. ECHOMAIL DISTRIBUTION PRINCIPLES
4. RHUB DISTRIBUTION SYSTEM
5. NEW ECHO REQUESTS
6. REC/RHUB TERMS OF REFERENCE
7. NEC TERMS OF REFERENCE
8. EMERGENCY BACKUP PLAN
-----------------------------------------------------------------------------
1. INTRODUCTION
============
1.1 Terms and definitions used in this document are:
Regional Coordinator .............. RC
Region Echo Coordinator ........... REC
Region Echomail Hub ............... RHub
Net Echo Coordinator .............. NEC
Cost Recovery Plan ................ CRP
Any NC, RC or ZC .................. *C
Any NEC, REC or ZEC ............... *EC
Regional Echomail ................. echoes local to Region 13
Backbone Echomail ................. echoes listed on BACKBONE.NA
1.2 This policy is intended to formalize the coordination of the
Region's echomail systems, and to provide for continuity and
consistency in that coordination.
1.3 Nothing in this document is intended to dictate any Net's internal
policies. Accepted echomail distribution principles, and in
particular, typical NEC terms of reference, are given by way of
guidance.
1.4 The REC is responsible for revisions to the policy, and
recommendations for change are welcomed from sysops in the region.
2. APPOINTMENTS
============
Position Sysop Admin Address Personal Address
RC David Mouferrage 1:13/0 1:2613/404
REC Jim Balcom 1:1/213 1:109/334
RHub Jim Balcom 1:13/25 1:109/334
RHub Thomas Leschander 1:13/21 1:2613/118
RHub David Calafrancesco 1:13/22 1:2624/803
3. ECHOMAIL DISTRIBUTION PRINCIPLES
================================
3.1 A mail feed may be obtained from anyone who is willing to provide
such a feed. No Policy 4 action may be taken against any node for
doing so.
3.2 Members of a Net are not obliged to obtain all their echomail from
the same source. *ECs may be able to assist nodes in coordinating
their echomail activities with others.
3.3 Groups of sysops may agree to contribute funds to share the costs
of long-distance polling, or equipment purchase.
3.4 A sysop who chooses not to receive mail from a CRP is under no
obligation to pay for that CRP's echomail, related mail services,
or equipment.
3.5 CRP participation and echomail feed choices do not affect a
sysop's privilege of holding a node number.
3.6 Distribution systems have a responsibility to coordinate and
monitor the content and structure of their mail distribution to
avoid disruption of other distribution systems to which they
forward mail.
3.7 Echomail content does not normally violate Policy 4. Local policy
problems can not be dealt with outside a net since there is only
one Fidonet Policy document. The only sanction applicable is a
moderator requested feed cut.
3.8 There is no requirement for a *EC to distribute mail personally,
or to be responsible for running a distribution system.
4. RHUB DISTRIBUTION SYSTEM
========================
4.1 The 3 RHubs operate an independent mail distribution system for
Backbone echomail, routed netmail and such other services as they
choose to offer. Access to this system is offered to interested
groups of sysops in regional Nets.
4.2 All matters concerning RHub polling schedules, downlink
connections, types of services offered, information files
maintained, and cost recovery, are decided by the RHubs.
4.3 The RHubs advise the REC of their region-related connections and
of any available help files. The RHubs and the REC maintain a
close liaison on such matters.
4.4 The REC helps to coordinate the selection of new RHubs, the
necessary zone and region links required by an RHub, and the
access to an RHub by regional downlinks.
5.a NEW ECHO REQUESTS for addition to the SPW distribution system
=================
5a.1 Where an echo is listed in BACKSTAT.NA as requesting addition to
the Backbone, any Region 13 sysop may request that their NEC
request that the REC recommend its addition to the Backbone.
5a.2 When the REC receives such a request, the REC will normally
forward to the ZEC the Region's recommendation that the echo be
added to BACKBONE.NA.
5a.3 Should the REC have reason to believe that such a recommendation
would not be representative of the Region's wishes, he may present
the request to the Region's NECs for comment, and will normally
act on their recommendations. NEC's are strongly encouraged to
obtain input from their nets.
5.b NEW ECHO REQUESTS for addition to the FidoSpine distribution system
=================
5b.1 Any Region 13 moderator may request that his/her nearest FidoSpine
hub make the addition to the FIDONET.NOW.
5b.2 The REC, and all Region 13 RHubs are not involved in the process
of adding echos to FidoSpine's distribution, as part of their
official Region 13 duties.
5.c NEW ECHO REQUESTS for addition to the Rhub distribution system
=================
5c.1 A request for a non-Backbone echo to be placed on regional
distribution should be directed to one of the Rhubs.
6. REC/RHUB TERMS OF REFERENCE
===========================
6.1 The REC is appointed by the RC to whom he is responsible. The RC
will usually make the appointment after consulting with the NECs
of the Region (by election, or some other process).
6.2 The function of the Region 13 Echomail Coordinator (REC) is to
coordinate the movement of echomail and echomail routed netmail as
requested by regional Nets, and to assist in maintaining its
reliability, efficiency and cost-effectiveness.
6.3 The responsibilities of the REC are:
a. to provide information concerning
feed sources
mail routing
help files sources
technical standards
echomail procedures and policies
developments in echomail issues
b. to provide liaison with
the ZEC and ZHubs
other regions
Region 13 Hubs
Region 13 NECs
c. to provide assistance to
the RC with echomail matters on request
RHubs in selecting additional RHubs when needed
RHubs in arranging ZHub connections
NECs in resolving echomail disputes
sysops with coordination of cross-regional links
d. to carry out administrative tasks such as
recommending addition of new echoes to the SPW Distribution
system
maintaining the region's echomail policy
participating in Zone discussions with other RECs and the ZEC
e. to represent Region 13 on the RECC (Region Echomail
Co-Ordinators Council)
6.4 An RHub is a node appointed by the REC in consultation with the
other RHubs to exchange mail with a ZHub, to make any inbound
echomail routed netmail available to regional downlinks, and to
provide a source of Backbone echomail to those downlinks.
7. NEC TERMS OF REFERENCE
======================
7.1 Many NCs appoint an NEC to handle any echomail issue which the NC
encounters. In addition, sysops in a Net usually select in some
manner a person to handle their echomail coordination concerns.
For efficiency, it is recommended that an NC choose as the NEC the
same person selected by the sysops.
NOTE: Beyond such specific delegation, an NC has no
responsibility for echomail matters unless the echomail is
conflicting with a specific Policy 4 requirement.
7.2 It is strongly recommended that the NEC not be the NC or be
involved in CRP administration, to avoid conflicts of interest.
7.3 It is strongly recommended that the NEC uses the /1 listing in the
nodelist, as well as using the UNEC flag in the nodelist so that
the NEC can be easily located.
7.4 The function of the Net Echomail Coordinator (NEC) is to
coordinate the movement of echomail and echomail routed netmail as
requested by the NC and Net sysops, and to assist in maintaining
its reliability, efficiency and cost-effectiveness.
7.5 The responsibilities of the NEC typically are:
a. on behalf of the NC, to
handle echomail-related enquiries which the NC has
received;
provide input to the NC on echomail issues;
troubleshoot echomail disputes in the net to avoid Policy
Complaints;
b. on behalf of the sysops, to
be an information source on the growing multitudes of
different distribution systems and how to contact each one;
be a knowledgeable resource person, including advising on
echomail standards, regional and zone-wide distribution;
watch for and help resolve technical conflicts including
feeds and routings where he is asked to do so;
provide advice for sysops who want to get involved in one
or more echomail distribution system, including acting as
liaison with moderators, hubs, other *ECs and sysops;
represent the sysops' needs by advising the REC on echomail
distribution and policy issues, and by participating in
Region discussions with other NECs and the REC.
8. EMERGENCY BACKUP PLAN
=====================
The REC and the RHubs have agreed to provide the following emergency
backup plan in the event of a major technical failure in regional mail
flow.
8.1 Each RHub maintains full access privileges with a ZHub and can
provide a Backbone mail feed to any regional downlink on
request of the REC, subject to normal system limitations.
8.2 RHubs and the REC exchange current critical system files and voice
phone numbers with each other.
---ooo000ooo---