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

What a reset token actually looked like #4286

Closed
larseggert opened this issue Oct 28, 2020 · 1 comment
Closed

What a reset token actually looked like #4286

larseggert opened this issue Oct 28, 2020 · 1 comment
Labels
-transport 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.

Comments

@larseggert
Copy link
Member

Having read to the end of section 10 I made a note that I was still trying
to figure out what a reset token actually looked like.

@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
@martinthomson martinthomson added the editorial An issue that does not affect the design of the protocol; does not require consensus. label Nov 5, 2020
@martinthomson
Copy link
Member

Addressed in #4317.

Late Stage Processing automation moved this from Triage to Issue Handled Nov 5, 2020
@project-bot project-bot bot moved this from Issue Handled to Editorial Issues in Late Stage Processing Nov 5, 2020
@larseggert larseggert moved this from Editorial Issues to Issue Handled in Late Stage Processing Nov 9, 2020
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. ietf-lc An issue that was raised during IETF Last Call.
Projects
Late Stage Processing
  
Issue Handled
Development

No branches or pull requests

2 participants