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

Jay Daley <exec-director@ietf.org> Mon, 21 February 2022 22:52 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 29F803A09E6 for <admin-discuss@ietfa.amsl.com>; Mon, 21 Feb 2022 14:52:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 eaVdAzHU6GjT for <admin-discuss@ietfa.amsl.com>; Mon, 21 Feb 2022 14:52:30 -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 D56483A09E1 for <admin-discuss@ietf.org>; Mon, 21 Feb 2022 14:52:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id C1B1C4092790; Mon, 21 Feb 2022 14:52:30 -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 O0MY-lXDIvU7; Mon, 21 Feb 2022 14:52:30 -0800 (PST)
Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id 134DF404BFB3; Mon, 21 Feb 2022 14:52:29 -0800 (PST)
Content-Type: text/plain; charset=utf-8
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: <80550864-8ada-2940-4062-d4ab200b085a@gmail.com>
Date: Tue, 22 Feb 2022 11:52:26 +1300
Cc: Bob Hinden <bob.hinden@gmail.com>, admin-discuss@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <58B127B5-7609-4073-AA22-F8F904898A18@ietf.org>
References: <12F3A997-DF48-4AA1-B744-8D310D460397@ietf.org> <0F630F4E-7646-4885-B31D-A16805B776CA@gmail.com> <2FA08C30-2D8D-4F2A-9B40-A865654B54E0@ietf.org> <6F023E98-7991-4DE0-9990-63E3F3A99AFB@ietf.org> <80550864-8ada-2940-4062-d4ab200b085a@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/admin-discuss/nVQQLNTHMMHFQJ11rpbyoB7-Ez8>
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 22:52:34 -0000


> On 22/02/2022, at 11:23 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> Thanks, this is getting better and better.
> 
> IANA is not just a liaison relationship. It's actually a service provider to the IETF, but under organisational agreements rather than a contract held by the LLC.

Yes, that could be captured.

> Also, should it be inside a box labelled ICANN?

No as it’s the function not the company that needs recording.  The Secretariat and RPC are not inside a box labelled AMS.

Jay

> 
> Regards
>   Brian
> 
> On 22-Feb-22 10:07, Jay Daley wrote:
>> New version now posted, which addresses all of this (except the position of NomCom) and adds IANA.  Also includes some lines tweaks to improve readability.
>> Jay
>>> On 22/02/2022, at 9:17 AM, Jay Daley <exec-director@ietf.org <mailto:exec-director@ietf.org>> wrote:
>>> 
>>> Signed PGP part
>>> 
>>> 
>>>> On 22/02/2022, at 5:11 AM, Bob Hinden <bob.hinden@gmail.com <mailto:bob.hinden@gmail.com>> wrote:
>>>> 
>>>> Jay,
>>>> 
>>>> Quite an undertaking!   No good deed shall go unpunished :-)
>>>> 
>>>> A few comments:
>>>> 
>>>> Looking at this, it would appear that ISOC is part of the IETF.   The ISOC community might be surprised to learn this.
>>> 
>>> The title includes "and inter-related organisations" partly to cover ISOC and partly because some people insist that "IETF" cannot be used as an umbrella term to include the IAB/IRTF while others insist that it has been used as such for many years.
>>> 
>>>> 
>>>> Having the NOMCOM on top, might cause some to conclude it’s the main leadership body for all below it.
>>> 
>>> I put it at the top because of the appointment authority but I agree that this needs some form of adjustment, as Brian suggested, to explain how it is constructed.  If we were instead to have the IESG/IAB etc as 
> the top layer then the arrows would likely become unmanageable.
>>>> 
>>>> 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.
>>> 
>>>> 
>>>> “owns” is used in different ways.   ISOC “owns” the IETF LLC is quite different from the IESG “owns” Working Groups.  I am not sure that “owns” is quite right for relationship between the IESG and Working Groups.  “Charters” might be better.
>>> 
>>> Agree and 'charters' is a better word.
>>> 
>>>> 
>>>> Lastly, the use of black and white to distinguish different kinds of roles in the KEY is very subtle.  You might consider also using colors or shading.
>>> 
>>> I was trying to avoid colour because of the problems with that - I will look at shading.
>>> 
>>> Jay
>>> 
>>>> 
>>>> Bob
>>>> 
>>>> 
>>>>> On Feb 20, 2022, at 3:24 PM, Jay Daley <exec-director@ietf.org <mailto:exec-director@ietf.org>> 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 <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
>>>>> 
>>>>> --
>>>>> Jay Daley
>>>>> IETF Executive Director
>>>>> exec-director@ietf.org
>>>>> 
>>>>> --
>>>>> admin-discuss mailing list
>>>>> admin-discuss@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/admin-discuss
>>>> 
>>> 
>>> --
>>> Jay Daley
>>> IETF Executive Director
>>> exec-director@ietf.org <mailto:exec-director@ietf.org>
>>> 
>>> 
>>> 
>> -- 
>> Jay Daley
>> IETF Executive Director
>> exec-director@ietf.org <mailto:exec-director@ietf.org>
> 

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