Check: Address checks and recovery evidence

Knowledge check · self-test
Check: Address checks and recovery evidence
Explain DAD outcomes and decide whether burst recovery meets the release budgets.
Explain DAD outcomes and decide whether burst recovery meets the release budgets.
Checkpoint: Evidence Before Release {.depth-l0}
- Prove uniqueness enforcement or duplicate recovery under concurrent joins.
- Prove airtime recovery under the busiest credible burst.
- Keep user-visible outcomes beside protocol counters.
:::::: {.callout-tip}
##
Checkpoint: Recovery Is Capacity {.depth-l0}
- Detection does not make a collision free.
- Eventual success can still miss latency, energy, or correctness budgets.
- Persistent recovery is an escalation signal, not normal background noise.
:::::: {.callout-tip}
###
Checkpoint: Collision Domain {.depth-l0}
- Address collisions and transmission overlaps can share pair-counting mathematics but have different consequences.
- “At least one overlap” is not the same metric as “percentage of packets lost.”
- If traffic is synchronized, independent-uniform assumptions are not credible.
:::::: {.callout-tip}
###
Checkpoint: Release Evidence {.depth-l0}
- Keep the model inputs and acceptance target with the release record.
- Stress duplicate detection or airtime recovery under the busiest credible event.
- Compare the estimate with field evidence and revise the model when they disagree.
:::Back to Collision Mitigation Strategies: Keep a Reviewable Release Record