I just recently came across FTS-5005 (Advanced BinkleyTerm Style Outbound flow
and control files) and I have some feedback.

First off, it's great that a specification like this is finally being
published. I've been going off 20+ year scraps of docs (e.g. BT-REF.TXT) for
our BSO/FLO support in SBBSecho and it's nice to see something more formal and
potentially more current or accurate. So, thanks!

On the document's contents, I noticed something that glared at me and I thought
I should share in hopes it may (if you agree) be changed in a future rev:
*.?ut (i.e. .out, .cut, .hut, .dut) files are FTN packets, not flow files. The
contents of these files conform with the "Packet Header" and "Packed Message"
definitions in FTS-1. While the file *name* may be BSO/FLO specific, the
contents most definitely are not. In fact, BSO mailers rename these files to
*.pkt before they are sent to a remote mailer (as noted in FTS-5005), further
emphasizing that these files are indeed packets.

"Flow files" are the *.?lo files used to direct a BSO mailers outbound activity
which are plain text files and held in contrast to packets, which are binary.

If you need references, see the BinkleyTerm docs (e.g. BT-USER.TXT, BT-REF.TXT)
which clearly differentiate between "packets" and "flow files". They're not
synonymous.

No insult or offense intended, so I hope none is perceived. Thanks,
--- SBBSecho 2.27-Win32