Fix assertion failure because of bad CRYPTO offset provisioning
This commit fixes the assertion failure which happens when acknowledgement of earlier packet increases CRYPTO offset. Previously, the offset is always the first CRYPTO frame offset in the queue (pktns->crypto.tx.frq). But passing this into ngtcp2_pkt_crypto_max_datalen() underestimates the space because acknowledgement might increase offset; it increases the required space to serialize offset.
Please register or sign in to comment