Re: [quicwg/base-drafts] RESET_STREAM should be allowed in 0-RTT packets (#2344)

[Martin Thomson <[e-mail]>]

@kazuho,

> The problem with 0-RTT in QUIC is that, unlike TLS 1.3 (that has max_early_data_size), there is no limit in the amount of data that the client can send using the 0-RTT key. IIUC, currently, it's entirely up to the client to decide when it switches from 0-RTT to 1-RTT keys.

QUIC uses `initial_max_data` for that purpose.  You can't receive a flow control update, so whatever value you have for that determines how much 0-RTT you can send.

In thinking through this, I realized that the client can't send 0-RTT after receiving 1-RTT from the server.  A client won't have the keys until it has the entire handshake flight from the server, at which point it has to switch to 1-RTT keys.  So this all comes down to the same calculus we have in TLS/TCP, after you have spent a little bit of time on the question of RESET_STREAM and its effect on long-term application state.

-- 
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/issues/2344#issuecomment-456240116