RFC 1219:On the Assignment of Subnet Numbers
RFC-Ref

address


Click on the red underlined text to get to the source

... 950std5, specifies that the Host part of the formally 2-level Internet address can be divided into two fields, Subnet and Host ...
... Subnet and Host. This gives the Internet address a third level of hierarchy, and the concomitant firewalls and savings in routing ...
... overhead. It also introduces increased inefficiency in the allocation of addresses. ...
... Ideally, we would like to simply change B's mask without changing any of the host addresses in B. However, the subnets numerically above and below B are already taken by A and C. (If say 3.0 was not taken ...
... and below B are already taken by A and C. (If say 3.0 was not taken by C, B's mask could be changed from 255.0 (ff00) to 254.0 (fe00). In this case, all of B's existing addresses would still match the new subnet. Indeed, if non-contiguous masks were in use, it might be ...
... subnet, and assigning host addresses under the new subnet. The result of this logical partition ...
... entries, and changing any other configuration files that have hardwired addresses for hosts in subnet B. ...


... subnets are assigned by splitting the host part of the address in two fields; the subnet field and the host ...
... bits, and 0 for host field bits. (In all of our addresses, the least significant bit (LSB) is on the right, the most significant bit ...
... hosts). Then the network administrator might assign two types of addresses: ...
... range 00010000 to 00101111 could not be assigned to the small subnets, otherwise there will be addresses that would match both subnets. ...
... to the maximum allowed, but that there is still room in the subnet field to assign more addresses. We then have the following: ...
... While the host field can no longer grow, there is still room in the address for growth. The problem is that because of where the growth areas are situated, the remaining growth has been effectively reserved for subnets ...
... state machine is executing it. In reality, there may be a root Address Authority (RootAA) that assigns subnet ...
... ones" value (which is the "all subnets" broadcast address) from being assigned to a subnet. (Since no hosts ...
... bit.) 3. Label all other bits in the address to be g-bits. (By address ...
... address to be g-bits. (By address, we mean that part of the IP address not including the network ...
... bits. (By address, we mean that part of the IP address not including the network number.) ...
... bit of Y to an s-bit. If the rootAA and YAA (the address authority for Y) are separate AAs ...
... AddHost(S): 1. Create an address A consisting of subnet number S concatenated with zeros. ...
... bits as the other host addresses. 3. Find the lowest non-zero (using normal counting) non-assigned ...
... (which is the "all hosts" broadcast address) from being assigned to a host. ...
... that if this is the last g-bit, this change must be coordinated with the address authority assigning subnet ...
... hosts if necessary. 7. Create a new address A consisting of S concatenated with H 8. Assign A to the host. ...
... but are shown as 1's and 0's according to the subnet number assignment. The space is just to make the addresses and masks easier to read. Finally, we number our bits 0 to 7 from right to left as ...
... Subnet Address Mask A 10gg ghhh 1111 0000 B 01gg ghhh 1111 0000 ...
... bits instead of just two. This is because with just two, the subnet address of C could be "11" (rather than "110"), which is a broadcast value. Step 2 of ...
... they were all different. In other words, a router would be able to distinguish an address in D from addresses in A, B, and C. ...
... router would be able to distinguish an address in D from addresses in A, B, and C. ...
... bits (step 62 of AddHost()). Notice also that if the person assigning host addresses for B (B Address Authority, or ...
... if the person assigning host addresses for B (B Address Authority, or BAA) is different than the person assigning network ...
... 011 (which is what comes after 101 in MI counting). The reason is that 1) 011 is not distinguishable from B's subnet address using B's mask, and 2) we can't increase B's mask to make it distinguishable because B has already assigned hosts ...


... Tsuchiya, P., "Efficient and Flexible Hierarchical Address Assignment", TM-ARH-018495, Bellcore, February 1991. ...


... Author's Address ...



Google
Web
RFC-Ref