Re: [Tools-discuss] IETF Administration LLC staffing update

Lars Eggert <lars@eggert.org> Tue, 08 June 2021 08:10 UTC

Return-Path: <lars@eggert.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 978B53A273D; Tue, 8 Jun 2021 01:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 gmDuUWEFAWEv; Tue, 8 Jun 2021 01:09:59 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7966D3A2742; Tue, 8 Jun 2021 01:09:58 -0700 (PDT)
Received: from smtpclient.apple (unknown [212.68.24.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 7CABF60031C; Tue, 8 Jun 2021 11:09:34 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1623139774; bh=dZbtIieohovCMqiW7FCxlxhV77BJJv6GaD6FVbZYNJU=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=zX4SP7ZRstXmpEuS6qb9NB3yQHOkgLcgvxU15gNNpznm0RQsRUJsdkdUAamShsQJ9 r24KEGbbTjvDuO+iCHtTQlrE6eXP+Gyf8kL1tXk89omyG/rtdzplb+VK86NtV+AKXp E4BQJZVKzD9Nq/mlUzxKCCRZIq7kPgcZTAk28FQ0=
From: Lars Eggert <lars@eggert.org>
Message-Id: <0E6E11C4-8A82-47AB-AEE1-1408C7A3E24D@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_6E3C35EE-1D47-4A2D-AFCC-9E7470D54E3D"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Date: Tue, 08 Jun 2021 11:09:33 +0300
In-Reply-To: <f87a8107-af42-de6f-cba4-7307f4ca158c@nostrum.com>
Cc: Jay Daley <jay@ietf.org>, The IESG <iesg@ietf.org>, Tools Team Discussion <tools-discuss@ietf.org>
To: Adam Roach <adam@nostrum.com>
References: <942b827f-d473-c31d-46e1-c3be8ee66823@nostrum.com> <5B3DE7C5-A10D-42E8-B2DE-624B53C4CA53@ietf.org> <f87a8107-af42-de6f-cba4-7307f4ca158c@nostrum.com>
X-MailScanner-ID: 7CABF60031C.A3822
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/XVMyJC5QprncqHbAQXkmXoKHSn8>
Subject: Re: [Tools-discuss] IETF Administration LLC staffing update
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2021 08:10:04 -0000

Hi,

On 2021-6-8, at 8:21, Adam Roach <adam@nostrum.com> wrote:
> On 6/7/21 23:59, Jay Daley wrote:
>> I’ll leave the IESG to speak for themselves but I will note that this new email address was created with the permission of the IESG. The previous email for our Senior SDE did not have prior permission because I thought there was an agreement to use a specific naming scheme - initialslastname@ietf.org - to avoid any possible future conflicts, but my recollection was off the mark and so this time I specifically sought permission.
> 
> Okay -- this approach of continuing to grant exceptions differs materially and importantly from the conclusion that the IESG seated at IETF 104 reached.

that conclusion doesn't seem to have been minuted - we searched, but couldn't find anything. (I wish it had been.)

> I can see how the current situation would be both frustrating for you and tenuous in general: an ad-hoc system of one-off approvals seems capricious and unsustainable, especially in the face of a steering group that changes composition every year.
> 
> As we all seem to be in agreement that the IESG has authority in this matter, I would implore this IESG to develop a formal position on the topic and write it down, both so that future IESGs have a point of reference for future decisions, and so that the community can be informed of decisions regarding stewardship of the ietf.org domain.

Actually, the current IESG is currently finalizing a policy together with the LLC Board that should go for public comment soon.

Since Lee-Berkeley started before that could happen, we decided to approve lbshaw@ietf.org as her personal email address. This is because she will almost exclusively interact with external individuals who may not have much familiarity with the IETF, and so an @ietf.org email address is therefore very helpful.

Thanks,
Lars