IETF Logo Mail Archive

Re: [admin-discuss] Attempt to diagram the structure of the IETF - IETF Trust

"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 20 February 2022 23:38 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: admin-discuss@ietfa.amsl.com
Delivered-To: admin-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2426D3A0124; Sun, 20 Feb 2022 15:38:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 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.714, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 7wtvpwRLHgHA; Sun, 20 Feb 2022 15:38:33 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DAA23A00AE; Sun, 20 Feb 2022 15:38:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4K221j0R1Zz1pMPW; Sun, 20 Feb 2022 15:38:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1645400313; bh=NhrcFZXcZ38Wk/Apv2EWjPEnPX8Qkv6buG3X0Sa7JbM=; h=Date:Subject:To:References:From:In-Reply-To:From; b=IQaJKfFCsO8fRrXLFgoSiDRrvRma15I7K8YSznZoX9+T+62uN63X/4Sh/gbnNNIJ6 w87StfRtLwhIlz5tq/r2SBqKvjazaM2JfHbK0HpzvyO4ENGHFlGyaKcI4MIbgRhJfP I+kbDGD0J4GHJxma4a1r+KARqwPHrhDQAAX9PSAs=
X-Quarantine-ID: <gBOnc_bZl39W>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.22.111] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4K221h48ZYz1nw5j; Sun, 20 Feb 2022 15:38:32 -0800 (PST)
Message-ID: <15b0d719-7c61-6426-4c6c-6bde8554b3ec@joelhalpern.com>
Date: Sun, 20 Feb 2022 18:38:31 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: Jay Daley <exec-director@ietf.org>, admin-discuss@ietf.org
References: <12F3A997-DF48-4AA1-B744-8D310D460397@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <12F3A997-DF48-4AA1-B744-8D310D460397@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/admin-discuss/fnDfribdvuZGAOESkotMXGUqzQ4>
Subject: Re: [admin-discuss] Attempt to diagram the structure of the IETF - IETF Trust
X-BeenThere: admin-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for IETF LLC administrative issues <admin-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/admin-discuss/>
List-Post: <mailto:admin-discuss@ietf.org>
List-Help: <mailto:admin-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Feb 2022 23:38:38 -0000

If you are going to point out that multiple parties appoint members of 
the LLC Board, then you should note that the ISOC board appoints one 
Trustee, and the IESG appoints one Trustee.

Yours,
Joel

On 2/20/2022 6:24 PM, Jay Daley wrote:
> I’ve had a go at diagramming the structure of the IETF and inter-related organisations to assist new staff and contractors:
> 
> 	https://www.ietf.org/media/documents/IETF_Structure_-_February_2022.png
> 
> While the RSWG/RSAB are not officially approved, they are included.
> 
> Any feedback most welcome.
> 
> cheers
> Jay
>

v2.8.7 | Report a Bug | By Email