[Last-Call] Re: Last Call: <draft-ietf-emailcore-as-26.txt> (Applicability Statement for IETF Core Email Protocols) to Proposed Standard

Ted Lemon <mellon@fugue.com> Tue, 06 January 2026 15:56 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: last-call@mail2.ietf.org
Delivered-To: last-call@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E7C3AA37E5D6 for <last-call@mail2.ietf.org>; Tue, 6 Jan 2026 07:56:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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_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=fugue.com header.b="ocM0dD9C"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="kYGLY3NL"
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 YktgP84Sbzz5 for <last-call@mail2.ietf.org>; Tue, 6 Jan 2026 07:56:02 -0800 (PST)
Received: from fout-b4-smtp.messagingengine.com (fout-b4-smtp.messagingengine.com [202.12.124.147]) (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 C4B78A37E2B8 for <last-call@ietf.org>; Tue, 6 Jan 2026 07:55:51 -0800 (PST)
Received: from phl-compute-01.internal (phl-compute-01.internal [10.202.2.41]) by mailfout.stl.internal (Postfix) with ESMTP id 2DC471D00133; Tue, 6 Jan 2026 10:55:51 -0500 (EST)
Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-01.internal (MEProxy); Tue, 06 Jan 2026 10:55:51 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue.com; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1767714951; x=1767801351; bh=JoWTQuUPVt Q9Y8rxHFC84rR5XvaR5IvsDBKz+A1DStM=; b=ocM0dD9C7RyyfzXXraOSTU0Qtg brhVqtc3Z+o1Vjyy/1cIg+NAj+VUkIGi52Ut35Xbkm+HAu0g+AgHqihcu9HKYboZ yO1PYz5ssszexhgjyGU1Jv4yXETTT9bIsVdl4MkCL/e0+VNtsDb59XoyT2LIGc95 ewpGCR4Y115Mnd6Tt7+572LbXY1fYkxZ3vYGBGNHFuRmkvwsoQjMQhWJvFeUIsQ+ a68vJ6ymDihWNy6W5X09aEaHI7RCkUWGmyWZ4btQUR0CeNveWoXCZPWccqa6NyxU I2mWFffuTIMl0InAJ6xDdqRs8h8lVVu7qZKZTELC+EmFUcqAXpN8z9aezwOQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1767714951; x=1767801351; bh=JoWTQuUPVtQ9Y8rxHFC84rR5XvaR5IvsDBK z+A1DStM=; b=kYGLY3NLbm4+G0jKul3mWw5rAyRSwmJcOtHjJ/EozWzfb9HFzJ6 5qHQkamjLtMl/AQFFfrIF2vuUFmFaPpjmQU8cnxxiQj+NjbG1UplMWFENsk7hYkB DfkozeGJbDyg9msvZiwkfFQpp+P21WBL6s834eUtkDHp8cxXVVLqP0R2N+6ng5gg 5YJeMeb8v4bRvC8c5vDOlkPTeyYjmxCLhVDmDUS/J//fVh+UexEQ+a2rOLEEcIHV /4Vl9ifpw2rm6TIt6o0jbjcQqq+FWMz9loAEqHfGXEEEmVnH8BIwN0I/xJRq/DTR mp5NKMTatGtYBq3WScOeIAc8retdST8MsVg==
X-ME-Sender: <xms:hjBdaWkYCam-eCwR3hxq2IQRXTEkPd8lQauyfWH24duyc5-pGgIU-Q> <xme:hjBdaaKnRHXDmx7qZ7iZMAag0VzM2pri5xuSvUkmKminvB6f4SFbU5m7LGB0LpMr5 3ybKRRU6XWZnvc7t80vUWX65zfUceDqb0M62gwwuoABShuseKAq2lrS>
X-ME-Received: <xmr:hjBdaXb1LbEnHcJ_2369EhoctjQuIKRnqoY4XPNJ493ugtjdC22HuCtTH44G2Fn-8g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgddutddtiedtucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhephffktgggufffjgevvfhfofesrgdtmherhhdtjeenucfhrhhomhepvfgvugcunfgv mhhonhcuoehmvghllhhonhesfhhughhuvgdrtghomheqnecuggftrfgrthhtvghrnhepvd dukeekfefhtdfhudefleeuheeujedvffevkefhgeekvdehvdffueelkedufffhnecuvehl uhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhgvlhhlohhnse hfuhhguhgvrdgtohhmpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuthdp rhgtphhtthhopehvihhkthhorhesughukhhhohhvnhhirdhorhhgpdhrtghpthhtoheplh grshhtqdgtrghllhesihgvthhfrdhorhhg
X-ME-Proxy: <xmx:hjBdacYmdTAZuLWy8-1z074bETLLUze30qq7CRlJNUE9cl8s-3LJEA> <xmx:hjBdaXlciIkdVxGXoac9zhPzOhzG9Qj7i8Qp4jwjT8qRO_fR_GGhSQ> <xmx:hjBdaYxeimcYCTisHpPy21smqclT5V98lUHyT-AVVteBVxP5LPkCUA> <xmx:hjBdaVOHsuGpT8Q4ZTgBAUIt_1CVcsGWA5SWBdEEDF8XRHvmHZ37ZA> <xmx:hzBdaZ7F44WblQZuOu6plNIpmbuO4VEzT2qZuXpq7iH_tBFcGwMozM7N>
Feedback-ID: i1136489e:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 6 Jan 2026 10:55:50 -0500 (EST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <9C97B223-EE6B-4F1A-BF54-944ED3BFC266@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C1E07AFD-3429-48CB-98B2-814F4F55676F"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.1\))
Date: Tue, 06 Jan 2026 16:55:39 +0100
In-Reply-To: <aVyU0_M1VfFPb5nI@chardros.imrryr.org>
To: Viktor Dukhovni <viktor@dukhovni.org>
References: <CAChr6SyXikDcXr+o0igPE_CwEpr0mLY_6VMNS_NwBFFAcNSsag@mail.gmail.com> <CABcZeBM114nod2UOq6-0evpezh-z61BiUR5qLYzmwp9xsB5A7A@mail.gmail.com> <MN2PR17MB4031CF7DAD2806972A950898CD86A@MN2PR17MB4031.namprd17.prod.outlook.com> <aVyU0_M1VfFPb5nI@chardros.imrryr.org>
X-Mailer: Apple Mail (2.3864.400.1)
Message-ID-Hash: EP3PMALMRNM3LCYHDTFE76OQBT4PIBOH
X-Message-ID-Hash: EP3PMALMRNM3LCYHDTFE76OQBT4PIBOH
X-MailFrom: mellon@fugue.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: last-call@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Last-Call] Re: Last Call: <draft-ietf-emailcore-as-26.txt> (Applicability Statement for IETF Core Email Protocols) to Proposed Standard
List-Id: IETF Last Calls <last-call.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/84dyki0-fp_YjB2s2i4akTvMtFM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Owner: <mailto:last-call-owner@ietf.org>
List-Post: <mailto:last-call@ietf.org>
List-Subscribe: <mailto:last-call-join@ietf.org>
List-Unsubscribe: <mailto:last-call-leave@ietf.org>

On 6 Jan 2026, at 05:51, Viktor Dukhovni <viktor@dukhovni.org> wrote:
> Meanwhile, my bank sends me notifications of new outstanding vendor
> bills in cleartext.  I don't choose to reject these notices for lack
> of TLS.

Whether you think this is okay or not, it's actually not a best practice, and I've never seen it done. All of the serious businesses with which I do business send notices that I can go to their web site and authenticate in order to receive communication. I have never received a notice with such private information in it via unencrypted SMTP, and I suspect it would be a violation of EU law. But even when I was living in the U.S., not that long ago, nobody did this. There is a reason why every business has to have a bespoke web-based messaging system, and it is that the IETF has refused to take secure email seriously at any point in the time I've been a participant. It's been proposed and shouted down so many times now that I think most of us have just given up.

But I am with Ekr and others here who have proposed that the document clearly indicate that this is not a best practice. I don't think it should even be allowed, but if it is allowed, it should be as a SHOULD NOT with a clear explanation of why the SHOULD NOT might be ignored and what the implications of doing so are.

I don't know how much can be done at this point—when I brought this up during the WG discussion I was told that this change was not welcome because of the attempt to move to Internet Standard. I think the proposed textual changes that have come up here in the last call are completely reasonable and actually represent current practice, as the google statistics clearly show, and so it should not be an obstacle to moving to Internet Standard. Sites that still don't do STARTTLS are unfortunate exceptions, not standard practice.