> On 12/10/2020, at 1:11 PM, Joel M. Halpern <jmh@xxxxxxxxxxxxxxx> wrote: > > In line for context, and I hope this does not get too deep. > Yours, > Joel > > On 10/11/2020 7:56 PM, Jay Daley wrote: >> Hi Joel >> Thanks! >>> On 12/10/2020, at 12:40 PM, Joel M. Halpern <jmh@xxxxxxxxxxxxxxx <mailto:jmh@xxxxxxxxxxxxxxx>> wrote: >>> >>> The policy cited seems strange in multiple regards. >>> >>> In regard to the LLC Board, the policy states that it applies to the board, and then does not seem to say anything clear about what the policy is for board members. Maybe I missed it? More likely, given that most board members are also community participants (the extreme case being the IETF Chair) I suspect that there is not much to say. So don't claim the policy applies to them. Or put it more explicitly that there is nothing to say about the board. >> While that’s true for two of the sections, 'Development of RFCs' and 'NomCom', the other two sections, 'Community Feedback' and 'Mechanisms' apply equally to board and staff. Does that need to be made clearer? > > Looking at those sections, I am not seeing how they would affect board members actions or discussions. Sometimes the board consults directly and they also have to follow these rules. > >>> >>> The restrictions on the RPC seem to go too far. While it is true that most of the people who work for the RPC are not IETF participants, some of them are. And they should be permitted to do so. >> My understanding is that this is not the case, but it is possible that some of the temporary RPC staff are and so I will check and add as an issue if that is the case. > > Please check more carefully. Added as issue #2 "Policy on RPC engagement in development of RFCs is too restrictive" at https://github.com/ietf-llc/community-engagement-policy-consultation/issues/2 > >>> >>> The only one that seems to be captured properly is the Contractors other than Secretariat / RPC. >>> >>> There is also the interesting complication that the RPC staffers have a business relationship with the secretariat. We normally veyr much want the Secretariat to stay out of IETF business. Is the distinction between the RPC and AMS really that clear? My understanding is that at least some of the RPC are employed by AMS? >> They are all employed/contracted by AMS. AMS provides us with >> - RPC >> - Secretariat >> -- Clerical >> -- Meetings >> -- IT > > So Secretariat in this policy means those people employed by AMS under funding from the Secretariat contract? And if they have a person who is split? > I think this needs clarification? The two are currently quite separate and tendered as two separate contracts. If someone did work for both then both sets of restrictions would apply. Added as issue #3 "Policy needs to address people in multiple roles" at https://github.com/ietf-llc/community-engagement-policy-consultation/issues/3 Jay > > Again, Thank you, > Joel > >> Jay >>> >>> 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 <mailto: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 <mailto:exec-director@xxxxxxxx> >>>> * Direct to the IETF LLC Board (not including the IETF Executive Director) at llc-board-only@xxxxxxxx <mailto:llc-board-only@xxxxxxxx> >>>> * To the ietf@xxxxxxxx <mailto: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 >>> >> -- >> Jay Daley >> IETF Executive Director >> jay@xxxxxxxx <mailto:jay@xxxxxxxx> > -- Jay Daley IETF Executive Director jay@xxxxxxxx
