FTSC library
203 documents · 339 revisions · Download all · Original 2018 archive & companion files
Files unchanged from their cited sources; same-named source variants may differ. FTS: standards; FSC/FSP: proposals; FRL: reference library; FTA: administration. Latest available revision or withdrawal notice shown; older files and source variants remain downloadable.
Support reviewed 2026-10-26. Yes: feature implemented; Partial: limited scope; No: not implemented; N/A: reference only; Unverified: not audited. These are implementation notes, not FTSC certification. Server is not released yet.
| File | Description | Server | Mobile |
|---|---|---|---|
| fts-0001.016 | A Basic FidoNet(r) Technical Standard | Partial — Type-2 packets and classic sessions; legacy interop limitations remain. | Partial — Type-2 packets, attributes and receipts; no FTS-0001 modem session. |
| fts-0004.001 | The Conference Mail System (EchoMail Specification) | Yes — Echomail tossing, routing, SEEN-BY and PATH. | Partial — Read/write as a point or leaf node; no hub routing. |
| fts-0005.003 | The Distribution Nodelist | See FTS-5000Successor document. | See FTS-5000Successor document. |
| fts-0006.002 | YOOHOO and YOOHOO/2U2 | Partial — YooHoo/2U2 and WaZOO; inbound pointnet identity has limits. | No — No YooHoo/2U2 session engine. |
| fts-0007.003 | Extending FTS-0001 to include SEAlink protocol | Partial — SEAlink windowing and RESYNC; no Overdrive negotiation. | No — No SEAlink transport. |
| fts-0008.003 | Extending FTS-0001 to include Bark requests | Yes — Bark requests in FTS-0001 sessions. | No — Uses .req files over binkp, not Bark. |
| fts-0009.001 | MSGID / REPLY; A standard for unique message identifiers and reply chain linkage | Yes — MSGID generation and REPLY threading. | Yes — MSGID generation and REPLY threading. |
| fts-0010.001 | Time zone information in FidoNet messages | See FTS-4008Successor document. | See FTS-4008Successor document. |
| fts-1024.001 | Raw ifcico mail transfer protocol | Yes — Raw ifcico sessions. | No — No ifcico transport. |
| fts-1025.001 | Simple E-Mail Attach Transport (S.E.A.T.) | No — No S.E.A.T. mail-attachment transport; SMTP gateway access is different. | No — No S.E.A.T. mail-attachment transport; SMTP gateway access is different. |
| fts-1026.001 | Binkp/1.0 Protocol specification | Yes — binkp sender and listener; full-duplex transfer. | Yes — binkp client; full-duplex transfer. |
| fts-1027.001 | Binkp/1.0 optional protocol extension CRAM | Yes — CRAM authentication, including CRAM-MD5. | Yes — CRAM authentication, including CRAM-MD5. |
| fts-1028.001 | Binkp protocol extension Non-reliable Mode | Partial — NR/resume implemented; late post-ACK OPT NR is limited. | Partial — NR and M_GET resume; late OPT NR cannot change already-made batch offers. |
| fts-1029.001 | Binkp dataframe compression (PLZ) | No — PLZ dataframe compression is not negotiated. | No — PLZ dataframe compression is not negotiated. |
| fts-1030.001 | Binkp optional protocol extension CRC Checksum | No — No binkp CRC extension; file/TIC CRC checks are separate. | No — No binkp CRC extension; file/TIC CRC checks are separate. |
| fts-4000.001 | CONTROL PARAGRAPHS | Yes — Parse and emit control paragraphs. | Yes — Parse and emit control paragraphs. |
| fts-4001.001 | ADDRESSING CONTROL PARAGRAPHS | Yes — INTL, FMPT and TOPT addressing. | Yes — INTL, FMPT and TOPT addressing. |
| fts-4008.002 | Time zone information (TZUTC) | Yes — Read and write TZUTC. | Yes — Read and write TZUTC. |
| fts-4009.001 | Netmail tracking (Via) | Yes — Via tracking on mail handling/routing. | Partial — Reads Via and stamps outgoing mail; no transit routing. |
| fts-4010.001 | The PING and TRACE flags | Yes — PING responder and transit TRACE. | Partial — PING responder; no transit TRACE. |
| fts-5000.005 | The Distribution Nodelist | Partial — Nodelist reader, CRC and NODEDIFF; not a coordinator compiler. | Partial — Nodelist reader and CRC; no NODEDIFF application. |
| fts-5001.006 | Nodelist flags and userflags | Partial — Parses flags for dialing; not every advertised transport is implemented. | Partial — Parses/displays flags; connects via supported client transports. |
| fts-5002.002 | POINTLIST formats | No — Pointlist service is not implemented. | Partial — Parses Boss/Point entries; no full pointlist workflow. |
| fts-5003.001 | Character set definition in Fidonet messages | Yes — CHRS decoding and emission, including UTF-8. | Yes — CHRS decoding and emission, including UTF-8. |
| fts-5004.001 | DNS Distributed Nodelist | Yes — DNS-distributed nodelist lookup for dialing. | No — No DDN lookup; FM-DNS is a separate protocol. |
| fts-5005.003 | Advanced BSO flow and control files | No — No BSO flow/control-file interface; sharing .req filenames does not implement BSO. | No — No BSO flow/control-file interface; sharing .req filenames does not implement BSO. |
| fts-5006.001 | TIC file format | Yes — TIC receive, forwarding and hatching. | Partial — TIC receive, validation and hatching; no hub forwarding. |
| fsc-0001.999 | A Basic FidoNet(tm) Technical Standard | See FTS-0001Successor document. | See FTS-0001Successor document. |
| fsc-0002.999 | The Distribution Nodelist (superseded) | See FTS-5000Successor document. | See FTS-5000Successor document. |
| fsc-0003.001 | FidoNet Route Files Explained | N/A — Historical routing discussion; not a single wire feature. | N/A — Historical routing discussion; not a single wire feature. |
| fsc-0004.001 | INTL kludge | Yes — Zones and points through standard addressing kludges. | Yes — Zones and points through standard addressing kludges. |
| fsc-0005.001 | Opus Matrix Password Methods | Partial — YooHoo password authentication; not the Opus BBS implementation. | No — No Opus/YooHoo session. |
| fsc-0006.999 | YOOHOO and YOOHOO/2U2 (superseded) | See FTS-0006Successor document. | See FTS-0006Successor document. |
| fsc-0007.002 | FidoNet RFC822-Style Message Format | No — No alternative RFC822-style FTN packet format. | No — No alternative RFC822-style FTN packet format. |
| fsc-0008.999 | Fundamentals of FOSSIL implementation and use (superseded by FSC-0015) | See FSC-0015Successor document. | See FSC-0015Successor document. |
| fsc-0009.001 | Nodelist capabilities identifier | Partial — Modern nodelist parser recognises legacy flags; no native ISDN stack. | Partial — Legacy flags are parsed/displayed; not modem or ISDN dialing. |
| fsc-0010.001 | RESYNC, a SEAlink protocol enhancement | Yes — SEAlink RESYNC/restart. | No — No SEAlink transport. |
| fsc-0011.001 | Experiences/corrections to FTS-0001 | N/A — Historical session state-table commentary; see FTS-0001/0006. | N/A — Historical session state-table commentary; see FTS-0001/0006. |
| fsc-0012.999 | The Conference Mail System (EchoMail Specification) (superseded) | See FTS-0004Successor document. | See FTS-0004Successor document. |
| fsc-0013.999 | A Standard for "Bark" File Requests (Superceeded by FTS-0008) | See FTS-0008Successor document. | See FTS-0008Successor document. |
| fsc-0014.001 | A Bundle Proposal | No — No implementation of this alternative packet format. | No — No implementation of this alternative packet format. |
| fsc-0015.001 | Fundamentals of FOSSIL implementation and use | No — No FOSSIL/VFOSSIL driver interface. | No — No FOSSIL/VFOSSIL driver interface. |
| fsc-0016.001 | FidoNet mail session startup | Partial — Modem session startup implemented; legacy timing limits remain. | No — No modem session startup. |
| fsc-0017.001 | FidoNet Standards Committee Archive Philosophy and Document Naming | N/A — Reference or administrative document; not a software feature. | N/A — Reference or administrative document; not a software feature. |
| fsc-0018.999 | FTSC File List (superseded) | See FTA-1004Successor document. | See FTA-1004Successor document. |
| fsc-0019.999 | The SEAlink file transfer protocol (Superceed by FTS-0007) | See FTS-0007Successor document. | See FTS-0007Successor document. |
| fsc-0020.001 | Alternate Nodelist Flag Proposal | Partial — Modern nodelist parser recognises legacy flags; no native ISDN stack. | Partial — Legacy flags are parsed/displayed; not modem or ISDN dialing. |
| fsc-0021.001 | VFOSSIL - An OS/2-Subset Video FOSSIL Appendage | No — No FOSSIL/VFOSSIL driver interface. | No — No FOSSIL/VFOSSIL driver interface. |
| fsc-0022.999 | FTSC Product Codes (superseded) | See FTA-1005Successor document. | See FTA-1005Successor document. |
| fsc-0023.001 | Bundle name format | No — Does not emit this proposed bundle naming format. | No — Does not emit this proposed bundle naming format. |
| fsc-0024.001 | Type-3 Mail Bundle | No — No implementation of this alternative packet format. | No — No implementation of this alternative packet format. |
| fsc-0025.001 | AVATAR; Advanced Video Attribute Terminal Assembler and Recreator | No — No AVATAR terminal decoder; ANSI support is different. | No — No AVATAR terminal decoder; ANSI support is different. |
| fsc-0026.999 | FTSC File List (superseded) | See FTA-1004Successor document. | See FTA-1004Successor document. |
| fsc-0027.999 | The Distribution Nodelist (Superceeded by FTS-0005) | See FTS-5000Successor document. | See FTS-5000Successor document. |
| fsc-0028.001 | A Collection of Notes on Moving Files | N/A — Historical file-distribution discussion; TIC support is under FTS-5006. | N/A — Historical file-distribution discussion; TIC support is under FTS-5006. |
| fsc-0029.000 | ** Not Used ** | N/A — Reference or administrative document; not a software feature. | N/A — Reference or administrative document; not a software feature. |
| fsc-0030.001 | Message Identification and Reply for FidoNet | No — Uses FTS-0009 MSGID/REPLY, not this alternative scheme. | No — Uses FTS-0009 MSGID/REPLY, not this alternative scheme. |
| fsc-0031.001 | EchoMail ^aEID: Dup-Checking with Linked Replies | No — Uses FTS-0009 MSGID/REPLY, not this alternative scheme. | No — Uses FTS-0009 MSGID/REPLY, not this alternative scheme. |
| fsc-0032.001 | Uniform Echomail Quoting Style | Yes — FidoNet initials and > quoting in reader/composer. | Yes — FidoNet initials and > quoting in reader/composer. |
| fsc-0033.001 | FidoNet Message ID Proposal | No — Uses FTS-0009 MSGID/REPLY, not this alternative scheme. | No — Uses FTS-0009 MSGID/REPLY, not this alternative scheme. |
| fsc-0034.002 | Gateways to and from FidoNet; Technical, Administrative, and Policy Considerations | N/A — Gateway technical/policy discussion, not a single protocol. | N/A — Gateway technical/policy discussion, not a single protocol. |
| fsc-0035.001 | Transparent Gateways to and from FidoNet; Technical Considerations | Partial — REPLYTO/REPLYADDR gateway-reply composition. | Partial — Preserves gateway kludges; no dedicated gateway-reply composer. |
| fsc-0036.001 | Group Mail Specifications | No — No GroupMail file format. | No — No GroupMail file format. |
| fsc-0037.001 | AVATAR; Advanced Video Attribute Terminal Assembler and Recreator | No — No AVATAR terminal decoder; ANSI support is different. | No — No AVATAR terminal decoder; ANSI support is different. |
| fsc-0038.001 | A Domain Proposal For FidoNet | Partial — 5D FTN addresses; does not implement every historical domain rule. | Partial — 5D FTN addresses; does not implement every historical domain rule. |
| fsc-0039.004 | A Type-2 Packet Extension Proposal | Yes — Type-2+ packet headers and capability word. | Yes — Type-2+ packet headers and capability word. |
| fsc-0040.001 | Extended Modem Handling | No — No interpretation of this proposal's Y/Z modem-protocol flags. | No — No interpretation of this proposal's Y/Z modem-protocol flags. |
| fsc-0041.999 | MSGID / REPLY; A standard for unique message identifiers and reply chain linkage (superseded) | See FTS-0009Successor document. | See FTS-0009Successor document. |
| fsc-0042.001 | Proposed Modification to the Gateway Agreement Between WWIVnet and FidoNet via the "NetSEX" Program | N/A — Reference or administrative document; not a software feature. | N/A — Reference or administrative document; not a software feature. |
| fsc-0043.002 | Some Hints on Recognizing Control Lines in Message Text | Yes — Control-line recognition. | Yes — Control-line recognition. |
| fsc-0044.002 | An improved method of duplicate message detection and prevention | Partial — Duplicate checking implemented; not a clause-by-clause audit. | Partial — Duplicate checking implemented; not a clause-by-clause audit. |
| fsc-0045.001 | Type-2.2 packet header | Partial — Type-2.2 input; normal output is Type-2+. | Partial — Type-2.2 input; normal output is Type-2+. |
| fsc-0046.005 | Product identifier (PID) | Yes — PID recognised/emitted; tosser identity also uses TID. | Yes — PID recognised/emitted; tosser identity also uses TID. |
| fsc-0047.001 | The SPLIT Kludge Line For Splitting Large Messages | Partial — SPLIT recognised for multipart UUE assembly. | Partial — SPLIT recognised for multipart UUE assembly. |
| fsc-0048.002 | A Proposed Type-2 Packet Extension | Partial — Type-2+ headers; the OrigNet=-1 / AuxNet point-address form is not decoded. | Yes — Type-2+ packet headers and capability word. |
| fsc-0049.001 | A Proposal for Passing Domain Information During an FTS-0006 Session | Partial — Domain field in YooHoo Hello; identity handling has limits. | No — No YooHoo session engine. |
| fsc-0050.001 | A Character Set Identifier For FidoNet Message Editors | Partial — Legacy charset input; current output uses CHRS. | Partial — Legacy charset input; current output uses CHRS. |
| fsc-0051.003 | I51; A System-Independent Way of Transferring Special Characters | No — No I51 escape encoding. | No — No I51 escape encoding. |
| fsc-0052.001 | A proposal for making the PATH zone aware | No — Does not generate ZPTH routing control lines. | No — Does not generate ZPTH routing control lines. |
| fsc-0053.002 | Specifications for the ^aFLAGS field | Partial — FLAGS parsing/emission and receipts; actions depend on the flag. | Partial — FLAGS parsing/emission and receipts; no transit routing. |
| fsc-0054.004 | CHARSET; A System-Independent Way of Transferring Special Characters, Character Sets and Style Information in Messages | Partial — CHRS charset handling; not the entire style/escape proposal. | Partial — CHRS charset handling; not the entire style/escape proposal. |
| fsc-0055.001 | Security Passwords in Nodelist Update Files | No — No coordinator nodelist-update password processor. | No — No coordinator nodelist-update password processor. |
| fsc-0056.001 | EMSI/IEMSI Protocol Definitions | Partial — EMSI mail sessions; no interactive IEMSI login. | No — No EMSI/IEMSI session engine. |
| fsc-0057.003 | Conference Managers - Specifications for Requests | Partial — AreaFix/FileFix clients and robots; command subsets vary by dialect. | Partial — AreaFix/FileFix client; no subscription server. |
| fsc-0058.002 | A New Way Of Addressing | No — Uses INTL/FMPT/TOPT; not the proposed replacement addressing. | No — Uses INTL/FMPT/TOPT; not the proposed replacement addressing. |
| fsc-0059.001 | Newsgroup Interchange within FidoNet | No — No FidoNet/Usenet gateway implementing this specification; NNTP reader access is separate. | No — No FidoNet/Usenet gateway implementing this specification; NNTP reader access is separate. |
| fsc-0060.001 | Calculation and Usage of CRCs | Partial — CRC algorithms used by mail transfers and TIC; not all examples. | Partial — CRC-16 nodelist and CRC-32 ZIP/TIC checks. |
| fsc-0061.001 | Proposed Guidelines for the FileBone | N/A — Reference or administrative document; not a software feature. | N/A — Reference or administrative document; not a software feature. |
| fsc-0062.003 | Nodelist flag indicating Online Times of a Node | Yes — Txy online-time flags parsed for dialing. | Partial — Parses/displays online windows; no modem scheduler. |
| fsc-0063.001 | A Proposal for FidoNet style messages | No — No replacement message structure. | No — No replacement message structure. |
| fsc-0064.007 | InterDomain Message Identification, Gating, Reply Linking and Addressing | Partial — Domain-aware addresses and MSGIDs; not every gating rule. | Partial — Domain-aware addresses and MSGIDs; not every gating rule. |
| fsc-0065.001 | Type 3 ASCII | No — No implementation of this alternative packet format. | No — No implementation of this alternative packet format. |
| fsc-0066.002 | Type 3 Binary | No — No implementation of this alternative packet format. | No — No implementation of this alternative packet format. |
| fsc-0067.001 | A Proposal For Sensible New Kludge Lines | No — No dedicated behaviour for these proposed control lines. | No — No dedicated behaviour for these proposed control lines. |
| fsc-0068.001 | A Proposed Replacement For FTS-0004 | Partial — Echomail rules implemented; no full-document conformance claim. | Partial — Point/leaf-node echomail subset; no hub distribution. |
| fsc-0069.001 | Proposal for a FidoNet Domain Name Service (DNS) | No — No file-request-based domain name service; DDN is separate. | No — No file-request-based domain name service; DDN is separate. |
| fsc-0070.002 | Improving Fidonet/Usenet gating and Dupe Checking | No — No FidoNet/Usenet gateway with the specified RFCID interchange. | No — No FidoNet/Usenet gateway with the specified RFCID interchange. |
| fsc-0071.001 | Distributed FREQ (DFREQ) Specifications | No — No distributed FREQ implementation. | No — No distributed FREQ implementation. |
| fsc-0072.001 | The HYDRA file transfer protocol | Yes — Hydra transfer engine. | No — No Hydra transport. |
| fsc-0073.001 | Encrypted Message Identification for FidoNet | No — No FidoNet encrypted-message identification/decryption workflow. | No — No FidoNet encrypted-message identification/decryption workflow. |
| fsc-0074.001 | Echomail Specification | Partial — Echomail rules implemented; no full-document conformance claim. | Partial — Point/leaf-node echomail subset; no hub distribution. |
| fsc-0075.001 | ISDN capability flags in the Nodelist | Partial — Modern nodelist parser recognises legacy flags; no native ISDN stack. | Partial — Legacy flags are parsed/displayed; not modem or ISDN dialing. |
| fsc-0076.001 | Netmail Areatags | No — No NETMAIL area-tag based routing. | No — No NETMAIL area-tag based routing. |
| fsc-0077.001 | Type-10 Packet Format | No — No implementation of this alternative packet format. | No — No implementation of this alternative packet format. |
| fsc-0078.001 | Gateway between Fidonet compatible networks | Partial — Multi-network routing; historical gateway policy not fully audited. | No — Client only; does not gateway between networks. |
| fsc-0079.002 | RTF Mail; Message Formatting in the Type 2 Message Packet | No — No RTF-mail renderer or sender. | No — No RTF-mail renderer or sender. |
| fsc-0080.002 | Describing FidoNet with a layered model | N/A — Reference or administrative document; not a software feature. | N/A — Reference or administrative document; not a software feature. |
| fsc-0081.001 | Type-3 Packet proposal | No — No implementation of this alternative packet format. | No — No implementation of this alternative packet format. |
| fsc-0082.001 | New Packet Type | No — No implementation of this alternative packet format. | No — No implementation of this alternative packet format. |
| fsc-0083.001 | Standard for message IDs | No — Does not replace FTN MSGIDs with this RFC822-style scheme. | No — Does not replace FTN MSGIDs with this RFC822-style scheme. |
| fsc-0084.001 | Electronic Data Exchange Standard Level 1 | No — No implementation of this alternative packet format. | No — No implementation of this alternative packet format. |
| fsc-0085.001 | Descriptions of the "NOZIP" and "ERX" nodelist flags | Unverified — NOZIP/ERX behaviour has not been audited against this proposal. | Unverified — NOZIP/ERX behaviour has not been audited against this proposal. |
| fsc-0086.001 | Standard Request Information File (SRIF) | No — No external SRIF request-processor interface; Server handles FREQ internally. | No — No external SRIF request-processor interface; Server handles FREQ internally. |
| fsc-0087.001 | File Forwarding | Yes — TIC file forwarding; see current FTS-5006. | Partial — TIC client and hatching; no downlink forwarding. |
| fsc-0088.001 | Compatibility and Link Qualifier Extensions for EMSI Sessions | Partial — EMSI link qualifiers; known negotiation/NRQ limits remain. | No — No EMSI session engine. |
| fsc-0089.001 | INTL addressing control line | No — Uses FTS-4001 INTL, not the alternate INTL: format. | No — Uses FTS-4001 INTL, not the alternate INTL: format. |
| fsc-0090.001 | FTSC Issued Product Codes | See FTA-1005Successor document. | See FTA-1005Successor document. |
| fsc-0091.001 | ISDN Nodelist Flags | Partial — Modern nodelist parser recognises legacy flags; no native ISDN stack. | Partial — Legacy flags are parsed/displayed; not modem or ISDN dialing. |
| fsc-0092.001 | New Control Lines for Forwarded Messages | See FRL-1010Successor document. | See FRL-1010Successor document. |
| fsc-0093.002 | Reduced seen-by lines | No — No reduced-SEEN-BY encoding. | No — No reduced-SEEN-BY encoding. |
| fsp-1001.999 | Time zone information (TZUTC) (superseded) | See FTS-4008Successor document. | See FTS-4008Successor document. |
| fsp-1002.999 | Numeric reply indication in FTN subject lines (superseded) | See FRL-1007Successor document. | See FRL-1007Successor document. |
| fsp-1003.999 | Suggested use of Nodelist Fields (superseded) | See FRL-1001Successor document. | See FRL-1001Successor document. |
| fsp-1004.999 | Standard Fidonet Addressing (superseded) | See FRL-1002Successor document. | See FRL-1002Successor document. |
| fsp-1005.999 | Zone 2 nodelist flags (superseded) | See FRL-1015Successor document. | See FRL-1015Successor document. |
| fsp-1006.999 | Kludge for specifying addition e-mail reply addresses (superseded) | See FRL-1008Successor document. | See FRL-1008Successor document. |
| fsp-1007.999 | Multiple recipient address specification to gateway (superseded) | See FRL-1009Successor document. | See FRL-1009Successor document. |
| fsp-1008.999 | New Control Lines for Forwarded Messages (superseded) | See FRL-1010Successor document. | See FRL-1010Successor document. |
| fsp-1009.999 | Year 2000 issues in FTN software (superseded) | See FRL-1011Successor document. | See FRL-1011Successor document. |
| fsp-1010.999 | Netmail tracking (Via) (superseded) | See FTS-4009Successor document. | See FTS-4009Successor document. |
| fsp-1011.999 | Binkp/1.0 Protocol specification (superseded) | See FTS-1026Successor document. | See FTS-1026Successor document. |
| fsp-1012.999 | Integration of IP-Nodes in the nodelist (superseded) | See FRL-1016Successor document. | See FRL-1016Successor document. |
| fsp-1013.999 | Character set definition in Fidonet messages (superseded) | See FTS-5003Successor document. | See FTS-5003Successor document. |
| fsp-1014.999 | Moderating by Voting echomail distribution system (superseded) | See FRL-1012Successor document. | See FRL-1012Successor document. |
| fsp-1015.999 | Simple E-Mail Attach Transport (S.E.A.T.) (superseded) | See FTS-1025Successor document. | See FTS-1025Successor document. |
| fsp-1016.003 | Automatic configuration of Points in FidoNet | See FRL-1033Successor document. | See FRL-1033Successor document. |
| fsp-1017.001 | FAQ on IP Connectivity Nodelistings | N/A — Reserved FAQ entry; not an implementable specification. | N/A — Reserved FAQ entry; not an implementable specification. |
| fsp-1018.999 | Binkp/1.0 Protocol specification (superseded) | See FTS-1026Successor document. | See FTS-1026Successor document. |
| fsp-1019.999 | Binkp/1.0 optional protocol extension CRAM (superseded) | See FTS-1027Successor document. | See FTS-1027Successor document. |
| fsp-1020.999 | Binkp optional protocol extension CRC Checksum (superseded) | See FTS-1030Successor document. | See FTS-1030Successor document. |
| fsp-1021.999 | Binkp/1.0 optional protocol extension Multiple Batch (superseded) | See FRL-1018Successor document. | See FRL-1018Successor document. |
| fsp-1022.999 | Binkp optional protocol extension Multiple Password (superseded) | See FRL-1013Successor document. | See FRL-1013Successor document. |
| fsp-1023.999 | Binkp protocol extension Non-reliable Mode (superseded) | See FTS-1028Successor document. | See FTS-1028Successor document. |
| fsp-1024.000 | Binkp/1.1 Protocol specification | Partial — binkp/1.1 multi-batch, NR and ND; late post-ACK OPT NR may miss the next file. | Partial — binkp/1.1 multi-batch, NR and ND; late OPT NR cannot change already-made batch offers. |
| fsp-1025.999 | IPv6 colon substitution in the nodelist. (superseded) | See FRL-1019Successor document. | See FRL-1019Successor document. |
| fsp-1026.999 | Translation of a Fidonet Address into an Internet Domain Name (superseded) | See FRL-1026Successor document. | See FRL-1026Successor document. |
| fsp-1027.001 | Binkp extensions: No Dupes mode and No Dupes Asymmetric mode (russian text) | Yes — ND/NDA peer handling and ND delivery confirmation. | Yes — ND/NDA peer handling and ND delivery confirmation. |
| fsp-1028.002 | FTN Address Format | See FRL-1028Successor document. | See FRL-1028Successor document. |
| fsp-1029.002 | Serial number allocation in message IDs | See FRL-1029Successor document. | See FRL-1029Successor document. |
| fsp-1030.999 | Character set definition in Fidonet messages (superseded) | See FTS-5003Successor document. | See FTS-5003Successor document. |
| fsp-1031.001 | Binkp Multiple One-Way Batch Mode | No — No MOW extension negotiation; ordinary multi-batch is separate. | No — No MOW extension negotiation; ordinary multi-batch is separate. |
| fsp-1032.001 | Binkp dataframe compression (PLZ) | See FTS-1029Successor document. | See FTS-1029Successor document. |
| fsp-1033.999 | The ICM flag (superseded) | See FRL-1017Successor document. | See FRL-1017Successor document. |
| fsp-1034.001 | Advanced BSO flow and control files | See FTS-5005Successor document. | See FTS-5005Successor document. |
| fsp-1035.999 | DNS Distributed Nodelist (superseded) | See FTS-5004Successor document. | See FTS-5004Successor document. |
| fsp-1036.999 | IPv6 numbers in the nodelist. (superseded) | See FRL-1036Successor document. | See FRL-1036Successor document. |
| fsp-1037.001 | Squish message-base format | Partial — Squish history importer; not a live Squish message base. | No — No Squish storage/importer. |
| fsp-1038.999 | The INO4 flag (superseded) | See FRL-1038Successor document. | See FRL-1038Successor document. |
| fsp-1039.001 | TIC file format. | See FTS-5006Successor document. | See FTS-5006Successor document. |
| fsp-1040.001 | SRIF file request interface | No — No external SRIF request-processor interface; Server handles FREQ internally. | No — No external SRIF request-processor interface; Server handles FREQ internally. |
| fsp-1041.001 | The BEER nodelist flag | N/A — April Fools proposal; not a mail feature. | N/A — April Fools proposal; not a mail feature. |
| frl-1001.001 | Suggested use of Nodelist Fields | N/A — Nodelist-field recommendations; not a protocol implementation. | N/A — Nodelist-field recommendations; not a protocol implementation. |
| frl-1002.001 | Standard Fidonet Addressing | Yes — FTN zone:net/node.point@domain address parsing. | Yes — FTN zone:net/node.point@domain address parsing. |
| frl-1003.003 | The Distribution Nodelist (was: FTS-0005.003) | See FTS-5000Successor document. | See FTS-5000Successor document. |
| frl-1004.002 | Timezone information in FTN messages | See FTS-4008Successor document. | See FTS-4008Successor document. |
| frl-1005.001 | Via kludge specification | See FTS-4009Successor document. | See FTS-4009Successor document. |
| frl-1006.001 | Binkp - a protocol for transferring FidoNet mail over reliable connections | See FTS-1026Successor document. | See FTS-1026Successor document. |
| frl-1007.001 | Numeric reply indication in FTN subject lines | Yes — Configurable numeric Re^n: reply subjects. | Yes — Optional Re:/Re^n: reply-subject handling. |
| frl-1008.001 | Kludge for specifying addition e-mail reply addresses | No — No dedicated multi-email-recipient gateway workflow. | No — No dedicated multi-email-recipient gateway workflow. |
| frl-1009.001 | Multiple recipient address specification to gateway | No — No dedicated multi-email-recipient gateway workflow. | No — No dedicated multi-email-recipient gateway workflow. |
| frl-1010.001 | New control lines for forwarded messages | Yes — FWD* provenance and forwarding/reply handling. | Yes — FWD* provenance and forwarding/reply handling. |
| frl-1011.001 | Year 2000 issues in FTN software | Partial — Two-digit-year parsing handled; not a whole-stack Y2K certification. | Partial — Two-digit-year parsing handled; not a whole-stack Y2K certification. |
| frl-1012.001 | Moderating by Voting echomail distribution system | No — No voting-based echomail moderation. | No — No voting-based echomail moderation. |
| frl-1013.001 | Binkp optional protocol extension Multiple Password | No — No deprecated multiple-password binkp extension. | No — No deprecated multiple-password binkp extension. |
| frl-1014.001 | Hudson Message Base (HMB) locking semantics | No — No Hudson message-base locking; uses database storage. | No — No Hudson message-base locking; uses database storage. |
| frl-1015.001 | Zone 2 nodelist flags | Partial — Relevant flags/address forms parsed by the modern nodelist implementation. | Partial — Parsed/displayed in the nodelist; only supported client transports dial. |
| frl-1016.001 | Integration of IP-Nodes in the nodelist | Partial — Relevant flags/address forms parsed by the modern nodelist implementation. | Partial — Parsed/displayed in the nodelist; only supported client transports dial. |
| frl-1017.001 | The ICM flag | Partial — Relevant flags/address forms parsed by the modern nodelist implementation. | Partial — Parsed/displayed in the nodelist; only supported client transports dial. |
| frl-1018.001 | Binkp/1.0 optional protocol extension Multiple Batch | No — No binkp/1.0 OPT MB extension. binkp/1.1 multi-batch is a different mechanism (FSP-1024). | No — No binkp/1.0 OPT MB extension. binkp/1.1 multi-batch is a different mechanism (FSP-1024). |
| frl-1019.001 | IPv6 colon substitution in the nodelist. | Partial — Relevant flags/address forms parsed by the modern nodelist implementation. | Partial — Parsed/displayed in the nodelist; only supported client transports dial. |
| frl-1020.001 | Character set definition in Fidonet messages | See FTS-5003Successor document. | See FTS-5003Successor document. |
| frl-1021.001 | Unicode character set in FidoNet messages | See FTS-5003Successor document. | See FTS-5003Successor document. |
| frl-1022.001 | Binkp optional protocol extension CRC Checksum. | See FTS-1030Successor document. | See FTS-1030Successor document. |
| frl-1026.002 | Translation of a Fidonet Address into an Internet Domain Name | Partial — FTN-derived hostnames in DDN; not an email-address gateway implementation. | No — No FTN-address-to-DNS resolution. |
| frl-1028.002 | FTN Address Format | Yes — FTN address parsing and wire formatting. | Yes — FTN address parsing and wire formatting. |
| frl-1029.002 | Serial number allocation in message IDs | Partial — Persistent serial sequencer with Unix-time floor; random fallback on failure. | Unverified — MSGIDs generated; serial-allocation recommendations not audited. |
| frl-1032.001 | Binkp dataframe compression (PLZ) | See FTS-1029Successor document. | See FTS-1029Successor document. |
| frl-1033.003 | Automatic configuration of Points in FidoNet | No — Does not implement this automatic point-configuration protocol; setup links are separate. | No — Does not implement this automatic point-configuration protocol; setup links are separate. |
| frl-1034.001 | Advanced BSO flow and control files | See FTS-5005Successor document. | See FTS-5005Successor document. |
| frl-1035.001 | DNS Distributed Nodelist | See FTS-5004Successor document. | See FTS-5004Successor document. |
| frl-1036.001 | IPv6 numbers in the nodelist. | Partial — Relevant flags/address forms parsed by the modern nodelist implementation. | Partial — Parsed/displayed in the nodelist; only supported client transports dial. |
| frl-1038.001 | The INO4 flag | Partial — Relevant flags/address forms parsed by the modern nodelist implementation. | Partial — Parsed/displayed in the nodelist; only supported client transports dial. |
| frl-1039.001 | Tic file format | See FTS-5006Successor document. | See FTS-5006Successor document. |
| frl-1040.001 | PING and TRACE flags | See FTS-4010Successor document. | See FTS-4010Successor document. |
| fta-1000.003 | FTSC Charter | N/A — Reference or administrative document; not a software feature. | N/A — Reference or administrative document; not a software feature. |
| fta-1001.007 | FTSC Operations | N/A — Reference or administrative document; not a software feature. | N/A — Reference or administrative document; not a software feature. |
| fta-1002.003 | Document Submission and Publication Standard | N/A — Reference or administrative document; not a software feature. | N/A — Reference or administrative document; not a software feature. |
| fta-1003.033 | FTSC Membership List | N/A — Reference or administrative document; not a software feature. | N/A — Reference or administrative document; not a software feature. |
| fta-1004.025 | FTSC File List | N/A — Reference or administrative document; not a software feature. | N/A — Reference or administrative document; not a software feature. |
| fta-1005.003 | FTSC Product Codes | Yes — Product-code recognition; emits the unallocated-product code. | Yes — Product-code recognition; emits the unallocated-product code. |
| fta-1006.002 | Key words to indicate requirement levels | N/A — Reference or administrative document; not a software feature. | N/A — Reference or administrative document; not a software feature. |
| fta-1007.002 | Intellectual Property Rights | N/A — Reference or administrative document; not a software feature. | N/A — Reference or administrative document; not a software feature. |
| ftscprod.020Numbering restarted; order follows the latest dated registry entry, not the filename suffix. | FTSC Product Codes | Yes — Product-code recognition; emits the unallocated-product code. | Yes — Product-code recognition; emits the unallocated-product code. |
No matching documents.