> On May 22, 2025, at 11:49 AM, Watson Ladd <watsonbladd@xxxxxxxxx> wrote: > > On Thu, May 22, 2025 at 11:36 AM Russ Housley <housley@xxxxxxxxxxxx> wrote: >> >> Watson: >> >> In the ASN.1 definition of the PUBLIC KEY structures on page 6 I am a bit >> confused by why the key can be throw in without additional wrapping. This is >> probably due to my ignorance of ASN.1, but I'm sure I'm not the only one. >> >> >> We explored the raw public key and the public key wrapped in an OCTET STRING. Work at the Hackathon resulted in a clear preferance by implementers to just carry the raw public key in the SubjectPublicKeyInfo and other places. This is how you say that using the PUBLIC-KEY class defined in RFC 5912. > > Thanks for the explanation. I think to address my concern we don't > need much text, but we should move "The PUBLIC-KEY ASN.1 types for > ML-DSA are defined here and the definitions" past the paragraph that > explains "subjectPublicKey BIT STRING contains this raw byte string > encoding of the public key." That way we don't switch topics > unnecessarily. It might be worth adding a note explicitly flagging > that there was this redefinition to those of us, myself included, who > somehow missed we'd redefined this in the past 15 years. There's a lot > of code that hasn't changed and follows the 5280 definitions into > internal data structures. It is not a re-definition. It uses the tools that are in the 2002 version of ASN.1 to say things that could not be expressed in the 1988 version of ASN.1. That is all explained in the Introduction to RFC 5912. Russ -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
