Reorganise key format and key derivation information #184
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.
[Updated: rebased after publication of Crypto API 1.2.1. Updated the rendered PDF]
This is a follow-up to #177, which moves the information about key formats, and key derivation, into each key type definition.
This is more user-centric than providing all the key formats in a single place, and all the key derivation methods in another single place. It will also scale better when we add additional formats, or key construction methods (see #149 and #167).
The new commits (since #177) start at 0733f81
Preview of the PDF: IHI0086-PSA_Certified_Crypto_API-1.3.0-key-formats-draft.2.pdf