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!

Enjoy The TCP/IP Guide? Get the complete PDF!
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
23
Next Page
IP Subnet Addressing ("Subnetting") Concepts
Next Topic/Section

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

The “classful” addressing system was the first major attempt to define a method for universal addressing of a large IP internetwork. The system had some advantages, as I mentioned in the overview of the “classful” scheme, and given that it was developed decades ago for a network that was limited in size, it did the job remarkably well for a long time.

Nobody ever expected the Internet to mushroom to anything close to its current size. As it grew, problems become apparent with the “classful” IP addressing mechanism—slowly at first, but then more rapidly as growth became more rapid. I've hinted at some of theses problems in my explanation of how this type of addressing works, but to help frame the discussion of newer addressing types, I think it is useful to look at this in more detail.

Summary of “Classful” Addressing Issues

There are three main problems with “classful” addressing, which are somewhat related to each other (making them a bit harder to explain). Let's start with a quick summary of what these issues are:

  1. Lack of Internal Address Flexibility: Big organizations are assigned large, “monolithic” blocks of addresses that don't match well the structure of their underlying internal networks.

  2. Inefficient Use of Address Space: The existence of only three block sizes (classes A, B and C) leads to waste of limited IP address space.

  3. Proliferation of Router Table Entries: As the Internet grows, more and more entries are required for routers to handle the routing of IP datagrams, which causes performance problems for routers. Attempting to reduce inefficient address space allocation leads to even more router table entries.
Addressing Inflexibility

Issue #1 results primarily from the fact that in the “classful” system, big companies get assigned a rather large (Class B) or truly enormous (Class A) block of addresses, all of which is considered by the Internet routers a single “network” with one “network ID”. Now, imagine that you are running a medium-to-large-sized company with 5,000 computers, and you are assigned a Class B address for your network. Do you really have 5,000 computers all hooked into a single network? I sure as heck hope you don't! Yet you would be forced to try to fit all of these into a single IP “network” in the original “classful” method. There was no way to create an internal hierarchy of addresses.


Previous Topic/Section
IP Multicast Addressing
Previous Page
Pages in Current Topic/Section
1
23
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.