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]

Reply via email to