Re: [Gendispatch] I-D Action: draft-eggert-ietf-and-trust-00.txt

Glenn Deen <rgd.ietf@gmail.com> Mon, 24 October 2022 14:55 UTC

Return-Path: <rgd.ietf@gmail.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBF4DC1522B4 for <gendispatch@ietfa.amsl.com>; Mon, 24 Oct 2022 07:55:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 xsMEzbuWQE3O for <gendispatch@ietfa.amsl.com>; Mon, 24 Oct 2022 07:55:19 -0700 (PDT)
Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 3BB1BC1522B0 for <gendispatch@ietf.org>; Mon, 24 Oct 2022 07:55:19 -0700 (PDT)
Received: by mail-pj1-x1034.google.com with SMTP id m6-20020a17090a5a4600b00212f8dffec9so3631209pji.0 for <gendispatch@ietf.org>; Mon, 24 Oct 2022 07:55:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:date:message-id:subject:mime-version:from:from:to:cc:subject :date:message-id:reply-to; bh=Pdx5aI0x+h6qW7tpwnd/R0tKvuapj7rKPbcfXzu8wrY=; b=mqbWFqNvZpWVZ4oxbDWS0ofn0DY9mFJY0v09tA8NVaMVhBmAZnftcZeECzka/nPzbe pw6jhesMNQqHSl10OQCcYXU0RuRjhN4lOWvZGaLqGDMsJMolEEN2B1qRpRbVcWTEqDKX f+PyOloTDlRu6ClzJkT2hQLX28/bLOSOqQoyxKGYdNwuAGmiq3P5wqtU4nN7yAo1gU3o c1I7t3tlZrt/8s1mPPn2fZVxVXE+0cjFzJ6wrA7xPC/shJZKyS2XA76VuAC6+vlhqezJ npWq6vFgwrCvOvk7BYrUbi2T83wWb0adj0TR2iRFzcpcUy7wan5pMiUeapwqxAh7Ro37 rlIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:date:message-id:subject:mime-version:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Pdx5aI0x+h6qW7tpwnd/R0tKvuapj7rKPbcfXzu8wrY=; b=DboKPiLnruUjuNIOo5ZlpMYbgZUFxLZ6xhcYIHgXV6vVG1CQtouNVGiSIz13/W6PHy ZSYR++02kTYfO9YAkXrzQpJF5ugXjj5dIV/T6kYzXWpg7ozfKXYrwoaj0v/ibUtDnKM7 FtDCjUuWq6TB+LWdU6bZK7y7/DLWE4fjwlT7fpuyN9+pQm7xns7fTdq8ys4x0iGptyhE +0gIuCdGxnjEPzRlF0zfGxEt9W8GktL/sAHsSR3jIRO80eIFtdAOnbuCcOLAsCm5JlwY 59kmZ//Q/tJh88f+TeYw8CsYqEArCwT+rej68vzqKsnTz8axfxSSpgdlse+JDq7lxedP YY1A==
X-Gm-Message-State: ACrzQf2gKJX9qipkDqGdGrv6p1cSeVSxJsK/pM/5VBhDGaAPc2aGQNmw 0t43a/eOTlA2D518a3EpX0TKq0Y4yoVfXA==
X-Google-Smtp-Source: AMsMyM6snq9mWrgXwhX+hQE4Uh0+hWxYBtIUdOBDBtapw0MpXRtfpaekW7r0FYYM5lMVab6Nq4fQHg==
X-Received: by 2002:a17:90b:4c0b:b0:20d:8572:ab27 with SMTP id na11-20020a17090b4c0b00b0020d8572ab27mr38655197pjb.193.1666623317991; Mon, 24 Oct 2022 07:55:17 -0700 (PDT)
Received: from smtpclient.apple (2603-8001-3503-2ff9-70a7-3bed-2a46-f010.res6.spectrum.com. [2603:8001:3503:2ff9:70a7:3bed:2a46:f010]) by smtp.gmail.com with ESMTPSA id w15-20020a1709029a8f00b001865e69b4d7sm3212654plp.264.2022.10.24.07.55.17 for <gendispatch@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Oct 2022 07:55:17 -0700 (PDT)
From: Glenn Deen <rgd.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7CDC0002-896F-41A4-9541-B20294E8174F"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Message-Id: <A016333A-A311-4F79-AC5A-79201B71E7B9@gmail.com>
Date: Mon, 24 Oct 2022 07:55:15 -0700
To: gendispatch@ietf.org
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/UBFVPDPi4xagJ3oUdNz8OuWVtvE>
Subject: Re: [Gendispatch] I-D Action: draft-eggert-ietf-and-trust-00.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2022 14:55:23 -0000

"Salz, Rich" <rsalz@akamai.com> Fri, 21 October 2022 21:28 UTCShow header <https://mailarchive.ietf.org/arch/msg/gendispatch/5X0pXN92vzdDcz4xQ9eZsn3JBwQ/#>
>>   I can't find anything in this draft that I disagree with. However, I can't really see why it's needed as a BCP, since it doesn't seem to >> me that it changes anything. I'd be happy to see this material on the Trust's web site as FYI.

> Well, for example, suppose the Trust decides that their annual presentation at an IETF Plenary is good enough.  Then what?
I would like to clarify the current Trust’s cadence of presenting at the IETF Plenaries.     
The Trust has long followed the principle that the Trust will present NO-LESS than annually at IETF Plenaries, this is a requirement built into the legal foundation documents of the IETF Trust.  
At least for my time on Trust (since 2019) Trustees have also followed the principle that it will present more frequently if there is something to present about.        
Following that, the Trust has presented at recent IETF plenaries at IETF 104,107,110,113,114 and will presenting at IETF115 to update the community on the restricting project and other topics.   
While we’re on the topic - the IETF Trust uses its web site to publish other updates including monthly financials.  You can also find general bigger events reported on https://trustee.ietf.org/about/announcements/ <https://trustee.ietf.org/about/announcements/>.    

> I think there are other examples of what the community expects, and (a) that should be reviewed by the community; and (b) perhaps decide  what to do if the Trust says “nope”
Ultimately the Trustees serve at the pleasure of their respective appointing bodies (1 from IESG, 3 from IETF noncom, and 1 from ISOC BoT) and there exist procedures for appointing bodies to replace their appointees to the Trust.  If some future Trustees were to act in ways that went against the community then I would image they would be replaced with Trustees who would listen to community consensus. 
-Glenn Deen, current IETF Trustee