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

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. Also, should it be inside a box labelled ICANN?

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