IETF Logo Mail Archive

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

Bob Hinden <bob.hinden@gmail.com> Tue, 22 February 2022 04:55 UTC

Return-Path: <bob.hinden@gmail.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 D149C3A10DD; Mon, 21 Feb 2022 20:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 K7AIQ53G6qNw; Mon, 21 Feb 2022 20:55:13 -0800 (PST)
Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 310D63A0D34; Mon, 21 Feb 2022 20:55:13 -0800 (PST)
Received: by mail-wr1-x42b.google.com with SMTP id u1so30638442wrg.11; Mon, 21 Feb 2022 20:55:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=xzjPAb8jWhL6++66gyWTNDyGqF9OTR1YL8W33M3wkHA=; b=PZBQx8oZthZVDK96ai7rGUvz6TaGO5Juu5RrI7yiPLwEAr3RMERlhzr/Ll3DtT4dOa 36PR/Aic6fq8C+b17iQps87AJ3bMtN1FtHOVhf9DRHdyaUqunyJOvFwSXe+beIFQrK+b DLpIo+r45RAV9Hwv1OBgXDNy38Wcghcy2l/0LXWLynK8edO8HfYpVNU9KtUGQEszdLHJ ufkZf0kSw75tt+DHfipecSayDasuWQg5bOJsBnzOr5qg8Q1yTYzx9JlqnqlYSZPMZWmG vLqRFSItUvKomjHA7Izbhmg4KyVXNa5o5lV9HVxmP65R/E9Gy7wZex/8YU2+PwOCup5U MbgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=xzjPAb8jWhL6++66gyWTNDyGqF9OTR1YL8W33M3wkHA=; b=D9kiky8ZEs+VE/RhgNKShpRU15b7GKzsaMvOSwQt6zKWxZRxACGLjzZxbFsT6Xbv0O Ffhqwe7LsdqMQ0DrOEl5A338Uql7zu04H5cL7xGJOrgIDlhLwFmzAMPsZF2f69K3GTry EhyVVMfJ+bBYj5krjCQ+nlrGj4257Hp/++HANkKv5Jqi0OEN1qW7K9c2VRSePyU4x6kf TvJ/NE7N0U+wvrXbmlWD3QzkQModElsCMqWRBMpzcykbn9g4jba6GF5b4fu2/z3OjdcZ +aUM30ISMMLf3ao7o8sfGbN0Kkf7z2X+ACs/FAt4T4+aUpPety0hRtPoh7BKQCFxXNHR Oqow==
X-Gm-Message-State: AOAM5328kMnQyeAbOLwFVI/pTBI4qX11ERIP8CUOfw4GEih5VwJuzD1O Rb9+CO3+fij59We0UV2nqVQxCUVE+Eg=
X-Google-Smtp-Source: ABdhPJxkFtX9/+P2cYcWZTaTH8b8gsqY1cfgXvffxNubZukIuvtfAMHWxBo+nXxH/Td70+yyAzZt3A==
X-Received: by 2002:a05:6000:1ac6:b0:1e9:3a52:4c86 with SMTP id i6-20020a0560001ac600b001e93a524c86mr15185425wry.389.1645505711127; Mon, 21 Feb 2022 20:55:11 -0800 (PST)
Received: from smtpclient.apple (99-31-208-116.lightspeed.sntcca.sbcglobal.net. [99.31.208.116]) by smtp.gmail.com with ESMTPSA id h11sm34110371wrr.64.2022.02.21.20.55.09 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Feb 2022 20:55:10 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_1889291F-938E-4880-B33C-A0272CE18353"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <BE917FFB-E149-4712-90B7-3EC356AF60B0@ietf.org>
Date: Mon, 21 Feb 2022 20:55:07 -0800
Cc: Bob Hinden <bob.hinden@gmail.com>, admin-discuss@ietf.org
Message-Id: <70488F54-D852-457C-9F77-6FC2A8868932@gmail.com>
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>
To: Jay Daley <exec-director@ietf.org>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/admin-discuss/Vq1i19fBL9u86R11AAC_K3pU47g>
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 04:55:18 -0000

Jay,

> On Feb 21, 2022, at 7:17 PM, Jay Daley <exec-director@ietf.org> wrote:
> 
> 
> 
>> On 22/02/2022, at 12:21 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
>> 
>> Jay,
>> 
>>> On Feb 21, 2022, at 12:17 PM, Jay Daley <exec-director@ietf.org> wrote:
>>> 
>>>> 
>>>> I think it would be good to distinguish between appointing volunteers, vs. hiring employees/contractors.   For example, the ISOC board hires (selects, contracts, pays) a CEO, vs. the IAB appointing the IRTF chair.
>>> 
>>> That is captured by the box style - thick lines for community appointed bodies and double lines for contracted roles.
>> 
>> I don’t think that relates to my suggestion.   I think you should distinguish between hiring someone (ISOC CEO, IETF Exec Dir, etc.) and for example, appointing a w.g. chair.   They both currently use dotted lines a text “appoint”.
> 
> Yes I understood - the difference is captured by the border of the subject of the appointment, where hired roles have the double line border, as do all contracted/legal entities.  However, I have changed "appoints" to "employs" for clarity.

Good, works for me.

> 
>> 
>> A general comment, I wonder if this digram is trying to capture so much information in different line styles, box styles, etc., that it is becoming less useful (without a document that explains it).
> 
> Ultimately this is only a map, it’s the territory that it is mapping that has the underlying complexity.
> 
> New version now up with all the changes people have asked for (I think) including creating a flat structure by moving the NomCom.
> 
> 	https://www.ietf.org/media/documents/IETF_Structure_-_February_2022.png

Good improvement.

Bob

> 
> Jay
> 
>> 
>> Bob
>> 
> 
> --
> Jay Daley
> IETF Executive Director
> exec-director@ietf.org
>

v2.8.7 | Report a Bug | By Email