MIME-Version: 1.0
From: Bas Westerbaan <bas@cloudflare.com>
Date: Tue, 9 Jun 2026 13:46:00 +0200
Message-ID: 
 <CAMjbhoXsZsgeLJi4ct_nWduA4ytAtLTg2HjT8D2T10iKvO+3Og@mail.gmail.com>
To: jmh@joelhalpern.com
Content-Type: multipart/alternative; boundary="0000000000008506b30653d0acde"
Message-ID-Hash: HZCQEMJTVKIZZO7SWKXA4TRA3OY7UNQ2
CC: "<tls@ietf.org>" <tls@ietf.org>, gen-art@ietf.org
Precedence: list
Subject: =?utf-8?q?=5BGen-art=5D_Re=3A_Genart_last_call_review_of_draft-ietf-tls-mlds?=
	=?utf-8?q?a-03?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/gen-art/GYfgcjP8addAuwksN32TYnUU4jY>

--0000000000008506b30653d0acde
Content-Type: text/plain; charset="UTF-8"

Hi Joel,

Thanks for the review.

Minor issues: The security considerations section seems remarkably light.
> It
> may be correct.
>

Original intention was to keep the security considerations specific to
anything particular about the use of ML-DSA in TLS and refer to existing
documents (FIPS 204, RFC 8446) for generally applicable considerations.

The working group has certainly thought a lot more about it then these
short few words might suggest. Among others, the WG discussed several
changes: whether to mention composites (hybrids); whether to discuss hedged
vs deterministic signing; and whether to repeat general guidance.  My guess
is that only https://github.com/tlswg/tls-mldsa/pull/36 will have WG
support.

Best,

Bas

--0000000000008506b30653d0acde
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Joel,<br><br>Thanks for the review.<div><br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex">Minor issues: The security considera=
tions section seems remarkably light.=C2=A0 It<br>may be correct.<br></bloc=
kquote><div>=C2=A0<br></div><div>Original intention was to keep the securit=
y considerations specific to anything particular about the use of ML-DSA in=
 TLS and refer to existing documents (FIPS 204, RFC 8446) for generally app=
licable considerations.</div><div><br></div><div>The working group has cert=
ainly thought a lot more about it then these short few words might suggest.=
 Among others, the WG discussed several changes: whether to mention composi=
tes (hybrids); whether to discuss hedged vs deterministic signing; and whet=
her to repeat general guidance.=C2=A0 My guess is that only <a href=3D"http=
s://github.com/tlswg/tls-mldsa/pull/36">https://github.com/tlswg/tls-mldsa/=
pull/36</a> will have WG support.</div><br>Best,</div><div><br>Bas</div></d=
iv>

--0000000000008506b30653d0acde--