[secdir] Re: Secdir last call review of draft-ietf-tls-rfc8447bis-11
Sean Turner <sean@sn3rd.com> Tue, 25 March 2025 13:32 UTC
Return-Path: <sean@sn3rd.com>
X-Original-To: secdir@mail2.ietf.org
Delivered-To: secdir@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 13341121C8A8 for <secdir@mail2.ietf.org>; Tue, 25 Mar 2025 06:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U1zAB8cE8SWi for <secdir@mail2.ietf.org>; Tue, 25 Mar 2025 06:32:13 -0700 (PDT)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 58535121C891 for <secdir@ietf.org>; Tue, 25 Mar 2025 06:32:13 -0700 (PDT)
Received: by mail-qt1-x829.google.com with SMTP id d75a77b69052e-47686580529so53633061cf.2 for <secdir@ietf.org>; Tue, 25 Mar 2025 06:32:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; t=1742909533; x=1743514333; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=AItZxgv5w6Qel4pJ2IE248lY+ZWh0d5N7v7GDyxqVL8=; b=gR07Lb0Vu0GPcVhu7P2qXSvcZl6Tx5yyQtvZjvsM1MGUddYZ1ddvColMyo8vZLI6CH ieJbHZzvhu82/ju1FMD9ONf0nFr7JWdO/YhJCwTcnS3t8VFQlA6Z+qGmfLrZyUhrO+XT l1LL58T0SI+XwaKsZAXu8Vp9Knu2wnjU/8bxs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742909533; x=1743514333; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=AItZxgv5w6Qel4pJ2IE248lY+ZWh0d5N7v7GDyxqVL8=; b=cqafuwHJ+kjFus6qxEivsgCwqCUX1bmBqPn5qpMpz6jzoSlur+zLxCj8GbXG43njUD 2ETJHjJPAaFXsYKbjaVdfQqP870XtbTPb1fWZugjL/GbBv/02pTGPScZRLEp9qLt0B+u uM/F+d6OjfPNfyIfOz60dVCH03N2eqIt1zXQ5Vi69eGtwqQPr9zyPZfzyIrQ/ZaWG2GM eV/K1JLTNIlJME7NFSwmMkWcMRPiASURQ1uHDY+806uvzXeGT/A2goEIczKjl2I2YSdM t5AgVJQJ+Ci3LNKsUlhqJUlfkp3MO+mXdsCoPsidW25KpQwkpgZke7FJ3PDiPcCvgzPg deww==
X-Gm-Message-State: AOJu0YyHzTfNmTRZAm57T7KrGgS3RQhfAS4aAVkLfSmQMoQrLNBiiQ23 zhjwdliYhCsoTJYHkAmpi80c2jgJ5O0Y0RmHHjVGxCTlgp6c1xFQ60lJMnIoxfQoLLuXYu3v0yC Z
X-Gm-Gg: ASbGnct4J8S4sGC/2YjX+YmWIEWHe+3Is5aBnuOem/DBYo/FkwSgy+gwQj+MSuVSYSS teMfDWUMDIU8Vouy2RSWrTdL/JzUetI26CXJZNwCaaeVQv67Gyv0ifrRkt51l++D1jMvTsJRY9p NBPpzKh1I9tEgGIoAIw7QwxRomKfdxyRgYbHhLJx61WkjXKnqRd7XduuszcaKh5tbHI7R+FhZql rSKX8yHfK+D5pe9MN9W/8A81uspIVsYK1tXI4Pq4KWu/U1+oi5KerkEqmnKSp27ByuXurvWQOwj 35nftsi4genRo34BUvnPKwA5lR4PWW6Ilvz9SPQF0vqq10pRz2D/6+j5o6Z5LPMF
X-Google-Smtp-Source: AGHT+IHOlwGqjPu1GN8ndLhE5fTqpDe6yynjijJzPPvDm3759dyjEVsXzU/RhS2ZGG5yZOenMmw89g==
X-Received: by 2002:a05:622a:1f0a:b0:476:a74d:f23b with SMTP id d75a77b69052e-4771de62897mr284263821cf.48.1742909532624; Tue, 25 Mar 2025 06:32:12 -0700 (PDT)
Received: from smtpclient.apple ([2600:4040:252a:8d00:9c9:f11c:31df:d1fd]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-4771d176093sm59613371cf.19.2025.03.25.06.32.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Mar 2025 06:32:11 -0700 (PDT)
From: Sean Turner <sean@sn3rd.com>
Message-Id: <4438BB2C-521A-4162-92CC-9E3592796EC3@sn3rd.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_12B9DC5C-9D3F-4F19-85FE-E77B29D7104C"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
Date: Tue, 25 Mar 2025 09:31:50 -0400
In-Reply-To: <174189701109.952601.10401495531190343196@dt-datatracker-775fc5cbb8-824tp>
To: Benjamin Schwartz <ietf@bemasc.net>
References: <174189701109.952601.10401495531190343196@dt-datatracker-775fc5cbb8-824tp>
X-Mailer: Apple Mail (2.3826.400.131.1.6)
Message-ID-Hash: 5VMT5GHFA3JNGDC2I3YWZL52J2LQCAT3
X-Message-ID-Hash: 5VMT5GHFA3JNGDC2I3YWZL52J2LQCAT3
X-MailFrom: sean@sn3rd.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-secdir.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: secdir@ietf.org, draft-ietf-tls-rfc8447bis.all@ietf.org, last-call@ietf.org, TLS List <tls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [secdir] Re: Secdir last call review of draft-ietf-tls-rfc8447bis-11
List-Id: Security Area Directorate <secdir.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/x16FsFL9-ZeH_N1mwOtMJO4eBfc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Owner: <mailto:secdir-owner@ietf.org>
List-Post: <mailto:secdir@ietf.org>
List-Subscribe: <mailto:secdir-join@ietf.org>
List-Unsubscribe: <mailto:secdir-leave@ietf.org>
> On Mar 14, 2025, at 3:16 AM, Benjamin Schwartz via Datatracker <noreply@ietf.org> wrote: > > Reviewer: Benjamin Schwartz > Review result: Ready > > Nit: "leave an items", lower case "* update the note on the role ...". Fixed via: https://github.com/tlswg/rfc8447bis/pull/70 > Use of BCP 14 "IANA SHALL" seems odd, but I assume IANA process experts have > reviewed this formulation. Yep! > 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. Fair point, but this one had legs. 1) I went through each of the entries that we are setting to do “D”. Most but not all had links to explain why they got a “D”. This PR at the end includes additions where I think they are needed. The only one that is weird is the curves, because what we did was suggested at IETF 118 that anything under 128-bits should be D. So, this is the draft that’s going to knock ‘em out. We could add that here or just point to the presentation. The PR points to the presentation. 2) This I-D has a very long list of cipher suites. Many of these are in -deprecate-obsolete-kex. -deprecate-obsolete-kex is pinned on this I-D. We’re going to leave those in this draft, but put them in another table and add to the reference column to refer to this draft where we taken them out for being NULL, weak, etc. 3) We should make it clear that when “D” is set that enough information be included to determine why it’s “D”. Added this to the PR ***NOTE the addition of the MUST": When marking a registry entry as “D”, either the References or the Comments Column MUST include sufficient information to determine why the marking has been applied. Here’s a link to the PR: https://github.com/tlswg/rfc8447bis/pull/73 spt
- [secdir] Secdir last call review of draft-ietf-tl… Benjamin Schwartz via Datatracker
- [secdir] Re: Secdir last call review of draft-iet… Sean Turner