You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The client sends an Initial packet. The unprotected payload of this
packet contains the following CRYPTO frame, plus enough PADDING
frames to make a 1162 byte payload:
[...]
The unprotected header includes the connection ID and a 4-byte packet
number encoding for a packet number of 2:
c300000001088394c8f03e5157080000449e00000002
If I'm reading this correctly, the variable-length integer encoding of
the packet Length is 0x449e which would indicate a 1182-byte payload
(including packet number), not 1162.
The text was updated successfully, but these errors were encountered:
I should have put money on @kaduk validating the examples...
The use of "payload" refers to the frames contained in the packet, which are 1182 - 4 (packet number length) - 16 (aead expansion). Would "The frames carried by this packet includes the following CRYPTO frame, plus enough PADDING frames to reach 1162 bytes." be better?
Ah, of course, the authentication tag. (I only remembered that the packet number length was included as an afterthought, but 4 != 20 and I didn't pause to think what might be adding 16 other bytes.)
Thanks for the PR, @MikeBishop !
I am not sure who would take the other end of that bet, though ... I seem to have a track record of putting DISCUSSes on for examples that don't match the protocol spec.
@kaduk said:
The text was updated successfully, but these errors were encountered: