Subj : Z1_REC
To   : Bob Seaborn
From : Carl Austin Bennett
Date : Tue Apr 17 2001 06:52 am

 BS> First of all, you do NOT have permission from me to make reference to
 BS> 1:140/1, REC17, or for that matter, ANY net in region 17, since you 
 BS> do not have specific permission from either RC17, REC17, or the NC of 
 BS> the net in question.  Accordingly, please remove ANY and All 
 BS> reference to 1:140/1, REC17, or the R17 nets until you do have such 
 BS> permission in verified writing.

Does this mean that you are not a valid inbound route for ERN destined to the 
REC12 system or its downlinks?

I've had the routes 379/1 <-> REC12 and REC17 <-> REC12 reported to me but had 
had some misgivings at the time about using the latter due to the current 
political games being played. Is REC17 <-> REC12 a valid route or is it bogus?

 BS> Secondly, the Z1_REC fileecho was founded by myself on behalf of the
 BS> REC's of zone 1, and the ONLY hatch permissions granted were for each 
 BS> REC to hatch out his regional routing chart.  Nothing more!  

This is interesting... you are completely incapable of grasping the concept 
that REG12 is a restricted administrative echo and allow out-of-region sysops 
to post, yet you lambaste REC12 for hatching a route list into Z1_REC.

Something doesn't quite mesh here, Bob!

 BS> Only the ZEC1 has the authority to hatch the zone 1 routing chart in
 BS> Z1_REC, therefore it is incumbent upon you, or those that you are 
 BS> fronting for, to supply the ZEC1 with files that you wish hatched in 
 BS> Z1_REC, and to NOT hatch anything other than your own regional 
 BS> routing chart.

If Z1_REC were a moderated echo (and restricted echo isn't enough as REC12 has 
the right to be there) may I ask where a copy of the .RUL file can be found?

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

.