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

Ben Kaduk's Transport Comment 28 #4640

Closed
LPardue opened this issue Jan 7, 2021 · 1 comment
Closed

Ben Kaduk's Transport Comment 28 #4640

LPardue opened this issue Jan 7, 2021 · 1 comment
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus. iesg An issue raised during IESG review.

Comments

@LPardue
Copy link
Member

LPardue commented Jan 7, 2021

@kaduk said:

Section 13.2.5

When the measured acknowledgement delay is larger than its
max_ack_delay, an endpoint SHOULD report the measured delay. This
information is especially useful during the handshake when delays
might be large; see Section 13.2.1.

I'm not sure I understand when this delay would not be reported even in
the absence of this guidance. Is the idea that you should specifically
send an ACK with Largest Acknowledged corresponding to the highly
delayed packet, even if you could send an ACK with a larger Largest
Acknowledged (but lower delay)?

@LPardue LPardue added -transport iesg An issue raised during IESG review. labels Jan 7, 2021
@LPardue LPardue added this to the transport-iesg milestone Jan 7, 2021
@martinthomson
Copy link
Member

This is to address the implication that max_ack_delay is a limit on the value of the field, as opposed to what it is (which is several things that are quite subtle and addressed well in -recovery, so I won't repeat them).

No action proposed here.

@larseggert larseggert added this to Triage in Late Stage Processing via automation Jan 11, 2021
@larseggert larseggert added the editorial An issue that does not affect the design of the protocol; does not require consensus. label Jan 12, 2021
@project-bot project-bot bot moved this from Triage to Editorial Issues in Late Stage Processing Jan 12, 2021
Late Stage Processing automation moved this from Editorial Issues to Issue Handled Jan 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus. iesg An issue raised during IESG review.
Projects
Late Stage Processing
  
Issue Handled
Development

No branches or pull requests

3 participants