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

IETF Chair <chair@ietf.org> Mon, 12 July 2021 19:11 UTC

Return-Path: <chair@ietf.org>
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 60E133A109C for <admin-discuss@ietfa.amsl.com>; Mon, 12 Jul 2021 12:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Hy8xP56rXj8Y; Mon, 12 Jul 2021 12:11:05 -0700 (PDT)
Received: from smtpclient.apple (unknown [85.131.57.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 3E55C3A108E; Mon, 12 Jul 2021 12:11:04 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
From: IETF Chair <chair@ietf.org>
In-Reply-To: <20210611012756.BE89FEDC972@ary.qy>
Date: Mon, 12 Jul 2021 22:11:01 +0300
Cc: admin-discuss@ietf.org, Bob Hinden <bob.hinden@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <21A550AB-5401-43EA-ACC2-5A6608E19465@ietf.org>
References: <20210611012756.BE89FEDC972@ary.qy>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/admin-discuss/aF9Qk9P8jLRAJknEzWEx8U4wc8A>
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: Mon, 12 Jul 2021 19:11:09 -0000

Hi,

back from vacation, sorry for the delay in responding.

On 2021-6-11, at 4:27, John Levine <johnl@taugh.com> wrote:
> 
> 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 was actually not a goal.

One goal of this policy was to not needlessly limit available names under @ietf.org, especially for short names (e.g., "jay", which as someone has pointed out prevents us from having "Jet Another YANG" BOF...)

A second goal was to avoid some confusion about whether someone mailing from an @ietf.org email address was speaking on behalf of the IETF.

That second goal was what motivated a subdomain over a naming scheme (such as "firstname.lastname", which Bob Hinden suggested.) The naming scheme addresses the first goal, but not the second.

I hope this provides some additional background for the proposed policy. I've otherwise seen pretty strong support, so I will take if forward with Jason, possible with some very minor modifications based on suggestions in this thread.

Thanks,
Lars