IETF Logo Mail Archive

[Emailcore] Re: draft-ietf-emailcore-as-27

"John R. Levine" <johnl@iecc.com> Fri, 06 March 2026 06:13 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: emailcore@mail2.ietf.org
Delivered-To: emailcore@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 26948C56B77E for <emailcore@mail2.ietf.org>; Thu, 5 Mar 2026 22:13:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.401
X-Spam-Level:
X-Spam-Status: No, score=-4.401 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.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 DBcDexQ4yLFK for <emailcore@mail2.ietf.org>; Thu, 5 Mar 2026 22:13:57 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 9E245C56B779 for <emailcore@ietf.org>; Thu, 5 Mar 2026 22:13:57 -0800 (PST)
Received: (qmail 44735 invoked from network); 6 Mar 2026 06:13:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=aebd69aa70a4.k2603; t=1772777626; x=1773123226; bh=uizrMukaAkLbcbcl4CTezBsGdLUZq6uHi7/mJOs4tg8=; b=CmheE3Y/DLpOnsTFXKx4qGOn16XbVJvQ4mENYIjpZaJ7yjn/pZWcCoG6rAZ34p2LSc1LwuJXv8Eah4zBFJmwZ1q/K7+9U/JB8ORkxNyNiODGw0SCGiDR+Dwfnjl94tQVPXDhDQVyLV2f+2DmFBiBTVDFSPvlUqZ/PpQGK0OmE2SktOKtLLqRI2yNR44kBUVltl46YZ1qeY010u6aQKa71DNe/7Ue8m+fqbjV5xxX+BbceknJHXM4bVozn0RstDUTMpGgI8kUpZ9MkO6FIBzgZk0kzx3s8UWJasb6t7PJx+Ek6cLoiAl/ICnwcf1mJsSuZnuEIeEV6B43E9LIQnHHQw==
Received: from ary.local ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 06 Mar 2026 06:13:56 -0000
Received: by ary.local (Postfix, from userid 501) id 50EEDFB47B18; Fri, 6 Mar 2026 06:13:54 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1]) by ary.local (Postfix) with ESMTP id 0CB61FB47AFA; Fri, 6 Mar 2026 06:13:54 +0000 (GMT)
Date: Fri, 06 Mar 2026 06:13:53 +0000
Message-ID: <42d0f5dc-4bd6-cfe1-eef6-c477e59b6f25@iecc.com>
From: "John R. Levine" <johnl@iecc.com>
To: Jeffrey Walton <noloader@gmail.com>, John C Klensin <john-ietf@jck.com>
In-Reply-To: <CAH8yC8=mxQg0umroRw35CBzmLhktmyHKcHrHhBRrRHkioUP0Dg@mail.gmail.com>
References: <999F11B4333A51B9CD1B4CAB@PSB> <CAH8yC8=mxQg0umroRw35CBzmLhktmyHKcHrHhBRrRHkioUP0Dg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: VLOCCXX47NE6SHB2CRQMQHF3BAY7PT4G
X-Message-ID-Hash: VLOCCXX47NE6SHB2CRQMQHF3BAY7PT4G
X-MailFrom: johnl@iecc.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: emailcore@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Emailcore] Re: draft-ietf-emailcore-as-27
List-Id: EMAILCORE proposed working group list <emailcore.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/fL0sHyK5bnn-5v3BTeDO9C-C5rY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emailcore>
List-Help: <mailto:emailcore-request@ietf.org?subject=help>
List-Owner: <mailto:emailcore-owner@ietf.org>
List-Post: <mailto:emailcore@ietf.org>
List-Subscribe: <mailto:emailcore-join@ietf.org>
List-Unsubscribe: <mailto:emailcore-leave@ietf.org>

On Wed, 4 Mar 2026, Jeffrey Walton wrote:
> Do eNULL and aNULL cipher suites meet the confidentiality and integrity
> goals or requirements for email messages in this A/S?

Probably not, but in the thirty years I've been managing mail servers, I 
do not ever recall this coming up.  When I added STARTTLS to my mail 
server, I just used whatever config the SSL library documentation 
recommended, which was TLS 1.0 or newer, which I think is typical.

I don't think we need to clutter up the A/S with statements along the 
lines of "do not do this obviously silly thing because it would be silly."

R's,
John

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