= Сообщение: 2329 из 7124 ====================================== FTSC_PUBLIC = От : Fred Riccio 1:132/174 27 Mar 17 10:14:38 Кому : Ward Dossche 27 Mar 17 10:14:38 Тема : Repost: Proposed changes: FTS-5001.006 - Part 1 FGHI : area://FTSC_PUBLIC?msgid=1:132/174+58d8e65b На : area://FTSC_PUBLIC?msgid=2:292/854+a4057252 = Кодировка сообщения определена как: CP866 ================================== ============================================================================== 27 Mar 17 15:54, Ward Dossche wrote to Fred Riccio:
WD> The message displays grunged on my system, obviously too long.
This document is a Fidonet Technical Standard (FTS) - it specifies the current technical requirements and recommendations for FTN software developers, coordinators and sysops of the Fidonet network and other networks using FTN technology.
This document is released to the public domain, and may be used, copied or modified for any purpose whatever.
Abstract --------
Nodelist flags extend the basic nodelist format described in FTS-5000, allowing a node to provide detailed information of its operation and capabilities.
Contents --------
1. Introduction 2. Supersessions 3. Purpose 4. Syntax 5. Normal flags 5.1 Operating Condition Flags 5.2 Modem Connection Protocol Flags 5.3 Session Level Error-correction and Compression Flags 5.4 File/Update Request Flags 5.5 Gateway Flag 5.6 Mail Period Flags 5.7 System Online Flags 5.8 ISDN Capability Flags 5.9 Internet Capabilities 5.10 Robot flags 5.11 Flag Redundancies 6. User Flags 6.1 Format Of User Flags 6.2 Mail Oriented User Flags
The Fidonet Distribution Nodelist (FTS-5000) is a comma-delimited database, i.e. each node's entry is made up of fields, each of which has a specific purpose.
While this is a fine system for holding information that all nodes must have (e.g. node number, sysop name, etc.) it is not well suited for data that varies wildly from system to system. To accommodate such data, the flag fields are defined as self-describing and non-position dependent fields.
This document is a registry of all commonly used flags in Fidonet, and companion to FTS-5000 in describing the Distribution Nodelist.
2. Supersessions ----------------
This document supersedes and replaces FTS-0005, FSC-0009, FSC-0040, FSC-0062, FSC-0075 and FSC-0091.
3. Purpose ----------
As with FTS-5000, this document is intended for both developers and nodelist maintainers to avoid duplication and conflicts. Normal sysops would also do well to have at least cursory knowledge of the nodelist's capabilities so they may provide their Coordinators with all the pertinent detail of their systems.
This document should be considered a guide, and not the final word on what are and aren't valid flags. There will obviously be an unavoidable lag between the introduction of new flags and their inclusion in this document, as well as experimental flags that will come and go with no official documentation at all.
4. Syntax ---------
Most flags are simple tokens that each occupy a single field and by their presence or absence in the nodelist, indicate the presence or absence of a certain feature in the node.
A more recent style is to subdivide the flag field, usually with a colon (3Ah) to allow for variable data under a common flag. These are essentially named fields, consisting of the flag itself and its payload as one or more subfields.
Unless otherwise stated, flags are not position or order dependent, with the exception that User Flags must follow Normal Flags.
CM Node accepts mail 24 hours a day using all listed methods ICM Node accepts mail 24 hours a day using all listed TCP/IP methods, but not all of the other listed methods (such as PSTN/ISDN) and therefore cannot be CM. See FRL-1017. MO Node does not accept human callers LO Node accepts calls Only from Listed FidoNet addresses MN Compressed mail packets will not be processed automatically
* NOTE: maximum possible speed; actual maximum will vary depending on implementation.
5.3. Session Level Error-correction and Compression Flags ---------------------------------------------------------
The following flags define type of error correction and/or data compression available. A separate error correction flag should not be used when the error correction type can be determined by the modem flag. See section I for details.
Flag Meaning
MNP Microcom Networking Protocol error correction of type MNP1 to MNP4 V42 ITU-T V.42: LAP-M error correction with fallback to MNP 1-4 V42b ITU-T V.42bis: LAP-M error correction and compression with fallback to MNP 1-5
