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

Adam Roach <adam@nostrum.com> Tue, 08 June 2021 05:21 UTC

Return-Path: <adam@nostrum.com>
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 70F843A2205; Mon, 7 Jun 2021 22:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.08
X-Spam-Level:
X-Spam-Status: No, score=-2.08 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, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 yB_mKxqupPZf; Mon, 7 Jun 2021 22:21:32 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 E49D33A2200; Mon, 7 Jun 2021 22:21:31 -0700 (PDT)
Received: from Zephyrus.local ([12.3.79.171]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 1585LS2t018420 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 8 Jun 2021 00:21:29 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1623129689; bh=Uu5ncOeILTzGn++UJgtCb3ebxSrv3RubwMFH1QoieRo=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=Yx9Zki+jzpeYtozbERM96tCskW+fE0D/6cAQjYUfjInVLpmH1E8nEFsueqC3CcpDy EgAMByfVioj4pSOLc4cQRTbuM/KP76dJfF+Fau2uoUkXinrN4ONG26Lpk02Mh57bkm nMJSkjIpAl729naxDRlMOwOHno9bqnEprKRU8/bU=
X-Authentication-Warning: raven.nostrum.com: Host [12.3.79.171] claimed to be Zephyrus.local
To: Jay Daley <jay@ietf.org>
Cc: Tools Team Discussion <tools-discuss@ietf.org>, The IESG <iesg@ietf.org>
References: <942b827f-d473-c31d-46e1-c3be8ee66823@nostrum.com> <5B3DE7C5-A10D-42E8-B2DE-624B53C4CA53@ietf.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <f87a8107-af42-de6f-cba4-7307f4ca158c@nostrum.com>
Date: Mon, 07 Jun 2021 22:21:28 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <5B3DE7C5-A10D-42E8-B2DE-624B53C4CA53@ietf.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/8w7QRXKSMVeVkghYE-kHqspoXOU>
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 05:21:38 -0000

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. 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.

/a