Subject: Re: [quicwg/base-drafts] 0-RTT can't use transport parameters or 1-RTT frames (#2461)
From: Kazuho Oku <[email-masked]>
To: quicwg/base-drafts <[email-masked]>
Cc: Subscribed <[email-masked]>
Date: Wed, 13 Feb 2019 13:59:22 -0800
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>

@ianswett 
> I think this is ok, but I think it's going to be difficult to get this correct in practice. I expect most implementations will migrate to 1-RTT keys as soon as possible and try to avoid writing special logic for this case, but I can't come up with a way to force clients to do that.

I think it's possible. I think that's what the PR is trying to suggest is that a server can:
* enforce limits based on TP to streams-related frames sent using 0-RTT packets (see #2461)
* refuse to handle any of the following frames in a 0-RTT packet: ACK, PATH_RESPONSE, RETIRE_CONNECTION_ID (see #2458)

-- 
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/2461#issuecomment-463392078