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 Kozierok
Author 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.

The Book is Here... and Now On Sale!

The whole site in one document for easy reference!
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Lower-Layer (Interface, Internet and Transport) Protocols (OSI Layers 2, 3 and 4)
      9  TCP/IP Internet Layer (OSI Network Layer) Protocols
           9  Internet Protocol (IP/IPv4, IPng/IPv6) and IP-Related Protocols (IP NAT, IPSec, Mobile IP)
                9  Internet Protocol Version 4 (IP, IPv4)
                     9  IP Addressing
                          9  IP "Classful" (Conventional) Addressing

Previous Topic/Section
IP Multicast Addressing
Previous Page
Pages in Current Topic/Section
1
2
3
Next Page
IP Subnet Addressing ("Subnetting") Concepts
Next Topic/Section

Problems With "Classful" IP Addressing
(Page 2 of 3)

The Key Problem with Classes: Low Granularity

Issues #2 and #3 are more closely related to each other than issue #1 and are both the result of the fact that the “granularity” in the “classful” system is simply too low to be practical in a large internet. By this I mean that there are too few choices in the sizes of networks available. Three sizes seems fine in principle, but the gaps between the sizes are enormous, and the sizes don't match up all that well with the distribution of organizations in the real world. Consider the difference in size between Class C and Class B networks—a jump from 254 hosts all the way up to over 65,000! There are many, many companies that need more than 254 IP address but a lot fewer than 65,000. And what about Class A? How many companies need 16 million IP addresses, even the truly large ones? Probably none, if you think about it, yet that's half the IP address space right there.

Considering our company with 5,000 computers again—what class network should they use? As Figure 64 shows, there is no good match for this company’s needs in the “classful” scheme at all. In the past, they would likely have been assigned a Class B network. However, giving a Class B to a company with “only” 5,000 computers means over 90% of the IP addresses are wasted. When the Internet was young this wasn't a big deal, but as it grew these inefficiencies quickly started to become significant.


Figure 64: The Main Problem With “Classful” Addressing

In this scale diagram, each square represents 50 available addresses. Since a Class C address has only 254 addresses, and a Class B contains 65,534 addresses, an organization with 5,000 hosts is “caught in the middle”. It can only choose to either waste 90% of a Class B address or use 20 different Class C networks.

 

 


The alternative to wasting all these IP addresses would be to give the company instead of one Class B, a bunch of Class C addresses. However as you can see, they would need 20 of them. This is more efficient in use of address space, but leads to Issue #3: every router on the Internet replaces the single Class B router table entry with 20 Class C router entries. Now multiply this by a few thousand “medium-sized” companies and you can see that this method would add dramatically to the size of router tables. Router tables have already been growing quickly as the Internet has expanded. The larger these tables, the more time it takes for routers to make routing decisions.


Previous Topic/Section
IP Multicast Addressing
Previous Page
Pages in Current Topic/Section
1
2
3
Next Page
IP Subnet Addressing ("Subnetting") Concepts
Next Topic/Section

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!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



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.