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

Giuseppe Fioccola via Datatracker <noreply@ietf.org> Thu, 03 April 2025 14:54 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: tls@ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from [10.244.8.216] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 6480116F04DC; Thu, 3 Apr 2025 07:54:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Giuseppe Fioccola via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174369205715.2732618.18280102439496098010@dt-datatracker-5b9b68c5b6-zxk6z>
Date: Thu, 03 Apr 2025 07:54:17 -0700
Message-ID-Hash: V4SCOYAJJAGTKBTT4SCOAHQW3QTHWMW5
X-Message-ID-Hash: V4SCOYAJJAGTKBTT4SCOAHQW3QTHWMW5
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-tls-rfc8447bis.all@ietf.org, last-call@ietf.org, tls@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
Subject: [TLS] Opsdir last call review of draft-ietf-tls-rfc8447bis-11
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/F7IIHkxOZmsoX4SqGi-XDWig9aA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

Reviewer: Giuseppe Fioccola
Review result: Has Nits

This document updates the changes in RFC 8447 and requests IANA to make changes
to a number of TLS and DTLS registries. In particular, it updates the
"Recommended" column in TLS registries by defining a third value "D" for items
that are discouraged and adds a "Comment" column to the registries that do not
already have it. This document updates several RFCs: RFC 3749, RFC 5077, RFC
4680, RFC 5246, RFC 5705, RFC 5878, RFC 6520, RFC 7301, and RFC 8447.

I think that the document has a well defined scope and is quite clear. However,
I have few suggestions:

- In the Abstract, I suggest to replace 'adds a Comments column to all active
registries' with 'adds a Comment column to all the registries that do not
already have it'.

- In section 3, I suggest to replace 'The permitted values are' with 'The
permitted values of the Recommended column are', just to avoid any confusion.

- In the sections from 4 to 14, I suggest to add some explanation on why
specific registries are changed to discouraged. Some insight would help the
reader.

- I would also add some observations on the operational and interoperability
impacts, if any, of the changes proposed in the document.

- Currently, the section on "IANA Considerations" simply says that the document
is entirely about changes to TLS-related IANA registries, as per RFC 8447.
Instead, I would put all the relevant sections on IANA requests (i.e. sections
from 4 to 14) under an "IANA Considerations" section. In this way you can avoid
the IANA section with no content.