Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Classful network
open-in-new
<h2 id="background">Background</h2> <p>In the original address definition, the most significant eight bits of the 32-bit IPv4 address was the <i>network number</i> field which specified the particular network a host was attached to. The remaining 24 bits specified the local address, also called <i>rest field</i> (the rest of the address), which uniquely identified a host connected to that network.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> This format was sufficient at a time when only a few large networks existed, such as the <a href="/facts/ARPANET/LyMGWurJ">ARPANET</a> (network number 10), and before the wide proliferation of <a href="/facts/Local_area_network/edUDxJ6J">local area networks</a> (LANs). As a consequence of this architecture, the address space supported only a low number (254) of independent networks. </p><p>Before the introduction of address classes, the only address blocks available were these large blocks which later became known as Class A networks.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> As a result, some organizations involved in the early development of the Internet received very large address space allocations (16,777,216 IP addresses each). </p> <h2 id="introduction-of-address-classes">Introduction of address classes</h2> <p>Expansion of the network had to ensure compatibility with the existing address space and the IPv4 packet structure, and avoid the renumbering of the existing networks. The solution was to expand the definition of the network number field to include more bits, allowing more networks to be designated, each potentially having fewer hosts. Since all existing network numbers at the time were smaller than 64, they had only used the 6 least-significant bits of the network number field. Thus it was possible to use the most-significant bits of an address to introduce a set of address classes while preserving the existing network numbers in the first of these classes. </p><p>The new addressing architecture was introduced by <a href="/facts/RFC_(identifier)/esftTvE7">RFC</a> <a href="https://www.rfc-editor.org/rfc/rfc791">791</a> in 1981 as a part of the specification of the Internet Protocol.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> It divided the address space into primarily three address formats, henceforth called address <i>classes</i>, and left a fourth range reserved to be defined later. </p><p>The first class, designated as <i>Class A</i>, contained all addresses in which the most significant bit is zero. The network number for this class is given by the next 7 bits, therefore accommodating 128 networks in total, including the zero network, and including the IP networks already allocated. A <i>Class B</i> network was a network in which all addresses had the two most-significant bits set to 1 and 0 respectively. For these networks, the network address was given by the next 14 bits of the address, thus leaving 16 bits for numbering host on the network for a total of 65536 addresses per network. <i>Class C</i> was defined with the 3 high-order bits set to 1, 1, and 0, and designating the next 21 bits to number the networks, leaving each network with 256 local addresses. </p><p>The leading bit sequence <i>111</i> designated an at-the-time unspecified addressing mode ("<i>escape to extended addressing mode</i>"),<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> which was later subdivided as Class D (<i>1110</i>) for multicast addressing, while leaving as reserved for future use the <i>1111</i> block designated as Class E.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> </p><p>This architecture change extended the addressing capacity of the Internet but did not prevent <a href="/facts/IP_address_exhaustion/8cxJwQ1Q">IP address exhaustion</a>. The problem was that many sites needed larger address blocks than a Class C network provided, and therefore they received a Class B block, which was in most cases much larger than required. Due to the rapid growth of the Internet, the pool of unassigned Class B addresses (214, or about 16,000) was rapidly being depleted. Starting in 1993, classful networking was replaced by <a href="/facts/Classless_Inter-Domain_Routing/YU0SEmfp">Classless Inter-Domain Routing</a> (CIDR),<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a><a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> in an attempt to solve this problem. </p> <h2 id="classful-addressing-definition">Classful addressing definition</h2> <p>Under classful network addressing, the 32-bit IPv4 address space was partitioned into five classes (A-E) as shown in the following tables. </p> Classes <table><tbody><tr><th>Class</th><th>Leading bits</th><th>Size of <i>network number</i> bit field</th><th>Size of <i>rest</i> bit field</th><th>Number of networks</th><th>Addresses per network</th><th>Total addresses in class</th><th>Start address</th><th>End address</th><th>Default <a href="/facts/Subnet_mask/s1rQsNDv">subnet mask</a> in <a href="/facts/Dot-decimal_notation/Tea5wKCB">dot-decimal notation</a></th><th><a href="/facts/CIDR_notation/YU0SEmfp">CIDR notation</a></th></tr><tr><td>Class A</td><td>0</td><td>8</td><td>24</td><td>128 (27)</td><td>16,777,216 (224)</td><td>2,147,483,648 (231)</td><td><i>0.0.0.0</i></td><td><i>127.255.255.255</i><a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a></td><td><i>255.0.0.0</i></td><td><i>/8</i></td></tr><tr><td>Class B</td><td>10</td><td>16</td><td>16</td><td>16,384 (214)</td><td>65,536 (216)</td><td>1,073,741,824 (230)</td><td><i>128.0.0.0</i></td><td><i>191.255.255.255</i></td><td><i>255.255.0.0</i></td><td><i>/16</i></td></tr><tr><td>Class C</td><td>110</td><td>24</td><td>8</td><td>2,097,152 (221)</td><td>256 (28)</td><td>536,870,912 (229)</td><td><i>192.0.0.0</i></td><td><i>223.255.255.255</i></td><td><i>255.255.255.0</i></td><td><i>/24</i></td></tr><tr><td>Class D (<a href="/facts/Multicast/D9IspSfl">multicast</a>)</td><td>1110</td><td>not defined</td><td>not defined</td><td>not defined</td><td>not defined</td><td>268,435,456 (228)</td><td><i>224.0.0.0</i></td><td><i>239.255.255.255</i></td><td>not defined</td><td>/4<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a></td></tr><tr><td>Class E (reserved)</td><td>1111</td><td>not defined</td><td>not defined</td><td>not defined</td><td>not defined</td><td>268,435,456 (228)</td><td><i>240.0.0.0</i></td><td><i>255.255.255.255</i><a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a></td><td>not defined</td><td>not defined</td></tr></tbody></table> Bit-wise representation <p>In the following bit-wise representation, </p> <ul><li><i>n</i> indicates a bit used for the network ID.</li> <li><i>H</i> indicates a bit used for the host ID.</li> <li><i>X</i> indicates a bit without a specified purpose.</li></ul> Class A 0. 0. 0. 0 = 00000000.00000000.00000000.00000000 127.255.255.255 = 01111111.11111111.11111111.11111111 0nnnnnnn.HHHHHHHH.HHHHHHHH.HHHHHHHH Class B 128. 0. 0. 0 = 10000000.00000000.00000000.00000000 191.255.255.255 = 10111111.11111111.11111111.11111111 10nnnnnn.nnnnnnnn.HHHHHHHH.HHHHHHHH Class C 192. 0. 0. 0 = 11000000.00000000.00000000.00000000 223.255.255.255 = 11011111.11111111.11111111.11111111 110nnnnn.nnnnnnnn.nnnnnnnn.HHHHHHHH Class D 224. 0. 0. 0 = 11100000.00000000.00000000.00000000 239.255.255.255 = 11101111.11111111.11111111.11111111 1110XXXX.XXXXXXXX.XXXXXXXX.XXXXXXXX Class E 240. 0. 0. 0 = 11110000.00000000.00000000.00000000 255.255.255.255 = 11111111.11111111.11111111.11111111 1111XXXX.XXXXXXXX.XXXXXXXX.XXXXXXXX <p>The number of addresses usable for addressing specific hosts in each network is always 2N - 2, where N is the number of rest field bits, and the subtraction of 2 adjusts for the use of the all-bits-zero host value to represent the network address and the all-bits-one host value for use as a broadcast address. Thus, for a Class C address with 8 bits available in the host field, the maximum number of hosts is 254. </p><p>Today, IP addresses are associated with a <a href="/facts/Subnet_mask/s1rQsNDv">subnet mask</a>. This was not required in a classful network because the mask was implied by the address itself; any network device would inspect the first few bits of the IP address to determine the class of the address and thus its netmask. </p><p>The blocks numerically at the start and end of classes A, B and C were originally reserved for special addressing or future features, i.e., <i>0.0.0.0/8</i> and <i>127.0.0.0/8</i> are reserved in former class A; <i>128.0.0.0/16</i> and <i>191.255.0.0/16</i> were reserved in former class B but are now available for assignment; <i>192.0.0.0/24</i> and <i>223.255.255.0/24</i> are reserved in former class C. While the <i>127.0.0.0/8</i> network is a Class A network, it is designated for <a href="/facts/Loopback/NvRL5LTG">loopback</a> and cannot be assigned to a network.<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a> </p><p>Class D is reserved for <a href="/facts/Multicast/D9IspSfl">multicast</a> and cannot be used for regular unicast traffic. Class E is reserved and cannot be used on the public Internet. Many older routers will not accept using it in any context. </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/IPv4_subnetting_reference/YU0SEmfp">IPv4 subnetting reference</a></li> <li><a href="/facts/List_of_assigned_%2f8_IPv4_address_blocks/3n8aoTQ2">List of assigned /8 IPv4 address blocks</a></li></ul> <h2 id="notes">Notes</h2> <h2 id="external-links">External links</h2> <ul><li><a href="https://web.archive.org/web/20100430190605/http://www.iana.org/assignments/ipv4-address-space/">IANA, Current IPv4 /8 delegations</a></li> <li><a href="https://web.archive.org/web/20110401192204/http://oreilly.com/catalog/coreprot/chapter/appb.html">Overview of IP addressing, both classless and classful</a> (404)</li> <li><a href="/facts/Jon_Postel/7FIv4teq">J. Postel</a> (September 1981). <a href="https://datatracker.ietf.org/doc/html/rfc790"><i>ASSIGNED NUMBERS</i></a>. Network Working Group. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.17487%2FRFC0790">10.17487/RFC0790</a>. <a href="/facts/Request_for_Comments/esftTvE7">RFC</a> <a href="https://datatracker.ietf.org/doc/html/rfc790">790</a>. <i>Obsolete.</i> It includes a list of Class A networks as of that date.</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>J. Postel, ed. (January 1980). INTERNET PROTOCOL - DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION. IETF. doi:10.17487/RFC0760. RFC 760. IEN 128. Obsolete. sec. 3.1. Obsoleted by RFC 791. Replaces IEN 123, 111, 80, 54, 44, 41, 28 and 26. Updated by RFC 777. <a href="/wiki/Jon_Postel" target="_blank">/wiki/Jon_Postel</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Clark, David D. (June 1978). A proposal for addressing and routing in the Internet. IETF. IEN 46. Retrieved 2014-01-08. <a href="https://www.rfc-editor.org/ien/ien46.txt" target="_blank">https://www.rfc-editor.org/ien/ien46.txt</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>J. Postel, ed. (September 1981). INTERNET PROTOCOL - DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION. IETF. doi:10.17487/RFC0791. STD 5. RFC 791. IEN 128, 123, 111, 80, 54, 44, 41, 28, 26. Internet Standard 5. Obsoletes RFC 760. Updated by RFC 1349, 2474 and 6864. <a href="/wiki/Jon_Postel" target="_blank">/wiki/Jon_Postel</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>J. Postel, ed. (September 1981). INTERNET PROTOCOL - DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION. IETF. doi:10.17487/RFC0791. STD 5. RFC 791. IEN 128, 123, 111, 80, 54, 44, 41, 28, 26. Internet Standard 5. Obsoletes RFC 760. Updated by RFC 1349, 2474 and 6864. <a href="/wiki/Jon_Postel" target="_blank">/wiki/Jon_Postel</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>S.E. Deering (July 1986). Host Extensions for IP Multicasting. Network Working Group. doi:10.17487/RFC0988. RFC 988. Obsolete. Obsoleted by RFC 1054 and 1112. <a href="/wiki/Steve_Deering" target="_blank">/wiki/Steve_Deering</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>Y. Rekhter; T. Li, eds. (September 1993). An Architecture for IP Address Allocation with CIDR. Network Working Group. doi:10.17487/RFC1518. RFC 1518. Historic. <a href="https://datatracker.ietf.org/doc/html/rfc1518" target="_blank">https://datatracker.ietf.org/doc/html/rfc1518</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>V. Fuller; T. Li; J. Yu; K. Varadhan (September 1993). Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy. Network Working Group. doi:10.17487/RFC1519. RFC 1519. Obsolete. Obsoleted by RFC 4632. Obsoletes RFC 1338. <a href="https://datatracker.ietf.org/doc/html/rfc1519" target="_blank">https://datatracker.ietf.org/doc/html/rfc1519</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>127.0.0.0 through 127.255.255.255 are reserved for loopback addresses. Although reserved, they are still part of the class A address group. <a href="/wiki/Localhost" target="_blank">/wiki/Localhost</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>MULTICAST_IP_ADDR. General Electric Digital Solutions. CIMPLICITY 10.0. In network prefix or Classless Inter-Domain Routing ( CIDR) notation, IP multicast addresses are summarized as 224.0.0.0/4. <a href="https://www.ge.com/digital/documentation/cimplicity/version10/oxy_ex-2/advanced_features/topics/g_cimplicity_advanced_features_multicast_ip_addr.html" target="_blank">https://www.ge.com/digital/documentation/cimplicity/version10/oxy_ex-2/advanced_features/topics/g_cimplicity_advanced_features_multicast_ip_addr.html</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>255.255.255.255 is reserved as the IPv4 broadcast address. <a href="/wiki/Broadcast_address" target="_blank">/wiki/Broadcast_address</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>M. Cotton; L. Vegoda (January 2010). Special Use IPv4 Addresses. RFC 5735. <a href="/wiki/RFC_(identifier)" target="_blank">/wiki/RFC_(identifier)</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> </ol>