Extending the Use of Address Masking

The original conception for three default masks defined by the leading bits in the address field was extended to allow installers and administrators to specify any mask value they wanted to use. In this way the restrictions placed on the addresses by the original masking were removed. The requirement remained, however, that the original masking be honored. It could be extended but not shortened. So, suppose that a site was assigned the address This would imply that all stations at the site were on the same network. The default masking forced the use of the first two octets to identify the network and the remaining octets identify the hosts. If this site wanted to subdivide into separate networks, however, there was no facility in the original scheme to allow the address to reflect anything other than one level of hierarchical division; the world is divided into networks – end of story.

Because the mask was now a configurable parameter, the Class B network could use a mask of, like a Class C network. The rest of the universe would see all stations at this site as being part of network but within the site the routers would see the world as being divided on the basis of the first three octets. These are referred to as subnetworks. The site would be divided into subnetworks,, up to

The extension of the original default address masks to allow any desired mask parameter assumes compliance with the original class masks. That is, a Class A network must have a mask of at least, a Class B network must have a mask of at least, and a Class C network must have at least A Class B network could, for example, have a mask of or any other mask as long as the first two octets are included in the mask; to remain compliant with the original mask definitions.

The extension of the address mask allows networks to be further subdivided into sub networks. For example, the Class B network could be subnetted with as a mask. This would create subnets like,,… up to