Subj : proposed new nodelist
To   : Goran Eriksson
From : Jasen Betts
Date : Tue Jul 16 2002 12:43 pm

Hi Goran.

14-Jul-02 11:07:00, Goran Eriksson wrote to Haakan Karlsson

 HK>> As long as all the needed information is included in the new
 HK>> format, the compatibility issue can be easily solved by a
 HK>> convertion program that outputs an old style nodelist that can
 HK>> serve as input to the old software.

 GE> There are at least a few cases where such a conversion isn't quite
 GE> straightforward

 GE> Firstly, how would you a convert a hub, host, region or zone entry
 GE> that doesn't announce any POTS capability

FTS-0005, 5001 etc say nothing whatsoever about how to crash-mail a PVT node
(what document covers crashmail addressing? )

 GE> Secondly, how would you convert a zone or region independent entry
 GE> that doesn't announce any POTS capability? (I know that the
 GE> current practice is to use the Hold keyword for indefinite periods
 GE> of time. That means a redefinition of the meaning of the Hold
 GE> keyword I'm not very fond of.

Yeah, anything that stops mail from flowing without atleast producing an
error message is a bad thing.

I'd suggest automatically routing it theough their ZC RC or NC by putting
that phone number on the ION. :-)


Hmm a similar problem already exists:
what if a point wants to crashmail someone flying the LO (listed only)
flag.


Hmm, does anyone know what's an "RVIA" flag for and where is it documented?

 -=> Bye <=-

---
 # Origin: Only God can make random selections. (3:640/531.42)
 * Origin: Baddog BBS (1:218/903)

.