- ripe-list - mailman.ripe.net

RIPE Working Group Chair Financial Support call for consensus by 15 June 2020
by Hans Petter Holen 16 Jun '20

16 Jun '20

To follow up on the proposal the community plenary at RIPE 80, to provide financial support Working Group (WG) Chairs if needed, I would like community input. The presentation can be seen at 7:45 into the video at https://ripe80.ripe.net/archives/video/383/ In principle, all RIPE Meeting attendees, including RIPE WG Chairs, Programme Committee members and presenters are expected to cover the costs of participating in a RIPE Meeting. However, in exceptional cases, for instance, if a WG would end up with no Chair during a meeting, a WG Chair can ask the RIPE Chair to request financial assistance from the RIPE NCC. This has mostly been limited to waiving the meeting fee, not for travel and accommodation. The matter was discussed at RIPE NCC Executive Board meeting December 2018 after it was brought to the attention of the RIPE NCC Executive Board through one of its members. The board was positive to provide support also for travel and accommodation if needed, and tasked the RIPE Chair trough EB402 tasked to make a draft procedure. The proposal is modelled after the RIPE Fellowship program and can be found at: https://www.ripe.net/participate/ripe/wg/cc/ripe-working-group-chair-financ… If there is consensus from the community on this I will do a formal request to the RIPE NCC for such support. Hans Petter Holen ad-interim RIPE Chair

21 26

New on RIPE Labs: COVID-19: Changing the Internet Governance Landscape
by Mirjam Kuehne 11 Jun '20

11 Jun '20

Dear colleagues, In this new article on RIPE Labs, my colleague Chris Buckridge is discussing possible impacts COVID-19 might have on Internet governance-related issues: https://labs.ripe.net/Members/chrisb/covid-19-changing-the-internet-governa… Kind regards, Mirjam Kühne RIPE NCC

1 0

NomCom has Started Candidate Selection
by Daniel Karrenberg 11 Jun '20

11 Jun '20

