IETF Logo Mail Archive

[TLS] Re: Deb Cooley's Yes on draft-ietf-tls-8773bis-10: (with COMMENT)

Russ Housley <housley@vigilsec.com> Wed, 03 September 2025 18:36 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id C6C7D5CDDC7A; Wed, 3 Sep 2025 11:36:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=vigilsec.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 6tXgEaHgWTCx; Wed, 3 Sep 2025 11:36:24 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 842D95CDDC3A; Wed, 3 Sep 2025 11:36:17 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 67BD31A2E8B; Wed, 3 Sep 2025 14:36:17 -0400 (EDT)
Received: from smtpclient.apple (pool-96-255-71-95.washdc.fios.verizon.net [96.255.71.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 4A7221A2C16; Wed, 3 Sep 2025 14:36:17 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <175685034411.1992531.9688241447600835083@dt-datatracker-67876766b7-bkzgr>
Date: Wed, 03 Sep 2025 14:36:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D0699EE-8CDA-46F1-9BE4-8511E53F8807@vigilsec.com>
References: <175685034411.1992531.9688241447600835083@dt-datatracker-67876766b7-bkzgr>
To: Deb Cooley <debcooley1@gmail.com>
X-Mailer: Apple Mail (2.3826.700.81)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=content-type:mime-version:subject:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=pair-202402141609; bh=kfyEbv4EdbK3Qvvo+5ROF0RpRZ8F80G1eHgcdr9Ws4A=; b=K7oqw75jRr0r/g7rjh2WezkXqTNSf6mZs0vZJpCQmzIvWHw7JdWva7NkQQwYsaF8BdenBx5v4xkdycz8tRxSCSZPhgU6BIcqswt8dlrDRpRHtaU8io8qrBROST1gJZw8eKFhixjv8SxKgGE9V6zbftou/xVfN8GChwsH+oO0+8TWg7uqjWeI2uYDczvrmIT2dxgrLYVPJM66qcws2dED/+z0P2dIZKaoCML0U1WlGMdh+KDj/JT+2axfNX6Ib+Yo5r76ATVqKJRypWokrEXjcP1pxnvEVbgWB+0gwxrxw81/GfEs43RHfr59q6ggSJyovcPZckwyWQUIyBZE1PsN8g==
X-Scanned-By: mailmunge 3.09 on 66.39.134.11
Message-ID-Hash: 4ISVYJHKU7GQFR2ACUORYTSFRJ4NGINR
X-Message-ID-Hash: 4ISVYJHKU7GQFR2ACUORYTSFRJ4NGINR
X-MailFrom: housley@vigilsec.com
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: IESG <iesg@ietf.org>, draft-ietf-tls-8773bis@ietf.org, tls-chairs@ietf.org, IETF TLS <tls@ietf.org>, Joe Salowey <jsalowey@gmail.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Deb Cooley's Yes on draft-ietf-tls-8773bis-10: (with COMMENT)
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/9CLqW_ZqQlvW7H0bcOZUCf9Ncgg>
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>

Corrected. draft-ietf-tls-rfc8446bis is now a normative reference.

Russ


> On Sep 2, 2025, at 5:59 PM, Deb Cooley via Datatracker <noreply@ietf.org> wrote:
> 
> Deb Cooley has entered the following ballot position for
> draft-ietf-tls-8773bis-10: Yes
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
> for more information about how to handle DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-tls-8773bis/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thanks to Brien Weis for their secdir review.
> 
> Security Considerations, para 4:  This is a key consideration, thank you for
> adding it.
> 
> Normative References:  I don't see that the mention in the Intro makes
> draft-ietf-emu-bootstrapped-tls normative, but it certainly isn't an issue.
> 
> Informative References:  I do think that draft-ietf-tls-rfc8446bis is
> normative.  Possibly this has confused various reviewers?
> 
> 
> 
> _______________________________________________
> TLS mailing list -- tls@ietf.org
> To unsubscribe send an email to tls-leave@ietf.org

v2.35.0 | Report a Bug | By Email | System Status