Emerging Paradigms · Study deck
ZRP Routing: Tuning and Deployment
A campus route now reaches beyond its local zone, but working once does not prove that the radius is right.
Blueprint Bina is your guide for this deck.
After studying this chapter
Learning objectives
You will be able to:
- Explain: At that point the reactive half of ZRP has little useful work left, because IERP rarely discovers an inter-zone route and BRP has few meaningful border nodes through which to direct a query.
- Explain: rho = 2: proactive overhead is 43.2 MB/hr, reactive overhead is 3.54 MB/hr, total overhead is 46.74 MB/hr, and coverage is about 57% proactive.
- Explain: The position is a design contract, not a promise of automatic balance; the later sizing record must prove that both halves are doing useful work under the observed topology.
Major section
ZRP Radius Trade-offs
Misconception: Students often believe that increasing zone radius always improves ZRP performance by reducing route discovery overhead.
- Risk: high proactive overhead from maintaining routes to 50-100 nodes continuously.
- Risk: the protocol approaches pure DSDV overhead and loses its hybrid purpose.
- Risk: increased latency because even nearby nodes may require discovery.
Major section
Visual: Ad Hoc Network Schematic
The nodes organize through peer links without a fixed routing authority, so every zone and border decision is derived from changing neighbour relationships.
- Its nearby peers are candidates for proactive intra-zone state; nodes beyond that neighbourhood require a reactive search through border nodes.
Major section
Ad Hoc Routing Protocols
ZRP only makes sense relative to the costs paid by the two routing families it combines.
- The position is a design contract, not a promise of automatic balance; the later sizing record must prove that both halves are doing useful work under the observed topology.
Major section
ZRP Zone Radius for Campus
rho = 2: proactive overhead is 43.2 MB/hr, reactive overhead is 3.54 MB/hr, total overhead is 46.74 MB/hr, and coverage is about 57% proactive.
- rho = 3: proactive overhead is 151.2 MB/hr, reactive overhead is 2.03 MB/hr, total overhead is 153.23 MB/hr, and coverage is about 85% proactive.
- Alternative: If latency were critical (fire alarms), choose ρ=3 despite 3× overhead.
- Key Insight: Optimal zone radius depends on traffic locality pattern.
Major section
Overlarge ZRP Zones
Finish with an operating rule that can be monitored after deployment.
- If the radius covers almost every destination, IARP is maintaining nearly a complete routing table.
- High periodic control traffic with almost no reactive discoveries is evidence that the hybrid has collapsed toward proactive operation.
- Zone size constraint: Zone should cover 30-50% of network.
Major section
Overlarge ZRP Zones (continued)
Result: ZRP with oversized zone is strictly worse than DSDV - same overhead, more complexity, more bugs, more maintenance.
- Discovery latency may still remain because topology changes and implementations impose work of their own; the presence of three protocol components does not guarantee that their costs balance.
- A useful comparison keeps node positions, traffic, radio assumptions, and observation window fixed while changing only the radius.
- Reactive traffic target: 20-40% of traffic should require inter-zone discovery.
Major section
Overlarge ZRP Zones (continued)
The exact radius is deployment evidence, not a universal constant; density, mobility, traffic locality, and link asymmetry can all move the useful boundary.
- Re-run the same trace across candidate radii and reject settings that merely transfer too much cost from periodic maintenance into repeated discovery.
- Key Lesson: ZRP's benefit comes from the hybrid behavior - proactive for common local routes, reactive for rare distant routes.
- At that point the reactive half of ZRP has little useful work left, because IERP rarely discovers an inter-zone route and BRP has few meaningful border nodes through which to direct a query.
Deck summary
Key takeaways
Misconception: Students often believe that increasing zone radius always improves ZRP performance by reducing route discovery overhead.
- The nodes organize through peer links without a fixed routing authority, so every zone and border decision is derived from changing neighbour relationships.
- ZRP only makes sense relative to the costs paid by the two routing families it combines.
- rho = 2: proactive overhead is 43.2 MB/hr, reactive overhead is 3.54 MB/hr, total overhead is 46.74 MB/hr, and coverage is about 57% proactive.
- Finish with an operating rule that can be monitored after deployment.
Retrieval practice
Recall check 1 of 2
Blueprint Bina says: answer from memory, then check your reasoning.
Q1A sensor network has frequent local traffic and occasional distant messages. Which ZRP feature matches that pattern?
Show answer
Answer: C The chapter presents this combination as a fit for localized communication.
Q2A team enlarges ZRP zones to reduce discovery traffic. Which cost should it expect to review?
Show answer
Answer: B Larger zones maintain more routes and can lose the intended hybrid balance.
Retrieval practice
Recall check 2 of 2
Blueprint Bina says: answer from memory, then check your reasoning.
Q3Place each ZRP route-discovery role where it lives so you can see when proactive knowledge ends and reactive bordercast begins.
Show answer
Answer: A Separate the source and its IARP zone, the border handoff, and IERP bordercast so you can avoid treating ZRP as either pure flooding or pure table routing.
Q4Complete the ZRP routing decision helper:
Show answer
Answer: A ZRP first uses the proactive IARP table for in-zone destinations.
Print reference
Answers
Answer key.
- C · The chapter presents this combination as a fit for localized communication.
- B · Larger zones maintain more routes and can lose the intended hybrid balance.
- A · Separate the source and its IARP zone, the border handoff, and IERP bordercast so you can avoid treating ZRP as either pure flooding or pure table routing.
- A · ZRP first uses the proactive IARP table for in-zone destinations.