Its job in the system
IP is the common layer that allows diverse networks to interconnect. A packet carries addressing and other control information along with its payload. Routers use the destination address to move packets towards a network that can deliver them. The payload can belong to many different applications without each intermediate network needing to understand that application.
How it works
An IP address identifies a network interface or addressing destination within the protocol’s scheme; it is not a permanent identity card for a person. IPv4 and IPv6 use different address formats and rules. IPv6 has a much larger address space. The two versions coexist, with deployment and transition arrangements varying between networks.
IP forwarding offers best-effort delivery: a packet can be lost, delayed, duplicated, or arrive out of order. IP by itself does not promise that a complete page will arrive. Higher layers provide the behaviours an application needs. A hop limit, or its IPv4 counterpart, helps prevent a packet from circulating indefinitely through routing loops.
Same application, different links
Illustrative example: a packet leaves a phone through a local radio link and later crosses an optical connection in the provider’s network. The local link framing changes as equipment forwards it between links, but IP provides a common addressing role across those technologies. A destination address is still not a delivery guarantee. This fictional path does not trace a real provider or packet capture; it explains why applications can communicate across a mixture of media without handling each physical link themselves.
What it connects to
The sending host places transport data into IP packets, and local link mechanisms carry each packet to the next hop. At another link the local framing changes, while the IP layer provides continuity across the route. Routers, transport protocols, and DNS each solve a different part of getting useful data to the right application.
Different places, different designs
Public addressing, private IPv4 networks, address translation, IPv6, tunnels, and enterprise policies create different deployments. A home may share one externally visible IPv4 address among several devices. These variations are deliberately collapsed in the overview, which focuses on communication roles rather than a full configuration.
Sources & further reading
Original explanations informed by these sources. Diagrams are conceptual; local systems differ.
- RFC 8200: Internet Protocol, Version 6 (IPv6) Specification IETF / RFC Editor; S. Deering and R. Hinden · 2017-07 · Source & rights record
- RFC 1122: Requirements for Internet Hosts — Communication Layers IETF / RFC Editor; R. Braden (editor) · 1989-10 · Source & rights record
- RFC 1812: Requirements for IP Version 4 Routers IETF / RFC Editor; F. Baker (editor) · 1995-06 · Source & rights record
- RFC 9293: Transmission Control Protocol (TCP) IETF / RFC Editor; W. Eddy (editor) · 2022-08 · Source & rights record