Summarisation and address-space design: planning prefixes before the topology grows
Hierarchy is what lets prefixes aggregate; a flat address plan cannot be summarised.

A plan is a design decision made before the topology grows, not a record of whatever was handed out. Its purpose is one route to a designed block instead of one per segment inside it. A summary — RFC 4632’s aggregate route — is a route to a prefix short enough to contain several more specific routes, valid only when those components are contiguous and fully covered. Forwarding still compares one address at a time, so a more specific route can always punch a hole in a summary. The reserved pools — private, unique-local, special-purpose — are the material a plan is drawn from.
The model: allocate down a hierarchy, then let a summary cover it
A plan is a hierarchy of blocks, each a contiguous, power-of-two slice of its parent; one route to a parent therefore describes all its children. RFC 4632 gives the reason: “The assignment of prefixes is intended to roughly follow the underlying Internet topology so that aggregation can be used to facilitate scaling of the global routing system.” (rfc4632.txt lines 215–217).
design the block before the devices
root block 10.0.0.0/8 one plan, one hierarchy
site / region 10.0.0.0/12 10.16.0.0/12 10.32.0.0/12 ...
role 10.0.0.0/16 (users) 10.1.0.0/16 (servers)
segment 10.0.1.0/24 10.0.2.0/24 ...
a summary is the shortest aligned prefix that exactly covers its components
10.0.0.0/16 + 10.1.0.0/16 -> 10.0.0.0/15
10.0.0.0/17 + 10.0.128.0/17 -> 10.0.0.0/16
10.0.1.0/24 + 10.0.3.0/24, with 10.0.2.0/24 left unallocated:
every prefix covering both also covers the gap -> not a summary
forwarding still sees one address at a time
the longest matching prefix wins, so a more-specific route beats the
summary that contains it -> that route is a hole in the aggregate,
and the aggregate must discard the hole
Two conditions make routes collapse into one: contiguous, bit-aligned components — “the site’s routing information may be aggregated into a single prefix” (rfc4632.txt lines 478–480) — and a summary covering nothing else, since a prefix spanning two non-adjacent blocks also reaches the gap between them.
Terms
- Prefix — an address plus a length, the length counting the fixed leading bits; prefixes “may be defined to describe any power of two-sized block of between one and 2^32 end system addresses” (
rfc4632.txtlines 299–300). - Aggregation (summarisation) — replacing several more specific routes with one route to a shorter prefix containing them.
- More-specific route — a longer prefix inside the summary; it wins the lookup, so it carves a hole.
- Bit-aligned — the block occupies one power-of-two range (
rfc4632.txtlines 640–641), so the mask is left contiguous. - Reserved block — a range set aside by an RFC for a stated purpose rather than global unicast.
The mechanism, step by step
- Fix the hierarchy before the first address — sites, roles, growth — and allocate per role, not per device.
- Allocate downwards as contiguous slices: “Hierarchical delegation of addresses in this manner implies that sites with addresses assigned out of a given service provider are, for routing purposes, part of that service provider” (
rfc4632.txtlines 547–549). - Keep every block a power of two, aligned to its own length (
rfc4632.txtlines 640–641). - Summarise upward: the summary is the shortest prefix covering exactly its components; the shortest of all,
0.0.0.0/0, is the default route (“MUST be accepted by all implementations”,rfc4632.txtlines 641–643). - Forward by longest match (
rfc4632.txtline 601) — a lookup the L2 routing-table sheet owns. A more specific route is “preferred over provider aggregates because it is a longer match” (rfc4632.txtlines 464–465): that is the hole. - Install the discard, or the hole loops: the advertiser of an aggregate “must discard packets that match the aggregate route” but not its specifics, “to prevent forwarding loops when some addresses covered by the aggregate are not reachable” (
rfc4632.txtlines 610–614). - Where summarisation is impossible, advertise the specific: multi-homed destinations “cannot be summarized” (
rfc4632.txtlines 602–604).
The blocks a plan is drawn from
- Private IPv4 — RFC 1918. The IANA “has reserved the following three blocks of the IP address space for private internets”:
10.0.0.0/8,172.16.0.0/12,192.168.0.0/16(rfc1918.txtlines 177–182). An enterprise uses them “without any coordination with IANA or an Internet registry”, but they “will only be unique within the enterprise” (rfc1918.txtlines 191–195) — the same block at two sites is a collision. - Unique local IPv6 — RFC 4193. The format is
fc00::/7, whose L bit is “Set to 1 if the prefix is locally assigned.”, with a pseudo-random 40-bit Global ID (rfc4193.txtlines 151–155, 214–215). They are “not expected to be routable on the global Internet” (rfc4193.txtlines 32–33) and “not designed to aggregate”. - Special-purpose and documentation — RFC 6890. The registry records each reserved block with the fields Source, Destination, Forwardable and Global (
rfc6890.txtlines 205–248). Documentation blocks —192.0.2.0/24,198.51.100.0/24,203.0.113.0/24,2001:db8::/32— are marked not forwardable and not global (rfc6890.txtlines 514, 626, 643, 962): usable in examples, never in production.
Limits and the common mistake
The plan is cheap once and expensive to change: moving a host between private and public “involves a change of IP address, changes to the appropriate DNS entries, and changes to configuration files on other hosts that reference the host by IP address” (rfc1918.txt lines 231–234). The cost of a flat plan arrives later, as routing state — the strategy exists to limit “the growth rate of global routing state” (rfc4632.txt lines 30–32).
The common mistake is treating a summary as a route that only adds reachability. It also claims addresses: the aggregate covers everything in its range, so an unallocated gap must be discarded explicitly, or traffic for the gap loops. Two further traps: believing any two blocks can be summarised, when only contiguous, aligned siblings collapse; and treating private space as interchangeable between sites.
Level and prerequisites
L3 — integration and technical control. It assumes the L1 vocabulary of prefixes and prefix lengths, and cites rather than re-explains the longest-prefix-match lookup owned by the L2 sheet on the routing table, next hop and default gateway.
Where to go next
References
- RFC 4632 — Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan (BCP 122, August 2006): the purpose of the strategy (lines 30–32); prefix notation and the power-of-two block (lines 261–300); aggregation as the method for reducing routing state (lines 417–418); hierarchical delegation (lines 547–549); the multi-homing and renumbering holes (lines 461–466); the contiguous power-of-two allocation that aggregates (lines 478–480); route advertisement rules 1 and 2, the discard and the forwarding-loop reason (lines 601–618); the contiguous mask and the default route (lines 640–643).
- RFC 1918 — Address Allocation for Private Internets (BCP 5, February 1996): the three private blocks (lines 177–182); use without coordination and uniqueness within the enterprise (lines 191–195); the renumbering cost and the no-global-propagation rule (lines 231–239).
- RFC 4193 — Unique Local IPv6 Unicast Addresses (Standards Track, October 2005): not routable on the global Internet (lines 32–33); format and the L bit (lines 140–165); pseudo-random Global IDs and no aggregation (lines 208–215); border filtering of FC00::/7 (lines 359–361).
- RFC 6890 — Special-Purpose IP Address Registries (BCP 153, April 2013): the fields each entry carries (lines 205–248); the private-use entries (lines 312, 419, 570); the documentation blocks (lines 514, 626, 643, 962); the unique-local entry (line 1037); the security note on authenticating control of a block (lines 1088–1091).
- RFC 5737 and RFC 3849 govern the IPv4 and IPv6 documentation blocks named above; both are reached through their RFC 6890 registry entries (
rfc6890.txtlines 514, 962).