home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Generic Fidonet Collection
/
fidonet.zip
/
fidonet
/
BOFAQ904.TXT
< prev
next >
Wrap
Text File
|
1999-04-04
|
24KB
|
536 lines
=====================================
== North American Backbone ==
== General Information & ==
== Frequently Asked Questions ==
=====================================
BOFAQ903.TXT - 01 Apr 99
Terms used throughout this file
=================================
North American Backbone - A group of volunteer FidoNet hubs who help
distribute echomail and routed netmail in North America (FidoNet
Zone 1). The structure is customarily recognized as a set of tiers
with the intention of distributing echomail in an accurate and
expeditious manner. Hereafter in this file the North American
Backbone is referred to simply as the Backbone.
Echo or Conference - An echomail conference is a message base or forum,
distributed under a specified echomail conference name, dealing
with a defined area of interest. Hereafter in this file echomail
conferences are referred to simply as echoes.
Backbone Hub - A hub who helps to distribute mail within the North American
Backbone. Backbone Zone Hubs (ZHubs) distribute mail at the zone
level. Backbone Region Hubs (RHubs) distribute mail at the region
level. Backbone Net Hubs (NHubs) distribute mail at the net level.
North American Backbone Coordinator (NAB Coordinator) formerly OBO - Person
responsible for the day-to-day operation of the North American
Backbone at the zone level. He coordinates routing to ensure
reliable and efficient transport of echomail and Backbone-routed
netmail while avoiding creation of duplicate messages. He also
serves as liaison to the ZEC and to other distribution systems.
Echomail Coordinators (ECs) - Echomail Coordinators have been recognized by
Fidonet since 1987. The Zone Echomail Coordinator (ZEC)
coordinates echomail at the zone level. Region Echomail
Coordinators (RECs) coordinate echomail at the region level. Net
Echomail Coordinators (NECs) coordinate echomail at the net level.
Backbone Council - An advisory group of RECs who represent the interests of
the zone. They provide input and perspective to the Backbone.
BACKBONE.NA - A text file listing all echoes, and their descriptions, that
are presently carried on the North American Backbone. This text
file is formatted in a manner which makes it easily readable by
echomail distribution software to use as a "forward list". It is
published weekly at the direction of the NAB Coordinator and
distributed in the BACKBONE file area.
BACKSTAT.NA - A North American Backbone newsletter published weekly which,
among other things, itemizes echoes which are in the process of
being added to or dropped from the North American Backbone, as well
as listing the NAB Coordinator and the Backbone Zone and Region Hubs. It is
published weekly at the direction of the NAB Coordinator and distributed in the
BACKBONE file area. It is advisable that those who rely on the
North American Backbone get in the habit of reading this file.
BOFAQxxx.TXT (xxx = version) - This file. It is published monthly by the
NAB Coordinator and distributed in the BACKBONE file area.
Moderator - Person(s) responsible for an echo and its liaison with the
Backbone.
Zone 1 EchoList - A database containing a list of echoes, published monthly
by the Zone 1 EchoList Coordinator (1:1/21). It customarily
contains echo names, moderator names and addresses, and
descriptions of the echoes. Hereafter in this file the Zone 1
EchoList is referred to simply as the EchoList.
Gateways - Echomail Gateways are nodes whose systems are used to exchange
mail with other groups. The term Gateway, as used here, includes
all forms of gating including, but not limited to, zone-gating,
inter-network gating, intra-network gating, and domain-gating.
Q1 ========================================================================
What is the purpose of this help file?
This help file has been assembled as a means to provide answers to
frequently asked questions regarding how the Backbone operates and to
provide an insight into its internal administration.
Q2 ========================================================================
How are Backbone Hubs selected?
ZHubs are selected by a vote of the NAB Coordinator and the other ZHubs.
RHubs are recognized by the NAB Coordinator upon application by their
respective RECs. An applicant should connect to either a ZHub or another
RHub and route netmail and/or echomail for at least a few nets other than
their own.
NHub selection is left up to the individual nets.
Q3 ========================================================================
Are all of the echoes listed in BACKBONE.NA available from all of the
Backbone Hubs?
The ZHubs make available all echoes which are listed in in BACKBONE.NA.
RHubs and NHubs are not obligated to carry all listed echoes. However, no
Backbone Hub is required to carry any echo which, in their opinion, could
subject them to consequences which might have a negative effect on their
well being.
Q4 ========================================================================
What are the responsibilities of a moderator of an echo which the Backbone
carries?
1) Seeing that messages in their echo correspond to the echo's theme.
2) Updating their echo's listing in the Echolist at least every six
months.
3) Preventing the distribution of their echo from interfering with the
operation of the Backbone.
4) Must be accessible via netmail through known channels.
5) Seeing that messages in their echo do not violate the standards set
in Q8, Q20 and Q26.
Q5 ========================================================================
What "tools" does the Backbone provide to a moderator in order to help
him/her carry out their responsibilities?
If a moderator believes that a node is violating an echo rule, he/she may
request the feed to that node be severed. This request is made in written
form (netmail), to the hub feeding the offending node, with a copy to the
offending node. It is recommended that a copy also be sent to the node's
NEC so that he or she is aware of such problems in the net and can provide
information and assistance.
Some important points to remember regarding feed cut requests:
1) Feed cuts should be initiated with an effort to cause the least
amount of disruption to the echo.
2) In most cases, the main goal of a feed cut is to remove a REPEAT
offender who is likely to cause future echo disruption.
3) Echo rule offenders are, in most cases, PEOPLE - not systems.
4) SYSTEMS should not be cut until efforts to remove the PERSON have
failed. Moderators should attempt to resolve problems as close to
the root of the problem as possible, i.e., user first, SysOp second,
hub third, etc.
5) Feed cuts at the Zone level are taken very seriously. Only use
them as a last resort after all other means have failed. Have
proper documentation ready to support a link cut request at the Zone
level showing that all other efforts have failed.
6) Feed cut requests are just that - requests. Communications should
be polite and not demanding as you are REQUESTING help from another
system.
Q6 ========================================================================
What means does the Backbone use to recognize the moderator of an echo?
A moderator is recognized as follows:
1) Upon formation of an echo, the person who forms the echo is the
moderator.
2) Upon resignation or replaceme