IETF Logo Mail Archive

[TLS] Re: AD review draft-ietf-tls-rfc8447bis-10

Sean Turner <sean@sn3rd.com> Tue, 11 March 2025 13:53 UTC

Return-Path: <sean@sn3rd.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 3B08D9FA1BB for <tls@mail2.ietf.org>; Tue, 11 Mar 2025 06:53:49 -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 V1ZMuwOi7EiY for <tls@mail2.ietf.org>; Tue, 11 Mar 2025 06:53:47 -0700 (PDT)
Received: from mail-qv1-xf36.google.com (mail-qv1-xf36.google.com [IPv6:2607:f8b0:4864:20::f36]) (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 5C7209FA1A8 for <tls@ietf.org>; Tue, 11 Mar 2025 06:53:47 -0700 (PDT)
Received: by mail-qv1-xf36.google.com with SMTP id 6a1803df08f44-6ddcff5a823so34741746d6.0 for <tls@ietf.org>; Tue, 11 Mar 2025 06:53:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; t=1741701226; x=1742306026; 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=PNQUlkUHfUDM7Re9i8PMD6FI6FgqJ+MGBo/rpPmNWtA=; b=Nz9B7Nhiyc2SkqQcstmU1LvCLFmIPVvJNasQoOQqvzAtSEJra9alq/q5B7F5f2VZO6 sbqa0KVsibSjIMyehjRayEdNIlE9Yi1y6HqFuqBvttvMLAgdwvqBFXsI4cbvFORTwsLS 0fN8WuBcGcNwUxdz9/jrvoVmmty22AA+jodvw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741701226; x=1742306026; 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=PNQUlkUHfUDM7Re9i8PMD6FI6FgqJ+MGBo/rpPmNWtA=; b=jkgUDWXyFmsrix4O6jeWB/K4/qZwrVHmKcJzVOSezXkWSWugkUqOtsaiWKz37jC/e6 mmkmBQrJwLgm3PbXWFNtNxpltcytDlGiK51TqLoDzXDgBftKOEnWwv7XrQzIxsGafP2E oVYzpglZpBn5udPUEGxlqKjDB3XBzJUtW48q8o7BS9J0zLoUvNvh7szHwUP0Tft8mYhB aX8iLkr+mIPucU+F5dUFT4uQhcLBtOHexO2npMHPt0op2PvZcN7ccjAI0O8crora60Jj 85eRGDRfjcZTq5Sb6oNgk/AYqVT/LR8coxTeM++AnC6AoQVPF/lVo1wPEfUe9URrZIhY v45w==
X-Gm-Message-State: AOJu0YwPJ1fzOK9QmGVBk1rtPkG/UsFDdjSZhc/gMNxnu9N2Ppgloda+ uDrLHQW+tjB0nYVDyQGoTODh3rEHEzHWkwpBL35HPITGGDd1MsowmOSaNpdXobUN7HCJMYuf5QK +
X-Gm-Gg: ASbGncvJRfo956RJsaAiY515TQUL5eNrZlExn3ZHrMz50CdI81/8oWxX1aYqCes7kyD mUE42DFMkCQ86XDRRtEE/B3OHbg0tOYFwHz3lpyvpCQ7nSfVaMxHklxE7qd2/ILmzLmPH0HnTyC 0/hggivEVKS5Op7dgeGEhPuJPy6hbHZ4wes2As3OrxZQHZ2jie4CT5odUebzFQaTaocrxnE/en5 ETpc3lubJk/OIfPdQHIonborbHz0nezLyl+AJie/iw0r9sFJFirB44nmfXE5A3+VFwnuBnk+5h2 ZdOe7juOGO4f2Z9IQu0PtTK2I5pR94zl7sQeTwR/vgKNKPuugN8otHcOuJy1fOwsdd2wh9iX1hh R
X-Google-Smtp-Source: AGHT+IHk8DkYWUL7hpsm8JZ04uXLKq0qjNbg1O72VSUf4Vm/tjKuk6NJqeieNsaBYwLbCcLY+pWT3A==
X-Received: by 2002:a05:6214:cc9:b0:6e6:6ba9:9e84 with SMTP id 6a1803df08f44-6e900650d39mr202561266d6.26.1741701225103; Tue, 11 Mar 2025 06:53:45 -0700 (PDT)
Received: from smtpclient.apple ([2600:4040:252a:8d00:e509:c24a:472e:7cbb]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-6e8f715b5a4sm72353446d6.72.2025.03.11.06.53.44 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Mar 2025 06:53:44 -0700 (PDT)
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>
X-Mailer: Apple Mail (2.3826.400.131.1.6)
Message-ID-Hash: VJHD6YVPNZ2F7T4TC7T4CTISJNFXCKAE
X-Message-ID-Hash: VJHD6YVPNZ2F7T4TC7T4CTISJNFXCKAE
X-MailFrom: sean@sn3rd.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: Paul Wouters <paul.wouters=40aiven.io@dmarc.ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: AD review draft-ietf-tls-rfc8447bis-10
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/t-u8YUwrXwxac7q87dWdkseAxd4>
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>

> On Mar 7, 2025, at 12:51 PM, Sean Turner <sean@sn3rd.com> wrote:
> 
>> Section 5  TLS Cipher Suites Registry
>> 
>> 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.
>> 
>> 
>> Note that this registry states:
>> 
>>         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].
>> 
>> Has this happened or is it scheduled? If so who is the contact I can follow up with?
> 
> 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

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