From Leonard Erickson · 1996-04-05 05:04 · #73011 in FREE25
In reply to NET_DEV by Jason Steck
-=> Quoting Jason Steck to Pierre Phaneuf <=- JS> This is exactly the kind of direction I was going in -- instead of JS> "mandating" the old FTS-0001 XModem session, the technology end of JS> things should only document an open-ended session negotiation method JS> (such as EMSI supplemented by certain information contained in a new JS> nodelist) which would allow systems to negotiate from among a range JS> of standards. I think you are mising the point here. The reason FTS-1 is "mandated" is quite simple and has little to do with any "vocal minorities". It is required so that regardless of what *else* systems may support, they will always have at least *that* as a common protocol. Any workable network that includes the idea that any node should be able to connect "directly" to any other node *has* to mandate support of some *one* item, so as to ensure that there is a common protocol in *any* possible connection. Negotiating from a range of standards is fine. And EMSI does allow this. But if you *don't* require that everyone support a particular one of those standards, then what happens when two systems try to negoiate but don't have any standards in common? That's the main reason FTS-1 has hung on. Neither FTS-6 nor EMSI are "inter-operable". So if I'm running FTS-6 and you are running EMSI with no FTS-6 support, we can't communicate. So to get rid of FTS-1, they'd have to *require* support of *either* FTS-6 or of EMSI. And that results in complaints from two vocal *majorities*. (well not *really* majorities, but I daresay each side would number 35-45% of Fidonet) The continuing support for "obsolete" systems is more of a bonus "side effect". You can't have a network without some sort of minimal standard of compatability. For Fido, it's FTS-1. For the Internet it's RFC-820(?) and RFC-1036 (mail and news specs). ... Emergency repair procedure #1: Kick it. --- Blue Wave/DOS v2.30 * Origin: Shadowshack (1:105/51)