-
Notifications
You must be signed in to change notification settings - Fork 205
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
Express MAX_DATA in octets rather than KB #874
Conversation
draft-ietf-quic-transport.md
Outdated
sent on the entire connection, in units of 1024 octets. That is, the updated | ||
connection-level data limit is determined by multiplying the encoded value by | ||
1024. | ||
sent on the entire connection, in units octets. |
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.
of ?
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.
imagine how many mistakes I can make in a diff more than 1 line long.
wohoo |
What about initial_max_data in the extension? |
are you suggesting it needs to be more than 32 as an initial value? That
sort of stretches the credulity of flow control...
…On Sun, Oct 22, 2017 at 2:54 PM, Subodh Iyengar ***@***.***> wrote:
What about initial_max_data in the extension?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#874 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAP5s02pqdP8p3YVkJ5zqfTRBlsy8mNbks5su49ogaJpZM4P4_zj>
.
|
no i'm suggesting it doesn't need to have a 1024 multiplier. |
+1! Let's just use octets. |
closes #873