Information-centric Networking
Information-centric networking (ICN) is a network architecture that retrieves data by content name rather than host address, shifting communication from host-to-host delivery toward named-content retrieval. The network locates and delivers requested content from any node that holds a copy.
What Is Information-centric Networking?
Information-centric networking (ICN) is a network architecture that retrieves data by content name rather than by host address, shifting the fundamental communication model of the internet from host-to-host delivery toward named-content retrieval. In the traditional IP model, a client opens a connection to a specific server identified by its IP address and port. In an ICN architecture, the client instead issues a request for a named piece of data, and the network itself is responsible for locating and delivering that content, potentially from any node that holds a copy. This design reflects the observation that most internet traffic is content retrieval rather than endpoint-to-endpoint communication.
The concept emerged from research in the 2000s, with two prominent architectures gaining traction: Named Data Networking (NDN), developed at UCLA, and Content-Centric Networking (CCNx), originally developed at Xerox PARC. Both share core design principles and their terminology is defined in IETF RFC 8793, which standardizes ICN vocabulary. NIST has also conducted a dedicated Information Centric Networking program examining ICN's potential for future internet architectures.
Name-Based Routing and Forwarding
In an ICN network, content is identified by hierarchical, human-readable names rather than IP addresses. A consumer node sends an Interest packet naming the desired content; routers forward the Interest toward producers using a Forwarding Information Base (FIB) that maps name prefixes to interfaces, analogous to how an IP routing table maps address prefixes. A router maintains a Pending Interest Table (PIT) recording which interface each outstanding Interest arrived on, so that the returning Data packet can be forwarded back along the reverse path without explicit return address headers. This stateful forwarding plane enables native multicast delivery: if multiple consumers request the same name, a single Data packet travels upstream and is replicated at branching points, reducing redundant transmission.
In-Network Caching
A distinguishing feature of ICN is that any network node, not just origin servers or dedicated CDN nodes, can cache and serve content. When a Data packet traverses a router, that router may store a copy in its Content Store (CS). Subsequent Interest packets for the same name can be satisfied from the cache without reaching the original producer, reducing latency and backbone traffic. This ubiquitous caching property makes ICN a natural architecture for content distribution at scale, and it also improves resilience: cached copies survive if the origin server becomes temporarily unreachable. Cache replacement policies, naming granularity, and the interaction between caching and content security are active research areas in the ICN literature covered in publications from the IEEE Communications Society.
Security and Trust
ICN incorporates content-centric security rather than channel security. Each Data packet is cryptographically signed by its producer and carries an embedded signature along with the signer's certificate, so authenticity can be verified by any node, including intermediate caches, without requiring a secure channel to the original source. This approach decouples data trustworthiness from the trustworthiness of the transport path, addressing a structural limitation of TLS, which secures the channel but not the data objects themselves. Interest packets can include authentication tokens for access-controlled content, and namespace ownership can be tied to cryptographic key pairs rather than administrative registries.
Applications
Information-centric networking has applications in a wide range of disciplines, including:
- Content delivery networks and large-scale video streaming
- Internet of Things deployments where devices publish sensor data by name
- Vehicular networking and connected infrastructure with intermittent connectivity
- Disaster response communications where topology changes frequently
- Edge computing scenarios requiring low-latency content retrieval