I keep re-reading the discussion of interaction with the nomcom. On one
level, avoidance of "backstabbing" makes sense.
And then I think about interesting cases that the nomcom needs to know
about. Creating an example that is to the best of my knowledge
completely fictitious, if a candidate for IETF Chair had a history of
difficult interactions with either the RPC or the IETF Executive
Director, it would seem that the nomcom should know about that. And be
able to get the information from the direct participants. This policy
would prohibit such direct communication.
(Yes, the nomcom might pick that person anyway. The reasons for choices
are manifold and complex. I am concerned merely that the nomcom be able
to get relevant information.)
Yours,
Joel
On 10/11/2020 7:23 PM, IETF Executive Director wrote:
The IETF Administration LLC (IETF LLC) has drafted a proposed IETF LLC Community Engagement Policy [1] that sets out how IETF LLC board, staff and contractors will engage with the IETF community, including
* what involvement board, staff and contractors may have in the the development of RFCs;
* what engagement they may have with the NomCom;
* How the IETF LLC seeks community feedback;
* What mechanisms the IETF LLC uses for community engagement.
The policy proposes a new mailing list ietf-admin@xxxxxxxx for the discussion of IETF LLC related matters.
The IETF LLC now seeks community feedback on this proposed policy. Please provide feedback by 26 October 2020 00:00 UTC using any of the following methods:
* Raising an issue on the Github repository [2]
* Direct to the IETF Executive Director at exec-director@xxxxxxxx
* Direct to the IETF LLC Board (not including the IETF Executive Director) at llc-board-only@xxxxxxxx
* To the ietf@xxxxxxxx list
[1] https://github.com/ietf-llc/community-engagement-policy-consultation/blob/master/DRAFT%20Community%20Engagement%20Policy.md
[2] https://github.com/ietf-llc/community-engagement-policy-consultation/issues
