ftp.wwiv.com

home *** CD-ROM | disk | FTP | other *** search

/ ftp.wwiv.com / ftp.wwiv.com.zip / ftp.wwiv.com / pub / HATCH / WWIVNEWS.ZIP / 9403_2.NWS < prev next >

Wrap

Text File | 1994-03-02 | 18KB | 501 lines

will be a problem. Somewhat contrary to my recommendations, Wayne has asked that each GC (who may if they wish designate some work to the ACs) leave "gaps" for growth when renumbering the group. Thus, there would be an attempt to keep the area codes together. For a group that is as large as group 4 (380 some odd nodes at last count), the matter creates some problems. For example, Wayne's recommendation was for a small area code using say AC01-AC03 that room be left so that it could grow up to AC10. For larger area codes like the Austin or Montreal area, more room would be left in the gap. THE FIRST TEST - RENUMBERING GROUP 4 ──────────────────────────────────── My problem in renumbering group 4 was that I ran out of numbers before getting through all of the areas. I tried renumbering the larger groups and leaving less room for growth, but that ultimately created some problems as well. I can do this under our current structure, but I feel that it will only be a short time before all of the numbers get "mixed up" anyway. My initial recommendation was to split Group 4 into two groups. The new group - let's call it group 15 - would consist of the following large area codes plus whatever smaller area codes might wish to join it: 512 -- Austin area having approximately 40 boards at present 614 -- Ohio area having approximately 25 boards 904 -- Florida area having approximately 30 boards This would a) reduce Group 4 by a third and still leave it as one of the largest groups in the network, b) create a new group of 95 boards or more which would not be the smallest group in the network, c) facilitate the renumbering of the nodes so that "gaps" for growth could be more easily established and maintained. While this was being formulated, Wayne became concerned that making too many changes at one time would be detrimental to the process. Thus, the initial proposal for the Group 4 split turned out to be what will happen initially: 1) Area Codes 512, 614, and 904 will be allowed to form Group 15 under H2O Doc as GC for that group. 2) The remaining boards in Group 4 will stay in Group 4 until after all renumbering has been accomplished. Then, the matter of a separate Group for the Canadian Boards and for the other Foreign Systems will be addressed. As a consequence of these changes, here is the revised listing for Group 4 as sent to Wayne: ───────────────────────────────────────────────────────────────────────────── Servers & Group Coordinator ─────────────────────────── 4000 2050 4001 1040 4002 1042 4003 1046 4020 - 4070 for Area Code 210 ───────────────────────────── 4020 2051 4021 2053 4022 2054 4023 2058 4024 2059 4025 2060 4026 2061 4027 2062 4028 2067 4029 2068 4030 2069 4031 2072 4050 2076 4051 2077 4052 2078 4053 2079 4054 2081 4056 2082 4057 2085 4058 2086 4059 2087 4060 2088 4061 2089 4062 2091 4063 2092 4064 2093 205 is reserved 4110-4129 ───────────────────────── 4110 2501 4111 2502 4112 2503 4113 2509 4114 2533 4115 2534 4116 2535 4117 2536 4118 2545 216 is reserved 4130-4149 ───────────────────────── 4130 2654 4131 2656 4132 2657 4133 2658 4134 2659 4135 2660 4136 2661 4137 2662 4138 2664 4139 2665 218 is reserved 4150-4159 ───────────────────────── 4150 2850 4151 2860 4152 2861 219 is reserved 4160-4169 ───────────────────────── 4160 2950 4161 2951 4162 2952 309 is reserved 4190-4199 ───────────────────────── 4190 3900 4191 3905 502 is reserved 4200-4219 ───────────────────────── 4200 5207 4201 5208 4202 5210 4203 5211 4204 5212 4205 5213 4206 5214 4207 5215 4208 5216 507 is reserved 4220-4229 ───────────────────────── 4220 5702 4221 5703 601 is reserved 4230-4239 ───────────────────────── 4230 6101 4231 6102 602 is reserved 4240-4259 ───────────────────────── 4240 6205 4241 6211 4242 6214 4243 6216 4244 6219 4245 6222 4246 6223 4247 6224 4248 6225 4249 6228 4250 6229 613 is reserved 4260-4269 Canada ───────────────────────── 4260 6350 4261 6351 605 is reserved 4270-4279 ───────────────────────── 4270 6503 4271 6504 606 is reserved 4280-4289 ───────────────────────── 4280 6600 607 is reserved 4290-4299 ───────────────────────── 4290 6706 4291 6707 4292 6710 4293 6711 403 is reserved 4300-4309 ───────────────────────── 4300 4300 4301 4301 701 is reserved 4310-4329 ───────────────────────── 4310 7101 4311 7102 4312 7103 4313 7107 4314 7109 4315 7111 4316 7112 4317 7116 4318 7117 4319 7122 4320 7123 4321 7124 708 is reserved 4330-4339 ───────────────────────── 4330 7805 4331 7806 4332 7807 4333 7808 812 is reserved 4340-4369 ───────────────────────── 4340 8251 4341 8252 4342 8253 4343 8254 4344 8255 4345 8257 4346 8258 4347 8259 4348 8261 4349 8262 4350 8265 4351 8266 4352 8267 4353 8268 4354 8270 4355 8271 4356 8273 4357 8280 4370 - 4349 Currently reserved for "Foreign Nods" ───────────────────────────────────────────────── 4370 - 4389 United Kingdom ───────────────────────── 4370 810 4371 812 4372 813 4373 814 4374 815 4390 - 4409 Spain ───────────────── 4390 871 4391 872 4392 873 4410 - 4429 Okinawa ──────────────────── 4410 850 4411 852 4412 853 4413 854 4414 855 4415 856 4416 857 4417 858 4418 860 4419 861 4420 862 4421 863 4422 864 414 is reserved 4450-4479 ───────────────────────── 4452 4452 4453 4453 4454 4454 4455 4455 4457 4457 4459 4459 4460 4460 4461 4461 4463 4463 4468 4468 4470 4470 4471 4471 4475 4475 514 is reserved 4500 - 4599 Montreal Canada ─────────────────────────────────────────── 4500 5450 4501 5451 4502 5452 4503 5454 4504 5456 4505 5457 4506 5458 4507 5459 4508 5460 4509 5461 4510 5462 4511 5463 4512 5464 4513 5465 4514 5466 4515 5468 4516 5469 4517 5473 4518 5474 4519 5475 4520 5477 4521 5479 4522 5480 4523 5481 4524 5482 4525 5485 4526 5486 4527 5487 4528 5489 4529 5490 4530 5491 4531 5493 4532 5495 4533 5496 4534 5497 4535 5498 4536 5499 4537 15451 4538 15465 4539 15482 4540 15498 4541 25451 4600 - 4610 Ontario Canada ─────────────────────────── 4600 5950 4601 5958 204 is reserved 4610-4619 Winnipeg Canada ────────────────────────────────────────── 4610 2402 4611 2404 4612 2405 306 is reserved 4620-4639 ───────────────────────── 4620 13600 4621 13602 4622 13604 4623 13605 4624 13606 4625 13609 4626 13611 4640 - 4650 Mexico ─────────────────── 4640 831 4641 832 409 is reserved 4900-4920 ───────────────────────── 4900 4900 4901 4901 4902 4902 4903 4903 4904 4904 4905 4905 4906 4906 4907 4907 4908 4908 4910 4910 4911 4911 4912 14903 4913 24903 419 is reserved 4950-4959 ───────────────────────── 4952 4952 4956 4956 4957 4957 4958 4958 4960 - 4999 Special Numbers ──────────────────────────── 4960 509 4961 520 4962 645 4963 645 4964 650 4965 651 4966 652 4967 655 4968 693 ───────────────────────────────────────────────────────────────────────────── As mentioned above, I have also recommended to Wayne that "foreign" nodes be assigned a special group range. The groups would be assigned according to the numbers listed below, but still be maintained under current groups. This means - if the suggestion is accepted - that Montreal, Mexico, and Okinawa - all currently in Group 4 - would be numbered as if they were outside our group, but I would still maintain their node numbers for them until such time as each had grown large enough to function as a separate group. The foreign countries would be renumbered as follows: 40xxx - 49xxx for use by foreign countries further subdivided as: 40001 - 40999 Canada 41001 - 41999 Mexico 42001 - 42999 Central & So. America (no Nodes there now) 43001 - 43999 Asia (including Japan & Okinawa where we do have boards) 44001 - 44999 Europe ───────────────────────────────────────────────────────────────────────────── "WE SHALL ACHIEVE, BEFORE THIS DECADE IS OUT..." ──────────────────────────────────────────────── So, now that we had an idea of how things needed to be renumbered, it became necessary to conceive a set of procedures on how this would be carried out. In essence, the renumbering is slated to go like this: Step 1 ────── For a short period of time, we will run "dual" networks. This one and a "temporary one" called WW4net. Step 2 ────── Initial traffic on WW4net will be limited to e-mail and updates. The idea is that we will send an update to everyone that will be the "starter" for this network. You will then add the new network in INIT and put your new node number for it. After the network has analyzed that update, you will send an e-mail to your GC stating that you have accomplished adding the new net. The receipt of that e-mail will be confirmed by me. If you do not get my confirmation back in a reasonable time period, you should write again. Step 3 ────── Once all nodes or a high percentage of them have confirmed the establishment of the new network, we will move to the next phase which will involve subscribing to subs on the "new" network. Once you start receiving a sub on the "new" network, you should drop the old one so that it will not have traffic on it. Over a short period, these procedures will "kill" the old network, subs and all, and establish the new one. Once things seem to be functioning fully, Wayne will send a notice to all sysops asking them to delete the old network and rename WW4net to WWIVnet. There will probably be some utilities written to facilitate various aspects of this, but part of our desire is to minimize the amount of DEAD.NET that will occur. FILO'S RENUMBERING SURVIVAL GUIDE ───────────────────────────────── Now, since things are still a tad bit nebulous right now, and some people may still be a bit confused about what's going on and what's being planned, I prepared this "Survival Guide" to help answer the most frequent questions about the renumbering. The guide is in two parts - one answering the "why" questions, the other answering the "how" questions. ───────────────────────────────────────────────────────────────────────────── GC's Survival Guide for Node Renumbering Part One -- March 29, 1993 Revised -- January 29, 1994 Q: Why must we renumber WWIVnet nodes? A: The telephone company will soon be using telephone numbers in the USA that do not have 1 or zero as a middle digit in the area code. If the node numbering scheme is not changed, those area codes will not be able to be a part of WWIVnet. Q: Why don't we use an alpha-numeric or long integer approach to node numbering. A: Basically this would require a major re-write of network and BBS software. The following plan should meet our current and foreseeable future needs. Q: What is the general outline of the new plan. A: The plan uses a GNNN or GGNNN node numbering system. Node numbers will initially be assigned as follows: Group 1 GC : 1000 Group 1 Servers : 1001 - 1019 Group 1 Nodes : 1021 - 1999 Group 2 GC : 2000 Group 2 Servers : 2001 - 2019 Group 2 Nodes : 2020 - 2999 ... Group 10 GC : 10000 Group 10 Servers : 10001 - 10019 Group 10 Nodes : 10020 - 10999 Group 11 GC : 11000 Group 11 Servers : 11001 - 11019 Group 11 Nodes : 11020 - 11999 ... Group 65 GC 65000 Group 65 Servers : 65001 - 65019 Group 65 Nodes : 65020 - 65534 Node 65535 reserved In other words, the first node G000 of each group is reserved for the GC of the group. The next 19 nodes are reserved for server systems. The remaining node numbers are for node assignments. This allows us to have 64 groups of 999 nodes each. Nodes with 3 digits are less will be reserved for charter systems and/or very special purposes. Group 65 will be a smaller group due to the limitation of the maximum short integer. Q: How does this new node numbering plan affect network administration? That is, will there still be group and area coordinators? A: Yes, the network will continue to have a 3-tiered administration: Net Coordinator, Group Coordinators, Area Coordinators. Area Coordinators will still be defined by area code, even though their node number does not reflect their area code. Q: How will the new node numbers be assigned? A: The GCs, perhaps with assistance from their ACs, will assign node numbers within their block of numbers. It is recommended that the numbers be assigned sequentially with some unassigned node numbers (UNNs) built into the sequencing in order to facilitate node number assignments by ACs as growth occurs. For example, let us say that Group 1 has the following area codes and nodes within it to begin with: Area Code Number of Nodes 301 30 407 45 519 32 Node numbers should be assigned sequentially with ten or more (round to the next highest 10) UNNs per area code. For example: Area Code Node Numbers Assigned Unassigned for AC use 301 1020-1050 1051-1059 407 1060-1105 1105-1119 519 1120-1152 1152-1169 Once an area coordinator has used up the original 10+ UNNs assigned initially, then the GC should assign that AC an additional 10 UNNs to work with. For example, let us say that area code 407 used up the UNNs assigned to it originally (1105-1119) and needed more numbers; then the GC would assign the next 10 unused numbers (1170-1179) for use. The GC should NOT attempt to develop a structure that would always keep a block of numbers available for an area as eventually that method would break down. Q: When should the GC begin to make new node number assignments? A: The GC may do this at any time; HOWEVER, the new assignments will NOT BE EFFECTIVE until a future (as yet undesignated) date. We plan to develop software which will take all node assignments in files such as SUBS.XTR, DEAD.NET, Sxxx.NET, Zxxxx.NET, Nxxxx.NET, and the headers for messages, and convert that information to the new format. If we are successful in this, then we will have a method to convert all existing data to the new format with a minimum of trouble for the sysops of the network and with a minimum loss of information and messages. It is essential that no one use the new numbers until the designated time for conversion and that everyone try to convert at or near the same time. This conversion will be discussed and coordinated long before it is scheduled to take place. Q: What should be done with "fake nodes" in the 5xx and 6xx series? A: These nodes should be assigned regular node numbers within the normal sequence for each group; however, these will still be handled specially by the coordinators of those respective gateways. This may necessitate closer communication between each of those gateway coordinators and the respective GCs. Q: What should be done with the "charter" nodes (ie those with node numbers between 1 and 25)? A: Those nodes will retain their charter number just as they do currently. Q: How will the renumbering affect subtypes? A: In order to avoid any more confusion than is absolutely necessary, if you host a sub, you should NOT attempt to change sub numbers immediately. And in fact, if you are using subtype by numbers now, you can continue using those. Any new Subs added to the net after the new node numbering goes into effect MUST BE subs-by-name. Part Two -- Creating a New NET The basic procedure here will be to create a new parallel NetWork called WW4NET. This network will be for E-Mail and NET UPDATES ONLY at first so that we can get everyone connected and working at a minimum cost to everyone. Many thanks to H20 Doc of 5284 for the suggestions. Note: People running versions prior to 4.21a will NOT be able to use this approach. Since such older versions of WWIV will become in- increasingly outdated, people are urged to upgrade to newer versions as soon as possible.0 PHASE ONE ───────── The purpose of this phase is to get a new network set of data files in place and to insure that everyone is receiving. No one should start any new subs during this process until all phases are completed. Step One ──────── GC's and AC's will develop the new node assignments, informing both 1@1 and the individual nodes what the new node numbers are.