[quicwg/base-drafts] Allow endpoints to generate traffic keys asynchronously (#3874)

[Kazuho Oku <[e-mail]>]

As pointed out in #3821, the drafts assume that the traffic keys are generated synchronously. But that's not what we see in the wild. In fact, clients often need to spend time while verifying the certificate, and some if not most of the clients do receive and send QUIC packets while they do so.

This PR acknowledges the existence of such implementation, recommending them to buffer the undecryptable packets while they calculate the next key, to prevent loss events that would kill the slow start. It also allows endpoints to postpone arming the PTO timer when it knows that the peer is going to send a handshake message.

Closes #3821.
You can view, comment on, or merge this pull request online at:

  https://github.com/quicwg/base-drafts/pull/3874

-- Commit Summary --

  * allow endpoints to generate traffic keys asynchronously, write down the expectations in relation

-- File Changes --

    M draft-ietf-quic-recovery.md (22)
    M draft-ietf-quic-tls.md (8)

-- Patch Links --

https://github.com/quicwg/base-drafts/pull/3874.patch
https://github.com/quicwg/base-drafts/pull/3874.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3874