Hi Joe,

 >  JD>     
 >  JD> Since nobody but Z1 will ever see it that way, because Malcolm
 >  JD> converts it anyway, there is no problem.
 >
 > Malcolm only "converts" for the the Zone 3 segment, 
 > he does not convert for
 > other Zones (as those segments are not his to convert)...

 JD> I was under the impression that he also converted the IC nodelist.

Malcolm would need to clarify this exactly himself, however my
understanding is that he attempts to protect Zone 3 Sysops, as the 000-*
issue is specific to Aus Sysops and nowhere else. So the FULL NODELIST
(with 000 made safe) he generates for Z3, and the Z3 SEGMENT he releases to
the other ZC's that are massaged to make them "Safe" for their
respective users.

 >  > The reality of this situation is that a different
 >  > "convention" implemented b
 >  > ONE zone does not stop other Zones attempting to
 >  > interpret it as a (invalid)
 >  > Telephone No.
 >
 >  JD> Setting your translation table to NOT dial any 
 >  JD> number with 000 will
 >  JD> solve the problem.
 >
 > But that does NOT stop anyone attemting to reach IP 
 > 0.0.0.0 (000-0-0-0-0).
 >

 JD> And they will reach nothing.  

Please see my message to Dan about that one, it is very platform specific
and may in fact go somewhere.

 JD> However, most have DNS or IP in other
 JD> places, using flags, or in in the system name field.

If that really is the case, then why is 000-* still needed then?

Cheers............pk.


--- Maximus/2 3.01