Re: [admin-discuss] Attempt to diagram the structure of the IETF
Jay Daley <exec-director@ietf.org> Tue, 22 February 2022 22:37 UTC
Return-Path: <exec-director@ietf.org>
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 772023A0958
for <admin-discuss@ietfa.amsl.com>; Tue, 22 Feb 2022 14:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001,
URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 K17CztaZG3TM for <admin-discuss@ietfa.amsl.com>;
Tue, 22 Feb 2022 14:37:02 -0800 (PST)
Received: from ietfx.ietf.org (ietfx.amsl.com [4.31.198.45])
(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id C61B93A095C
for <admin-discuss@ietf.org>; Tue, 22 Feb 2022 14:37:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
by ietfx.amsl.com (Postfix) with ESMTP id AB9CD409278F;
Tue, 22 Feb 2022 14:37:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.ietf.org ([4.31.198.45])
by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id qPFvuaNQVYFV; Tue, 22 Feb 2022 14:37:02 -0800 (PST)
Received: from smtpclient.apple (unknown [158.140.230.105])
by ietfx.amsl.com (Postfix) with ESMTPSA id 295D6409277C;
Tue, 22 Feb 2022 14:37:02 -0800 (PST)
Content-Type: multipart/signed;
boundary="Apple-Mail=_0F73216F-C310-4267-875C-81EBB360EAD7";
protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <6473d6d2-0cac-35c7-3ff0-982989f29aec@cs.tcd.ie>
Date: Wed, 23 Feb 2022 11:36:56 +1300
Cc: admin-discuss@ietf.org
Message-Id: <E065500E-2B48-452C-ACAB-152CA9A02F0D@ietf.org>
References: <12F3A997-DF48-4AA1-B744-8D310D460397@ietf.org>
<0F630F4E-7646-4885-B31D-A16805B776CA@gmail.com>
<2FA08C30-2D8D-4F2A-9B40-A865654B54E0@ietf.org>
<49BE4C0D-87F7-4B5B-8342-789E678F0238@gmail.com>
<BE917FFB-E149-4712-90B7-3EC356AF60B0@ietf.org>
<6473d6d2-0cac-35c7-3ff0-982989f29aec@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/admin-discuss/vQqUww6CcYKGmv950jQcp98zFqo>
Subject: Re: [admin-discuss] Attempt to diagram the structure of the IETF
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: Tue, 22 Feb 2022 22:37:08 -0000
> On 22/02/2022, at 7:27 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: > > Signed PGP part > > Hiya, > > I do think this effort is worthy and useful. That said... > > On 22/02/2022 03:17, Jay Daley wrote: >> https://www.ietf.org/media/documents/IETF_Structure_-_February_2022.png > > One comment on the graphic, and one on the thread: > > Graphic: I'd suggest s/structure/super-structure/ in the > title because... I understand the point but super-structure seems a bit cryptic. See below for a different suggestions > > On the thread: I don't think one can fit the concepts of an > IETF participant nor of the "volunteers" relationship in any > diagram like this, and those (IMO) are the really central > concepts that are important in understanding (what I think of > as) the important players and relationships. > > It is a good thing to better understand how the various > designed components of superstructure relate, but that'd, > if taken alone, (which isn't I'm sure the intent at all), > give a misleading impression. > > But, were there a useful graphical way to indicate that > all this hinges on participants who choose to volunteer to > do stuff, then that'd be a useful improvement to the image. Currently, the community is represented as an attribute of the boxes and that is reflected in the key, where five of the six items have the word community in them. This to me reflects the underlying principle that the IETF is a community organisation and by default community controlled. This could be made even clearer by adding community into the title, such as "Community structures of the IETF and inter-related organisations"? I looked at a number of alternatives for representing the community and settled on the mechanism above for the following reasons: 1. A separate community box. That would definitely be misleading because it would make it seem as if the community was a separate thing that had connections into these bodies rather than these bodies being drawn from and part of the community. It would also require a bunch of arrows that would clutter the diagram even further. 2. A big box round everything except the contracted parts that said Community. This remains a possibility but is quite hard to do without including contracted roles, such as mine, and that would probably lose the point about community control and participation. Perhaps this could be made clearer still by replacing the word community here with "Volunteer participant" in the key and possibly the title? Jay > > Cheers, > S. > <OpenPGP_0x5AB2FAF17B172BEA.asc> > > -- Jay Daley IETF Executive Director exec-director@ietf.org
- [admin-discuss] Attempt to diagram the structure … Jay Daley
- Re: [admin-discuss] Attempt to diagram the struct… Joel M. Halpern
- Re: [admin-discuss] Attempt to diagram the struct… Joel M. Halpern
- Re: [admin-discuss] Attempt to diagram the struct… Joel M. Halpern
- Re: [admin-discuss] Attempt to diagram the struct… Jay Daley
- Re: [admin-discuss] Attempt to diagram the struct… Colin Perkins
- Re: [admin-discuss] Attempt to diagram the struct… Brian E Carpenter
- Re: [admin-discuss] Attempt to diagram the struct… Jay Daley
- Re: [admin-discuss] Attempt to diagram the struct… Bob Hinden
- Re: [admin-discuss] Attempt to diagram the struct… Russ Housley
- Re: [admin-discuss] Attempt to diagram the struct… John Levine
- Re: [admin-discuss] Attempt to diagram the struct… Russ Housley
- Re: [admin-discuss] Attempt to diagram the struct… Jay Daley
- Re: [admin-discuss] Attempt to diagram the struct… Jay Daley
- Re: [admin-discuss] Attempt to diagram the struct… Jay Daley
- Re: [admin-discuss] Attempt to diagram the struct… Deen, Glenn (NBCUniversal)
- Re: [admin-discuss] Attempt to diagram the struct… Jay Daley
- Re: [admin-discuss] Attempt to diagram the struct… Deen, Glenn (NBCUniversal)
- Re: [admin-discuss] Attempt to diagram the struct… Brian E Carpenter
- Re: [admin-discuss] Attempt to diagram the struct… Jay Daley
- Re: [admin-discuss] Attempt to diagram the struct… Bob Hinden
- Re: [admin-discuss] Attempt to diagram the struct… Jay Daley
- Re: [admin-discuss] Attempt to diagram the struct… Bob Hinden
- Re: [admin-discuss] Attempt to diagram the struct… Stephen Farrell
- Re: [admin-discuss] Attempt to diagram the struct… Jay Daley
- Re: [admin-discuss] Attempt to diagram the struct… Stephen Farrell
- Re: [admin-discuss] Attempt to diagram the struct… Brian E Carpenter