Expand description
How old a signed control frame is allowed to be.
control_signing_payload_v2 puts the frame’s timestamp inside the
signature. This module is what reads it back: the windows the two ends
allow, and the one comparison that turns a stamp and a clock into a
verdict.
§Why the windows live beside each other
A phone and a leaf node allow different ages, and that difference is a shared fact rather than each end’s private policy. A frame the phone is still willing to retransmit is a frame the leaf may be asked to verify, so a leaf window shorter than the phone’s retransmission horizon is a pair that refuses its own traffic. Keeping both numbers in one file is what makes that relationship checkable; splitting them is how one end is later retuned alone and the refusals show up on a device.
Enums§
- Freshness
- What a verifier concluded about a control frame’s age.
Constants§
- CTRL_
FRESHNESS_ FUTURE_ MS - How far into the future a control frame’s timestamp may sit before a verifier refuses it.
- CTRL_
FRESHNESS_ PAST_ MS - How far in the past a control frame’s timestamp may sit before a phone refuses it.
- LEAF_
CTRL_ FRESHNESS_ PAST_ MS - How far in the past a control frame’s timestamp may sit before a leaf node refuses it.
Functions§
- control_
frame_ freshness - Judges a control frame’s timestamp against a verifier’s clock.