Hi Carol!

22 Oct 04, Carol Shenkenberger wrote to Vladimir Donskoy:

 VD> CS>> Sorry, I was thinking you knew.  There's a specification out there
 VD> CS>> that by design actually assigns netnumbers to regions.

 VD>> Where it is write - FTS, Policy or another official document?

 CS> Netnumbers to regions?  FTS I think.  I'm not totally sure.  Once in a
 CS> while it comes up.

No, is not FTS for this numbering. It is only:

=== Begin FTS-5000 ===
Field 2 - Zone/Region/Net/Node number

     This field contains only numeric digits and is a number in the
     range of 1 to 32767.  If the line had the "Zone", 
"Region",  or
     "Host" keyword,  the number is the zone, net, or region number,
     and the node has an implied node number of 0, therfore the use of
     a 0 in this field is strictly forbidden.  Otherwise,  the
     number is the node number. The zone number, region or net number,
     and the node number, taken together, constitute a node's FidoNet
     address.

     Zone numbers must be unique.  Region or net numbers must be
     unique within their zone.  Hub numbers must be within their net.
     Node numbers must be unique within their region (for regional
     independents) or net (for members of a local network).  Duplicate
     node numbers under different hubs within the same net are not
     allowed.
=== End ===

So - number of Region must be unique, and no more! But count of regions (or
networks) is undefine.

 VD> CS>> In Z6, RC's start with 6:6#/# and in Z1 they are 1:1#/# but it
 VD> CS>> varies outside that a bit.

 VD>> Now these zones very small, and theirs regions have not
 VD>> more 20 sysops (in middle)... Regions on Z2 have from 1 to

 CS> True, but the discussion was on the overall design system that has been
 CS> used, not the actual size.

 VD>> near 4500 sysops, in middle - 100 nodes per region.
 VD>> Arithmetic: our region's count of sysops (4500) divide by
 VD>> 100 (nodes per region) - result 45 regions. If divide by 20
 VD>> (as other zones) - result 225 regions (very large! It is
 VD>> impossible for control!).

 CS> Well, I'd start thinking small and work around as needed.  I'd tend to
 CS> start with 10 if starting a new Z7.

Z6? Not new, but exist - what will modify.

 CS> There will be enough trouble just splitting that way.  Sees more 'do-able'
 CS> to me looking in from the outside and considering the task.

Yes, it's possible.

 CS>  * OLX 2.1 TD * Unable to locate Coffee -- Operator Halted!

Well, looking for Tee :-) .

Regards, Vladimir

--- GoldED+/W32 1.1.5-040321