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

Update the IANA considerations text to match our other TLS policies. #627

Merged
merged 1 commit into from
Sep 15, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion draft-ietf-tls-esni.md
Original file line number Diff line number Diff line change
Expand Up @@ -1896,7 +1896,18 @@ Notes:
{: spacing="compact"}

New entries in the "ECHConfig Extension" registry are subject to the
Specification Required registration policy ({{!RFC8126, Section 4.6}}).
Specification Required registration policy ({{!RFC8126, Section
4.6}}), with the policies described in {{!RFC8447, Section 17}}. IANA
[shall add/has added] the following note to the TLS ECHConfig Extension
registry:

Note: The role of the designated expert is described in RFC 8447.
The designated expert [RFC8126] ensures that the specification is
publicly available. It is sufficient to have an Internet-Draft
(that is posted and never published as an RFC) or a document from
another standards body, industry consortium, university site, etc.
The expert may provide more in depth reviews, but their approval
should not be taken as an endorsement of the extension.

This document defines several Reserved values for ECH configuration extensions.
These can be used by servers to "grease" the contents of the
Expand Down
Loading