Rework the encoding of asymmetric key types #196
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
athoelke
added
enhancement
athoelke
force-pushed
the
crypto-asymmetric-key-encoding
branch
from
24f5ff1 to
5300ed5
Compare
This is an artefact of the original documentation generation tooling.
This provides more flexibility to allocate additional asymmetric key types for PAKE and PQC algorithms. Allocate the top bit of the FAMILY field to the ASYM-TYPE field. This makes FAMILY 6 bits and ASYM-TYPE 5. The top bit of FAMILY was previously for IMPDEF families, but support for IMPDEF key types is already provided via bit 15 in the type. So it was not used in any specification defined family values. Defined ASYM-TYPE 0 to be a category of non-parameterized asymmetric keys, including RSA. * Updated the ECC family and DH family definitions. Also added clarification about the inclusion of the parity bit. * Updated all relevant sections of the encoding appendix, including the bit field graphics and ASYM-TYPE values in the tables. * Updated the example macros in the appendix to mask FAMILY and ASYM-TYPE fields correctly.
athoelke
force-pushed
the
crypto-asymmetric-key-encoding
branch
from
5300ed5 to
bfe9485
Compare
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.
This provides more flexibility to allocate additional asymmetric key types for PAKE and PQC algorithms.
Allocate the top bit of the FAMILY field to the ASYM-TYPE field. This makes FAMILY 6 bits and ASYM-TYPE 5.
The top bit of FAMILY was previously for IMPDEF families, but support for IMPDEF key types is already provided via bit 15 in the type. So it was not used in any specification defined family values.
Defined ASYM-TYPE 0 to be a category of non-parameterized asymmetric keys, including RSA.
Fixes #109