Use seed as private key

[bwesterb]

• Add text that we use seed as private key
• Add examples for all three parameter sets.
• Deduplicate.

[seanturner]

I can decode the .pub examples, but none of the .priv examples. I am getting "Length over 48 bits not supported at position 1."

[bwesterb]

I can decode the .pub examples, but none of the .priv examples. I am getting "Length over 48 bits not supported at position 1."

Not sure what issue you hit, but I updated the examples because I noticed I didn't replace the private key by the seed yet 😬.

[seanturner]

I can decode these just fine. Will add the ASN.1 pretty prints via another PR.

Will look to do a Certificate we get the ML-DSA I-D closer to done.

[dconnolly]

I agree with using the 64-byte seed, but technically, a FIPS 203-compliant ML-KEM private key is / can be either a 64-byte seed or the fully expanded decapsulation key format; in this phrase, what is the meaning of 'is'? The ML-KEM in use in this document? Or the ML-KEM in FIPS 203? (Making this harmonious with the next paragraph would help)

[bwesterb]

Strictly speaking this sentence could be removed from the standard. It's here as a stepping stone to the precise definition. We could add a marker like "essentially" or "in short".

[dconnolly]

Cool, went with 'in short': #68