MUST pace or limit bursts to 10 packets #3106
Conversation
Fixes part or all of #3094
Remove the old paragraph
| Implementations MUST either use pacing or limit such bursts to minimum | ||
| of 10 * kMaxDatagramSize and max(2* kMaxDatagramSize, 14720)), the same | ||
| as the recommended initial congestion window. | ||
|
|
There was a problem hiding this comment.
Sorry again late here... To we recommend a fixed value of 10 packets or do we recommend to have the burst limit the same as the initial window? E.g. if we decide in future to increase our recommendation for the initial window, should that also increase the recommendation for the burst limit? I guess to be really smart about this, you would need to say that you set the burst but initial window but decrease if you see tail loss in the initial burst (but that might be an overkill).
There was a problem hiding this comment.
Or you could say that there are different initial window and burst limits, which is probably OK. I don't think that we need to be that smart though.
There was a problem hiding this comment.
That's a good point. We could swap the sentence and say "same as the initial congestion window, which is recommended to be ..." if you think it's preferable. But I'm also not sure it matters much.
There was a problem hiding this comment.
I think that explicitly saying "Initial congestion window" here as the primary target of the MUST requirement would be better.
There was a problem hiding this comment.
PR created, PTAL: #3160
From discussion on #3106 #3106 (comment)
* MUST limit bursts to the initial congestion window From discussion on #3106 #3106 (comment) * Update draft-ietf-quic-recovery.md * Update draft-ietf-quic-recovery.md Co-Authored-By: Martin Thomson <mt@lowentropy.net>
Came from the discussion of #3094