mail-alias-created-date: 1725731591227
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>
Message-ID-Hash: L5GMS76PFCLQFISEVUDHEEDAPUIEPGCA
CC: Process Enthusiasts <procon@ietf.org>
Precedence: list
Subject: =?utf-8?q?=5Bprocon=5D_Re=3A_I-D_Action=3A_draft-eggert-procon-chair-delegat?=
	=?utf-8?q?e-02=2Etxt?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/procon/juc49s8Za3ITbBNdnYeZyyyNM_Q>

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=E2=80=99t =
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:
>=20
> While I philosophically agree, I have two concerns.
>=20
> 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.)
>=20
> 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.    =46rom 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.
>=20
> Yours,
>=20
> Joel
>=20
> 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:
>>=20
>> 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.
>>=20
>> 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?
>>=20
>> Regards/Ng=C4=81 mihi
>>    Brian Carpenter
>>=20
>> On 29-Jun-26 20:52, internet-drafts@ietf.org wrote:
>>> Internet-Draft draft-eggert-procon-chair-delegate-02.txt is now =
available.
>>>=20
>>>     Title:   The IETF Chair May Delegate
>>>     Author:  Lars Eggert
>>>     Name:    draft-eggert-procon-chair-delegate-02.txt
>>>     Pages:   11
>>>     Dates:   2026-06-29
>>>=20
>>> Abstract:
>>>=20
>>>     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.
>>>=20
>>> The IETF datatracker status page for this Internet-Draft is:
>>> https://datatracker.ietf.org/doc/draft-eggert-procon-chair-delegate/
>>>=20
>>> There is also an HTML version available at:
>>> =
https://www.ietf.org/archive/id/draft-eggert-procon-chair-delegate-02.html=
=20
>>>=20
>>> A diff from the previous version is available at:
>>> =
https://author-tools.ietf.org/iddiff?url2=3Ddraft-eggert-procon-chair-dele=
gate-02=20
>>>=20
>>> Internet-Drafts are also available by rsync at:
>>> rsync.ietf.org::internet-drafts
>>>=20
>>>=20
>>> _______________________________________________
>>> 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
>=20
> _______________________________________________
> procon mailing list -- procon@ietf.org
> To unsubscribe send an email to procon-leave@ietf.org