AEAD seq shouldn't be a uint64 about go-hpke HOT 3 CLOSED

We also opted to use uint64 in BoringSSL. It does feel a little wrong to diverge from the spec, but it's unlikely to matter in real life.

Let's say we have a 10 GHz CPU and each HPKE operation takes 1 clock cycle. That's 1e10 HPKE operations per second. (2**64 / 1e10) seconds ≈ 58 years before we hit the max uint64 value.

Maybe that's not an astronomically long time, but it's longer than we expect one HPKE context to live. I'm curious what others think.

from go-hpke.

I agree with @dmcardle here. As long as the nonce formation complies with the draft, it's OK if we don't support the whole space of nonces. And since we have checking for wrapping, we fail safe if we do exhaust the space we support.

from go-hpke.

Agreed. Closing.

from go-hpke.