A campus with 64 subnets is reachable through a single upstream router. Why does summarizing those 64 routes into one entry speed up packet forwarding on distant routers?
Summarization compresses each IP packet so it travels across the backbone faster.
A shorter routing table means fewer records to search when looking up a destination match.
The summary route increases the link bandwidth available to the campus.
Summarization encrypts the routes so lookups skip a decryption step.
Inside a summarized block, one link keeps failing and recovering repeatedly ("flapping"). Why do distant routers remain undisturbed by this churn?
The summary route hides the block's internal detail, so a change inside it does not alter the advertised summary.
Distant routers automatically ignore any route that changes more than once per minute.
Flapping links are removed from the routing table permanently after the first failure.
The summarizing router forwards each flap event to every distant router so they can prepare.
A network designer scattered subnets as 10.1.5.0, 10.1.200.0, and 10.1.12.0 across the address space. Why can these NOT be folded into one clean summary?
They belong to different address classes and classes cannot be mixed.
They use the private 10.0.0.0 range, which cannot be summarized.
They are not contiguous, so they do not share a common high-order bit pattern that a single prefix could represent.
They each have a different subnet mask, and summarization requires identical masks.
The chapter compares a summary route to an international mail sorting center. What is the key idea that analogy illustrates?
Every router must eventually store the exact address of every network on Earth.
Distant devices hold one coarse entry for a whole region, and fine-grained detail is resolved locally near the destination.
Mail and packets both travel faster when split into smaller pieces.
Routing tables should be organized alphabetically like postal codes.
Why is hierarchical (structured, contiguous) address allocation described as a prerequisite for summarization rather than an optional optimization?
Because routing protocols refuse to advertise any address that is not hierarchical.
Because only contiguously assigned blocks share common high-order bits, which is what a summary prefix captures.
Because hierarchical addressing is the only way to assign more than 254 hosts to a subnet.
Because non-hierarchical addresses consume more memory per routing entry.
The Case for Summarization
Key Points
- Route summarization creates one general summary route that stands in for many specific routes; applied to classful blocks it is called supernetting.
- Shorter routing tables use less router memory and are searched faster, so packet forwarding speeds up.
- Advertising one summary instead of many routes reduces update traffic and saves bandwidth between routers.
- Summarization improves stability: it hides internal topology changes (like a flapping link) so distant routers are not forced to reconverge.
- All of this depends on hierarchical addressing — contiguous allocation so related networks share common high-order bits.
Route summarization creates one summary route that represents multiple networks or subnets. It is also called route aggregation, and when applied to whole classful blocks it is called supernetting. A summary route is the single, more general entry that stands in for a group of more specific routes.
Without summarization every subnet needs its own routing entry. A campus with 64 subnets produces 64 entries on every router that must reach it, and across a large enterprise tables balloon into thousands of records. Large tables cost real resources: more memory on every router, and slower lookups because more records must be searched for a match. Summarization shortens the table, so decisions and forwarding happen faster. The most dramatic case is the Internet backbone, where CIDR and supernetting let an ISP advertise one aggregated block instead of thousands of individual class-based networks.
Summarization also reduces advertisement traffic: sending one summary instead of many specific routes means fewer and smaller routing updates, saving bandwidth. It adds stability too — when a summary hides a block's internal detail, a link that flaps inside the block does not force distant routers to update. The summarizing router absorbs the churn; the rest of the network never sees it.
Visual animation — coming soon
Hierarchical addressing means allocating blocks in a structured, contiguous way so related networks share common high-order bits and can be folded together cleanly. If subnets are scattered randomly — 10.1.5.0 here, 10.1.200.0 there, 10.1.12.0 elsewhere — no clean summary boundary exists, and each subnet must be advertised on its own. Good address design enables summarization; it is a planning-stage decision, not an afterthought.
Figure 9.2: Hierarchical addressing collapsing a routing table into nested summaries
graph TD
B["Backbone router sees: 10.0.0.0/8"]
B --> C1["Region East: 10.1.0.0/16"]
B --> C2["Region West: 10.2.0.0/16"]
C1 --> S1["Campus A: 10.1.0.0/22"]
C1 --> S2["Campus B: 10.1.4.0/22"]
C2 --> S3["Campus C: 10.2.0.0/22"]
S1 --> L1["10.1.0.0/24 ... 10.1.3.0/24"]
S2 --> L2["10.1.4.0/24 ... 10.1.7.0/24"]
S3 --> L3["10.2.0.0/24 ... 10.2.3.0/24"]
A campus with 64 subnets is reachable through a single upstream router. Why does summarizing those 64 routes into one entry speed up packet forwarding on distant routers?
Summarization compresses each IP packet so it travels across the backbone faster.
A shorter routing table means fewer records to search when looking up a destination match.
The summary route increases the link bandwidth available to the campus.
Summarization encrypts the routes so lookups skip a decryption step.
Inside a summarized block, one link keeps failing and recovering repeatedly ("flapping"). Why do distant routers remain undisturbed by this churn?
The summary route hides the block's internal detail, so a change inside it does not alter the advertised summary.
Distant routers automatically ignore any route that changes more than once per minute.
Flapping links are removed from the routing table permanently after the first failure.
The summarizing router forwards each flap event to every distant router so they can prepare.
A network designer scattered subnets as 10.1.5.0, 10.1.200.0, and 10.1.12.0 across the address space. Why can these NOT be folded into one clean summary?
They belong to different address classes and classes cannot be mixed.
They use the private 10.0.0.0 range, which cannot be summarized.
They are not contiguous, so they do not share a common high-order bit pattern that a single prefix could represent.
They each have a different subnet mask, and summarization requires identical masks.
The chapter compares a summary route to an international mail sorting center. What is the key idea that analogy illustrates?
Every router must eventually store the exact address of every network on Earth.
Distant devices hold one coarse entry for a whole region, and fine-grained detail is resolved locally near the destination.
Mail and packets both travel faster when split into smaller pieces.
Routing tables should be organized alphabetically like postal codes.
Why is hierarchical (structured, contiguous) address allocation described as a prerequisite for summarization rather than an optional optimization?
Because routing protocols refuse to advertise any address that is not hierarchical.
Because only contiguously assigned blocks share common high-order bits, which is what a summary prefix captures.
Because hierarchical addressing is the only way to assign more than 254 hosts to a subnet.
Because non-hierarchical addresses consume more memory per routing entry.
You summarize the four networks 10.1.0.0/24, 10.1.1.0/24, 10.1.2.0/24, and 10.1.3.0/24. In the third octet their binary values are 00000000, 00000001, 00000010, 00000011. What summary prefix results, and why?
/22, because the first six bits of the third octet are common (16 + 6 = 22).
/24, because all four networks are already /24 networks.
/26, because four networks means adding two host bits.
/20, because you always drop a full octet when summarizing.
An engineer summarizes 32 contiguous /24 networks that align on a proper boundary. What summary prefix length should result?
/29, because 32 hosts need 5 host bits.
/19, because 32 = 2⁵, so the /24 prefix shortens by 5 bits.
/32, because 32 networks map to a /32 mask.
/22, because summarizing always shortens the prefix by 2 bits.
Eight /24 networks summarize cleanly to 172.16.0.0/21 only when they begin on a /21 boundary. Which starting network would NOT summarize exactly to a single /21?
172.16.0.0
172.16.8.0
172.16.3.0
172.16.16.0
The summary 172.16.0.0/21 was computed by keeping the common high-order bits. What role do the varying (non-common) bits play in the summary?
They are discarded entirely and no longer represent anything.
They become host space inside the summary and are set to 0 in the summary address.
They are copied unchanged from the last network in the set.
They determine the next-hop router the summary points to.
An administrator later configures 192.168.104.0/24 and expects it to be covered by an existing 192.168.100.0/22 summary. Why does it fall outside?
Because /22 summaries can only cover three /24 networks, not four.
Because the /22 covers 192.168.100.0 through 192.168.103.0; 104 is beyond that power-of-two range.
Because 192.168.104.0 is a broadcast address and cannot be summarized.
Because the fourth octet changed, which breaks the summary.
How to Summarize
Key Points
- A summary is the longest common bit pattern shared by all networks; its length is the summary prefix length.
- Procedure: write the differing octet in binary, count consecutive matching bits from the left, add them to the fixed prefix bits.
- Summarizing 2ⁿ contiguous networks shortens the prefix by n bits (4 → /22, 8 → /21, 16 → /20, 32 → /19).
- Varying bits become host space and are set to 0 in the summary address.
- For an exact summary the block must be contiguous AND start on a power-of-two boundary, or it will miss or over-cover networks.
A router calculates a summary by finding the longest common bit pattern shared by all networks in the set. That common prefix length becomes the summary route's prefix length. Take four contiguous /24s and write the third octet in binary:
| Network | Third octet (binary) |
|---|
| 10.1.0.0 | 00000000 |
| 10.1.1.0 | 00000001 |
| 10.1.2.0 | 00000010 |
| 10.1.3.0 | 00000011 |
The first six bits of the third octet (000000) are identical; only the last two vary. The common prefix is 8 + 8 + 6 = 22 bits, so the summary is 10.1.0.0/22.
Figure 9.1: Four contiguous /24 networks aggregating into one summary route
graph TD
S["Summary route: 10.1.0.0/22"]
S --> N0["10.1.0.0/24"]
S --> N1["10.1.1.0/24"]
S --> N2["10.1.2.0/24"]
S --> N3["10.1.3.0/24"]
A Full Worked Example
Summarize eight /24s from 172.16.0.0 to 172.16.7.0. The first two octets (172.16) are fixed, so the action is in the third octet. The first five bits (00000) are identical; the last three cycle through 000 to 111. Adding 16 fixed bits + 5 common bits = 21, so the summary is 172.16.0.0/21. A /21 mask is 11111111.11111111.11111000.00000000 = 255.255.248.0.
Figure 9.3: The common-high-order-bits summarization procedure
flowchart TD
A["List all networks in binary"] --> B["Focus on the octet where they differ"]
B --> C["Compare left to right; count consecutive matching bits"]
C --> D["Summary prefix = fixed bits + common bits"]
D --> E["Set varying (host) bits to 0 for the summary address"]
E --> F["Convert prefix length to dotted-decimal mask"]
F --> G["Summary: 172.16.0.0/21 (255.255.248.0)"]
The rule of thumb: the number of contiguous networks summarized is always a power of two, and summarizing 2ⁿ networks shortens the prefix by n bits.
| Contiguous /24s | Power of two | Prefix shortens by | Summary prefix |
|---|
| 2 | 2¹ | 1 bit | /23 |
| 4 | 2² | 2 bits | /22 |
| 8 | 2³ | 3 bits | /21 |
| 16 | 2⁴ | 4 bits | /20 |
| 32 | 2⁵ | 5 bits | /19 |
Visual animation — coming soon
Contiguity Requirements
Two conditions must hold for a summary to be exact. First, the block must be contiguous — networks adjacent with no gaps, sharing a common high-order pattern. Second, the summary boundary must fall on a power-of-two boundary: the starting network must be a multiple of the block size. Eight /24s summarize cleanly to a /21 only when they start on a /21 boundary (172.16.0.0, 172.16.8.0, 172.16.16.0). Eight /24s starting at 172.16.3.0 would not align to a single /21. Ignore these rules and a summary can accidentally cover addresses you never intended, or leave intended networks stranded.
You summarize the four networks 10.1.0.0/24, 10.1.1.0/24, 10.1.2.0/24, and 10.1.3.0/24. In the third octet their binary values are 00000000, 00000001, 00000010, 00000011. What summary prefix results, and why?
/22, because the first six bits of the third octet are common (16 + 6 = 22).
/24, because all four networks are already /24 networks.
/26, because four networks means adding two host bits.
/20, because you always drop a full octet when summarizing.
An engineer summarizes 32 contiguous /24 networks that align on a proper boundary. What summary prefix length should result?
/29, because 32 hosts need 5 host bits.
/19, because 32 = 2⁵, so the /24 prefix shortens by 5 bits.
/32, because 32 networks map to a /32 mask.
/22, because summarizing always shortens the prefix by 2 bits.
Eight /24 networks summarize cleanly to 172.16.0.0/21 only when they begin on a /21 boundary. Which starting network would NOT summarize exactly to a single /21?
172.16.0.0
172.16.8.0
172.16.3.0
172.16.16.0
The summary 172.16.0.0/21 was computed by keeping the common high-order bits. What role do the varying (non-common) bits play in the summary?
They are discarded entirely and no longer represent anything.
They become host space inside the summary and are set to 0 in the summary address.
They are copied unchanged from the last network in the set.
They determine the next-hop router the summary points to.
An administrator later configures 192.168.104.0/24 and expects it to be covered by an existing 192.168.100.0/22 summary. Why does it fall outside?
Because /22 summaries can only cover three /24 networks, not four.
Because the /22 covers 192.168.100.0 through 192.168.103.0; 104 is beyond that power-of-two range.
Because 192.168.104.0 is a broadcast address and cannot be summarized.
Because the fourth octet changed, which breaks the summary.
How does supernetting relate to subnetting?
It is the inverse: subnetting uses a longer prefix to create smaller networks, supernetting uses a shorter prefix to create a larger one.
It is identical to subnetting but performed only on Class A addresses.
It uses a longer prefix than subnetting to pack in more hosts.
It replaces subnetting entirely and cannot coexist with it in one network.
Four consecutive Class C networks 192.168.0.0/24 through 192.168.3.0/24 are aggregated. What supernet represents them, and what range does it cover?
192.168.0.0/22, covering 192.168.0.0 through 192.168.3.255.
192.168.0.0/24, covering only 192.168.0.0 through 192.168.0.255.
192.168.0.0/23, covering 192.168.0.0 through 192.168.1.255.
192.168.0.0/20, covering 192.168.0.0 through 192.168.15.255.
Why does a supernet such as 192.168.0.0/22 require CIDR rather than the traditional classful system?
Because CIDR is the only system that allows private addresses to be routed.
Because a /22 prefix is shorter than the /24 classful default and does not match any traditional class boundary.
Because classful routing cannot forward packets to Class C addresses at all.
Because CIDR encrypts the prefix so it can cross class boundaries.
A router advertises a 192.168.50.0/22 summary but only 192.168.50.0/24 and 192.168.51.0/24 actually exist behind it. What is the danger?
The summary is too narrow, so the two real networks become unreachable.
The summary is too broad, so the router attracts traffic for .52.0 and .53.0 that it cannot deliver, black-holing packets.
Nothing — a broader summary always improves reachability.
The router will automatically split the summary back into /24s.
Given the risks of over-summarization, what is the disciplined design practice the chapter recommends?
Always summarize as broadly as possible to keep tables as small as they can be.
Summarize only truly contiguous, power-of-two-aligned blocks and reserve address ranges hierarchically so future growth fits inside existing boundaries.
Never summarize on the backbone, only inside a single campus.
Summarize non-contiguous blocks by padding the gaps with static routes.
Supernetting in Practice
Key Points
- Supernetting combines multiple (often classful) blocks into a larger block using a prefix shorter than the classful default — the inverse of subnetting.
- Four consecutive Class C /24s (192.168.0.0–192.168.3.0) become one supernet, 192.168.0.0/22, covering .0.0 through .3.255.
- CIDR makes the shorter-than-classful prefix legal and routable; protocols like BGP, OSPF, EIGRP, and RIP advertise the aggregate.
- Over-summarization is the chief danger: a too-broad summary black-holes traffic; a misaligned one strands networks.
- Summarize only clean, contiguous, power-of-two-aligned ranges and plan address space for future growth.
Supernetting combines multiple smaller network blocks into a larger, more efficient block. It is precisely the inverse of subnetting: subnetting uses a longer prefix (more network bits) to create smaller networks, while supernetting uses a shorter prefix (fewer network bits) to create a larger one.
The classic scenario combines contiguous Class C /24 blocks. Given four consecutive Class C networks — 192.168.0.0/24, 192.168.1.0/24, 192.168.2.0/24, 192.168.3.0/24 — the first six bits of the third octet are common, so they combine into the single supernet 192.168.0.0/22, covering 192.168.0.0 through 192.168.3.255 in one routing entry.
Figure 9.4: Four Class C blocks combined into a single CIDR supernet
graph TD
SN["Supernet: 192.168.0.0/22 (covers .0.0 through .3.255)"]
SN --> B0["192.168.0.0/24"]
SN --> B1["192.168.1.0/24"]
SN --> B2["192.168.2.0/24"]
SN --> B3["192.168.3.0/24"]
| Without supernetting | With supernetting |
|---|
| 192.168.0.0/24 → next hop | 192.168.0.0/22 → next hop |
| 192.168.1.0/24 → next hop | |
| 192.168.2.0/24 → next hop | |
| 192.168.3.0/24 → next hop | |
| 4 routing entries | 1 routing entry |
CIDR Supernets
Supernetting is closely tied to CIDR (Classless Inter-Domain Routing), which abandons rigid class boundaries for arbitrary prefix lengths. A supernet is expressed in CIDR notation — e.g. 192.168.0.0/22 — precisely because a /22 mask matches no traditional class. CIDR is what makes the shorter-than-classful prefix legal and routable. Protocols such as EIGRP, OSPF, RIP, and BGP support configuring summary or aggregate addresses at routing boundaries; on the backbone, BGP is exactly how an ISP announces one aggregated block on behalf of many customer networks.
Pitfalls of Over-Summarization
Summarizing too aggressively creates its own problems: a summary can advertise reachability to address space that does not exist behind the summarizing router. Recall that 192.168.100.0/22 covers 192.168.100.0 through 192.168.103.255; folding in 192.168.104.0/24 fails because it lies outside the /22.
| Pitfall | What happens | Consequence |
|---|
| Summary too broad | Claims a larger range than the networks that actually exist behind the router | Attracts traffic it cannot deliver; packets may be black-holed |
| Summary too narrow / misaligned | Some intended networks fall outside the summary boundary | Those networks are unreachable via the summary; need separate routes |
| Non-contiguous block | Networks do not share a clean common prefix | No exact summary exists; forcing one over-includes address space |
The disciplined practice: summarize only truly contiguous, power-of-two-aligned blocks, and reserve address ranges hierarchically so future growth fits inside existing boundaries. Over-summarization is almost always a symptom of address space that was not allocated with aggregation in mind.
How does supernetting relate to subnetting?
It is the inverse: subnetting uses a longer prefix to create smaller networks, supernetting uses a shorter prefix to create a larger one.
It is identical to subnetting but performed only on Class A addresses.
It uses a longer prefix than subnetting to pack in more hosts.
It replaces subnetting entirely and cannot coexist with it in one network.
Four consecutive Class C networks 192.168.0.0/24 through 192.168.3.0/24 are aggregated. What supernet represents them, and what range does it cover?
192.168.0.0/22, covering 192.168.0.0 through 192.168.3.255.
192.168.0.0/24, covering only 192.168.0.0 through 192.168.0.255.
192.168.0.0/23, covering 192.168.0.0 through 192.168.1.255.
192.168.0.0/20, covering 192.168.0.0 through 192.168.15.255.
Why does a supernet such as 192.168.0.0/22 require CIDR rather than the traditional classful system?
Because CIDR is the only system that allows private addresses to be routed.
Because a /22 prefix is shorter than the /24 classful default and does not match any traditional class boundary.
Because classful routing cannot forward packets to Class C addresses at all.
Because CIDR encrypts the prefix so it can cross class boundaries.
A router advertises a 192.168.50.0/22 summary but only 192.168.50.0/24 and 192.168.51.0/24 actually exist behind it. What is the danger?
The summary is too narrow, so the two real networks become unreachable.
The summary is too broad, so the router attracts traffic for .52.0 and .53.0 that it cannot deliver, black-holing packets.
Nothing — a broader summary always improves reachability.
The router will automatically split the summary back into /24s.
Given the risks of over-summarization, what is the disciplined design practice the chapter recommends?
Always summarize as broadly as possible to keep tables as small as they can be.
Summarize only truly contiguous, power-of-two-aligned blocks and reserve address ranges hierarchically so future growth fits inside existing boundaries.
Never summarize on the backbone, only inside a single campus.
Summarize non-contiguous blocks by padding the gaps with static routes.