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

Make the deprecation of status_request_v2 extension more explicit #1075

Merged
merged 1 commit into from Oct 27, 2017

Conversation

tomato42
Copy link
Contributor

No description provided.

@@ -3304,6 +3304,13 @@ The body of the "status_request" extension
from the server MUST be a CertificateStatus structure as defined
in {{RFC6066}}, which is interpreted as defined in {{!RFC6960}}.

Note: status_request_v2 extension ({{!RFC6961}}) is deprecated. TLS 1.3 servers
MUST NOT act upon its presence or information in it when processing Client
Hello, in particular they MUST NOT send status_request_v2 extension in the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a "the" is needed as "the status_request_v2 extension".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that should be fixed now

@ekr ekr merged commit 5dbee41 into tlswg:master Oct 27, 2017
@tomato42 tomato42 deleted the ocsp-status-request-v2 branch November 3, 2017 11:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants