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

Clarify state that is reset on Retry or VN #2058

Closed
janaiyengar opened this issue Nov 27, 2018 · 0 comments · Fixed by #3148
Closed

Clarify state that is reset on Retry or VN #2058

janaiyengar opened this issue Nov 27, 2018 · 0 comments · Fixed by #3148
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing

Comments

@janaiyengar
Copy link
Contributor

Follow-up to #2040. As @marten-seemann suggests, we might want to add text to the transport draft that enumerates what is reset: all state except for connection IDs, packet numbers and, optionally, an RTT measurement.
@janaiyengar janaiyengar added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels Nov 27, 2018
@mnot mnot added this to Editorial Issues in Late Stage Processing Feb 27, 2019
martinthomson added a commit that referenced this issue Oct 24, 2019
@martinthomson
Fix handling of Retry in recovery
af478ca 
This section was well out of date.  Also, this covers what needs to be
retained across this transition better.  Basically, the only thing that
needs to go is the congestion and loss recovery state.  The rest can
stay; in fact, the crypto handshake has to stay.

Closes #2058.
@martinthomson martinthomson mentioned this issue Oct 24, 2019
Merged
Late Stage Processing automation moved this from Editorial Issues to Text Incorporated Oct 29, 2019
ianswett added a commit that referenced this issue Oct 29, 2019
@martinthomson @ianswett
Fix handling of Retry in recovery (#3148)
61aeda9 
* Fix handling of Retry in recovery

This section was well out of date.  Also, this covers what needs to be
retained across this transition better.  Basically, the only thing that
needs to go is the congestion and loss recovery state.  The rest can
stay; in fact, the crypto handshake has to stay.

Closes #2058.

* cannot/MUST NOT

potato/tomato

Co-Authored-By: ianswett <ianswett@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing
  
Issue Handled
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix handling of Retry in recovery quicwg/base-drafts
1 participant
@janaiyengar