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

"Recommended" Column #32

Closed
emanjon opened this issue Feb 25, 2024 · 1 comment · Fixed by #33
Closed

"Recommended" Column #32

emanjon opened this issue Feb 25, 2024 · 1 comment · Fixed by #33

Comments

@emanjon
Copy link

emanjon commented Feb 25, 2024 •
edited

Recommended, which is a Y/N value determined in the document defining the optional feature.

I assume this should follow the definition in Section 3 of draft-ietf-tls-rfc8447bis. Three suggestions:

  • I think it should be Y/N/D
  • A reference to RFC8447bis would maybe be good.
  • I think it would be better to just remove "determined in the document defining the optional feature." as a later document might redefine the value.
@seanturner
Copy link
Collaborator

I think this is just a case of this I-D pre-dating -rfc8447bis. It should be aligned when it gets revived/revised.

seanturner added a commit that referenced this issue Mar 12, 2024
@seanturner
Align with draft-ietf-tls-rfc8447bis
811ad08 
Closes #32.
@seanturner seanturner mentioned this issue Mar 12, 2024
Merged
yoavnir added a commit that referenced this issue Mar 13, 2024
@seanturner @yoavnir
Align with draft-ietf-tls-rfc8447bis (#33)
61d9a9f 
Closes #32.

Co-authored-by: Yoav Nir <ynir.ietf@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Align with draft-ietf-tls-rfc8447bis tlswg/tls-flags
2 participants
@seanturner @emanjon