RFC 791

RFC 791

RFC 791 is the Internet standard document that specifies the Internet Protocol version 4. It defines packet formats, addressing, fragmentation, and basic routing behaviors that underpin early and modern internetworking. The specification was authored during the ARPANET era and has influenced protocols, implementations, and standards bodies across computing and telecommunications.

Overview

RFC 791 establishes the Internet Protocol (IPv4) packet structure, header fields, addressing scheme, and fragmentation mechanisms used for internetwork datagram delivery. The document formalizes interactions between the protocol and related specifications such as Transmission Control Protocol, User Datagram Protocol, ICMP, and works from the ARPANET project and DARPA research. It situates IPv4 within standards processes involving the Internet Engineering Task Force, Internet Research Task Force, and the Internet Assigned Numbers Authority for address allocation practices.

Historical context and development

RFC 791 was developed in the late 1970s and published in 1981 amid efforts by researchers from institutions including the University of California, Los Angeles, Stanford University, Massachusetts Institute of Technology, and contractors associated with Bolt Beranek and Newman. The work followed earlier documents like the RFC 760 series and drew on experiments from the ARPANET and packet-switching deployments explored by DARPA funding. Key contributors included figures from USC Information Sciences Institute and academics who collaborated via the Internet Configuration Control Board and early IETF precursor groups. The specification helped align commercial vendors such as IBM, DEC, Xerox, and Sun Microsystems with academic research, promoting interoperability across campus networks, government labs, and early commercial internets.

Technical specifications

RFC 791 prescribes the IPv4 datagram header, including fields for Version, Internet Header Length, Type of Service, Total Length, Identification, Flags, Fragment Offset, Time to Live, Protocol, Header Checksum, Source Address, and Destination Address. These elements interact with upper-layer protocols like Transmission Control Protocol and User Datagram Protocol and with diagnostic protocols such as Internet Control Message Protocol. Addressing in RFC 791 uses 32-bit addresses and implicit class-based allocations that later motivated CIDR and address exhaustion mitigation efforts coordinated by the Internet Assigned Numbers Authority and regional registries like ARIN, RIPE NCC, and APNIC. Fragmentation and reassembly rules affect routers and hosts built by vendors including Cisco Systems, Juniper Networks, and network stacks in Microsoft Windows and BSD families. The Time to Live field was intended to prevent loops, aligning routing behavior with protocols like Border Gateway Protocol and interior protocols such as OSPF and IS-IS. Security assumptions in the original specification influenced later work by the Internet Engineering Task Force and security researchers at institutions like SRI International and RAND Corporation.

Implementation and deployment

IPv4 as specified by RFC 791 was implemented in operating systems and network devices from vendors and projects including BSD, NetBSD, FreeBSD, Linux, SunOS, VMS, Cisco IOS, and academic prototypes on machines such as the DEC PDP-11 and VAX. Deployment across research networks, campus networks, commercial service providers, and national backbones connected via organizations like NSFNET, CERFnet, BITNET, and later commercial carriers led to global adoption. Network management and address assignment practices evolved through coordination with the Internet Assigned Numbers Authority, regional registries ARIN, RIPE NCC, APNIC, and operational communities like the Operational Research Group and IETF working groups. Performance and interoperability testing involved labs at MITRE Corporation, Bell Labs, and university networking groups, while commercial routers by Cisco Systems and switching equipment by Juniper Networks implemented routing behaviors consistent with RFC 791’s semantics.

Impact and legacy

RFC 791’s specification of IPv4 underlies the modern Internet’s architecture and influenced successor work such as Internet Protocol version 6, address allocation policies by IANA, and many protocol families standardized by the IETF. Its addressing limitations prompted projects and policies addressing IPv4 exhaustion, including Classless Inter-Domain Routing and the development of IPv6 adoption initiatives led by organizations like IETF and RIPE NCC. The document shaped vendor implementations across Cisco Systems, Juniper Networks, Microsoft, and open-source communities like NetBSD and Linux Kernel networking. Educational curricula at institutions including MIT, Stanford University, and Carnegie Mellon University teach RFC 791 as foundational reading, and research in areas such as network security, routing scalability, and protocol design continues to reference its concepts in papers from ACM SIGCOMM, IEEE INFOCOM, and other conferences. Category:Internet standards