Re: potable e-mail, now Trying to do too much (was Re: the introduction problem, etc.)

John Levine <johnl@taugh.com> Thu, 19 May 2022 16:49 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78040C1D351A for <ietf@ietfa.amsl.com>; Thu, 19 May 2022 09:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.841
X-Spam-Level:
X-Spam-Status: No, score=-1.841 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=eNLpYGEP; dkim=pass (2048-bit key) header.d=taugh.com header.b=MD9Dt0ud
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 VuFohp-5yLt5 for <ietf@ietfa.amsl.com>; Thu, 19 May 2022 09:49:46 -0700 (PDT)
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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BACCC1D3518 for <ietf@ietf.org>; Thu, 19 May 2022 09:49:46 -0700 (PDT)
Received: (qmail 91041 invoked from network); 19 May 2022 16:49:44 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=1639e.62867528.k2205; bh=uBbW6ArHW7fL1Ss8kxy1c5bWF13xNHK6Wn/J+l7lrpM=; b=eNLpYGEPJlx+Rlcuo8WTymxtt4+MK7JWHkYMH0YBibcSpLNHFDVyPN3P2YmMc+ITzOsxArr0Df7IfAMBuYK0E5CYY01LRUP9zalOjZIrSmnDs5KjFRikNcLb9LwHMZvu1q+K/oK2jpdvFi4LY4G6QDoI0S5XS8gWM34mGwNGdnMpCLNYEmZFVn8TZcMIZmAZ0qsd/cSzY7UnZks8F4FZQa6auovKhSrIouy3LX1KsJCKoVL4LsXC2/pHxmr3n7cB9p4XWzO5WKGj60HD7+eqLlBoYhxHXa8Wx8SL6O5DQKrrVpkoVIdbqsfo2ALaXaG0lcu17eRFpDrSRtU6B7vv1w==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=1639e.62867528.k2205; bh=uBbW6ArHW7fL1Ss8kxy1c5bWF13xNHK6Wn/J+l7lrpM=; b=MD9Dt0udhKLffIHHrPyVL9mQiGjAdg7r50ylmMLLQVyOgAmb/aecJxeqRs4mmnbUSaPcJZBgOIOvSEFItL00+SEWUCcn+MmRv4jQZyRk381cI7WcrXA/t+ZEORhGmm9LO+Ts3GM7QxUU+UVJyx6h6tZWYjpnQNNsi1kY7N5hc8ACp+SGuFn6EJdyMTIkxP5OSr8ReGq2t0mo0M3asu3P8HXOsEeGi5ZLDjEjIGKLMYPbBAGt/fliL677hd5SRbVUcANRE37lXlBD3sYTc67liJX247KR16mQfJDQJ9dhGJehBarY3c6f9GxrdyM8wwDTET3ssSjqJF4Vy8f+mHEdyA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 19 May 2022 16:49:44 -0000
Received: by ary.qy (Postfix, from userid 501) id 3DD824144C1C; Thu, 19 May 2022 12:49:41 -0400 (EDT)
Date: Thu, 19 May 2022 12:49:41 -0400
Message-Id: <20220519164943.3DD824144C1C@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Cc: mcr+ietf@sandelman.ca
Subject: Re: potable e-mail, now Trying to do too much (was Re: the introduction problem, etc.)
In-Reply-To: <711190.1652960694@dooku>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X3YDVoBe52cFuv64IRXnahfCPYM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 May 2022 16:49:51 -0000

It appears that Michael Richardson  <mcr+ietf@sandelman.ca> said:
>Keith Moore <moore@network-heretics.com> wrote:
>    > But even though it's slightly cumbersome and a bit too expensive,
>    > anyone can get their own DNS name, point their MX records at a mail
>    > service provider of their choice, and change those MX records and
>
>No, that's not a portable (phone) email address.
>That's a new phone number.

Um, what?  I'm using the same e-mail in the same domain I registered in 1993
wven though it's gone through a whole lot of different providers in the past
two decades.  Mail domains are extremely portable.

On the other hand, to the limited extent we have portable phone numbers, it's
because you need a government license to connect to the phone system and one
of the conditions for that license is that you make your numbers portable.
RFC 3482 explains number portability, which is similar to a DNS lookup of
the dialled number before routing the call.

Technically it would not be hard to add a per-mailbox DNS lookup to SMTP,
ignoring the detail that no two mail systems agree what a mailbox is.
(Are bobsmith and bob.smith the same mailbox? Are bob and bob+smith
the same?) But unless you plan to license mail systems, there's no
reason for any mail system to do it.

Oh, and phone numbers aren't really portable.  Even though the US and Canada have
the same number formats and the same signalling underneath, if I want to port a US
number to Canada or vice versa, too bad, can't do it.  They're not *that* portable.

R's,
John

PS: On the third hand, I can take my US mobile phone nearly anywhere
in the world and it will work on the local network with my US number
without problems, other than the ridiculous amount US carriers charge
when you do that.