Remove root ca terminology #66
Closed
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
draft-ietf-lamps-rfc4210bis.md
Outdated
| DN, e.g., indicating a generation identifier like the year of issuance or | ||
| a version number, for instance in an OU element. How to bridge trust to | ||
| the new root CA certificate in a CA DN change or a cross-certificate scenario | ||
| a new CA certificate in a CA DN change or a cross-certificate scenario |
There was a problem hiding this comment.
Could also say "How to bridge trust to a newly trusted CA Certificate in a CA DN change..."
draft-ietf-lamps-rfc4210bis.md
Outdated
| Profile of how a Certificate structure may be "self-signed". These | ||
| structures are used for distribution of CA public keys. This can | ||
| Profile of how a certificate structure may be "self-signed". These | ||
| structures are used for distribution of new trusted CA public keys as self-signed certificate. This can |
There was a problem hiding this comment.
I think I would say "newly trusted"
| @@ -4784,13 +4810,12 @@ PreferredSymmAlg present (object identifier one | |||
| value | |||
| -- the symmetric algorithm that this CA expects to be used | |||
| -- in later PKI messages (for encryption) | |||
| RootCaKeyUpdate optionally present, with | |||
| relevant value | |||
| RootCaKeyUpdate optionally present, with relevant value | |||
There was a problem hiding this comment.
Should this name change from RootCAKeyUpdate to TrustedCaKeyUpdate?
There was a problem hiding this comment.
It would be great to also update the types. But this would be a breaking change for RFC 9483 because we introduced the new types already with RFC 9480 and we also registered some OIDs using the old language. Therefore, I think we should keep the syntax and address this with the note.
|
Option 1 was rejected in favor of option 2, #67 was merged |
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.
Implements #65