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

Better if explanation of operation proceeded the detail #4302

Closed
larseggert opened this issue Oct 28, 2020 · 0 comments · Fixed by #4319
Closed

Better if explanation of operation proceeded the detail #4302

larseggert opened this issue Oct 28, 2020 · 0 comments · Fixed by #4319
Labels
-transport ietf-lc An issue that was raised during IETF Last Call.
Projects
Late Stage Processing
Milestone
transport-genart

Comments

@larseggert
Copy link
Member

With this mechanism, the server reflects the spin value received,
while the client 'spins' it after one RTT. On-path observers can
measure the time between two spin bit toggle events to estimate the
end-to-end RTT of a connection.

It would be clearer to the reader if the explanation of operation proceeded
the detail.
@larseggert larseggert added -transport ietf-lc An issue that was raised during IETF Last Call. labels Oct 28, 2020
@larseggert larseggert added this to the transport-genart milestone Oct 28, 2020
@larseggert larseggert added this to Triage in Late Stage Processing via automation Oct 28, 2020
@MikeBishop MikeBishop mentioned this issue Oct 30, 2020
Merged
Late Stage Processing automation moved this from Triage to Issue Handled Nov 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport ietf-lc An issue that was raised during IETF Last Call.
Projects
Late Stage Processing
  
Issue Handled
Milestone
transport-genart
Development

Successfully merging a pull request may close this issue.

Move spin bit explanation to beginning of section quicwg/base-drafts
1 participant
@larseggert