New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How long is Initial #2167
Comments
Clients MUST pad UDP datagrams that contain only Initial packets to It is a bit vague if this includes AEAD tag or not. I assume it includes tag since this is the definition of QUIC packet size. |
Well the text doesn't say "at least". It says "to". so are we talking about negative padding? |
It was my suggestion to clarify the text. Not negative padding, merely 0 padding if necessary. I think that is quite normal. |
What it is is that the ClientHello needs to fit into a 1200 byte packet. That's a requirement on the cryptographic handshake. It is also the case that a packet of less than 1200 bytes needs to be padded. So we add "at least" and we're done, I think. |
I'm still confused, because here you're saying it has to fit in 1200 bytes, but the text above says it has to fit into a packet which implies that you could go to (say) 1600 bytes and have IP fragmentation. So which is it? |
packet = QUIC packet unless specifically qualified. This doesn't say anything about IP fragmentation. |
I agree. So my point is that this text says it's legal to have your Initial packet by 2048 bytes long, because that fits in a QUIC packet. But your message above says that that's not OK. |
An Initial packet can be 2048 bytes long. The 1200 byte cap is on the cryptographic handshake protocol and the FIRST Initial packet. (Yikes, this is starting to confuse me.) |
Hmm... I looked and tried to find that restriction on either of these and couldn't find it. Maybe I'm just missing it though? |
You will observe that the first text you quote says "first" and the second does not. Is that too subtle? |
Maybe I just need to read this more closely, but here's how I read this text.
However, I don't see where in the text we say that the first initial may not be arbitrary sized (within the limits of IP packets). Do you agree with this, or am I missing something. |
Yes, we don't explicitly say that the first Initial has to be a single packet (or even a single IP packet, which is probably best). |
I don't think that is the case. I believe the first UDP packet payload including coalesced packets must be at least 1200. It is one of the arguments for having coalesced packets, but not the primary one. But this is from memory of discussions, not concrete text. |
the TLS draft says:
This clearly implies that you can have an Initial > 1200 bytes.
However, transport S 7.1 says
But you can't pad to 1200 bytes if you are over 1200 bytes. so which one is it?
The text was updated successfully, but these errors were encountered: