[TLS] Secdir last call review of draft-ietf-tls-rfc8447bis-11

Benjamin Schwartz via Datatracker <noreply@ietf.org> Thu, 13 March 2025 20:16 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Schwartz via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174189701109.952601.10401495531190343196@dt-datatracker-775fc5cbb8-824tp>
Date: Thu, 13 Mar 2025 13:16:51 -0700
Message-ID-Hash: 5S7BO4NFUCYRK35AA6TVRFC4QBMHOIVX
CC: draft-ietf-tls-rfc8447bis.all@ietf.org, last-call@ietf.org, tls@ietf.org
Reply-To: Benjamin Schwartz <ietf@bemasc.net>
Subject: [TLS] Secdir last call review of draft-ietf-tls-rfc8447bis-11
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/J7x5Jnw1_ZdqY2UqHRRFJVVILdM>

Reviewer: Benjamin Schwartz
Review result: Ready

Nit: "leave an items", lower case "*  update the note on the role ...".

Use of BCP 14 "IANA SHALL" seems odd, but I assume IANA process experts have
reviewed this formulation.

I wish this document would populate the "Comment" column on some of the
discouraged entries, or at least note the reasoning in the body of the
document.  As it stands, it seems that a reader could find a discouraged entry
in these registries, read the Comment column, read all the linked reference
documents (including this one), and still find no explanation for why it is
discouraged.

[TLS] Secdir last call review of draft-ietf-tls-r… Benjamin Schwartz via Datatracker
[TLS] Re: Secdir last call review of draft-ietf-t… Sean Turner