| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: ZC/2-status |
Hi Carol! 14 Oct 04, Carol Shenkenberger wrote to Vladimir Donskoy: VD> CS>> Not a problem. It was an unused one. We have 7 unused ones. I VD> CS>> think only Z1 and Z2 use the full quota. Z2 has more than 10 VD> CS>> already so it's not a pure '10 per zone' in the design. VD>> What do you read about "quota for count of RCs in Zone"? It VD>> is nonsense IMHO... CS> Sorry, I was thinking you knew. There's a specification out there that CS> by design actually assigns netnumbers to regions. Where it is write - FTS, Policy or another official document? CS> Most regions pretty much have a slot of 10 possible RC's but there's a CS> bending of that so that Z2 has more and the numbers kinda arent so CS> automatically obvious to the eye. For example, own region have number 50 :-) . But maximum number of region in Zone2 is 55 (minimum - 20). CS> In Z6, RC's start with 6:6#/# and in Z1 they are 1:1#/# but it varies CS> outside that a bit. Now these zones very small, and theirs regions have not more 20 sysops (in middle)... Regions on Z2 have from 1 to near 4500 sysops, in middle - 100 nodes per region. Arithmetic: our region's count of sysops (4500) divide by 100 (nodes per region) - result 45 regions. If divide by 20 (as other zones) - result 225 regions (very large! It is impossible for control!). So - I think what we need from 20 to 100 (number of federal areas in Russia, plus samething for old sysops and another countries) regions. But certain networks may join to other, so - real number of regions will low then maximum. Vladimir --- GoldED+/W32 1.1.5-040321* Origin: DVB Station (2:5020/2992) SEEN-BY: 633/267 270 5030/786 @PATH: 5020/2992 715 292/854 140/1 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.