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

RTO in handshake in recovery draft #3467

Closed
mirjak opened this issue Feb 17, 2020 · 3 comments
Closed

RTO in handshake in recovery draft #3467

mirjak opened this issue Feb 17, 2020 · 3 comments
Labels
-recovery needs-discussion An issue that needs more discussion before we can resolve it.
Projects
Late Stage Processing

Comments

@mirjak
Copy link
Contributor

mirjak commented Feb 17, 2020

The draft says:
"To allow the client to
improve its RTT estimate, the new packet that it sends MUST be ack-
eliciting. If Handshake keys are available to the client, it MUST
send a Handshake packet, and otherwise it MUST send an Initial packet
in a UDP datagram of at least 1200 bytes."
Is the second sentence actually needed (in this draft). What are the other options?
@LPardue LPardue added this to Triage in Late Stage Processing Feb 17, 2020
@larseggert larseggert added the needs-discussion An issue that needs more discussion before we can resolve it. label Feb 24, 2020
@ianswett
Copy link
Contributor

ianswett commented Mar 7, 2020

We could drop "send an Initial packet in a UDP datagram of at least 1200 bytes." because all client Initial packets are padded to make it less duplicative with transport. Besides that, I'm not aware of any other options.

@larseggert
Copy link
Member

@mirjak this looks like it can be closed with no action?

@mirjak
Copy link
Contributor Author

mirjak commented Mar 11, 2020

I think the use of normative language is somehow redundant. But that not really an issue. Closing...

@mirjak mirjak closed this as completed Mar 11, 2020
Late Stage Processing automation moved this from Triage to Text Incorporated Mar 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-recovery needs-discussion An issue that needs more discussion before we can resolve it.
Projects
Late Stage Processing
  
Issue Handled
Milestone
No milestone
Development

No branches or pull requests
4 participants
@larseggert @LPardue @mirjak @ianswett