[openpgp] context parameter in draft-ietf-openpgp-nist-bp-comp

Heiko Schäfer <[email protected]>
Newsgroups gmane.ietf.openpgp
Message-ID <[email protected]>
Hello Falko, list,

On 10/14/25 12:48 PM, Falko Strenzke wrote:
>
> There is actually one other point worthy of discussion the authors 
> would like to raise. The discussion about the use of the context 
> parameter for ML-DSA and SLH-DSA in draft-ietf-openpgp-pqc concluded 
> that the draft should continue using the empty string as the context 
> parameter. The question that we would like to raise is whether the 
> draft-ietf-openpgp-nist-bp-comp should take the same choice, or, 
> switch to using a non-empty context parameter for ML-DSA.
>
> If there should no opinion of the WG become apparent, the authors tend 
> to continue using the empty context parameter.
>

In the context of draft-ietf-openpgp-pqc, I argued against specifying 
use of the context parameter at the 11th hour, most of all to avoid 
delay in the finalization of that draft.
That argument seems less pressing for draft-ietf-openpgp-nist-bp-comp 
(which, I believe, does not currently have test vectors or a comparable 
range of implementations).

So if the authors favored adding a context parameter in 
draft-ietf-openpgp-nist-bp-comp, I would not be opposed.

However, I share the authors' preference for continued use of the empty 
context parameter.
Keeping things symmetrical between both PQC drafts and RFC 9580 is nice.

Thanks,
Heiko

_______________________________________________
openpgp mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.