Hello,
Thank you for the thorough reviews of the document. A new version
of the draft has just been released, addressing all requested
changes (both discussion points and nits). The draft is available
here:
https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-mlkem/04/
Here below is a short summary of changes:
* References: Make [hybrid] normative; add/clarify HKDF reference
via RFC 5869; update to RFC 9847 (replacing draft-ietf-tls-
rfc8447bis).
* Text: Rename “Discussion” to “Regulatory context” and expand it
(incl. NIST SP 800-227 notes).
* IANA/TLS registry: Obsoletes the experimental pre-standard
Kyber768 groups X25519Kyber768Draft00 (25497) and
SecP256r1Kyber768Draft00 (25498); instruct IANA to set
Recommended = “D”, update Reference to this RFC, and update
Comments accordingly.
* Editorial: Addressed nits, including normalizing reference
labels to a consistent format (e.g., RFC7748 instead of rfc7748
or ad-hoc labels like HKDF) and renaming NIST references to the
NIST-... form.
Kind regards,
Kris
On 05/02/2026 10:12, Eric Vyncke (evyncke) wrote:
Kris,
Thanks for promptly creating the PR that would indeed address my concerns.
Regards
-éric
*From: *Kris Kwiatkowski <[email protected]>
*Date: *Thursday, 5 February 2026 at 10:19
*To: *Eric Vyncke (evyncke) <[email protected]>, The IESG <[email protected]>
*Cc: *[email protected]
<[email protected]>, [email protected] <[email protected]>,
[email protected] <[email protected]>, [email protected] <[email protected]>
*Subject: *Re: Éric Vyncke's No Objection on draft-ietf-tls-ecdhe-mlkem-03:
(with COMMENT)
Dear Éric, Thank you for the review. I've tried to addressed your comments
in following gihub pull request. Please see references inline below:
On 2/3/26 10:02, Éric Vyncke via Datatracker wrote:
----------------------------------------------------------------------
COMMENT:
---------------------------------------------------------------------- #
Éric Vyncke INT AD comments for draft-ietf-tls-ecdhe-mlkem-03 CC
@evyncke Thank you for the work put into this document. Please find
below some non-blocking COMMENT points/nits. I hope that this review
helps to improve the document, Regards, -éric Note: this ballot comments
follow the Markdown syntax of
https://github.com/mnot/ietf-comments/tree/main, i.e., they can be
processed by a tool to create github issues. ## COMMENTS (non-blocking)
### Section 2 Please add reference (at least expansion) for the FIPS and
NIST acronyms (and of course prefix them with US to avoid any ambiguity).
https://github.com/tlswg/tls-ecdhe-mlkem/pull/64
### Section 5 Who is the "we" in `For this reason we put the ML-KEM
shared secret first` ? The authors ? The WG ? The IETF ? Please avoid
such ambiguities.
https://github.com/tlswg/tls-ecdhe-mlkem/pull/62
### Section 7 Please add a URI reference to the registry, e.g.,
https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-8
https://github.com/tlswg/tls-ecdhe-mlkem/pull/63 Please let me know in case
you have further comments. Kind regards, Kris
_______________________________________________
TLS mailing list -- [email protected]
To unsubscribe send an email to [email protected]
