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.

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

Remove a MUST accidentally introduced by #3315 #3537

Closed
wants to merge 1 commit into from

Conversation

ianswett
Copy link
Contributor

@ianswett ianswett commented Mar 21, 2020

I'm not sure I agree with it in all cases, and it's a new MUST, which makes #3315(Rewrite section on ack range limiting) inadvertently not editorial.

#3541 opened to discuss this issue.

I'm not sure I agree with it in all cases, and it's a new MUST, which makes #3315 inadvertently not editorial.
@martinthomson
Copy link
Member

We need to keep this, but we should ask for a consensus call. I'll open an issue.

@janaiyengar
Copy link
Contributor

@martinthomson to produce some text here that separates retention policy (MUST) from signaling policy (SHOULD).

@martinthomson martinthomson linked an issue Apr 15, 2020 that may be closed by this pull request
martinthomson added a commit that referenced this pull request Apr 15, 2020
This explains what needs to be kept and why.  Specifically, you need to
keep ranges unless you have other means of ensuring that you don't
accept packets from those ranges again.  You also need to keep the
largest acknowledged so that you can get a packet number from subsequent
packets.

This also recommends that ACK frames include the largest acknowledged
always.  That is primarily to ensure that ECN works properly, and even
there, you only disable ECN if you get some weird reordering, so it's
probably not a big deal if you don't follow this recommendation.

Closes #3541.
Closes #3537.
@martinthomson martinthomson deleted the ianswett-remove-must branch August 4, 2020 23:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Retaining the largest received packet number
4 participants