# Comparing IP and CLNP: Network State Summarization

DevFeed: [Comparing IP and CLNP: Network State Summarization](<https://devfeed.tech/articles/comparing-ip-and-clnp-network-state-summarization-11150.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2025/03/comparing-ip-clnp-state-summarization/>)

Published: 2025-03-19T06:59:00Z

Content type: article

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [IP routing](<https://devfeed.tech/topics/ip-routing.md>), [networking](<https://devfeed.tech/topics/networking.md>), [IS-IS](<https://devfeed.tech/topics/is-is.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [BGP](<https://devfeed.tech/topics/bgp.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [ip-routing](<https://devfeed.tech/tags/ip-routing.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [is-is](<https://devfeed.tech/tags/is-is.md>), [networking-fundamentals](<https://devfeed.tech/tags/networking-fundamentals.md>), [routing](<https://devfeed.tech/tags/routing.md>), [tcp-ip](<https://devfeed.tech/tags/tcp-ip.md>)

## AI overview

This article compares how TCP/IP and CLNP summarize network state in routing protocols. It explains that TCP/IP routing generally provides subnet, intra-area, and inter-area summarization levels, while most CLNP networks used two levels based on node and area addresses, with BGP enabling additional levels in either design.

## Source excerpt

In the previous blog posts, we discussed how TCP/IP and CLNP reach adjacent nodes and build ARP/ND/ES caches and how they reach off-subnet nodes. Now, let's move from the network edge into the network core and explore how the two protocol stacks reduce the amount of information they have to propagate in routing protocols. While I'm not exactly an OSI fan, I must admit they got many things right (and IPv6 copied those ideas), but TCP/IP is a clear winner in this aspect. Read more ...