| 
 | Please Whitelist This Site?I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
 If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads. If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK. Thanks for your understanding! Sincerely, Charles KozierokAuthor and Publisher, The TCP/IP Guide
 | 
 
 
   
  
    | 
  
| NOTE: Using software to mass-download the site degrades the server and is prohibited. If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
 |  |  | 
| 
 
 
 | 
 
 IP Subnet Addressing Overview, Motivation, and Advantages
 (Page 2 of 3)
 The Development of Subnet Addressing In order to address this problem 
adequately, an enhancement was required to the classful 
addressing scheme. This change was outlined in RFC 950, which defined 
a new addressing procedure called subnet addressing or subnetting. 
(This RFC was published way back in 1985, which surprises some people!) The basic idea behind subnet addressing 
is to add an additional hierarchical level in the way IP addresses are 
interpreted. The concept of a network remains unchanged, but instead 
of having just hosts within a network, a new two-level hierarchy 
is created: subnets and hosts. Each subnet is a subnetwork, and 
functions much the way a full network does in conventional classful 
addressing. A three-level hierarchy is thus created: networks, which 
contain subnets, each of which then has a number of hosts. Thus, instead of an organization 
having to lump all of its hosts under that network in an unstructured 
manner, it can organize hosts into subnets that reflect the way internal 
networks are structured. These subnets fit within the network identifier 
assigned to the organization, just as all the unorganized 
hosts used to.Advantages of Subnet Addressing In essence, subnet addressing allows 
each organization to have its own internet within the Internet. 
Just as the real Internet looks only at networks and hosts, a two-level 
hierarchy, each organization can now also have subnets and hosts within 
their network. This change provides numerous advantages over the old 
system: 
Better Match to Physical Network Structure: 
Hosts can be grouped into subnets that reflect the way they are actually 
structured in the organization's physical network.
 
Flexibility: The number of subnets and 
number of hosts per subnet can be customized for each organization. 
Each can decide on its own subnet structure and change it as required. 
 
Invisibility To Public Internet: Subnetting 
was implemented so that the internal division of a network into subnets 
is visible only within the organization; to the rest of the Internet 
the organization is still just one big, flat, network. This 
also means that any changes made to the internal structure are not visible 
outside the organization.
 
No Need To Request New IP Addresses: Organizations 
don't have to constantly requisition more IP addresses, as they would 
in the workaround of using multiple small Class C blocks.
 
No Routing Table Entry Proliferation: 
Since the subnet structure exists only within the organization, routers 
outside that organization know nothing about it. The organization still 
maintains a single (or perhaps a few) routing table entries for all 
of its devices. Only routers inside the organization need to worry about 
routing between subnets.
 
 
 | 
 | If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |  
|  | 
 | 
 
 
 Home - 
Table Of Contents - Contact Us
 
 The TCP/IP Guide (http://www.TCPIPGuide.com)
 Version 3.0 - Version Date: September 20, 2005
 
 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
 Not responsible for any loss resulting from the use of this site.
 |