Hi Daniel, For the IETF nomcom, there are only 2 Advisors:
* Past chair * IETF Tools Team Advisor The Tools Team Advisor is mainly there to provide support for the process (candidate feedback, encrypted committee deliberations and so on). The rest are Liaisons: IAB Liaison IESG Liaison ISOC Board Liaison IETF LLC Liaison IETF Trust Liaison I am not sure I understand how Advisors are selected in the RIPE context: "An advisor is responsible for such duties as specified by the invitation that resulted in the appointment." Can you clarify what this means in practice. Ole Ole J. Jacobsen Editor and Publisher The Internet Protocol Journal Office: +1 415-550-9433 Cell: +1 415-370-4628 E-mail: olejacob...@me.com Skype: organdemo On Fri, 13 Dec 2019, Daniel Karrenberg wrote: > > > On 12 Dec 2019, at 12:21, Daniel Karrenberg wrote: > > > Working within the current procedure, if you wish and the NomCom agrees, you > > could become an advisor to the NomCom, both for the purpose of bringing more > > diversity and for helping with that final report. How’s that? > > To be sure: as laid out in ripe-728 advisors are full members of the NomCom, > participate, contribute and vote on all matters except on the selection of > candidates. > > From my observations of IETF NomComs I can say that advisors can have > considerable influence on the work of the NomCom and the outcomes of that > work. > > The NomCom will have liaisons from the WG-chairs collective, the RIPE program > committee and the RIPE NCC board. Ana Wilson has agreed to be an advisor > filling the role of ‘previous chair’. > > If anyone in the RIPE community has suggestions for additional advisors that > would help the NomCom please let us hear them. > > Daniel > > >
