This is a HTML-ized version of Mark Allen's
original draft document, translated at
All input is welcomed, please email me at redness-at-iname.com.
**** Rough Draft Revision 1 ****
its a RFC.......
With the introduction of the Brisbane Mesh Project, it has come to the attention of all users concearned that we have to quickly and correctly make a decision about where we are going to allocate our finite amount of IP's to. The debate has been raging for some time now, between the implimenation of IPv6 and IPv4, I hope that this overview and document will allow for the mesh to proceed, and In the future when the mesh becomes populated, we update our routers with the new IPv6 scheme, or perhaps even use IPv4 to IPv6 routing/filtering software, but until that time comes, the best option for all concearned is to use IPv4, mainly becuase nearly all peeople that are interested (I Hope, sorry for the generalisation) in this project have had some degree of experience with Windows and the Microsoft implimenation of the TCP/IP stack.
My Proposal is that we work in with the schemes already established for other cities in Australia, we use the 10.x.x.x network, and we Subnet our networks, therefor reducing the amount of wasted IP's. I have taken the liberty of creating a very large space for us on the list of mesh groups around the world, we have 5 class B spaces allocated, and hopefully this will be more than enough for us, until we convert accross to IPv6.
visit http://www.freenetworks.org/moin/index.cgi/NetworkAddressAllocations for more information.
The plan is to have 1 Class B Nodes (Out of the Class A 10.x.x.x Network) per Region (Region == Brisbane North, Brisbane South etc), so for example Brisbane North Would be 10.25.x.x, so all routers/servers/clients north of the city (True North ok) will abide by this Class B. Each region will be governed by the controller of the Class B License, who will setup a method (Electronic etc) of distributing the IP's to C Class/D Class/E Class/F Class Nodes.
Each regions IP address will be exclusive for that area, no other area can use the IP's from another region, except for setting up routes to other regions.
I have been thinking about this for some time now, ever since I first relised that the 192.168.x.x Class C network wasnt going to cut the 'cheese', becuase so many people would have to rework there internal networks to get onto the mesh, it would just be a pain for all concearned. So after a little bit of thought I came up with a novel way of structuring the distribution of nodes.
I want to first clear the air about this node type, it probably wont exist (But in the immportal words of our forbears 'Who would every possibly want to own a PC?"), so I have decieded to include this node type into the class system just in case people like myself want to do some serious routing, or the oppertunity arises where we can get a position with a excellent view of the surrounding area, and would like to service a lot of clients (Mobile PC's?)
A 'A Class' Site is a system setup that is purely designed for backbone routing, it doesnt serve any other purpouse. It will get its IP address from the special IP range of 10.30.200.x/24 10.30.249.x/24. This type of node is in existance for a special reason only, to provide 'B Class' Sites with there uplink to other 'B Class' sites.
This type of node will provide 'B Class' and Perhaps 'C Class' routing requirements only, and is not designed for general purpose use by the Mesh Public.
All connections would be secured via VPN and Use IP/SEC to secure uplinks. There would be no Managed AP mode on these connections, because they would be acting as the backbone, they would have to use AD-Hoc for there protocol training.
**** This type is most likely not going to be used *****
A 'B Class' site is the IP range given to region controllers. They are the masters of the '10.2x.x" that has been given out by the BrisMesh Administration (to Come I Hope). The job of B Class Sites is to route traffic to other 'B Class' (and if there is ever a 'A Class' site) sites
The Job of the B Class site (be the site physical or imaginary) is to connect the 'C Class' Access Points to the other Regions or to 'A Class' Backbone Nodes, 'D Class' Clients Will Not Hookup to 'B Class' Regions.
This type is designed for the managing on the individual regions, allocating addresses, providing DHCP to 'C Class' Access Points and other Services (RIP/DNS)
All connections would be secured via VPN and Use IP/SEC to secure uplinks. There would be no Managed AP mode on these connections, because they would be acting as the backbone, they would have to use AD-Hoc for there protocol training.
These nodes would use the subnet mask of 255.255.255.0 (/24) and would be responsible for routing between regions.
**** This type is most likely not going to be used *****
A 'C Class' site is a site which has the primary goal of routing traffic between 'D Class' Sites, this type on site is going to be the most plentiful for the next few years, as the mesh matures I hope to see 'B Class' and 'A Class' sites coming online.
A 'C Class' site has been allocated a C Class portion of the upstream 'B Class' nodes IP range, for example, say I live in Capalaba, this suburb would fall under the Eastern Regions Duristricition, I would apply for a 'C Class License' from the controller of my area. He/She would give me the following information 10.28.1.x, this would idicate to me that I am the first class C in use in this area. My subnet would be 255.255.255.224, this would give me 30 usable address (-1 Route/-1 Broadcast) for My equipment. I would then allocate my remaining 222 address's to the D Class nodes that where connecting to me, subneting them into either 255.255.255.224 (30 Usable/32 Allocated) or 255.255.255.240 (14 Usable/16 Allocated) or 255.255.255.224 (6 Usable/8 Allocated)
The 'C Class' site would talk to other 'C Class' sites directly or through the regions 'B Class' Site.
All connections (Uplink side) would be secured via VPN and Use IP/SEC to secure uplinks. There would be no Managed AP mode on these connections, because they would be acting as the backbone, they would have to use AD-Hoc for there protocol training.
All connection (Downlink side) would only be secured if the client requests. Modes could be either Managed or Un-Managed and would be based on the decision of the operator of the 'C Class' site, depending on the characteristics on the area.
A 'D Class' site is a site that will only every be a client/user of the 'C Class' 's resources, they have no plans to be a 'C Class' user and only have one adapter for the uplink to the local access point.
Address's would be given to the user from the local 'C Class' user, and there uplink would be the 'C Class' site that they got there IP from.
This node type is only given out in special circumstances. For example, say you live in a remote area of brisbane, and there is no 'C Class' sites within distance, but you have a friend a few hundred meters away, apply for this type of node and when the mesh comes to your area, no re-allocation is neccissary, becuase you have a IP that is already registered for that area. (Similar to the Seed Node Idea)
Each B Class IP (10.25/10/26 etc) will have a range reserved for these users, they will be allocated either 32 or 64 address's depending on there needs, and when a C Class Site comes to there area, the C Class will not have to allocate them a part of there 255 address allocation.
This range of IP's from 10.30.0.1 to 10.30.255.254 is being set aside for links to other cities, links to mesh's inside of brisbane, that dont want to be part of the BrisMesh, and special servers (IRC/News/FTP/WWW)
Any user can apply for a special node type, this allows for them to get a slice (be it 32/64/128/255) IP's for special needs. If a user already has a C or D Class license, and they wish to host a special service, something the entire mesh can use, all they have to do it apply for a Special Serice License, and this will grant them exclusive permission to use this range for there own special needs or the needs of the group.
As discussed above, I believe for the time being that the 'A and B Class' sites will not be in existance, and we will have numerous 'C Class' sites up and running talking to other 'C Class' sites.
If we act quickly, we can create a page that allows people to register there area be it north/south/east/west and get a IP for that area, we will all have to be realistic on the grabbing for IP's that is sure to follow. People that are not interested in carrying any traffic will have to apply for a S Class or a D Class only, otherwise we are going to have people rushing for 255 address's when all that they need is 8 or 16.
Frankly, we all are going to have to do something and quickly about this problem, it wont go away, if sites start poping up in geographical seperate areas, and there is no infrastructure in place, when they eventually meet, it is going to cause headaches for all concearned. IPv4 is the way to go until the mesh is humming along, and then we start to impliment IPv6 over the top, while keeping the IPv4 infrastructure in place.
Brisbane North 10.25.x.x Region North of Brisbane City to Sunshine Coast A Class -- Backbone 10.25.0.1 to 10.25.0.255 -- Total Hosts Possible 253 Total AP Points -- NA Backbone Routing (253 Max Nodes) B Class -- Region Controllers 10.25.1.1 to 10.25.30.255 -- Total Hosts Possible 7590 Total AP Points -- 29 Per Region C Class/D Class/E Class -- AP's and Clients 10.25.31.1 to 10.25.199.255 -- Total Hosts Possible 42504 Total AP Points -- 168 AP Per Region S Class -- Seed Nodes 10.25.200 to 10.25.249.255 -- Total Hosts Possible 12397 Total AP Points -- 49 Seed Points Reserved for Special Cases 10.25.250.1 to 10.25.255.255 -- Total Hosts Possible 1265 Reserved for Expansion or Special Needs Brisbane South 10.26.x.x Region South of Brisbane City to Gold Coast A Class -- Backbone 10.26.0.1 to 10.26.0.255 -- Total Hosts Possible 253 Total AP Points -- NA Backbone Routing (253 Max Nodes) B Class -- Region Controllers 10.26.1.1 to 10.26.30.255 -- Total Hosts Possible 7590 Total AP Points -- 29 Per Region C Class/D Class/E Class -- AP's and Clients 10.26.31.1 to 10.26.199.255 -- Total Hosts Possible 42504 Total AP Points -- 168 AP Per Region S Class -- Seed Nodes 10.26.200 to 10.26.249.255 -- Total Hosts Possible 12397 Total AP Points -- 49 Seed Points Reserved for Special Cases 10.26.250.1 to 10.26.255.255 -- Total Hosts Possible 1265 Reserved for Expansion or Special Needs Brisbane West 10.27.x.x Region West of Brisbane City to Dalby A Class -- Backbone 10.27.0.1 to 10.27.0.255 -- Total Hosts Possible 253 Total AP Points -- NA Backbone Routing (253 Max Nodes) B Class -- Region Controllers 10.27.1.1 to 10.27.30.255 -- Total Hosts Possible 7590 Total AP Points -- 29 Per Region C Class/D Class/E Class -- AP's and Clients 10.27.31.1 to 10.27.199.255 -- Total Hosts Possible 42504 Total AP Points -- 168 AP Per Region S Class -- Seed Nodes 10.27.200 to 10.27.249.255 -- Total Hosts Possible 12397 Total AP Points -- 49 Seed Points Reserved for Special Cases 10.27.250.1 to 10.27.255.255 -- Total Hosts Possible 1265 Reserved for Expansion or Special Needs Brisbane East 10.28.x.x Region East of Brisbane City Encompassing all Sea-Side Areas and Moreton Island (Fraser Is etc) A Class -- Backbone 10.28.0.1 to 10.28.0.255 -- Total Hosts Possible 253 Total AP Points -- NA Backbone Routing (253 Max Nodes) B Class -- Region Controllers 10.28.1.1 to 10.28.30.255 -- Total Hosts Possible 7590 Total AP Points -- 29 Per Region C Class/D Class/E Class -- AP's and Clients 10.28.31.1 to 10.28.199.255 -- Total Hosts Possible 42504 Total AP Points -- 168 AP Per Region S Class -- Seed Nodes 10.28.200 to 10.28.249.255 -- Total Hosts Possible 12397 Total AP Points -- 49 Seed Points Reserved for Special Cases 10.28.250.1 to 10.28.255.255 -- Total Hosts Possible 1265 Reserved for Expansion or Special Needs Brisbane Central 10.29.x.x Encompassing all Inner City and Outer City Suburbs A Class -- Backbone 10.29.0.1 to 10.29.0.255 -- Total Hosts Possible 253 Total AP Points -- NA Backbone Routing (253 Max Nodes) B Class -- Region Controllers 10.29.1.1 to 10.29.30.255 -- Total Hosts Possible 7590 Total AP Points -- 29 Per Region C Class/D Class/E Class -- AP's and Clients 10.29.31.1 to 10.29.199.255 -- Total Hosts Possible 42504 Total AP Points -- 168 AP Per Region S Class -- Seed Nodes 10.29.200 to 10.29.249.255 -- Total Hosts Possible 12397 Total AP Points -- 49 Seed Points Reserved for Special Cases 10.29.250.1 to 10.29.255.255 -- Total Hosts Possible 1265 Reserved for Expansion or Special Needs Special Servers 10.30.x.x Special Servers 10.30.1.1 to 10.30.2.255 -- Total Hosts Possible 506 Reserved for Special Servers Events or Experimental Equipment Special Services 10.30.3.1 to 10.30.4.255 -- Total Hosts Possible 506 Reserved for Special Services (Global DNS/DHCP/RIP/WINS etc) Non-Connected Networks --- NEVER to be Used by A/B/C/D/E/S Nodes 10.30.5.1 to 10.30.6.255 -- Total Hosts Possible 506 Reserved for Ever No USE POSSIBLE! Note: I added this is the hope that people that want to setup there own little network inside of the mesh would use it , in the hope that when the come online with the mainstream mesh users, there IP's wont clash with anything thats setup Dedicated Hardware/Incompatible Equipment 10.30.7.1 to 10.30.19.255 -- Total Host Possible 3289 Note: Stand Alone Equipment might include distant machines, not compatible with the 802.11 Network but would still like to route packets (Packet Radio/StarNet/900Mhz Bands/CB Data Networks/Mobile Phone Data Networks) Telephone/Satellite/Cable/Community Links 10.30.20.1 to 10.30.40.253 -- Total Hosts Possible 5313 Note: This address range is specially assigned for equipment that might be to distant to be connected via radio, but has existing dry pairs or dialup connections to a site that has mesh access, can use either one of these special numbers or a section of the C/D/E License Assigned to the upstream user. InterCity Links North To Northern Australia (Above Noosa-Tewantan) 10.30.41.1 to 10.30.41.253 -- Total Hosts Possible 253 South To NSW Border (Gold Coast to Tweed Heads) 10.30.42.1 to 10.30.42.253 -- Total Hosts Possible 253 West From Dalby to Mt Isa 10.30.43.1 to 10.30.43.253 -- Total Hosts Possible 253 Note: Inside Queensland! InterState Links New South Wales 10.30.45.1 to 10.30.45.255 -- Total Hosts Possible 253 Note: Router Uplinks Only Australian Capital Territory 10.30.46.1 to 10.30.46.255 -- Total Hosts Possible 253 Note: Router Uplinks Only Victoria 10.30.47.1 to 10.30.47.255 -- Total Hosts Possible 253 Note: Router Uplinks Only South Australia 10.30.48.1 to 10.30.48.255 -- Total Hosts Possible 253 Note: Router Uplinks Only Western Australia 10.30.49.1 to 10.30.49.255 -- Total Hosts Possible 253 Note: Router Uplinks Only Northern Territory 10.30.49.1 to 10.30.49.255 -- Total Hosts Possible 253 Note: Router Uplinks Only International Links 10.30.50.1 to 10.30.50.253 -- Total Links Possible 253, More Likely 32 'D Class' 8 IP Range Addresses Note: Inserted for the Sake of Sanity Reserved for Future Expansion 10.30.51.1 to 10.30.200.1 -- Total Hosts C Class 150 Note: If We ever run out of C Class's in a area and all the reserved IP's for that area have gone, reserverd IP's are here Special Nodes 10.30.201.1 to 10.30.250.255 -- Total Hosts Possible 12650 Experimental Equipment and Nodes 10.30.251.1 to 10.30.255.255 -- Total Hosts Possible 1265 Note: Used for Persons/Groups wanting to do experimental links, eg bouncing signals off the moon or using the dark zone for RF propergation etc. .fin. RFC
Created By Mark Allen, Holland Park West, Brisbane, Queensland, Australia. Please Remember that this is mostly my own work, with information and sources taken from others. All other information is property of there respective owners and I dont want to get spam/flames becuase it might co-incidide with a idea you scribbled on a napkin 10 years ago, while waiting for a plane in a train station. OK.