-
Notifications
You must be signed in to change notification settings - Fork 158
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
Add max_early_data_size to TicketEarlyDataInfo #674
Conversation
@FiloSottile this needs a rebase. correction: Github just was freaking out |
@ekr done, the damned GitHub editor doesn't detect conflicts. This is a bit ridiculous. |
@FiloSottile Don't forget to email the list. |
} TicketEarlyDataInfo; | ||
~~~~ | ||
|
||
This extension indicates that the ticket may be used to send 0-RTT data | ||
({{early-data-indication}})). It contains one value: | ||
({{early-data-indication}})). It contains two values: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(editorial nit: do we really need to have the number here? Could it just be "Its contents are:"?)
|
||
max_early_data_size | ||
: The maximum amount of 0-RTT data that the client is allowed to send when using | ||
this ticket, in bytes. Only Application Data payload is counted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A serer receiving more than this many bytes of 0-RTT data will abort the connection with a XYZ alert.
Merged by hand |
Email to list coming.