Matt Whelan, 3:3/1000 International Coordinator FidoNet Gateway Policy ---------------------- I have accepted the following document, the final draft version of the FidoNet Gateway Policy, and it will be implemented as part of FidoNet policy commencing immediately upon publication of this issue of FidoNews. I'm sure I'd better follow that statement immediately with some points of clarification: o When the first draft of the document was published in January, a few people assumed it was designed to cut off communication with other networks, especially FidoNet-technology (or 'break- away') networks. This is entirely incorrect. o The document is an attempt to establish a valid technical base for increasing contact between the various networks. It is designed to encourage communication between FidoNet and _all_ other networks. o The document was revised after publication in an attempt to correct areas where its intent was clearly misunderstood. Its implementation was further intentionally delayed to allow discussion of its content, and an international echomail conference was established for that purpose. o This is definitely not a case of FidoNet telling others how to run their nets. We are saying how others should behave when present in our network, just as they should have the right to say how we should behave when 'guests' in their 'house'. o Please note where I said "commencing" in the opening paragraph -- we will, naturally, allow time for adjustment where anyone thinks that is necessary. The Gateway Policy deliberately does not specify implementation details. There are many ways to achieve its requirements, several of which already exist in experimental or released software. The aim was to specify the 'end', leaving the 'means' to the software authors and users who have made our 'hobby' a hub of pioneering creativity. I thank everyone involved for their work on the document, especially Tim Pearson and David Dodell for their effort, perseverence and, in the end, patience. FidoNet(tm) Internetwork Gateway Policy July 22, 1990 Section 1 - Purpose =================== This document sets forth the administrative policy require- ments for interconnection between the FidoNet amateur interna- tional electronic mail network and other electronic mail net- works. As an amateur network, membership in FidoNet is open and available to any individual or group capable of meeting the technical challenge and willing to participate constructively within the technical and administrative guidelines employed within FidoNet. FidoNet desires to extend this idea, "The free exchange of information," to include other electronic mail net- works. While connectivity with other networks can be beneficial to all parties involved, it cannot be expected to operate smooth- ly unless the parties involved understand and agree to observe technical and administrative guidelines designed to promote the orderly flow of traffic between networks and to provide a mecha- nism for problem resolution should problems arise. This document intends to address those points. Section 2 - Definitions ======================= "FidoNet" --------- An amateur electronic mail wide area network consisting of several thousand computer systems world wide. Most of these systems operate electronic bulletin board (BBS) software giving each system the capability to provide electronic mail services to up to several hundred users. Detailed information on the techni- cal and organizational aspects of the FidoNet mail network is beyond the scope of this document. Further information can be obtained from various FidoNet publications including the FidoNet official policy document. "Other Network" --------------- The term "Other Network" will be used in this document as a shorthand term referring to any other electronic mail network, whether inherently compatible with the technology employed within FidoNet or not. This term will often be used to refer specifi- cally to the electronic mail network making application to Fido- Net for a "Gateway" (defined below). "Gateway" --------- A gateway is a system of computers equipped with the hard- ware and software necessary to pass electronic mail messages (possibly of various types, see below) between FidoNet and a specific Other Network. A Gateway acts as a translator, allowing messages entered on a system in the Other Network and addressed to a destination within FidoNet to be translated into a form that is technically acceptable to and compatible with FidoNet and vice versa. All messages originated in the Other Network and ad- dressed to a destination within FidoNet are first routed to a Gateway. At a Gateway, the message is made technically acceptable to and compatible with FidoNet and forwarded into FidoNet's wide area network for delivery to its final destination. A message originated within FidoNet and addressed to a destination within the Other Network is handled in a similar manner. "Netmail" --------- The term Netmail, as used within FidoNet, refers to an electronic mail message that is addressed to a specific physical destination. Netmail messages can be addressed to a particular individual at the destination site. Public messages can be read by users other than the named addressee while private messages cannot typically be read by any user other than the named ad- dressee and the system administrator/operator at the destination site. Further information on Netmail is available in other Fido- Net technical and policy documents. "Conference Mail" ----------------- Echomail is the term used within FidoNet to refer to elec- tronic "Conference Mail" messages that, while possibly containing the name of a particular individual in the "To:" field, are copied and distributed to multiple (possibly several hundred) destination systems. Some Other Networks refer to their analo- gous capability under the terms "GroupMail" or "newsgroup". Echomail messages are segregated into "Conferences" based upon the topic being discussed. Echomail message content is usually restricted to the topic(s) for which the particular conference was created. Several hundred Echomail conferences exist within FidoNet dedicated to topics ranging from technical discussions of various computer systems and peripherals to philosophy and reli- gion. Further information on Echomail can be obtained by con- sulting other FidoNet technical and policy documents. "FidoNet Technology Network" (FTN) ---------------------------------- For the purposes of this document, a "FidoNet Technology Network" (FTN) shall be defined as an Other Network whose message format and transmission protocols strictly meet the technical requirements set forth by the FidoNet Technical Standards Commit- tee (FTSC). FidoNet Technology Networks are inherently techni- cally compatible with FidoNet. Connectivity options are avail- able to FTN's that are not (for technical reasons) available to non-FTN Other Networks. Internetwork Coordinator (INC) ------------------------------ The Internetwork Coordinator is the individual within Fido- Net who has the responsibility for overseeing the granting, in- stallation, and maintenance of FidoNet to Other Network Gateways. The INC shall be designated by and act as the agent of the Fido- Net International Coordinator. Multi-Network (MultiNet) ------------------------ A "multinet" is a type of "super" network whose function is to provide connectivity between many other networks and to allow bidirectional communication between these networks. Duplicate Message ----------------- Because of the technology employed by some FidoNet Confer- ence Mail distribution systems, improper routing information or topology can cause multiple copies of the same message text to be delivered to FidoNet systems. A duplicate message is as any message arriving at a FidoNet node whose message body (the text entered by the human originator of the message) is identical to the message body of a previously received message. Messages manually forwarded to another recipient are not considered dupli- cates for the purposes of this document. Section 3 - Administrative Guidelines ===================================== This section is intended to outline the administrative framework under which Other Networks may connect to FidoNet. FidoNet reserves the right to reject any Other Network Gateway application for any reason. 3.1 - Other Network Connectivity to FidoNet Through "MultiNets" --------------------------------------------------------------- FidoNet may elect to seek and obtain connectivity to various multinet host facilities for the purposes of communicating with a wide range of Other Networks. Any Other Network that desires to communicate with FidoNet may elect to facilitate such communica- tion via the multinet. However, FidoNet reserves the right to refuse to deliver incoming message traffic arriving via such an arrangement based upon the guidelines set forth in this document. An Example: FidoNet is now gated into Internet via UUCP. It has agreed to the terms and conditions necessary for membership in and connectivity to the Internet multi-network "umbrella". One obvious method for achieving connectivity to FidoNet (and a whole host of other wide area networks) is for the Other Network to apply to Internet for a gateway. Under this scenario, the Other Network is bound by the terms and conditions of Internet just as FidoNet is. In this peer relationship, the terms and conditions stated in this document are used by FidoNet to determine if Other Network message traffic arriving at a FidoNet/Internet gateway will be accepted into FidoNet. 3.2 - Connectivity Only Through Mutually Recognized Gateways ------------------------------------------------------------ While FidoNet has no desire to inhibit experimentation or connectivity between consenting systems it must maintain the technical and administrative integrity of its network. Hence- forth, FidoNet will not permit non-FidoNet addresses to appear in any addressing or routing control fields (Some current examples include: the "From" or "To" address fields, the "* Origin" lines, the "seen-by" fields, or the "^APath" fields.) of any netmail or echomail messages traveling on any portion of FidoNet's wide area network. This restriction applies to all present and future FidoNet nodes. FidoNet nodes who wish to participate in Other Networks may do so but must insure that all message traffic transmitted to other FidoNet systems contain only valid FidoNet addresses in the addressing and routing control fields. The Fido- Net coordinators will enforce this requirement and are authorized by the International Coordinator to take whatever action may be necessary to prevent non-FidoNet addresses from entering Fido- Net, including without limitation, referring the offending nodes to this document and to the InterNetwork Coordinator for informa- tion on how to establish proper Gateways. The sole exception to this requirement is set forth in the following paragraph: The exchange of message traffic, on an experimental or private and closely controlled basis, between an Other Network and a system or systems that happen to be members of FidoNet is permitted and encouraged if such message traffic is confined to the consenting FidoNet systems and is not allowed to travel on or to any portion of FidoNet's wide area network that has not previ- ously consented to carry such traffic and if such connectivity does not prohibit the FidoNet system(s) from fulfilling the technical and policy requirements necessary for membership in FidoNet. FidoNet requests that the INC be informed of such ar- rangements so that any unintentional "leakage" of Other Network message traffic into FidoNet's wide area network may be rapidly isolated and corrected. The exchange of message traffic between any Other Network and FidoNet on any basis other than the one mentioned in the paragraph above shall only be done through mutually recognized and proper Gateways meeting the requirements set forth in this document. 3.3 - Administrative Agreement and Registration ----------------------------------------------- FidoNet requires that an Administrative agreement be execut- ed by and between the individual(s) responsible for the adminis- tration of the Other Network and the FidoNet International Coor- dinator, or the IC's authorized agent. This agreement should out- line, at a minimum, the following items: 1 - The name of the organization. 2 - The name, address, and voice telephone number where the administrator of the Other Network may be reached. (Administrative contact and responsi- ble party). 3 - A brief description of the organization. 4 - The name, address and voice telephone number where the individual(s) responsible for the operation of the FidoNet/Other Network Gateway(s) may be reached. (Technical Contact(s)) 5 - A list of computer system(s) requesting Gateway status containing the following information: o The name of the gateway system as it will appear in the FidoNet nodelist. o The Locality, State / Province / Department / etc., and Country where the Gateway is physically located. o The name of the system administrator for the particular Gateway. o The complete data telephone number for the Gateway, including country code. o The maximum baud rate supported by the Gate- way and all modem standards supported. o The hours during which the Gateway will support FidoNet dial up mail sessions. (*SEE NOTE BELOW*) o The date the Gateway is expected to become operational. o The FidoNet compatible session protocol(s) supported o If the Gateway is now a member of FidoNet, the zone, net, and node number of the FidoNet system applying for Gateway status. NOTE: For a system to be granted Gateway status, it must at least be available for FidoNet dial up mail sessions during the FidoNet dedicated mail period for the geographic locality concerned. FidoNet calls its mandatory dedicated mail period the "Zone Mail Hour". The time for "Zone Mail Hour" varies through- out the world and can be found in Appendix A of the current FidoNet Policy Document. 6. A clearly worded statement indicating that the responsible party in the Other Network and Fido- Net agree to the terms and conditions set forth in the Administrative Agreement and those in this document (included by reference as a part of the agreement). 3.4 - Application of FidoNet Administrative Policy -------------------------------------------------- For the purposes of applying FidoNet policy, FidoNet will view the entire Other Network as a single FidoNet "node" under the control of the individual named as the "Administrative Con- tact/Responsible Party" (or an authorized agent thereof) in the administrative agreement outlined in paragraph 3.3 above. All other systems and their users will be viewed by FidoNet as users on the "responsible party's" node for the purposes of FidoNet official policy application. FidoNet holds the operator of a FidoNet node responsible (from an administrative policy standpoint) for the actions of that node's users, subordinate "point" systems, and the "point" system's users. FidoNet views single or multiple Other Network Gateways as a single "boss" node under the control of the "re- sponsible party" and will apply FidoNet official policy accord- ingly. FidoNet reserves the right to sever links to one or more of the Other Network's Gateways as its final remedy for viola- tions of administrative policy. (see the paragraph titled "Points" in the "Overview" section and the paragraph titled "Responsible for All Traffic Entering FidoNet Via the Node" in the "Sysop Procedures" section of FidoNet's official policy document, for further information). 3.5 - Supported Message Types ----------------------------- FidoNet will grant Gateway interconnection for the purposes of exchanging messages of the type defined above as "Netmail" and optionally for the purposes of exchanging messages of the type defined above as "Echomail". FidoNet will not grant Gateway interconnection for the purposes of exchanging "Echomail" only. The ability to generate a private and personal "Netmail" reply to an "Echomail" message is one of the basic facets of FidoNet and cannot be compromised. 3.6 - Acceptance Criteria (All Other Networks) ---------------------------------------------- The granting of Other Network Gateways into FidoNet is not automatic nor is it based solely on the Other Network's ability to demonstrate technical compliance with the objectives set forth in section 4 below. Some other criteria include: o The Other Network should have an individual will- ing and able to carry out the role of "Responsible Party" as defined herein. The Other Network "administration" should be willing to help in assuring that technical, social, and administra- tive policy standards are consistently met in all message traffic emanating from the Gateway(s). FidoNet pledges to do likewise. o The Other Network must have demonstrable stabili- ty. It should have been in operation as a free standing network for a period of time sufficient to prove its reliability. It should be able to prove that it has the technical and administrative expertise to maintain and regulate reliable Gate- ways over an extended period of time. 3.7 - Other Criteria (FTN Other Networks) ----------------------------------------- Current FidoNet compatible software allows a system to par- ticipate simultaneously in FidoNet and in other FTN networks, completely isolating one network from the other; i.e., using only valid FidoNet addresses in FidoNet traffic and only valid Other- Net addresses in OtherNet traffic. This "isolated dual identity" approach is simple to use and eliminates any need for gateways, administrative controls, written agreements, etc. An OtherNet node wishing to participate in FidoNet simply does so, isolating their own memberships similarly to separating participation in Compu$erve and the Internet. This approach allows for FidoNet connectivity on a node by node basis, speeds mail transfers (since messages from each node enter FidoNet's wide area network at the point of origin rather than having to first pass through a Gateway), gives each node contact with a nearby FidoNet coordinator to provide FidoNet ser- vices more effectively, and eliminates possible administrative policy conflicts between the OtherNet and FidoNet as the node ad- heres to FidoNet policy in FidoNet and to OtherNet policy in OtherNet message traffic. Given the simplicity and advantages of the isolated dual-identity scheme and the non-trivial technical and administrative work of maintaining gateways and policies for linked/gatewayed OtherNet connections to FidoNet, there is an onus on OtherNets wishing to gate to FidoNet to show mutually be- neficial technical and/or social considerations which would justify the work of setting up gateways and administrative agree- ments as opposed to merely encouraging OtherNet nodes who wish to participate in FidoNet to do so in the simple isolated dual- identity fashion discussed above. This is not meant to preclude gateways to FTN OtherNets, but rather to place an onus to show cause in order to reduce trivial or unnecessary formal gateways and gateway agreements. 3.8 - Shared Echomail Conferences --------------------------------- Echomail conferences shared between networks must be regis- tered with the appropriate FidoNet echomail coordinator. It is the responsibility of the Other Network and its Echomail source(s) within FidoNet to insure that proper topology is ob- served between the FidoNet / Other Network Gateway(s) and that duplicate echomail messages do not enter FidoNet. It cannot be overemphasized that all message traffic emanating from a Gateway must contain only valid FidoNet addresses in the message's ad- dressing and routing fields. Current examples include, without limitation, the "from" and "to" addresses in the message header, the *ORIGIN line address, the SEEN BY addresses and the ^APath addresses. 3.9 - Network Integrity ----------------------- In the event that FidoNet determines that significant harm is being caused to the technical or social integrity of its network, it may immediately sever links between the Other Network Gateway(s) and FidoNet. FidoNet will make all reasonable at- tempts to contact the "Responsible Party" as soon as possible (before the severing of links if possible) to inform the Other Network of the problem and to work toward its resolution. Section 4 - Technical Objectives ================================ At this time, FidoNet has not published a detailed technical standard for Gateways. FidoNet reserves the right to develop, implement, and require adherence to such a standard at a future date. In the mean time, the following general guidelines are set forth for Other Networks that desire to communicate with FidoNet. 4.1 - Technical Standards within FidoNet ---------------------------------------- The FidoNet Technical Standards Committee (FTSC) has de- veloped and published technical standards for message packets and mailer-to-mailer protocols. The Gateway system(s) must be able to assemble and transmit FidoNet standard message packets using FidoNet standard session protocol. A gateway must also be able to receive and disassemble FidoNet standard message packets using FidoNet standard session protocol. Translation from the Other Network's internal message format to FidoNet standard packets and vice versa is the responsibility of the Gateway. 4.2 - Logical Other Network Address ----------------------------------- Software at a Gateway shall modify each message entering FidoNet (whether Netmail or Echomail) such that FidoNet software will interpret the logical address of origin of the message as the Gateway's FidoNet address. 4.3 - Physical Other Network Address ------------------------------------ Software at a Gateway shall embed the Other Network address (physical point of origin), in human readable form, at a predict- able location in the message body immediately preceded by a predictable identifier such that software designed to facilitate the automatic inclusion of this information in FidoNet replies to Other Network messages will be able to glean this information from the other text in the body of the message reliably. This requirement applies to Other Network messages entering FidoNet, both Netmail and Echomail. 4.4 - FidoNet to Other Network Addressing (Netmail) --------------------------------------------------- FidoNet users must be provided with a procedure for routing what FidoNet defines as "Netmail" to Other Network users via a Gateway. FidoNet users will be instructed to address netmail to Other Network users to the FidoNet Zone:Net/Node address for an Other Network Gateway. The exact method by which these messages are forwarded to their final destination within the Other Network is left to the discretion of the Other Network. One obvious method is to have the FidoNet user enter the "physical Other Network address" in the proper location preceded by the proper identifier as outlined in paragraph 4.4 above. FidoNet will help the Other Network in educating FidoNet users on the proper form and location of the additional address information necessary to route a FidoNet to Other Network message to its final destination automatically via a Gateway. FidoNet netmail arriving at a Gateway with improper Other Network addressing information must either be corrected and forwarded to the proper Other Network address or returned to the FidoNet sender with text inserted notifying the sender that the message was undeliverable. 4.5 - Echomail Standards ------------------------ Echomail entering FidoNet shall conform to FidoNet (FTSC) standard format. FidoNet control, routing, and addressing infor- mation in each message shall show that it originated from the Gateway's FidoNet address. Internal Other Network routing infor- mation (if any) attached to echomail messages must be removed at the Gateway with the exception being the "Physical Other Network Address" as defined in paragraph 4.3 above. Section 5 - Network Policy Implications ======================================= 5.1 - Interpretation -------------------- FidoNet retains the exclusive right to interpret the terms and conditions stated herein based upon its representatives' best understanding of those terms and conditions and upon its knowl- edge of the original intent of the authors. Draft Administrative Agreement This agreement made this ________ day of _________, __________ between "FidoNet" and __________________________________________________, hereinafter referred to as "Other Network", shall be mutually exclusive and binding upon the parties herein until rescinded or revised by agreements of the parties. Article 1. ---------- Other Network and FidoNet desire to exchange electronic mail between their respective networks. The parties do therefore mutually covenant and agree as follows: Article 2. ---------- The parties hereto agree that the FidoNet document titled "Internetwork Gateway Policy" shall be controlling and is incor- porated as if referenced and set out in full. Paragraph 2.1 - Internetwork Gateway Policy ------------------------------------------- Other Network and FidoNet agree to be bound by the terms and conditions set forth in the FidoNet document titled "Internetwork Gateway Policy" included by reference in Article 1 above. Paragraph 2.2 - Gateway Certification ------------------------------------- FidoNet and Other Network agree not to exchange or attempt to exchange electronic mail via the proposed Gateway system(s) other than on a limited and mutually agreed "test" basis until both parties certify that the Gateway(s) are open for general message traffic. Paragraph 2.3 - Registration Information ---------------------------------------- Other Network agrees to provide FidoNet with complete and accurate information as requested in Articles 3 and 4 below and with any other information FidoNet may deem necessary as a prior condition for the certification of any FidoNet/Other Network gateways. Article 3 - General Information. -------------------------------- Organization name : _________________________________________ Administrative Contact/Responsible Party: Name:___________________________________ Address:___________________________________ City:___________________________________ State/Province:___________________________________ Country:___________________________________ Voice Telephone:___________________________________ Other Network Address:___________________________________ Technical Contact: Name:___________________________________ Address:___________________________________ City:___________________________________ State/Province:___________________________________ Country:___________________________________ Voice Telephone:___________________________________ Other Network Address:___________________________________ Brief Description of the Other Network Organization: _______________________________________________________________ _______________________________________________________________ _______________________________________________________________ Article 4 - Gateway Specific Information (duplicate if needed) -------------------------------------------------------------- Gateway name as it is to appear in FidoNet nodelist: ____________________________________________________ Gateway System Administrator: ____________________________________________________ Physical Gateway Location: Address:___________________________________ City:___________________________________ State/Province:___________________________________ Country:___________________________________ Voice Telephone:___________________________________ Gateway dial-up telephone number: _____________________________ Maximum asynchronous baud rate: ________________ Hours FidoNet dial-up mail sessions are supported (GMT):_______ Anticipated operational date: ____/____/____ FidoNet session protocols supported: __________________________ Is this system at present a FidoNet node? ___Yes ___No If yes, Zone:_____ Net:______ Node:______ Article 5 - Termination ----------------------- This agreement shall be terminated _______ days after the giving of notice by either party at which point all Gateway activities will cease. Article 6 - Sole and Exclusive Agreement ---------------------------------------- This agreement is the sole and exclusive agreement between the parties. Article 7 - Remedies -------------------- Both parties agree that their sole and exclusive remedy for non compliance with the Internetwork Gateway Policy shall be to terminate gateway activities. Witnessed: For FidoNet: Name:___________________________________________ Title:___________________________________________ Date: ___________________ For Other Network: Name:___________________________________________ Title:___________________________________________ Date:____________________ -----------------------------------------------------------------