then there'd be a sible field with all the "system flags" - flags that
apply to a fido system rather thanto the connection requirements,
(flags like NEC or UUCP flags would be examples of this)
instead of commas "," they'd be separated using semicolons. ";"
that's mean that they could be treated as a lump when reading the line and
the start of the connection information is indicated by the next comma.
following that on the same line would come any number of connections,
a connection consists of three fields, the first filed is type specifier,
to specify the type of the connection, for example POTS (regular dial-up
modem) or IP (internet), ISDN, the second fields is the address,
for a dialup node it's be the international telephone number, for IP it's
be the IP address or domain name, etc...
private, down, or other uncontactable nodes nodes wouldn't have any connections
listed
eg:
someone with multiple dial-up modems cpould list them all against a single
node entry in the nodelist,just by repeating the POTS,phone-numbe,flags
for each modem or possibly listing all the phone numbers with semicolons
if the modems all have the same capabilities.
new types of conection could be added by using a different connection-type
keyword as mailers would be written to ignore connection types they
couldn't handle...
some exalples of connection types.
POTS - regular dialup modem
ISDN - isdn digital connection
IP - intenrnet connection (maybe it should be divided into
protocols like TELNET,IREX,FTP,EMAIL,BINKP)
VIA - specify some other node to accept the packets.
Mark Lewis has a different proposal that in some ways follows the existing
nodelist more closely and uses multiple lines to list some nodes,
I'll let him explain it as he understands its intracisies better than me.
-=> Bye <=-
*---/
-=> Bye <=-
---
* Origin: Drive defensively. Buy a tank. (3:640/531.42)