Re: Proposal for a Joint Statement on Structural Separation of Secretariat Delegations
Joel Halpern <jmh@joelhalpern.com> Fri, 30 October 2026 20:14 UTC
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 17AF046 for <ietf@ietf.org>; Fri, 30 Oct 2026 20:14:04 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=joelhalpern.com header.s=2.tigertech header.b=QNDXOCTu; spf=pass (mx.ietf.org: domain of jmh@joelhalpern.com designates 208.80.4.152 as permitted sender) smtp.mailfrom=jmh@joelhalpern.com; dmarc=pass (policy=none) header.from=joelhalpern.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1793391243; bh=6v5ZuqgrhWhkUj9YqYzuMPeL06PlVPTMo4ZOW8qBMhc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=QNDXOCTuQFEtqRReqVR5Sn5MbWl1ghHrDPOT/66oxW0HnYlUs0nRXooeCjcVheINS Z4Rk7T1vEtJK11Dl9OOUZfS/aMyfFRW1jEQ6nTra8EXm6VTz2a097fAEYfMzpjuDlF B5eVn/I5mMjvMrRqILlF+kpIrBELcd1RilPWSaok=
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4jGXP71mXPz6LBvj; Fri, 30 Oct 2026 13:14:03 -0700 (PDT)
X-Quarantine-ID: <5LvZ7XIR1A8S>
X-Virus-Scanned: Debian amavis at a2.tigertech.net
Received: from [192.168.0.109] (ip68-100-242-223.dc.dc.cox.net [68.100.242.223]) (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 maila2.tigertech.net (Postfix) with ESMTPSA id 4jGXP473tPz6G7xD; Fri, 30 Oct 2026 13:14:00 -0700 (PDT)
Message-ID: <99ef2036-5e8e-4036-b813-cfc45d1a0e50@joelhalpern.com>
Date: Fri, 30 Oct 2026 16:13:58 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Proposal for a Joint Statement on Structural Separation of Secretariat Delegations
To: "Scott O. Bradner" <sob@sobco.com>, Timo Gerke <ietf@timogerke.de>
References: <69ffffed-2242-43ef-ac86-56a46feb25ee@timogerke.de> <34908135-11a7-453f-82bc-8bb1f64820b9@timogerke.de> <92D16C31-58B7-4CBF-B771-E60913DAF150@sobco.com>
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <92D16C31-58B7-4CBF-B771-E60913DAF150@sobco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Spamd-Bar: ------------------------
Message-ID-Hash: JEACGFRB44G3JBTOLK6N6B7TK6TPEGA7
X-Message-ID-Hash: JEACGFRB44G3JBTOLK6N6B7TK6TPEGA7
X-MailFrom: jmh@joelhalpern.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ietf.ietf.org-0; header-match-ietf.ietf.org-1; header-match-ietf.ietf.org-2; header-match-ietf.ietf.org-3; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ietf@ietf.org
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MnZMW3ggE77H9TrVDzQgGftXxKc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>
I have a different question. This appears to be about the Secretariat staff who while employeed by AMS have their actual work directed by the IETF LLC (via the Executive Director and his reports.) Is this a matter of the LLC asking the IESG and IAB to confirm a policy decision that is in their remit and their operational control, or is there something more complicated here? Thank you, Joel PS: I suspect that answering Scott's first question below would also answer my question. On 10/30/2026 3:59 PM, Scott O. Bradner wrote: > 1/ what problem is being solved by this proposal? > 2/ what would be the cost to implement the proposal? > > Scott > >> On Oct 30, 2026, at 3:37 PM, Timo Gerke <ietf@timogerke.de> wrote: >> >> Dear IETF Community, >> >> For the sake of transparency and procedural integrity regarding the >> checks and balances between our collective bodies, I am sharing a >> governance proposal originally submitted directly to the IAB and the >> IESG on July 19, 2026. >> >> As this architectural query regarding the mandatory separation of >> Secretariat delegations between the IAB, IESG, RPAT, and RSAB has >> remained completely unaddressed by both collective bodies for over three >> months, it is now evident that this matter requires open community >> review to safeguard our institutional framework. >> >> Please find the original proposal below for public evaluation and >> discussion. >> >> Sincerely, >> Timo Gerke >> >> -- Forwarded Message -- >> Date: July 19, 2026 16:24 +0200 >> Message-ID: <69ffffed-2242-43ef-ac86-56a46feb25ee@timogerke.de> >> Subject: Proposal for a Joint Statement on Structural Separation of Secretariat Delegations >> From: Timo Gerke <ietf@timogerke.de> >> To: Internet Engineering Steering Group <iesg@ietf.org>, Internet Arichitecture Board <iab@iab.org> >> >> >> Dear IAB and IESG members, >> >> The Internet Architecture Board and the Internet Engineering >> Steering Group MAY consider issuing a Joint Statement limiting >> the delegation of IETF Secretariat employees to a maximum of two >> of the following collective bodies: >> >> - Internet Architecture Board >> - Internet Engineering Steering Group >> - RFC Series Production Advisory Team >> - RFC Series Approval Board >> >> Furthermore, the delegated IETF Secretariat employees MUST NOT be >> delegated to the IAB and the IESG simultaneously. >> >> It SHOULD even be considered that Secretariat employees MUST NOT >> be delegated to the RPAT and the RSAB simultaneously. >> >> Yours sincerley, >> >> Timo Gerke >> >> -- >> Timo Gerke >> Hamburg, Germany >> >> "If you think technology can solve your security >> problems then you don't understand the problems >> and you don't understand the technology." >> -- Bruce Schneier >> <OpenPGP_0x9F03DF9F597BF31E.asc>_______________________________________________ >> ietf mailing list -- ietf@ietf.org >> To unsubscribe send an email to ietf-leave@ietf.org > _______________________________________________ > ietf mailing list -- ietf@ietf.org > To unsubscribe send an email to ietf-leave@ietf.org
- Fwd: Proposal for a Joint Statement on Structural… Timo Gerke
- Re: Proposal for a Joint Statement on Structural … Scott O. Bradner
- Re: Proposal for a Joint Statement on Structural … Joel Halpern
- Re: Proposal for a Joint Statement on Structural … Salz, Rich
- Re: Proposal for a Joint Statement on Structural … Joel Halpern
- Re: Proposal for a Joint Statement on Structural … Timo Gerke
- Re: Proposal for a Joint Statement on Structural … Job Snijders
- Re: Proposal for a Joint Statement on Structural … Timo Gerke
- Re: Proposal for a Joint Statement on Structural … Nathanael Ritz
- Re: Proposal for a Joint Statement on Structural … George Michaelson
- AI translations [Re: Proposal for a Joint Stateme… Brian E Carpenter
- Re: Proposal for a Joint Statement on Structural … Salz, Rich
- Re: Proposal for a Joint Statement on Structural … John C Klensin
- Re: Proposal for a Joint Statement on Structural … Nick Hilliard
- Re: Proposal for a Joint Statement on Structural … Nick Hilliard
- Re: Fwd: Proposal for a Joint Statement on Struct… Brian E Carpenter
- Re: Fwd: Proposal for a Joint Statement on Struct… Timo Gerke
- Re: Fwd: Proposal for a Joint Statement on Struct… S Moonesamy
- Re: Proposal for a Joint Statement on Structural … Paul Wouters
- Re: Proposal for a Joint Statement on Structural … Warren Kumari
- Re: Fwd: Proposal for a Joint Statement on Struct… Brian E Carpenter
- Re: Proposal for a Joint Statement on Structural … Pete Resnick
- Re: Proposal for a Joint Statement on Structural … Brian E Carpenter