From Paul Edwards · 1996-04-03 06:36 · #73048 in FREE25
PE> What about FTS-0501 (just out of curiosity)? BFN. Paul. JS> Where can the FTS-05?? documents be obtained (ftp if possible)? If they No, I don't have ftp. If you just keep connected to this echo, you see them when they come out. Probably easier to just keep a large messagebase. I will post the latest draft (ie not approved) of FTS-0501, as it fixes some glaring typos. JS> are really cleaner and more complete than the old FTSC versions, than they JS> may integrate into the OmniNet Technical Library more readily. Well, if they aren't clean and complete, I want to know about it, to FIX that. Bear in mind that the only one I have done so far is meant to describe the PKT format. Feel free to modify/integrate etc any of the FTS-05* specs, they are public domain for that reason. JS> Also, does the 0501 spec include the 2.2 format in addition to the 2 and 2+ No it doesn't. Type 2.2 would make it incompatible with Type 2. As an extension for cooperating systems, it should be included somewhere. JS> format? 2.2 is a very nice format, IMHO, much cleaner and more capable JS> than any other type 2 derivative. Of course, I support all three in my So is RFC-822 most likely. I'm not sure where the boundary is. You see, I modified Type 2+ to make sure it was compatible with Type-2, by mandating a product code of 0 for new applications, which indeed is no different to the FTSC and their x'FE'. Even if there ever was a point in identifying every mailprocessor in the world so that you can find out something which you rarely need to know anyway, and can find out by asking the person sending you the mail in the first place, since it was sent direct. BFN. Paul. --- * Origin: X (3:711/934.9)