BF>> Well, you've now seen my attempts. I'm sure that with you BF>> onboard the FTSC could really start making a difference, cleaning BF>> out all the dusty old stuff and paving way for some novelties.
AL> FTS-1 really could be split into several documents. The stored message AL> definition section is useful information, but not absolutely required AL> for a FTS-1 compatible implementation. The packet header and packed AL> message definitions are the key components to how things work in AL> FidoNet. The FTS-1 session protocol is largely obsolete, although in AL> theory any dialup node is required to support inbound FTS-1 sessions AL> during their Zone's Mail Hour.
Some of this has been spoken about years ago then forgotten about.
Andrew Leary is spot on.
Policy4 refers only to FTS-1 with regards to ZMH. Obviously this only applies to the small number of dialup nodes we have in 2018, relative to Internet nodes.
For dialup nodes, honouring ZMH was (and still is) the absolutely bare minimum necessary to be nodelisted. Their phone number could be freely used for BBS/voice/fax/other services outside ZMH. There were a few dialup nodes in the mid '90s that operated that way.
Expanding on Andrew's suggestion, I propose that:
1. FTS-0001.017 should be issued, superceding FTS-0001.016.
2. The newly issued FTS-0001.017 is used solely as a reference document that only points to other documents, for ease of maintenance.
3. FTS-0001.016 should be renamed FSC-0001.016 to be used as an historical reference, and is otherwise left completely untouched. This completely bypasses potential issues with the document's copyright.
4. We prioritise documenting the required (non-optional) parts of a compatible node, especially Internet nodes, as they are the obvious majority of FidoNet in 2018.
5. Ensure these parts are documented separately, again for ease of maintenance, and refer to them in the new FTS-1.
6. (optional, but probably sensible) Have FTS-0001.017 refer to (and apply to) FSC-0001.016 in the case of remaining dialup nodes. Effectively this would mean the new FTS-1 would apply only to Internet nodes. This could obviously change in future as the need arises, with further issues of FTS-1.
7. Re-document the optional parts (eg. stored message format) as time and interest permits. In the interim simply refer to the appropriate section in FSC-0001.016.
Regards Andrew
--- GoldED+/BSD 1.1.5-b20180707 * Origin: Blizzard of Ozz, Melbourne, Victoria, Australia (3:633/267)
