[procon] Re: I-D Action: draft-eggert-procon-chair-delegate-02.txt

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Tue, 30 June 2026 14:47 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: procon@mail2.ietf.org
Delivered-To: procon@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D08A710ADA89F for <procon@mail2.ietf.org>; Tue, 30 Jun 2026 07:47:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782830835; bh=/NTaWWljKzYFjbsl5ZU/B3NlS7GcDenpSXYBWRt5Hio=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=ryQ94X45p0j5uKtm0QaJ+Qrjves52cR9xoi+njRvAO819hXbQpBDWjjAiNrpQXvtN aUpkk5KP4ok/oRzPfLeS9ZtarGCB+rt0qJo+ZifUuqKj04H4cWZVK+mNEH6mNtxizc p91dblwHnovuQfQCsKPwtB4/tY6VgU2IEkTLCkVA=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=kuehlewind.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PjRVukbMMgwR for <procon@mail2.ietf.org>; Tue, 30 Jun 2026 07:47:15 -0700 (PDT)
Received: from outbound.st.icloud.com (p-east2-cluster6-host10-snip4-4.eps.apple.com [57.103.76.205]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 645CE10ADA6EC for <procon@ietf.org>; Tue, 30 Jun 2026 07:45:12 -0700 (PDT)
Received: from outbound.st.icloud.com (unknown [127.0.0.2]) by p00-icloudmta-asmtp-us-east-1a-100-percent-9 (Postfix) with ESMTPS id D8F3B1800136; Tue, 30 Jun 2026 14:45:05 +0000 (UTC)
X-ICL-RepId: 019f18fd-aca4-70ac-9237-960c51be62da
X-ICL-Out-Info: HUtFAUMHWwJACUgATUQeDx5WFlZNRAJCTQBLHV8EXRxED1YHWRcOVk1QHUcLdwBHFVEUVhpeBVZeVx1HTVEPDxtMHVsBUhxbHl1WXQhDS0ATBEoTBVIHXU1WDUcPWB5cFBcLR0NeCF4fTBwdDlgGEgBNCg42BlkFXglWA0MFNhIUXUVYGFIDXhVOEV0JGQVXBBkVWgkKVwNFD013X3RTH0Z4OQZAA1N0RBQ5Ay8ORnRIADoKKw8qBEIMPXMGQg5aHFwPWgNTRVwVTUYTGU4bV01aDUAZWAZtFFYVUgRZ
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kuehlewind.net; s=sig1; t=1782830706; x=1785422706; bh=mg4VvK7hdLp2ZWYUc8hQXCM/o46olanmZbMyOzWY3FQ=; h=Content-Type:Mime-Version:Subject:From:Date:Message-Id:To:x-icloud-hme; b=3DF89wItfMbbkyc0iJ7L8bxbVvY9iCsTfPtnRqOqaIXBnSutTjDEz7l4EyhHTdvJbKog0rChYdIMGJmwTCSn96QXn/EP6Qqvz0Ws0BUAyLw1B8oK/5K8X6ogHzeuJmof+ZO7y7cCAcdpeqs6s/mOvqEZsE+LunVkQ1zrvnmkDAnBj7lA8/2OvkvckSP7+4iXUi3ZlGuHzakDfIVm7XflmTGbUQji5GZO2MTpaMhQ39YI6PcnOv/TL2/fzbxZLlafpZ82T3WNqreu8wxawE7SvEyNDEAKnigrJtJtm1A7a/HHTtoKcJuoazAcu4E/IttJLWvnbh3GJWA2HYplN1Yp1Q==
mail-alias-created-date: 1725731591227
Received: from smtpclient.apple (unknown [17.42.251.67]) by p00-icloudmta-asmtp-us-east-1a-100-percent-9 (Postfix) with ESMTPSA id 0D4F41800193; Tue, 30 Jun 2026 14:45:04 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <a5fd6ac2-ec14-46bf-ac02-60544a46aa44@joelhalpern.com>
Date: Tue, 30 Jun 2026 16:44:52 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1565D2C8-6AA5-48F4-A0B9-F89B9F8A625E@kuehlewind.net>
References: <178272312952.2114666.8663062125812559312@dt-datatracker-f9b87776f-8pmmg> <8446827b-7343-41fe-be65-d9ed0d03561f@gmail.com> <a5fd6ac2-ec14-46bf-ac02-60544a46aa44@joelhalpern.com>
To: Joel Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3776.700.51.11.1)
X-Proofpoint-GUID: WP4EzwKokwoPJ6B9Wh7aW8X8YMmCMmHF
X-Proofpoint-ORIG-GUID: WP4EzwKokwoPJ6B9Wh7aW8X8YMmCMmHF
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwNjMwMDEzOSBTYWx0ZWRfX5kyB1lRaDwXk YRj+iOJ7d6c1ei9i9/uF9m30o+aDsEHvbUOca0geBvAre7T3JzaGVbF4n6uaj8u7wRPmOREU1/M k1eDgG9tbXIz1Ysa/e20WQwVhxqTfeiA0rKHcWR/SRvEP87NuXg/97aYPrwPd6IRJAiv3ksQhrB 4QqsINFVlIi1IMQGPu1pZH1nwMOyLwJZdchaR1Wj0o4hcoFH5NVvUYdZP37D9+l4ztSMqWcsKpq Ddtn7HOiSwoFr1d3zi9GUIGmAMR66SGKlX8jVohxjFOvqceX5zXcPMfqdF5EhBTY7bntnYAibdg 5rOF8seTOXcNxHwoUwk
Message-ID-Hash: L5GMS76PFCLQFISEVUDHEEDAPUIEPGCA
X-Message-ID-Hash: L5GMS76PFCLQFISEVUDHEEDAPUIEPGCA
X-MailFrom: ietf@kuehlewind.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Process Enthusiasts <procon@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [procon] Re: I-D Action: draft-eggert-procon-chair-delegate-02.txt
List-Id: "Discussion of consolidating process documents and changes to the standards process per IETF 121 ALLDISPATCH." <procon.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/procon/juc49s8Za3ITbBNdnYeZyyyNM_Q>
List-Archive: <https://mailarchive.ietf.org/arch/browse/procon>
List-Help: <mailto:procon-request@ietf.org?subject=help>
List-Owner: <mailto:procon-owner@ietf.org>
List-Post: <mailto:procon@ietf.org>
List-Subscribe: <mailto:procon-join@ietf.org>
List-Unsubscribe: <mailto:procon-leave@ietf.org>

