Re: [ietf-smtp] Make username optional in email addresses

Russ Allbery <eagle@eyrie.org> Fri, 17 February 2023 22:11 UTC

Return-Path: <eagle@eyrie.org>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8BEC1524DE for <ietf-smtp@ietfa.amsl.com>; Fri, 17 Feb 2023 14:11:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TNhw-Kfif1n4 for <ietf-smtp@ietfa.amsl.com>; Fri, 17 Feb 2023 14:11:50 -0800 (PST)
Received: from haven.eyrie.org (haven.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3539]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47856C14F5E0 for <ietf-smtp@ietf.org>; Fri, 17 Feb 2023 14:11:49 -0800 (PST)
Received: from lothlorien.eyrie.org (96-90-234-101-static.hfc.comcastbusiness.net [96.90.234.101]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by haven.eyrie.org (Postfix) with ESMTPS id 1C3BC1182DC; Fri, 17 Feb 2023 14:11:48 -0800 (PST)
Received: by lothlorien.eyrie.org (Postfix, from userid 1000) id 96E44B44F6B; Fri, 17 Feb 2023 14:11:46 -0800 (PST)
From: Russ Allbery <eagle@eyrie.org>
To: Dave Crocker <dhc@dcrocker.net>
Cc: Scott Antipa <scottantipa@gmail.com>, dcrocker@bbiw.net, ietf-smtp@ietf.org
In-Reply-To: <fd84d2c9-e15d-111d-7bc0-cfa6c6a3ccc6@dcrocker.net> (Dave Crocker's message of "Fri, 17 Feb 2023 13:55:01 -0800")
Organization: The Eyrie
References: <CAG6nNWe_7-JN4mzTcsfHBj-cO9qO8twXr+GOg=kiQ8e5XataPA@mail.gmail.com> <87mt5cezkb.fsf@hope.eyrie.org> <fd84d2c9-e15d-111d-7bc0-cfa6c6a3ccc6@dcrocker.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Date: Fri, 17 Feb 2023 14:11:46 -0800
Message-ID: <87h6vkeycd.fsf@hope.eyrie.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/aiL-hFXp0x8W1Jzv-ZN0NPJhRx4>
Subject: Re: [ietf-smtp] Make username optional in email addresses
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2023 22:11:54 -0000

Dave Crocker <dhc@dcrocker.net> writes:
> On 2/17/2023 1:45 PM, Russ Allbery wrote:

>> I think a comparable change would be MIME, which introduced structured
>> email and non-ASCII character sets, and that change took decades to be
>> reliably usable

> MIME is a likely guess for comparison, but it's actually fundamentally
> different.  It did not touch the infrastructure. MIME is a pure
> value-add function that rides on top of the existing email handling and
> content standards.  In terms of pure computer science, it is arguably
> ugly but in terms of demonstrating how to upgrade a global system, it's
> been astonishingly effective engineering.

I completely agree, and indeed that was the point of the rest of the
paragraph that you didn't quote.  :)  But I probably didn't make that
clear enough.

> And while I don't have measurements, I think it became useful far more
> quickly than decades.

Also agreed, but the term I used was "reliably useful" not just "useful."
What I was trying to get at, without enough elaboration, is that it takes
a really long time to upgrade enough software for a new feature to become
something people can *rely* on working, particularly with a stranger with
no prior negotiation.

That's relevant in the choice in, say, whether you feel comfortable giving
out a domain name as your email address and being confident any email
sender you care about will use it.  And providing your email address to
people who don't already have it feels like the compelling use case of
this feature.

(That said, email is a lot more centralized these days, and if Gmail and
Outlook both implement something, you get a lot of coverage very, very
quickly.  I'm not sure they would be interested in this feature, though.)

-- 
Russ Allbery (eagle@eyrie.org)             <https://www.eyrie.org/~eagle/>