Re: [lamps] New Version Notification for draft-turner-lamps-nist-pqc-kem-certificates-01.txt

[Sean Turner <[e-mail]>]

> On Mar 17, 2022, at 09:02, Daniel Kahn Gillmor <[e-mail]> wrote:
> 
> On Tue 2022-03-15 18:09:27 +0000, Salz, Rich wrote:
>> Strongly agree.  It's not just wire format but configuration
> 
> Count me as another advocate for explicitly declaring the private key
> format.  Even doing interoperability testing is difficult if there's no
> standard, commonly-adopted way to load a private key into the software.
> 
> If the goal of the IETF is to produce interoperable standards, we can't
> ignore private key formats.
> 
> On a different topic, I appreciate that this draft is looking like it
> will have sample keys in it.  I recommend that the authors place each
> sample key in a separate subsection for easier reference.
> 
> I also hope that when the actual samples end up in this document, there
> will be a sample private key that corresponds to each sample public
> key.  I assume that will be the case, but the text as currently written
> doesn't imply that the samples are related to one another, so i just
> wanted to explicitly encourage that.
> 
>       --dkg

Interesting, I had forgot those To Dos were there. I will make sure that the examples (however many we have) end up having a public-private key pair that correspond.

spt