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

Bob Hinden <bob.hinden@gmail.com> Mon, 21 February 2022 23:21 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 723413A0B6D; Mon, 21 Feb 2022 15:21:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_DNSWL_BLOCKED=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 Tp1Z_y-MPce4; Mon, 21 Feb 2022 15:21:17 -0800 (PST)
Received: from mail-oo1-xc2a.google.com (mail-oo1-xc2a.google.com [IPv6:2607:f8b0:4864:20::c2a]) (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 C0E773A0B44; Mon, 21 Feb 2022 15:21:17 -0800 (PST)
Received: by mail-oo1-xc2a.google.com with SMTP id p206-20020a4a2fd7000000b0031bfec11983so15123851oop.13; Mon, 21 Feb 2022 15:21:17 -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=0cE7zctoaaNjlYiVZo1PQZafMnfAiiIgB7QqGex1z3k=; b=Omxpp0SQEANY1Y6plAG352VkJnI5JO97AlsyrJpxMSbOEnhk5m/nwDeMkSGxiH0MUq eJCUrBPEz36KZqrXL+zdgKPYTlO2JOwVSqbhYGq5DpjqZ8ZWp6rZdYSSwrakURTwsRlj x6yBahTE08yAfmyHcyhqBb5pyVDZ931d9FyxFZtNGbVGYBX++f0xH3tpXVhI3gAgx67/ eFWpVmmOKzyoIuKwlyxzG7Pi0RbT8GhKT+xd+/ruX1esEWbjpxVVyj5rSMhzPq4HnTTN sUboYY1KcjUcAaAIdgsUsvAJf9azprDfOXt6TZxqQqIqZbGR1x+J97SA9nN5P/tqo07v 9nDw==
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=0cE7zctoaaNjlYiVZo1PQZafMnfAiiIgB7QqGex1z3k=; b=MxYhmTpwSFoUkMYZ/2l6uiBegITDRnxxebHdWFqowAPyqBVWlALOursj/faRwgsiaB JjDpuEwmhI7JFBm3Vg7wCcsVhLqpU9+llI4Wxoi/4Kbj1SzILWaPO0OS6xBDKRy/zkzd 2Qp2h5D7EiU+KQbVwnEPHAJCAEg6Et5ddV1Ue+J4vZXAOBMKHAqe2uBYTihrovwO5Dmz nLghlI0aRDUNxMDvJh02/HH7i3HXoux8BWexMHNqbmX8HnpPJ7n0Sqsa/lFaAJn1n1sj KbzVKF1ZZnVdeJwshID3UqhNwHLl8bkJOXrZxefFzeH8ZLKXjHfOpOCA0SJm9oiyAvqE 5v6Q==
X-Gm-Message-State: AOAM53229Tcl8bSkNkOtmL2D6jY9ZLK2aEvwOn5fKrcxta9IoHUZuqkX 8coqBKYD3amrqa1Vmxu5awW9rpdXcCk=
X-Google-Smtp-Source: ABdhPJxkmd0ekk1tPqkbUajq0GiSTQIwFGzLt3byNBZNxtzMeXrnCwGmT22cQ/QoF3nz4t6hPA8CCA==
X-Received: by 2002:a05:6870:588:b0:d4:1d43:7520 with SMTP id m8-20020a056870058800b000d41d437520mr524865oap.318.1645485676662; Mon, 21 Feb 2022 15:21:16 -0800 (PST)
Received: from smtpclient.apple ([2600:1700:4383:c05f:10a8:8d3c:da27:f436]) by smtp.gmail.com with ESMTPSA id c5sm5477313otm.64.2022.02.21.15.21.15 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Feb 2022 15:21:16 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_CDAE7DDD-BCDF-49B8-BF6B-8BF8F90DE767"; 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: <2FA08C30-2D8D-4F2A-9B40-A865654B54E0@ietf.org>
Date: Mon, 21 Feb 2022 15:21:14 -0800
Cc: Bob Hinden <bob.hinden@gmail.com>, admin-discuss@ietf.org
Message-Id: <49BE4C0D-87F7-4B5B-8342-789E678F0238@gmail.com>
References: <12F3A997-DF48-4AA1-B744-8D310D460397@ietf.org> <0F630F4E-7646-4885-B31D-A16805B776CA@gmail.com> <2FA08C30-2D8D-4F2A-9B40-A865654B54E0@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/xXKi_6JOaJYEXrFYsdfv1y7Ml2g>
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: Mon, 21 Feb 2022 23:21:20 -0000

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”.

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).

Bob