-
Notifications
You must be signed in to change notification settings - Fork 5.8k
JDK-8261510: Use RFC numbers and protocol titles in sun.security.ssl.SSLExtension comments #2517
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
Conversation
👋 Welcome back jjiang! A progress list of the required criteria for merging this PR into |
@johnshajiang The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
// TLS 1.3 PSK extension must be last | ||
// RFC 8446 PSK extension must be last |
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.
What do you think if using "TLS 1.3 (RFC 8446)"?
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 agree with previous suggestion, but could you do throughout the file? Having something like either:
// extension defined in RFC 7301 (ALPN)
// extension defined in ALPN (RFC 7301)
throughout this file is encouraged and appreciated. Having the RFC #/short name of the document would be a lot more readable, rather than having to look up the RFC for a synopsis. e.g.
// extensions defined in RFC 8472
should be
// extensions defined in Token Binding Protocol Negotiation (RFC 8472)
or
// extensions defined in RFC 8472 (Token Binding Protocol Negotiation)
I noticed the previous comment for TLS1.3 wasn't fully addressed (line 314).
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.
Looks good, thanks.
@johnshajiang This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 16 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
/integrate |
@johnshajiang Since your change was applied there have been 17 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit f4cfd75. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This is a simple cleanup for sun.security.ssl.SSLExtension.
The comments for the extension groups would use the RFC numbers and the protocol titles correspondingly.
It also removes a trailing space in extension token_binding, and move signature_algorithms and signature_algorithms_cert to RFC 8446 extension group.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2517/head:pull/2517
$ git checkout pull/2517