Foreward - Internet IP address assignment has certain conventions to allow uniformity and intuitive setup of routers by those who may not be familiar with a neighboring network, but need to gain access to it. There are other subtle conventions that allow relatively easy interoperability. For this reason, it is proposed that Internet address assignment for the Wisconsin and Upper Michigan Amateur Packet Radio Network (amprnet) be standardized.
It is important for the amprnet to have a standardized address assignment method, as we have a cooperative network that has more administrative interaction than may be custom on the internet. Amprnet operators are, by custom, more open than their Internet counterparts as communication is our hobby. We also have a host of unique-to-Amateur services and this makes it is even more desirable to have conventions that are as intuitive as they can possibly be.
In addition to our own operating compatibility, we also have to consider that it is more common than ever for amprnet hosts to be interconnected to the Internet. Even more common is the practice of linking local area networks via closed links (IP Tunnels) through the Internet.
There are expected exceptions to this proposed standardization, however. For instance, it is impractical for existing holders of IP addresses to make a massive change in an existing subnet simply to satisfy a certain system of addressing. There also may be valid reasons that are not yet known to violate this proposed protocol.
However, when new subnets are created or the cooperation of operators in an existing subnet is obtained, the convention should be followed as closely as possible so that IP routing and related issues are intuitive.
In addition to this issue, this convention will also allow for a number of uniqe-to-Amateur Packet Radio situations and services.
Proposed IP Addressing Structure:
The best way to illustrate this proposed system is by example. In our example, we will use a currently non-existent network of 44.92.240.0.
44.92.240.0
This is the network address, as per the Internet standard.
44.92.240.1
Is the primary high-speed network access point - the router used to acess the 44.92.240.0 network. This should be a reliable connection as it is the primary acess point - generally a node or IP host with IP routing capabilities.
44.92.240.2 through 44.92.240.6
These addresses are designated for other secondary routing ports in a nodestack or multi-port IP host/BBS. The preference is to have lower numbered routers, nodes, or a multi-port host within this block as the most reliable connections. Higher numbered hosts within the block are the least reliable or less-used routers, nodes, or ports in a multi-port IP host.
For example:
44.92.240.1 is a UHF, SHF or Microwave high-speed X-1J backbone node 44.92.240.2 is a VHF or UHF 9600 bps X-1J backbone node 44.92.240.3 is a 220 MHz 9600 bps backbone node 44.92.240.4 is a 50 MHz 2400 bps backbone node 44.92.240.5 is a low-speed VHF user port routing to the Local Area Network 44.92.240.6 is a high-speed UHF user port routing to the Local Area Net
44.92.240.7 and 44.92.240.8
These are reserved for future usage. Should some new technology allow us to take advantage of an as-yet unseen service, these addresses will be available for such use.
44.92.240.9, 44.92.240.10, and 44.92.240.11
These are reserved for Primary, Secondary, and Tertiary Domain Name Servers designed to serve the Local Area Network.
44.92.240.12 and 44.92.240.13
These two addresses are designated for POP3 (or subsequent protocol-based) mail servers.
44.92.240.14 through 44.92.240.20
This address block is to be divided between DX Cluster BBSs, Local IP hosts (such as NOS) that are not performing network routing functions but are public facilities, and standard AX.25 BBSs that support IP operation (such as MSYS or FBB) and are public facilities.
The operative term here is "public facilities". This address block is not designed to be issued to an end user simply because he or she uses a NOS program as a client. They are to be assigned to public server-type facilities.
44.92.240.21 through 44.92.240.180
This block is designated for end users who wish a permanent IP address. These addresses are not limited to client use only. An end user may provide a public service of some type that does not fit into the above reserved-block.
For example, a private user may provide a public weather station that provides local weather conditions on demand. If a private user decides to provide supplemental DNS service for a LAN, there is no valid reason to deny that end user the opportunity to provide such a service. If an end user is the only DNS on a local LAN however, it is suggested that he or she be assigned one of the addresses from the block or 3 reserved for that purpose.
In some circumstances, this end user address block may be further subdivided into different LAN frequencies for ease of routing.For example, our 44.92.240.0 network has two user LAN ports on different frequencies. A common situation would be one low-speed VHF port and one high-speed UHF port. In this case, the block of 44.92.240.21 to 44.92.240.120 may be designated for the VHF user LAN, while 44.92.240.121 to 44.92.240.180 may designated for the UHF user LAN.
As higher-speed operation becomes more common, and more user ports are added, this subdivision or the numbering scheme for end users may be carried out further. It is entirely possible to envision 900 MHz ports in the near future, making yet one more division desirable.
44.92.240.181 through 44.92.240.253
These addresses are reserved for dynamically-assigned addresses. Again, this block may be further subdivided to accomodate different user ports.
Subdivision of End User Address Blocks
This policy is to be set in accordance with local operating situations. In some cases where a subnet is not well populated, and there is only one user LAN, then there may not be a need for subdivision of network address blocks. In other areas with multiple well-populated user LANs, it makes sense to do this.
Whatever situation is needed, it is suggested that the operator(s) of the local router, node or IP host consult and work with the local subnet IP address coordinator (if one is available), or the state IP address coordinator.
44.92.240.254
This is a designated _short-term_ network address reserved for testing purposes and should not be assigned.
44.92.240.255
This is a Network Broadcast Address and should -never- be issued to a host. This will cause widespread havoc on the local network, as it is typically used for arp (address resolution protocol) requests.
Special Conditions
There are circumstances where an end user may request a block of addresses for his or her own personal network, and may wish to have access to and from the Local Area Network. Routing and subnet issues come into consideration here, and as such, a block may be assigned for purposes that conflict with the poroposed addressing system.
The nature of such a network cannot be anticipated, and no special provision is made to guarantee ease of routing. In addition, local IP address Subnet Mangers and the State IP address coordinator are not network engineers and cannot be asked to provide such expertise. Their function is to cheerfully assign a suitable address.
Many may be able to help in such matters, if they have knowledge of such a network. If an end user has such special circumstances, attempts will be made to accomodate them. However, end users and network service providers should not expect anything other than an IP address (or block of addresses) from the IP address coordinator that they are interacting with.
System Changes
While there has been an attempt at providing for future changes and additions in network technology and services, no one can fully anticipate what the future will bring. For that reason, this system and this document are subject to change. In referncing this system, it will be referred to as IPAP-1 (IP Addressing Plan 1)
Submitted for comments on November 16, 2001 by Andy Nemec, KB9ALN Wisconsin and Upper Michigan IP amprnet address coordinator (44.92.0.0)