-
Notifications
You must be signed in to change notification settings - Fork 5
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
proposed text from errata 6648 #151
base: master
Are you sure you want to change the base?
Conversation
dtbootstrap-anima-keyinfra.xml
Outdated
When TLS 1.3 is used the use of Server Name Indicator (SNI, | ||
<xref target="RFC6066" />) is not required, per <xref | ||
target="RFC8446" /> section 9.2, this | ||
specification is an application profile specification. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When TLS 1.3 is used the use of Server Name Indicator (SNI, | |
<xref target="RFC6066" />) is not required, per <xref | |
target="RFC8446" /> section 9.2, this | |
specification is an application profile specification. | |
While the use of a Server Name Indication (SNI) is not required per this (<xref target="RFC8446" />, Section 9.2) application profile specification, pledges MAY include one. | |
Registrars MUST ignore any SNI that they see. |
(This aligns with BRSKI-CLOUD needs)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggesting to change to "Server Name Indication (SNI)" (i.e. use the official term) and to use lowercase on "application profile specification" and for "pledges". (Conforms to RFC 8995 caps use)
We can also commit this suggestion soon to allow further wordsmithing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
( I can't commit my own suggestion, it seems)
Co-authored-by: Esko Dijk <[email protected]>
Co-authored-by: Esko Dijk <[email protected]>
Co-authored-by: Esko Dijk <[email protected]>
Co-authored-by: Esko Dijk <[email protected]>
Co-authored-by: Esko Dijk <[email protected]>
No description provided.