The revised draft
https://www.ietf.org/archive/id/draft-reddy-cose-jose-pqc-hybrid-hpke-04.html
addresses all the comments raised during the WG adoption call. Regarding
Michael's comment on the terms 'traditional' and 'Post-Quantum,' this issue
has been discussed in the PQUIP WG. However, no decision has been made to
change the terminology, and this issue is beyond the scope of this
document

-Tiru

On Sat, 30 Nov 2024 at 22:42, Michael Jones <[email protected]>
wrote:

> Only two replies to the call for adoption clearly stated that they favored
> adoption.  Whereas more messages were sent than that with critiques of the
> draft.  Therefore, the draft is not adopted in its present form.
>
>
>
> The chairs suggest that the authors update the specification to address
> the feedback from Ilari, Orie, Mike P., and Michael R. and publish a new
> draft, and then ask for feedback on the revised draft on the mailing list.
> Following that, we can consider a call for adoption of the revised draft.
>
>
>
>                                                                 For the
> chairs,
>
>                                                                 -- Mike
>
>
>
> *From:* Michael Jones
> *Sent:* Friday, November 8, 2024 7:04 AM
> *To:* [email protected]
> *Subject:* Call for adoption of draft-reddy-cose-jose-pqc-hybrid-hpke
>
>
>
> Per discussions at the IETF 121 COSE working group meeting, this note
> starts a two-week call for adoption of the PQ/T Hybrid KEM: HPKE with
> JOSE/COSE specification.  Please let us know whether you are in favor of
> adoption or not by Friday, November 22, 2024.
>
>
>
>                                                                 Thank you,
>
>                                                                 -- Mike &
> Ivo
>
>
> _______________________________________________
> COSE mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to