Classful network

Classful network
Jon Postel · Public domain · source
Name	Classful network
Type	Historical IP addressing scheme
Introduced	1981
Obsoleted	1993–1994
Standard	RFC 791; superseded by CIDR
Notable	Internet Engineering Task Force, ARPANET, XNS

Classful network

Classful addressing was an early Internet Protocol addressing architecture that partitioned the IPv4 address space into fixed-size ranges called classes. It originated during the development of ARPANET and early Internet Engineering Task Force standards and influenced deployments by organizations such as MIT, BBN Technologies, Bolt Beranek and Newman (BBN), and early Stanford University research networks. The scheme affected routing, allocation policy, and operational practice across networks run by institutions like NASA, DARPA, NASA Ames Research Center, and commercial providers that emerged in the 1980s and early 1990s.

Overview

Classful addressing divided 32-bit IPv4 addresses into discrete blocks identified by leading bit patterns standardized in RFC 791. The model produced fixed-size address populations used by registries including the Internet Assigned Numbers Authority and later regional bodies like RIPE NCC, ARIN, and APNIC as the Internet expanded. Major engineering work by groups at Xerox PARC, USC/ISI, University of California, Berkeley, and AT&T Bell Labs informed early TCP/IP allocation practices that relied on class boundaries. Academic projects such as Usenet, CSNET, NSFNET, and corporate networks at IBM and Hewlett-Packard adopted classful allocations, shaping operational guidance circulated through publications from IEEE and ACM conferences.

Address Classes and Formats

Classful addressing defined primary blocks known as Class A, Class B, Class C, Class D, and Class E based on leading bit patterns documented in RFC 791. Class A blocks began with a 0 bit and were allocated to major entities including government research groups and large corporations such as IBM, offering 8-bit network identifiers and 24-bit host fields. Class B blocks began with 10 and served mid-sized organizations including universities like Harvard University and University of Michigan with 16-bit network and 16-bit host fields. Class C blocks began with 110 and catered to smaller networks operated by companies such as Xerox and educational departments. Class D (1110) served multicast activities used by projects influenced by work at Bell Labs and in standards bodies like IETF working groups, while Class E (1111) was reserved for experimental uses considered by researchers at MIT AI Lab and Stanford Research Institute. Address notation used dotted-decimal representation popularized in teaching materials from Cisco Systems and texts by authors associated with Prentice Hall and O'Reilly Media.

Routing and Subnetting in Classful Networks

Routing in classful systems used network prefixes tied to class boundaries, implemented in early routers produced by vendors such as Cisco Systems, Juniper Networks predecessors, and research routers at UC Berkeley. Classful routing protocols like Routing Information Protocol (RIP) and early versions of Interior Gateway Routing Protocol reflected assumptions about contiguous class networks, influencing routing tables maintained by backbone providers including Sprint, MCI, and universities operating NSFNET nodes. Subnetting within classes introduced techniques formalized in documents produced by working groups at IETF and tools in network management suites from Sun Microsystems and HP. Administrators at institutions such as Princeton University and Columbia University used subnet masks to partition Class A or Class B allocations, a practice taught in courses referencing labs at MIT and Carnegie Mellon University.

Limitations and Decline

Operational strain appeared as the number of networks and hosts expanded across the academic, commercial, and government sectors including DARPA projects, commercial ISPs like UUNET, and corporate networks at Microsoft and Apple. The wasteful allocation granularity—especially of Class B blocks—led to address exhaustion pressures discussed at meetings of IETF and regional registries such as RIPE NCC. Scaling problems in backbone routing, routing table growth experienced by providers like Level 3 Communications and GTE affiliates, and the administrative overhead for registries accelerated interest in alternatives. Research by network engineers at Stanford University and MIT Laboratory for Computer Science contributed to proposals that culminated in the design of classless schemes.

Historical Impact and Transition to Classless Addressing

The classful era shaped early Internet topology, operational culture in entities like National Science Foundation, and addressing pedagogy used in textbooks by authors associated with Addison-Wesley and O'Reilly Media. Debates at IETF meetings and policy shifts at Internet Assigned Numbers Authority led to adoption of Classless Inter-Domain Routing (CIDR) and protocols such as OSPF and enhanced BGP implementations by vendors like Cisco Systems and research groups at RIPE NCC. Transition milestones included allocation policy changes coordinated with APNIC and ARIN and the retirement of classful assumptions in routing software used by backbone operators including Sprint and MCI WorldCom. The move to classless addressing enabled finer-grained aggregation, mitigated address exhaustion that affected stakeholders such as Microsoft, Sun Microsystems, and academic consortia, and set the stage for later developments like IPv6 advocated by institutions including IETF and Internet Society.

Category:Internet standards