const SSA_REPEAT_RESEND_GRACE: Duration;Expand description
How long after a batch’s commitments last went out the Entry takes a repeat of its request to mean that they were lost on the way, rather than that the repeat crossed them.
The Exit repeats a successor request while some member of it has received no part of its
commitment. A repeat it sent before the burst reached it can still be arriving up to a round trip
after the burst went out, and answering that one would spend a retransmission on a burst that is
not lost. A repeat that arrives later says the burst went out and none of it arrived. Publishing
a burst only means the local transport took it, and a relayer that dies on the forward path loses
all of it. The Exit then has no part it could name in a scoped re-request, so the repeat is the
only prompt there is. See SessionSsaState::unpublished.
Well over a round trip, and equal to the Exit’s default re-send interval. A path slower than this
costs at most one needless re-send per grace, and each re-send spends one of the cycle’s
MAX_COMMITMENT_RETRANSMISSIONS.