TIP: Click on subject to list as thread! ANSI
echo: net_dev
to: Mel Pheasant
from: joaquim homrighausen
date: 1995-03-27 16:05:34
subject: Minimum requirements for compliance

> Well, it is technical - due to the fact that some platforms
 > cannot support higher than FTS1. The politics only dictate
 > whether or not we continue to support them :(

I disagree. Why would it be so hard to support FTS-6 (or even EMSI) for
these platforms? In FTS-6, there's SEAlink. Nothing says that SEAlink
_must_ have a NN-block window, it has a block zero with file information,
and block numbers and their complements accompany ACKs and NAKs.

Zmodem might be a hill too steep for these platforms, but EMSI with
"SLK" (SEAlink) oughta work just fine. CRC code doesn't have to
be table driven (if code/data space is an issue).

 > Yes, in N.A. for the most part, ISDN=It Still Does Nothing.

Right, but the FTS-1 requirement is Fido-wide, not specific to Z1.

 > Also, you realize, there are nodelist flags at least for
 > this, right? If we had a nodelist flag specifying FTS1 only,
 > some problems would be cleared up, since you wouldn't try to
 > call them if you couldn't.

But there are no approved ISDN flags (which I can't quite understand),
there are many combinations of "ISDN" flags. V120,
"U,ISDNC", "ISDNC", "ISDN", etc. etc.

And, in the case of ISDN, the situation isn't quite the same. An ISDN node
knows that it can only call other nodes with ISDNxxx in their nodelist
entry. An FTS1-only capable node wouldn't know if the system it's trying to
call is FTS-1 capable, unless you turn it around and have a
"NOTFTS1" (or something) flag. That should take care of it.

 > Well, to be honest, this is true, but this is something that's
 > just not under our control.

Nor is a node that's behaving in a "excessively annoying manner".
What I mean is that if the line is to be drawn, it should be drawn the same
in all cases. If you cannot communicate, you cannot participate - but that
isn't the case at present.

 > Well, this is choice really, and again I don't see the problem
 > hanging around for long, due to firmware upgrades and V.34.

And the majority of nodes may not have been affected by the problem. But
I'm sure there are those unlucky enough to run software that has spent
hours trying to connect their new Neato-Whizz-Bang-VFC modem to another
"VFC" modem and gotten nothing but failed handshakes - and then
noticed it the next time the individual happen to browse the logs (or the
phone bill arrives).

 >> In the ISDN case, who's breaking policy? The ISDN nodes or
 >> the analog nodes?

 > Tough call :).

No sh*t :-)

---
* Origin: Absolute Solutions (2:270/17.6)
SEEN-BY: 10/8 1650 11/157 13/13 50/99 104/821 105/69 103 330 115/2 153/920
SEEN-BY: 170/400 201/505 209/720 260/1 261/1023 270/101 102 103 280/1 282/1
SEEN-BY: 332/1 353/218 357/1 396/1 620/243 632/348 640/75 201 206 217 305
SEEN-BY: 640/820 822 823 690/660 711/409 410 413 430 431 807 808 809 816 934
SEEN-BY: 712/515 713/888 800/1 1000/1 2605/606 2613/5 3615/50 3619/25
SEEN-BY: 7877/2809
@PATH: 270/17 24/24 396/1 270/101 209/720 640/820 711/409 808 809 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.