The intent of this paper is to document the backgroun behind the current IP address assignments which I have offered to coordinate. The proposed scheme has been reviewed by Phil Karn,Bdale Garbee and (verbally with) Mike Chepponis, all of whom have encouraged that it be used.
Phil's code does NOT currently support the subnetwork
I have offered to issue and keep track of SUBNET addresses
The basic premise behind the proposed plan is that amateur
The natural limitations on span of control will probably limit the service area of each of these networks. This is another factor leading to the partitioning of the AMPRNET address space with respect to separate subnetworks.
[NOTE: Throughout this paper, Host or Host/User represents
WA6JPR may be "a user" on hosts on more than one network such that a station in Washington D.C.,logged onto an AMPRNET host, may send internet traffic successfully to WA6JPR@JPRHOST.WESTNET (this traffic would be routed to Westnet
Accordingly, the following is proposed as an initial addressing scheme and methodology for address assignment. [Bit numbering is per RFC-960 Pg.2]
Bit 8 to be 0 for USA stations and 1 for non-USA stations.
Bits 9 - 18 to represent politically separate subnetworks within
Bits 19 - 23 to be unassigned and reserved for future allocation
Bits 24 - 31 to be used within politically separate AMPRNET
The resulting network addresses would be as follows:
44:0...127:193:0...255--+ | +- 1,015,808 addresses reserved
44:128:xxx:xxx----------+ | +- 8,388,608 addresses assignable (non USA)
The above allocation and assignment scheme allows network (subnet) and intranet (host/user) addresses to begin to b
If it should become clear that every user on a network needs his or her own IP address, each network could allocate user blocks in 256 user increments from the least significant reserved bits.