Hi Joel, hi all,

I agree about the IAB part and have raised this at the mic at some point but probably should have opened an issue as well. In the IAB charter RFC2850, the IETF Chair is called out as a member of the IAB and this is not just a role or responsibility that can be delegated. Similar as any IAB member cannot delegate its membership to someone else; especially any voting rights cannot be delegated. However, I also don’t think there is a need for delegation here. There is also the liaison from the IESG to the IAB; so there is also a second link between the groups. And similar as IAB members are potentially less active for some periods of time, it is also not a real problem if the IETF Chair would not be able to actively participate in IAB activities for a while; again the membership, however, remains, no matter if someone is actively contributing or not.

Mirja



> On 30. Jun 2026, at 16:22, Joel Halpern <jmh@joelhalpern.com> wrote:
> 
> While I philosophically agree, I have two concerns.
> 
> One concern is probably unfixable, and we just live with it.  In principle, the person appointed by the nomcom could delegate all of their day-to-day responsibility to other ADs.  Without having told the nomcom that they intended to do that.  I consider that undesirable.  The fixable aspect of this is probably just to note that the nomcom can ask IETF chair candidates what parts of the job they intend to delegate so the nomcom knows which parts of the job they are choosing a person to do, and which parts of the job they are choosing a person to choose a person for.  (Those are different skills.)
> 
> The other piece is that I am concerned about the delegation of the IAB participation.  The delegation of the LLC participation is called out in the LLC documents.   I don't think it is up to the IESG without explicit confirmation from the IAB to change the IAB participation.  I think that delegation someone needs to be signed off on by the IAB.    From where I sit, that delegation could use some better explanation of what properties the IETF Chair should look for in a person when they delegate that role.  My own read is that the IETF Chair inclusion is not merely to ensure close communication (the laiison in each direction already can do that) but to provide a particularly broad view of IETF operations and activities that may otherwise be lacking.  However, that is a guess since I don't think it is spelled out in the existing documents and is not not spelled out here.
> 
> Yours,
> 
> Joel
> 
> On 6/29/2026 11:55 PM, Brian E Carpenter wrote:
>> I support clarifying the IETF Chair's power to delegate. Personally I'd
>> enable it by a much more general provision. Something like:
>> 
>> The Chair may delegate any specific part of their role to another AD,
>> unless specifically disallowed by a BCP. Delegations must be for a
>> specific period of time and must be announced. However, ultimate
>> responsibility remains with the Chair.
>> 
>> That said, I agree with the draft, because it really amounts to exactly
>> that. It just seems that there's a lot of detail that most readers will
>> not care about. Maybe the main text could be rather short, with the details
>> in an Appendix?
>> 
>> Regards/Ngā mihi
>>    Brian Carpenter
>> 
>> On 29-Jun-26 20:52, internet-drafts@ietf.org wrote:
>>> Internet-Draft draft-eggert-procon-chair-delegate-02.txt is now available.
>>> 
>>>     Title:   The IETF Chair May Delegate
>>>     Author:  Lars Eggert
>>>     Name:    draft-eggert-procon-chair-delegate-02.txt
>>>     Pages:   11
>>>     Dates:   2026-06-29
>>> 
>>> Abstract:
>>> 
>>>     This document affirms that the IETF Chair may delegate some of their
>>>     responsibilities to other Area Directors, and updates several
>>>     existing RFCs to enable that.
>>> 
>>> The IETF datatracker status page for this Internet-Draft is:
>>> https://datatracker.ietf.org/doc/draft-eggert-procon-chair-delegate/
>>> 
>>> There is also an HTML version available at:
>>> https://www.ietf.org/archive/id/draft-eggert-procon-chair-delegate-02.html 
>>> 
>>> A diff from the previous version is available at:
>>> https://author-tools.ietf.org/iddiff?url2=draft-eggert-procon-chair-delegate-02 
>>> 
>>> Internet-Drafts are also available by rsync at:
>>> rsync.ietf.org::internet-drafts
>>> 
>>> 
>>> _______________________________________________
>>> I-D-Announce mailing list -- i-d-announce@ietf.org
>>> To unsubscribe send an email to i-d-announce-leave@ietf.org
>> _______________________________________________
>> procon mailing list -- procon@ietf.org
>> To unsubscribe send an email to procon-leave@ietf.org
> 
> _______________________________________________
> procon mailing list -- procon@ietf.org
> To unsubscribe send an email to procon-leave@ietf.org