Re: [ietf-smtp] Make username optional in email addresses
Scott Antipa <scottantipa@gmail.com> Fri, 17 February 2023 20:49 UTC
Return-Path: <scottantipa@gmail.com>
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 8FCD3C152564 for <ietf-smtp@ietfa.amsl.com>; Fri, 17 Feb 2023 12:49:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ciHnDrbfptE0 for <ietf-smtp@ietfa.amsl.com>; Fri, 17 Feb 2023 12:49:21 -0800 (PST)
Received: from mail-qv1-xf33.google.com (mail-qv1-xf33.google.com [IPv6:2607:f8b0:4864:20::f33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 E9089C1522D3 for <ietf-smtp@ietf.org>; Fri, 17 Feb 2023 12:49:21 -0800 (PST)
Received: by mail-qv1-xf33.google.com with SMTP id ks14so3013608qvb.11 for <ietf-smtp@ietf.org>; Fri, 17 Feb 2023 12:49:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=QXyNQSlBAvyjJ3xg9iBx6ucK3HECeoEX6rFIPzodWKE=; b=elzsdveqk/xW9vgThNoEXjQJPSsOGpNDZx8gxY/a1hsROa0IISguiRM7zamP04hA18 reSiWwHZqfIzIaLIxPuQ3fjQUdDsrMuC6lw1o/Mzsd97owcVWgy8jnAno/k56zYBjPKj Yw8Rgxv/RAzST4snT7bVdcApMJDSI7OI3P9vK6z3ulThFmdukDKeBw42AE9JBB92ocy9 tsxUlhPDVbS9jcf+z34lDeydMpKLB2MV4AeSPNoCbrwUKMDE4RAKuHCdMORIhdlU30OY aJntbjqN6frwNFBfOpkRdLyX306Ceth/2gzb2JHA9e+rUjSRfvegHtoxJWA4ECf93I1n qvrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=QXyNQSlBAvyjJ3xg9iBx6ucK3HECeoEX6rFIPzodWKE=; b=q1wSBlRsweSfUU8U0M5/gFv/9YXKeqrJVq29Wi+fflEA0Is8MORLIKD8/g5Wob11O9 PTNnmakpUV4fcvs/UNBsdKu//aDuoLkidiBCGA49yGDcBqXC8CQZ0dCkoYZJJ0flr2hF aPVY/KD1RRt+cGw/uw5YXD/ftCt2MkxQvkvhkwwqfpUmJ5Qv30vnNcRkQcVrgnXc0f/O BYaYEpJRhauYrsEoIL/ZhiU8Wr8xVL6bCmfUxX6Owc2AS5JOhEc7nkXJvLRgOTCcgRRm jmtcKutMDJo0fDBRfEX2S2oB2P2Xsj7bx6Djs90Q9Y8GrxqokpSeNEvCceh+on9jaeS/ VsdA==
X-Gm-Message-State: AO0yUKUBlAUnOZuWlYisApHYRydRQHdyEKIKbHk1Kb+g0aAUD0ot5ET3 moTzaFfbhULf8lz6evT/L1wWBgK/gdBm8DZf7/aN+1y7Mzc=
X-Google-Smtp-Source: AK7set8dIYcJV6lUReykHntebmK7ZrGlgPTSSmu27l3igiUoc8FH4A+LpvlvmZITrIJ7n01ZojzRqe/FkVxwr9+MVzo=
X-Received: by 2002:a0c:dc06:0:b0:56f:fe45:9408 with SMTP id s6-20020a0cdc06000000b0056ffe459408mr508868qvk.71.1676666960882; Fri, 17 Feb 2023 12:49:20 -0800 (PST)
MIME-Version: 1.0
References: <CAG6nNWe_7-JN4mzTcsfHBj-cO9qO8twXr+GOg=kiQ8e5XataPA@mail.gmail.com> <480da1fd-864a-ba4b-47b3-082c041ed447@dcrocker.net>
In-Reply-To: <480da1fd-864a-ba4b-47b3-082c041ed447@dcrocker.net>
From: Scott Antipa <scottantipa@gmail.com>
Date: Fri, 17 Feb 2023 12:49:10 -0800
Message-ID: <CAG6nNWcd1XRbyMH_coFv+WtzE_JJ0ntwdcNeyW-u6KuBMkW6bg@mail.gmail.com>
To: dcrocker@bbiw.net
Cc: ietf-smtp@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009c316905f4eb72ce"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/QeuPdM-beLdqxbGhC849rU2Wnos>
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 20:49:25 -0000
Thanks, Dave! Also Eliot Lear sent me the below when I first inquired: > I think something like this may have been tried in the very early days of the internet. Have a look at RFC 1183, and the RP record in DNS. It might be possible to cause a query for that record to be made by a client when no @ is present. But the user interface would have to convert the domain to a real email address at that time, lest too many things break. That @ is expected throughout the architecture. On Fri, Feb 17, 2023 at 12:38 PM Dave Crocker <dhc@dcrocker.net> wrote: > On 2/17/2023 12:26 PM, Scott Antipa wrote: > > As Dave mentioned to me > > To prime the thread a bit more, here's the technical substance of the > note I sent to Scott... > > > -------- Forwarded Message -------- > > > > ... > > > > Less for convenience, and more for the ability to query the DNS for > > person-specific information, there have periodically been suggestions > > for a convention for turning a regular email address into a form that > > can be used to query the DNS. So, for example, permit > > scottantipa.gmail.com as a query for per-user information. Clearly the > > DNS has no problem with that, syntactically. However the consensus > > has been that it wouldn't scale very well. > > > > While the example you gave was for a simple, two-part domain name, the > > construct has to work for any arbitrary domain name. And it has to > > work for potentially billions of users. DNS servers tend not to be > > built to handle the resulting query rate. > > > > A consideration for any proposal is to have a clear and compelling > > value proposition, which is likely to motivate developers, operators > > and users. The barrier is especially high for modifying an existing > > service, because the modification generally needs to work in a way > > that does not affect, or at least does not hurt, that installed base. > > > > What you are proposing needs to cause all email address parsers to > > change. Modifying the entire email infrastructure to support this > > change is unlikely to happen, even with strong incentives -- take a > > look at the decades-long delays that have occurred for DNSSec, DANE, > > and IPv6, each of which has quite a strong value proposition. > > > > While your proposal has the intuitive appeal of a simplification, in > > the example use you gave, the practical benefit of it seems small. > > First, there is likely (almost) no current base of domain owners who > > would benefit from the capability. Even the small market niche of > > technical folk who own domains typically want multiple email addresses > > to work for the domains they own. Then balance this the global, > > systems-level changes that would be needed to support it. > > > > Working through incentives and downsides is a hassle, especially in > > the face of the enthusiasm that comes with thinking up a technical > > proposal. Worse is that it's a realm of guesses about human behavior. > > > > ... > > -- > Dave Crocker > Brandenburg InternetWorking > bbiw.net > mast:@dcrocker@mastodon.social > > _______________________________________________ > ietf-smtp mailing list > ietf-smtp@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-smtp >
- [ietf-smtp] Make username optional in email addre… Scott Antipa
- Re: [ietf-smtp] Make username optional in email a… Dave Crocker
- Re: [ietf-smtp] Make username optional in email a… Scott Antipa
- Re: [ietf-smtp] Make username optional in email a… Russ Allbery
- Re: [ietf-smtp] Make username optional in email a… Dave Crocker
- Re: [ietf-smtp] Make username optional in email a… Russ Allbery
- Re: [ietf-smtp] Make username optional in email a… Dave Crocker
- Re: [ietf-smtp] Make username optional in email a… John C Klensin
- Re: [ietf-smtp] Make username optional in email a… tjw ietf
- Re: [ietf-smtp] Make username optional in email a… Scott Antipa
- Re: [ietf-smtp] Make username optional in email a… John C Klensin
- Re: [ietf-smtp] Make username optional in email a… Nathaniel Borenstein
- Re: [ietf-smtp] Make username optional in email a… Paul Smith
- Re: [ietf-smtp] Make username optional in email a… Scott Antipa
- Re: [ietf-smtp] Make username optional in email a… Valdis Kl ē tnieks
- Re: [ietf-smtp] Make username optional in email a… John C Klensin
- Re: [ietf-smtp] Make username optional in email a… Peter J. Holzer
- Re: [ietf-smtp] Make username optional in email a… Steffen Nurpmeso
- Re: [ietf-smtp] Make username optional in email a… John Levine
- Re: [ietf-smtp] Make username optional in email a… John Levine
- Re: [ietf-smtp] Make username optional in email a… Keith Moore
- Re: [ietf-smtp] Make username optional in email a… Scott Antipa
- Re: [ietf-smtp] Make username optional in email a… Scott Antipa
- Re: [ietf-smtp] Make username optional in email a… Tim Wicinski
- Re: [ietf-smtp] Make username optional in email a… John C Klensin
- Re: [ietf-smtp] Make username optional in email a… Keith Moore
- Re: [ietf-smtp] Make username optional in email a… John Levine
- Re: [ietf-smtp] Make username optional in email a… Paul Smith