[jose] Re: Call for adoption: https://datatracker.ietf.org/doc/draft-reddy-cose-jose-pqc-kem/

[tirumal reddy <[e-mail]>]

On Tue, 17 Sept 2024 at 15:07, Neil Madden <[e-mail]> wrote:

> I’ll try and give this a proper read through today, but a couple of
> initial questions:
>
> - the general consensus in CFRG seems to be towards hybrid KEMs (eg some
> combo of X25519/P-256 + ML-KEM), so is there a need for a “naked” ML-KEM
> option?
>

A PQ KEM may be preferred due to regulatory requirements. For example,
ML-KEM supports users who need to comply with CNSA 2.0. If a PQ KEM meets
the needs of your applications, it offers certain advantages such as a
clean key agreement process and avoids the complexity associated with
hybrid key shares and mixing logic.


>
> - more broadly, unless we’re actually going to merge the COSE and JOSE
> WGs, it seems procedurally awkward to have drafts in the JOSE WG that
> dictate COSE algorithms. Is it really that hard to have two drafts?
>

Many of the same WG members participate in both groups, and it seems a
common practice to have shared drafts between COSE and JOSE WGs, for
instance, see draft-ietf-cose-dilithium. Anyways, the COSE/JOSE chairs can
determine whether separate drafts are necessary or if a consolidated draft
would be more effective.

-Tiru


>
> — Neil
>
> > On 14 Sep 2024, at 21:50, Karen ODonoghue <[e-mail]> wrote:
> >
> > JOSE and COSE working group members,
> >
> > The following draft has been submitted for consideration by the JOSE
> > working group. The chairs agreed, at IETF 120, to issue a call for
> > adoption.
> >
> > https://datatracker.ietf.org/doc/draft-reddy-cose-jose-pqc-kem/
> >
> > Please review the document and indicate (by responding to this email
> > and keeping the subject line intact) whether or not you think this is
> > a good place to start the development of this document. Please provide
> > comments.
> >
> > This call for adoption will close on Monday 30 September.
> >
> > Thank you,
> > Karen
> >
> > _______________________________________________
> > jose mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
>
> _______________________________________________
> jose mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>