Re: [admin-discuss] Proposed ietf.org email address policy

John Levine <johnl@taugh.com> Fri, 11 June 2021 01:28 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: admin-discuss@ietfa.amsl.com
Delivered-To: admin-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B35A3A2276 for <admin-discuss@ietfa.amsl.com>; Thu, 10 Jun 2021 18:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 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.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=GKoAtZCr; dkim=pass (2048-bit key) header.d=taugh.com header.b=ZU2ywLtM
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U8mZ_c-oXj_o for <admin-discuss@ietfa.amsl.com>; Thu, 10 Jun 2021 18:27:59 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 699CD3A2275 for <admin-discuss@ietf.org>; Thu, 10 Jun 2021 18:27:59 -0700 (PDT)
Received: (qmail 26327 invoked from network); 11 Jun 2021 01:27:57 -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=66d4.60c2bc1d.k2106; bh=krlWAGaFm0IbEZB7KIrf3ZnzEdIzBXc9cLTLXFk8oDU=; b=GKoAtZCrwHV8F202bUUSmMYxjLJCeZqTUbssG3NWcrMsbE9LMcW5l1aEweM+8hwh+p6XtqhILpkBUYlEa5DDv+G2zFYS6AqVTeU0oaJp3nbpsoF8XVEJHjKw4322xop6OhqGvJsW2eNBlrC9cu31WFvD6BTA6GyyeHKbyLDPU1NTtlWwhg8Zm9jcZIDwLGvmHOjQwVPnF5NcdbLTV+258U2REQWl2dghiQJtjyajmS3Pi9c8pHdp2Ie/o/ezM2/sIus1u7F+4rLuMuEpnay4KShy9HOFjUYGiCLV+9fFjuRFGVyIKlDZ7V8WAO8sme5rBgCoz9puoy7gh9j27G3Rmg==
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=66d4.60c2bc1d.k2106; bh=krlWAGaFm0IbEZB7KIrf3ZnzEdIzBXc9cLTLXFk8oDU=; b=ZU2ywLtMC8k3Ws21s/mTyJ4OO9uh+zMAwKrxVOfOKUDZq9KQryjCROFfAoTE1Ra2NxaFr8dFYgY6t9my5wyOyIhCV4ookfHtBCfPljozeUmBCfJOyWNlCuae9JpbHiJk/JNyP7ZJ9Bvs0G0nlpNJ86FuTR20Zq+ZEnguV/L9LFgHBRHY1J3iA7J6sohUjSVa6yV4MPw3SwyKET61SiJ3RH54RcyBanhlrcMDpHMm0h2Otx0ETpSm031KKTCtiSxBlQdhOYOdU/73KVQYcgk4FWfLSe2N/huc3gXTZ8Y6mHKhE7TxqsGM503FEKVQQ2BcoL101V33Nwker6tTrC8/4w==
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.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 11 Jun 2021 01:27:57 -0000
Received: by ary.qy (Postfix, from userid 501) id BE89FEDC972; Thu, 10 Jun 2021 21:27:56 -0400 (EDT)
Date: Thu, 10 Jun 2021 21:27:56 -0400
Message-Id: <20210611012756.BE89FEDC972@ary.qy>
From: John Levine <johnl@taugh.com>
To: admin-discuss@ietf.org
Cc: chair@ietf.org
In-Reply-To: <59562F9B-8DDE-408C-ACCD-BC087FE86E1A@ietf.org>
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/admin-discuss/2WvmUO1I6lED3_xKSNwsBhAh1KU>
Subject: Re: [admin-discuss] Proposed ietf.org email address policy
X-BeenThere: admin-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for IETF LLC administrative issues <admin-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/admin-discuss/>
List-Post: <mailto:admin-discuss@ietf.org>
List-Help: <mailto:admin-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jun 2021 01:28:05 -0000

It appears that IETF Chair  <admin-discuss@ietf.org> said:
>* the IESG must be consulted before any new email addresses under
>  ietf.org are created and will have the sole responsibility for
>  approving and managing addresses under ietf.org
>
>* new individual email addresses for LLC personnel will be allocated
>  under a new staff.ietf.org subdomain, with the LLC being solely
>  responsible for the approval and management of those addresses

I understand the goal here is to make it possible to make bob@ietf.org
be a mailing list, and bob@staff.ietf.org an unrelated person.  That is
a terrible idea.  I can assure you that if you do that, bob the mailing
list will get an endless stream of mail intended for bob the person, and
there is no way to stop it.

I happen to have a Gmail address which is my first and last names. It
gets lots and lots of mail intended for people with names similar to
mine who think that my address is their address. Or maybe they know
their address, it's mrjohnlevine@gmail.com or
johnlevine90210@gmail.com, but whatever it is, people don't hear the
extra part and I get the mail. I tell them it's wrong, they apologize,
and more often than not the mail continues. (There is a pharmacist in
Paris who has given me a standing invitation to drop by the shop due
to all the wrong mail he and his friends and the French government
have sent me.)

For the same reason, no matter how clearly bob@staff.ietf.org tells
people his address, they will send mail to bob@ietf.org.  He will tell
them again, they'll say, oh, right, sorry, and they will send more mail
to bob@ietf.org.

There are about 8 billion seven-character strings we can use as list names,
or 50 billion with embedded digits.  When we're setting up a new list or WG,
we already have to check that it doesn't collide with any of the existing
addresses, and I don't understand why a few more addresses for the collision
check is a problem, or that we will be unable to find a suitable address
among the billions of available strings.

But I am quite sure that moving some of the addresses into a subdomain
will create needless pain because you just can't force people to
remember that. So let's not try.

R's,
John