PFS and integrity-only ciphersuites #54
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix #43 Signed-off-by: Thomas Fossati <[email protected]>
draft-ietf-uta-tls13-iot-profile.md
Outdated
|
|
||
| TLS 1.3 allows the use of PFS with all ciphersuites since the support for it is | ||
| negotiated independently. | ||
| RFC8446 has removed Static RSA and Diffie-Hellman cipher suites, therefore all public-key-based key exchange mechanisms available in TLS 1.3 provide forward secrecy. |
There was a problem hiding this comment.
Suggested change
| RFC8446 has removed Static RSA and Diffie-Hellman cipher suites, therefore all public-key-based key exchange mechanisms available in TLS 1.3 provide forward secrecy. | |
| RFC 8446 removed cipher suites that did not provide forward secrecy. |
There was a problem hiding this comment.
I framed the section as:
- Public-key-based ciphersuite, vs
- PSK-based ciphersuite
and their FS properties.
I believe the suggestion drops some of the semantics.
|
|
||
| # Authentication and Integrity-only Cipher Suites | ||
|
|
||
| For a few, very specific Industrial IoT use cases {{?RFC9150}} defines two cipher suites that provide data authenticity, but not data confidentiality. |
There was a problem hiding this comment.
Suggested change
| For a few, very specific Industrial IoT use cases {{?RFC9150}} defines two cipher suites that provide data authenticity, but not data confidentiality. | |
| To address use cases from Industrial IoT, such as railway control and power system automation, {{?RFC9150}} defines two cipher suites that provide data authenticity, but not data confidentiality. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #43