Internet Protocol

Internet Protocol
Name	Internet Protocol
Acronym	IP
Developer	Vint Cerf; Bob Kahn; DARPA
Initial release	1981 (RFC 791)
Type	Network layer protocol
Related	Transmission Control Protocol; User Datagram Protocol; OSI model
Status	Core protocol of the Internet

Internet Protocol is the principal network-layer standard that provides addressing and packet delivery across heterogeneous networks. It defines the format of datagrams, addressing semantics, and the mechanisms that enable internetworking among systems developed by disparate institutions such as ARPANET participants, research networks, and commercial providers. IP underlies many widely used protocols and services including World Wide Web applications, Simple Mail Transfer Protocol, and Voice over IP.

Overview

IP specifies how datagrams are formatted and routed to enable host-to-host communication over the Internet and interconnected networks. It separates addressing and forwarding from transport semantics used by Transmission Control Protocol and User Datagram Protocol, allowing diverse hardware and software platforms—such as routers from Cisco Systems and operating systems like Unix variants—to interoperate. The protocol’s responsibilities include logical addressing, fragmentation, reassembly, and minimal metadata for service classification used by devices adhering to standards from IETF and implementations in stacks provided by BSD and Linux.

History and Development

Design of the protocol began in the 1970s during research funded by DARPA for the ARPANET project led by researchers at institutions including Stanford University and BBN Technologies. Key architects such as Vint Cerf and Bob Kahn defined the end-to-end architecture that decoupled host-to-host packet transfer from underlying link technologies, inspired by earlier work at RAND Corporation and tests across campus networks like those at UCLA. The protocol suite evolved through standards produced by the IETF and documented in Requests for Comments, progressing from early experimental drafts to formal specifications such as RFCs shepherded by working groups that included contributors from Bell Labs, Xerox PARC, and major universities.

Protocol Design and Architecture

IP embodies an internetworking model that treats networks as a mesh of links connected by routers performing forwarding decisions. The architecture uses hierarchical addressing to abstract location from identity, enabling scalability across large topologies such as backbone networks operated by Level 3 Communications and regional ISPs. Design trade-offs—like the choice to provide a best-effort, connectionless service rather than guaranteed delivery—were influenced by principles advocated in papers presented at forums hosted by ACM and IEEE conferences. The protocol relies on complementary protocols for congestion control and reliability, exemplified by interactions with Transmission Control Protocol and routing protocols standardized by the IETF Routing Area.

Versions and Addressing (IPv4, IPv6)

Two primary families of the protocol coexist: a widespread 32-bit addressing version that emerged in early standards and a newer 128-bit addressing successor developed to address exhaustion and feature limitations. The legacy version’s address classes and subnetting were widely adopted by commercial networks and academic campuses including MIT and Carnegie Mellon University, while the successor introduced features such as hierarchical aggregation, built-in support for extension headers, and a vastly larger address space intended for global deployment across providers like AT&T and Verizon. Transition mechanisms, tunneling strategies, and dual-stack deployments were recommended by the IETF to enable gradual migration within operational contexts such as campus networks and content delivery infrastructures run by companies like Akamai.

Header Structure and Encapsulation

Each IP datagram contains a header with fields that control delivery, identification, and handling by routers and hosts. Header components include identifiers for version, length, service classification, and time-to-live values used by routers made by vendors such as Juniper Networks. Optional fields and extension headers allow protocols defined by working groups in the IETF to carry metadata for features like quality of service adopted by service providers and cloud operators such as Amazon Web Services and Google Cloud Platform. Encapsulation enables IP to carry payloads from higher-layer protocols including Transmission Control Protocol segments, User Datagram Protocol datagrams, and more specialized protocols used in environments managed by entities like NASA.

Routing and Fragmentation

Routers implement forwarding algorithms based on routing information exchanged via protocols standardized by the IETF Routing Area, including link-state and distance-vector protocols developed and deployed by networks operated by Sprint and research networks like Internet2. When datagrams traverse links with smaller maximum transmission units, fragmentation can occur: the sender or intermediate devices split datagrams into fragments that are reassembled at endpoints, a process governed by identification and offset fields specified in the protocol. Fragmentation behavior has operational implications for performance and security observed in carrier networks and academic testbeds, prompting network engineers at organizations such as IEEE-affiliated labs to prefer path MTU discovery techniques.

Security, Extensions, and Future Directions

Although the original design prioritized simplicity over built-in security, later work by standards bodies like the IETF produced companion specifications and extension frameworks—such as authentication and encryption mechanisms proposed in collaboration with groups like IETF working groups and security researchers from MITRE—to address confidentiality, integrity, and source authentication. Contemporary extensions and research explore integration with architecture proposals from initiatives at institutions like ITU and CNRS, enhanced routing security using mechanisms developed by teams at RIPE NCC and APNIC, and evolutions to support emerging requirements from platforms including Internet of Things deployments and edge computing initiatives by companies like Microsoft Azure. Future directions emphasize resiliency, automation, and privacy-preserving addressing while preserving interoperability across the diverse ecosystem of vendors, research labs, and service providers.

Category:Internet standards