I support adoption of this draft. Like others have said, there is a desire
to have support of post-quantum key establishment in protocols such as
IKEv2 so implementations are ready when the NIST process for algorithm
standardization completes.
Jonathan
Tero Kivinen Sun, 03 November 2019 22:42 UT
I verified that the example in Appendix A of RFC 8031 is incorrect as
reported, but I do not believe that updating the values as suggested
in this errata completely fixes the example.
The corrected values given in the report are valid if they are
interpreted as little-endian encoded coordinates (i
Dear Tobias:
> I think it's the other way around. The byte-separated values are all in
> little-endian encoding and d_i and d_r are simply given as hex-encoded
> numbers (in their natural big-endian encoding as you'd write a decimal
> number). So I think the test vectors are correct.
I suppose
I also support the WG adoption of this draft.
Jonathan
On Tue, Mar 18, 2025, 16:08 IETF Secretariat <
ietf-secretariat-re...@ietf.org> wrote:
>
> The IPSECME WG has placed draft-kampanakis-ml-kem-ikev2 in state
> Call For Adoption By WG Issued (entered by Tero Kivinen)
>
> The document is availa