[See https://blog.ripe-nomcom.org/nomcom-starts-candidate-selection/ for a version of this message with convenient links.] Before and during RIPE 80 there were calls for the NomCom to halt the process and calls to re-open the call for nominations. See the archives of the ripe-chair-discuss and ripe mailing lists. The NomCom has listened carefully to these discussions and decided in its 5th meeting to postpone candidate selection and seek community support for continuing the process before proceeding. After further consultation within the NomCom I have published this request via this mailing list on 25 May. The NomCom pondered the whole community discussion again in its 6th meeting and decided unanimously to continue with candidate selection at the next meeting. Last Friday the NomCom has re-affirmed this decision at its 7th meeting and started with candidate selection. The NomCom stresses that it has carefully addressed all suggestions made during the discussions and that it has not taken its decisions lightly or without regard to what has been said. We considered *all* input as well as the current circumstances and concluded that there is no consensus in the community to deviate pragmatically from the agreed process as it is codified in ripe-727 and ripe-728. Now that we have made the decision according to our mandate and the process agreed by the community before, we ask the community to unite and support us in our effort. Daniel Karrenberg Chair RIPE 2020 NomCom

4 3

RIPE 81 will be a Virtual Meeting, 27-30 October 2020.
by Hans Petter Holen 08 Jun '20

08 Jun '20

Dear colleagues, Following the success of RIPE 80, and with the ongoing risks posed by large gatherings still very much in mind, I have decided together with the RIPE NCC Meeting staff and the RIPE NCC MD, that RIPE 81 will take place as a virtual meeting. We have the support from the RIPE Programme Committee and the RIPE Working Group Chairs in making this decision. This means we are no longer bound by the availability of the venue when setting the date of the event, so after careful consideration, we have decided to change the date of the event. RIPE 81 will now take place from 27-30 October 2020. This change will not only help to ensure that the timing of RIPE 81 is better aligned with other industry events, but it also gives the RIPE Programme Committee, RIPE Working Group Chairs and RIPE NCC staff an extra month to prepare for the meeting, and so to explore options on how to improve the overall virtual experience for all our attendees. We are making this decision now rather than later in the hopes that this will give everyone plenty of time to make plans and come take part in RIPE 81. Best regards, Hans Petter Holen ad-interim RIPE Chair

1 0

Post-RIPE 80 Working Group Chair Meeting Summary
by Antony Gollan 05 Jun '20

05 Jun '20

Dear colleagues, The RIPE Working Group Chairs form a collective that meets at every RIPE Meeting. Summaries from these meetings are published on ripe.net. You can find the summary from the collective's post-RIPE 80 meeting here: https://www.ripe.net/participate/ripe/wg/cc/summaries/post-ripe-80-working-… Kind regards Antony Gollan Senior Communications Officer RIPE NCC

1 0

New on RIPE Labs: RIPE 80: Setting up a Zoom Alternative with AWS
by Mirjam Kuehne 05 Jun '20

05 Jun '20

Dear colleagues, Not all of the RIPE 80 attendees were able to use Zoom to participate in the remote meeting for different reasons. We therefore provided an alternative way, which did not rely on Zoom, for people to join in the meeting. Read on RIPE Labs how we did that and what challenges we faced on the way: https://labs.ripe.net/Members/oliver_payne/ripe-80-setting-up-a-zoom-altern… Kind regards, Mirjam Kühne RIPE NCC

1 0

Nomination Call for ASO Representative to 2021 ICANN Nominating Committee
by Antony Gollan 04 Jun '20

04 Jun '20

This message is sent on behalf of the Number Resource Organization (NRO). --- This announcement can also be found on the ASO website: https://aso.icann.org/nomination-call-for-aso-representative-to-2021-icann-… --- Nomination Call for ASO Representative to 2021 ICANN Nominating Committee ICANN’s Nominating Committee (NomCom) is responsible for the selection of eight ICANN Board Members, two directors of the Public Technical Identifiers (PTI) and for other selections as are set forth in the Bylaws (see Article 8, Section 8.1). The NomCom is also charged with appointing some members of the ALAC, ccNSO Council and the GNSO Council. The NomCom complements the other means for filling a portion of key ICANN leadership positions achieved within ICANN Supporting Organizations and Advisory Councils. As per the ICANN Bylaws (Article 8, Section 8.2), the Address Supporting Organization Address Council (ASO AC) is pleased to invite nominations for candidates from the “Internet Numbers Community” to run for an open seat on the ICANN NomCom 2021 as delegate of the ASO. The term for the selected delegate will be one year starting in ICANN 69 in Hamburg, Germany, in October 2020 (see Article 8, Section 8.3 for term limits). All ICANN Bylaws described above can be found here: https://www.icann.org/resources/pages/governance/bylaws-en/#article8 Time Commitment for the ASO NomCom Representative The person should be able to join (in person - ONLY when it is safe to travel and travel restrictions are lifted), three ICANN (69, 70 and 71) meetings and an intersessional meeting (location decided by NomCom 2020). Travel support for all meetings is provided by ICANN. - ICANN69 - Annual General Meeting - 17-22 October 2020 – Hamburg - EUR - ICANN70 - Community Forum - 20-25 March 2021 – Cancún - LAC - NomCom Intercessional - Assessment meeting - TBD April 2021 - (Location tentative) - ICANN71 - Policy Forum - 14-17 June 2021 - The Hague - EUR In 2020 due to COVID-19, the NomCom has only conducted online meetings and this may continue in 2021 unless and until it is safe to travel. Online meetings take more time per week compared to in-person. Please review the time commitments in view of COVID-19. In case global travel resumes and there is an in-person meeting, travel support will be provided by ICANN. The ICANN NomCom has a set of guidelines and procedural documents available here for reference that provide additional information about the work of the NomCom. The person should be able to join monthly teleconferences (typically 15:00 or 16:00 UTC). Note that the committee’s workload will increase significantly during Apr/May/June 2021 when the candidate assessment process will be at its busiest. Conference calls are held more frequently (typically weekly) and the duration of the calls may last up to 3 hours during this time. Deadlines and Important Dates The ASO AC will be responsible for the selection of the delegate based on the following timeline: - Announcement of call for nominations for 2021 ICANN NomCom: 4 June 2020 - Nomination period ends: 17 June 2020 - Evaluation of nominations by the ASO AC: 18 June 2020 – 28 June 2020 - Voting period by the ASO AC: 29 June 2020 – 7 July 2020 - Announcement of selected delegate: around 8 July 2020 (second week of July) All nominations should be sent to secretariat [at] aso [dot] icann [dot] org by 17 June 2020 23:59 UTC, with answers to the following questions (ll questions are mandatory). You can also provide your CV as well. - Have you read the time commitment for NomCom and are you willing to commit the time required to fulfil this role? - Have you been part of NomCom in the past representing any other constituency? - How many ICANN/RIR meetings you have attended in last 5 years? and which SOs/ACs you actively follow? - Please share briefly why you want to join the NomCom as ASO AC appointee. ASO Secretariat Regards Antony Gollan Senior Communications Officer RIPE NCC

1 0

Call for input on all virtual RIPE 81
by Hans Petter Holen 28 May '20

28 May '20

At the meeting with RIPE Working group chairs on 20 May we discussed my original plan to decide on RIPE 81 as soon as the new RIPE Chair is appointed, but no later than the end of June. The consensus following the discussion the topic was that it would be unreasonable to expect the next RIPE Chair and vice-Chair to be able to take this decision just after the appointment. The PC and WG Chairs will use the upcoming weeks to discuss this, and your input is highly appreciated. The RIPE NCC Executive board meets on 16 June, and I would like to make the decision already at that time. While it is a decision on the location of a RIPE meeting is made by the RIPE Chair together with the RIPE NCC, it is also a responsibility of the RIPE NCC MD and Executive board to take the safety and employees arranging the meeting into account. Please let me know your thoughts by Friday, 12 June. Sincerely, Hans Petter Holen RIPE ad-interim Chair

8 9

Re: [ripe-list] The NomCom Requests your Support
by Christian Kaufmann 28 May '20

28 May '20

2nd try.... > On 28. May 2020, at 10:38, Christian Kaufmann <ck(a)minxs.net> wrote: > > Dear NomCom, > Dear Community, > > The independence and stability of the RIPE Chair role is the highest priority for the RIPE NCC Executive Board. For this reasons we will stick to the documented and agreed process, this said let me share some more thoughts of us. > > We appointed Daniel as a non voting NomCom Chair as he knows the process:-), but also was not running himself. As he is non voting but just chairing and facilitating we did not perceive this as a conflict of interest. The NCC is running many services for the community so we did not see this any different. > We did not foresee that NCC staff would apply for the role but then again we have an independent NomCom in which we trust and the process is not forbidding this either. > > Our second task is to review if the process was followed, not who was elected and why and we are still happy to fulfill this task. > > Regarding the renumeration, this topic came up and the board promised to financially support the chair/vice-chair construct if the candidates wishes so to ensure their independence. > We also made clear we do not want another MD type person to manage, so even if we support the RIPE Chair we do not want to manage the yearly performance or salary increase of this position as this clearly wouldn’t go well with our goal of an independent Chair. A suggestion we started to discuss, but which is not yet defined is to offer a fixed salary for 5 years and a “performance review” executed by the community if they wish so. > This salary would then be earmarked and reserved so nobody can touch it or change it, means the independence of the Chair does not get compromised. > We as the board believe this should be a solid enough construct and do not want to create a RIPE Community B.V. Or any other legal body to facility a potentially salary payment. But then again this is up to the community and not to us. > > We have heard and read the comments here on the list and sympathies with many of them and there is clearly more work to be done for round 2. > This said we have full trust in the NomCom and the process and will do our part in it. > > Best regards on behalf of the NCC Executive Board, > > /ck > > Sent from a mobile device at the end of the galaxy... > > > >> On 26. May 2020, at 22:32, Franziska Lichtblau <rhalina(a)old-forest.org> wrote: >> >> Hi Daniel, hi folks, >> >> writing this with my PC chair hat on. >> >> After giving everyone time to express their thoughts on the matter I >> can confirm that we have consensus within the PC that the NomCom still >> has our support. Jan, our liason member in the NomCom has kept us in >> the loop and confirmed that the process which was agreed upon by the >> RIPE community was followed. >> >> Yes, the process we designed has flaws, but we do not feel them to be >> substantial enough to restart the process. The candidates themselves >> seem to have the general support of the community and the flaws within >> the process do not outweigh that in our opinion. >> >> As the concerns per se are valid, we should make it a priority task to >> the next RIPE (vice)chair to make sure this discussion takes place and >> the policy is adapted so that the concerns get addressed. >> >> Best regards, >> Franziska >> >> (RIPE PC Chair) >> >>>> On Mon, 2020-05-25 at 16:44 +0200, Daniel Karrenberg wrote: >>> Dear Friends and Colleagues of the RIPE community, >>> >>> If your feeling is something like "Oh no, not another long message >>> from >>> the NomCom! I wish they would just get on with it." you do not need >>> to >>> read further. It would certainly help us if you explicitly told us >>> briefly to "just get on with it". >>> >>> Thanks >>> >>> Daniel >>> >>> ------------------ >>> >>> From: >>> >>> Daniel Karrenberg - Chair of the RIPE 2020 Nominating Committee. >>> >>> >>> To: >>> >>> Christian Kaufmann - Chair of the RIPE NCC Executive Board, >>> >>> Franziska Lichtblau - Chair of the RIPE Program Committee, >>> >>> Hans Petter Holen - RIPE Chair ad-interim & Chair of the RIPE WG >>> Chairs, >>> >>> RIPE Community. >>> >>> >>> Christian, Franziska, Hans Petter, Friends and Colleagues, >>> >>> The process to select two persons to succeed Hans Petter Holen as >>> RIPE >>> chair has been under way since September 2019. The NomCom has worked >>> diligently to run the process that has been agreed by the community >>> and >>> codified in ripe-727 and ripe-728. We have called for nominees, >>> canvassed when we had only one nomination and received four further >>> nominations. We have dealt with the unforeseen withdrawal of Hans >>> Petter. We have recognised the increased urgency that Hans Petter's >>> resignation as RIPE Chair puts on the process by slightly tightening >>> our >>> time line without compromising on running an exemplary process. We >>> have >>> held three formal and two informal meetings, talked to the nominees >>> by >>> teleconference and received substantial input about all nominees from >>> a >>> diverse set of people in the community. We have kept the community >>> informed by announcements on the RIPE mailing list, by providing a >>> dedicated blog, by publishing complementary material on RIPE Labs, >>> by >>> reporting to the community plenary at RIPE80 and by talking about >>> our >>> work whenever the opportunity presented itself. >>> >>> Last week, during RIPE80, there were some calls from within the RIPE >>> community to stop this process and start over. There also have been >>> suggestions to issue another call for nominations and then continue >>> as >>> before. Since our mandate does not extend beyond executing the >>> process >>> along an agreed time line we are extremely reluctant to deviate from >>> this unless we observe a clear and strong consensus in the community >>> to >>> deviate for the sake of pragmatism. >>> >>> We have discussed this extensively and decided against changing the >>> planned time line because we see no such consensus. We also >>> considered >>> the consequences: Deviating from the plan at this time would put >>> Hans >>> Petter into the difficult position of having to work a new and >>> demanding >>> job next to filling the RIPE Chair ad interim role. This is too much >>> to >>> ask of anyone even without taking into account the recent discussion >>> on >>> ripe-chair-discuss. Hans Petter has told us that he accepted the >>> ad-interim role on the assumption that we will finish our work on >>> time >>> and that he will likely have to resign if we take significantly >>> longer >>> than planned. >>> >>> Unfortunately during the RIPE 80 community plenary there has been no >>> discussion that provides further guidance to us. It is difficult for >>> us >>> to assess whether this was due to the virtual format of the meeting, >>> widespread agreement with what we have done so far or any other >>> reason. >>> We certainly expected those who had called for changes to the >>> process >>> earlier during the week to speak up and a discussion to take place >>> that >>> would provide further guidance for us. This has not happened. >>> >>> We have therefore decided to briefly pause our process and not to >>> start >>> candidate selection after RIPE 80 as originally planned. We have >>> continued with preparations but have not started discussing the >>> nominees >>> among ourselves yet. >>> >>> We ask the RIPE NCC Board, the PC, the WG Chairs and the community >>> at >>> large to give us timely guidance on how to proceed. The question >>> before >>> us is whether we still have the support of the community to continue >>> with the agreed process and time line or whether there is consensus >>> in >>> the community that we should do something different. We need this >>> guidance now so that we can keep the delay in the time line as short >>> as >>> possible. >>> >>> We also ask the community as a whole to support us once we do >>> proceed. >>> >>> Daniel Karrenberg, >>> Chair, >>> RIPE 2020 Nominating Committee >>> >> >>

2 1

Join us for the RIPE NCC Educa::IPv6-only
by Ondřej Caletka 28 May '20

28 May '20

Dear RIPE community, You are invited to join us for a deep-dive into an IPv6-only world! We’re hosting the fourth edition of a RIPE NCC::Educa - a one day online event, bringing together experts from around the world to take a deeper look at topics of interest. Registration is free. To mark the anniversary of World IPv6 Launch Day, we’re hosting the RIPE NCC::Educa IPv6-only on Monday, 8 June from 10:00 UTC+2 onwards. Expert presenters will talk about what it means to run IPv6-only data centres, ISPs and enterprises, among other topics. You can view the agenda at: https://www.ripe.net/support/training/ripe-ncc-educa/ripe-ncc-educa-ipv6-20… Register at: https://www.eventbrite.nl/e/ripe-ncceduca-ipv6-only-tickets-106761053184 We hope to see you online soon! Best regards, Ondřej Caletka RIPE NCC

1 0