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

added a sentence to offset table #93

Merged
merged 4 commits into from
Dec 11, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions draft-ietf-lamps-pq-composite-sigs.md
Original file line number Diff line number Diff line change
Expand Up @@ -849,11 +849,16 @@ Deserialization Process:

## ML-DSA public key, private key and signature sizes for serialization and deserialization

As noted above in the public key, private key and CompositeSignatureValue
As noted above in the composite public key, composite private key and composite signature value
serialization and deserialization methods, ML-DSA uses fixed-length values for
all of these components. This means the length encoding of the first component is
known and does NOT need to be encoded into the serialization and deserialization process
which simplifies the encoding. If future composite combinations make use of
which simplifies the encoding. The second traditional component may be variable-length but
can still be parsed correctly by taking the rest of the value after the specified offset
as the traditional component.

This encoding is optimized for the fact that all values related to ML-DSA are fixed-length.
If future composite combinations make use of
algorithms where the first component uses variable length keys or signatures, then
that specification will need to ensure the length is encoded in a
fixed-length prefix so the components can be correctly deserialized.
Expand All @@ -866,8 +871,7 @@ sizes for ML-DSA which can be used to deserialzie the components.
| ML-DSA-44 | 1312 | 32 | 2420 |
| ML-DSA-65 | 1952 | 32 | 3309 |
| ML-DSA-87 | 2592 | 32 | 4627 |
{: #tab-mldsa-sizes title="ML-DSA Key and Signature Sizes"}

{: #tab-mldsa-sizes title="ML-DSA Key and Signature Sizes in bytes"}

# Composite Key Structures {#sec-composite-structs}

Expand Down
Loading