Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Packet reordering thresholds less than 3 are not sufficiently reordering tolerant #3256

Closed
ianswett opened this issue Nov 18, 2019 · 1 comment · Fixed by #3240
Closed

Packet reordering thresholds less than 3 are not sufficiently reordering tolerant #3256

ianswett opened this issue Nov 18, 2019 · 1 comment · Fixed by #3240
Labels
-recovery design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.
Projects
Late Stage Processing

Comments

@ianswett
Copy link
Contributor

Gorry suggested that the QUIC recovery draft should specifically recommend against packet reordering thresholds less than 3 because it will not be sufficiently tolerant of real-world reordering.

Pull #3240 already created.
@ianswett
Copy link
Contributor Author

FWIW, I think this is likely design because it adds a SHOULD NOT, but it also doesn't substantively change the existing recommendation.

@mnot mnot added the design An issue that affects the design of the protocol; resolution requires consensus. label Nov 25, 2019
@mnot mnot added this to Design Issues in Late Stage Processing Nov 25, 2019
@ianswett ianswett mentioned this issue Nov 28, 2019
Merged
@martinthomson martinthomson added the proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. label Nov 28, 2019
@mnot mnot moved this from Design Issues to Consensus Emerging in Late Stage Processing Nov 29, 2019
@mnot mnot moved this from Consensus Emerging to Consensus Call issued in Late Stage Processing Nov 29, 2019
@mnot mnot added has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. and removed proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. labels Dec 9, 2019
@mnot mnot moved this from Consensus Call issued to Consensus Declared in Late Stage Processing Dec 9, 2019
Late Stage Processing automation moved this from Consensus Declared to Text Incorporated Dec 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-recovery design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.
Projects
Late Stage Processing
  
Issue Handled
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

SHOULD NOT use a reordering threshold less than 3 quicwg/base-drafts
3 participants
@martinthomson @mnot @ianswett