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

Recovery section 4.2 possible references #4418

Closed
LPardue opened this issue Dec 2, 2020 · 1 comment · Fixed by #4425
Closed

Recovery section 4.2 possible references #4418

LPardue opened this issue Dec 2, 2020 · 1 comment · Fixed by #4425
Assignees
@janaiyengar
Labels
-recovery editorial An issue that does not affect the design of the protocol; does not require consensus. ietf-lc An issue that was raised during IETF Last Call.
Projects
Late Stage Processing
Milestone
recovery-genart

Comments

@LPardue
Copy link
Member

LPardue commented Dec 2, 2020

In the Recovery genart review, Vijay Gurbani wrote:

S4.2, first paragraph: Perhaps citing rfc6298 is helpful here to further
provide information on the "retransmission ambiguity" problem?
@LPardue LPardue added -recovery ietf-lc An issue that was raised during IETF Last Call. labels Dec 2, 2020
@LPardue LPardue added this to the recovery-genart milestone Dec 2, 2020
@larseggert larseggert added this to Triage in Late Stage Processing via automation Dec 4, 2020
@janaiyengar janaiyengar mentioned this issue Dec 8, 2020
Merged
@janaiyengar janaiyengar self-assigned this Dec 8, 2020
@martinthomson martinthomson changed the title Recovery section 4.2 possbile references Recovery section 4.2 possble references Dec 8, 2020
@martinthomson martinthomson changed the title Recovery section 4.2 possble references Recovery section 4.2 possible references Dec 8, 2020
@LPardue
Copy link
Member Author

LPardue commented Dec 8, 2020

Based on the proposed PR, I'm marking this as editorial.

@LPardue LPardue added the editorial An issue that does not affect the design of the protocol; does not require consensus. label Dec 8, 2020
@LPardue LPardue moved this from Triage to Editorial Issues in Late Stage Processing Dec 8, 2020
@LPardue LPardue added the proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. label Dec 8, 2020
@project-bot project-bot bot moved this from Editorial Issues to Consensus Emerging in Late Stage Processing Dec 8, 2020
Late Stage Processing automation moved this from Consensus Emerging to Issue Handled Dec 8, 2020
@LPardue LPardue removed the proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. label Dec 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@janaiyengar janaiyengar

Labels
-recovery editorial An issue that does not affect the design of the protocol; does not require consensus. ietf-lc An issue that was raised during IETF Last Call.
Projects
Late Stage Processing
  
Issue Handled
Milestone
recovery-genart
Development

Successfully merging a pull request may close this issue.

Fix recovery references and some text quicwg/base-drafts
2 participants
@LPardue @janaiyengar