From: Sean Turner <sean@sn3rd.com>
Message-Id: <83D52266-EB3E-4F52-AF35-971D58896643@sn3rd.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_319F9D6D-4B33-4DAD-95AE-A1946768AB2E"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
Date: Tue, 11 Mar 2025 09:53:23 -0400
In-Reply-To: <F0DE2499-2422-4F72-B0AD-8CA90A20F152@sn3rd.com>
To: TLS List <tls@ietf.org>
References: 
 <CAGL5yWZy1xXLTVGhj3s_gNCoph_3XcShO7DWm=aDsYR1ySvY6g@mail.gmail.com>
 <F0DE2499-2422-4F72-B0AD-8CA90A20F152@sn3rd.com>
Message-ID-Hash: VJHD6YVPNZ2F7T4TC7T4CTISJNFXCKAE
CC: Paul Wouters <paul.wouters=40aiven.io@dmarc.ietf.org>
Precedence: list
Subject: =?utf-8?q?=5BTLS=5D_Re=3A_AD_review_draft-ietf-tls-rfc8447bis-10?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/tls/t-u8YUwrXwxac7q87dWdkseAxd4>


--Apple-Mail=_319F9D6D-4B33-4DAD-95AE-A1946768AB2E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Mar 7, 2025, at 12:51=E2=80=AFPM, Sean Turner <sean@sn3rd.com> =
wrote:
>=20
>> Section 5  TLS Cipher Suites Registry
>>=20
>> This section contains some reasoning why it is Discouraging things. =
The current
>> IANA registry also contains such reasoning on the form of notes, but =
this section
>> does not add to the notes. So now this inforation is splintered =
between RFC and
>> Registry. I think the easiest fix is to add these few reasons =
specified here
>> as Note: to the IANA registry.
>>=20
>>=20
>> Note that this registry states:
>>=20
>>         When this registry is modified, the YANG module
>>         "iana-tls-cipher-suite-algs" [iana-tls-cipher-suite-algs] =
must
>>         be updated as defined in [RFC9645].
>>=20
>> Has this happened or is it scheduled? If so who is the contact I can =
follow up with?
>=20
> The YANG module is empty right now so I assume it needs to be =
scheduled. I assume IANA will run this as part of their IANA Actions =
process.  Confirming with Kent now.

For the list, I checked with Kent (author of RFC 9645) and he confirmed =
that IANA will does this as part of their process.

spt=

--Apple-Mail=_319F9D6D-4B33-4DAD-95AE-A1946768AB2E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: =
after-white-space;"><br><div><blockquote type=3D"cite"><div>On Mar 7, =
2025, at 12:51=E2=80=AFPM, Sean Turner &lt;sean@sn3rd.com&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div><meta =
charset=3D"UTF-8"><div class=3D"Singleton" style=3D"overflow-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div><blockquote type=3D"cite" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: 400; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div><div dir=3D"ltr"><div>Section 5 &nbsp;TLS =
Cipher Suites Registry<br><br>This section contains some reasoning why =
it is Discouraging things. The current<br>IANA registry also contains =
such reasoning on the form of notes, but this section<br>does not add to =
the notes. So now this inforation is splintered between RFC =
and<br>Registry. I think the easiest fix is to add these few reasons =
specified here<br>as Note: to the IANA =
registry.<br></div><div><br></div><div><br>Note that this registry =
states:<br><br>&nbsp; &nbsp; &nbsp; &nbsp; When this registry is =
modified, the YANG module<br>&nbsp; &nbsp; &nbsp; &nbsp; =
"iana-tls-cipher-suite-algs" [iana-tls-cipher-suite-algs] must<br>&nbsp; =
&nbsp; &nbsp; &nbsp; be updated as defined in [RFC9645].<br><br>Has this =
happened or is it scheduled? If so who is the contact I can follow up =
with?<br></div></div></div></blockquote><div style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: 400; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><br></div><div style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: 400; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">The YANG module is empty right now so I assume =
it needs to be scheduled. I assume IANA will run this as part of their =
IANA Actions process. &nbsp;Confirming with Kent =
now.</div></div></div></div></blockquote></div><br><div>For the list, I =
checked with Kent (author of RFC 9645) and he confirmed that IANA will =
does this as part of their =
process.</div><div><br></div><div>spt</div></body></html>=

--Apple-Mail=_319F9D6D-4B33-4DAD-95AE-A1946768AB2E--