Subj : alternate routing chart
To   : Foxy Ferguson
From : Carl Austin Bennett
Date : Tue Apr 17 2001 03:20 pm

 FF> Odd. I don't _ever_ recall even *suggesting* to anyone that they should 
 FF> publicly distribute their own private little list, just that they should 
 FF> compile and maintain their own. For their own internal use, of course. 

That doesn't make any sense. If every affected node has to do this, this 
creates unnecessary duplication of effort. Much better that any node with an 
accurate and usable list share it with the rest of us as one's sorely needed.

 FF> As for those "existing channels", the one ya'll used is for RECs to hatch 
 FF> their region lists such that the ZEC gets it and for the ZEC to hatch the 
 FF> zone list.

Maybe the list should be hatched in an area where it's accessable to more 
people... such as every node in zone one. No point in creating a list if it 
isn't available to anyone and everyone that might have a use for it, eh?

 FF> None of those individuals (including myself) has the privilege of hatching 

 FF> anything OTHER than the specified file for which they are responsible.

To specify what should be in the route files hatched by the various RECs, there 
would have to be a moderator and a set of posted rules, much like in an echo. 
I've asked if anyone has such a document for Z1_REC and come up empty.

--- Msged/LNX TE 06
 * Origin: Pause-Cafe Kingston 613-549-5599 telnet:cafe.dyndns.org (1:249/116)

.