- ripe-list - mailman.ripe.net

Microlearning: New in the RIPE NCC Academy
by Pedro Vaz 04 May '21

04 May '21

Dear colleagues, We’re happy to introduce ‘Microlearning’, a new section in the RIPE NCC Academy providing quick lessons that can be completed in under 15 minutes to help you do your work on the Internet. Microlearning kicks off with two tutorials on the ping and traceroute utilities. We plan to add more bite-sized lessons to this section going forward. Access Microlearning via: https://academy.ripe.net <https://academy.ripe.net> All learning on the RIPE NCC Academy is free and open to all. Simply log in to your RIPE NCC Access account to go to the Microlearning section, just like our e-learning courses. We’d like to hear what you think of Microlearning, and which topics you’d like to learn more about. Best regards, Pedro Vaz Senior Learning & Development Officer --- RIPE NCC

1 0

Community Wellbeing Survey
by Erik Bais 30 Apr '21

30 Apr '21

Dear RIPE Community, A couple months ago we began discussing in a small group the challenges around personal mental wellbeing in the RIPE community and how we could potentially investigate the issue and what we could potentially put in place to make things better. One outcome of that was the development of a questionnaire around how the community is coping in the current Covid-19 era. ( The questionnaire is here: https://www.surveymonkey.com/r/JPNJG57 ) Participating in this is a personal decision for you but we do appreciate your feedback, either via the questionnaire or other means. As some of you may know, I did a presentation in 2019 at the Dutch Network Operator Group ( NLNOG ) - https://www.youtube.com/watch?v=7areInUXbyo about working in a toxic work environment and the risks of running into a burnout. This topic, ( having a burnout . .the risks and being able to talk about this in groups of small peers or even in public ) is in many countries and communities still a taboo topic. Based on the experiences that we have from that presentation and what it did for the people in the Dutch NLNOG community.. and providing a safe place for people to talk and discuss about this.. We decided that we also would like to see what the current state is in the larger community .. and start with a questionnaire on the topic. The feedback and results of the questionnaire ( and your input is highly appreciated if you participate ) will be looked at and I will do a presentation in a plenary at RIPE82 in a couple weeks. The goal is to see if we as a RIPE community need to provide similar ways for people in our region to (anonymously) be able to communicate about various topics that may or may not be directly work related. It could be that we need to have a place where we can discuss about the situation working remote .. not being able to go to the office.. the additional stress that this brings .. or that we need to talk about what all those additional social distancing rules bring to you.. or how you feel about these rules.. for some it is a blessing .. and for some it works like a new stress factor as the rules are changing per shop / public store / building .. and some of us like to have nice and clear directions .. But also about how people deal with the lockdowns .. and don’t get to meet other people that have a similar interest .. or a relation .. So what we like to see is how are you feeling .. how are you coping .. or not .. And then the question comes .. can we help .. and how I’m aware that I’m currently the one that is pushing this as a topic in public (and here for instance) .. but I’m very aware of the group of great people that helped to get this initiative and questionnaire to a state as where it is today. And I would especially like to thank Eileen (INEX), Mirjam ( RIPE Chair ), Carolien (NCC HR) , Alastair ( NCC ), Ulka ( NCC ) Alun ( NCC ), Vesna ( NCC - for her mad Wiki and notary skills ) and the people assisting in reviewing the questionnaire already for us. We like to get the information before May 11th 2021, so that we have some time to look at the results and prep the ppt for the week of the RIPE82 meeting. The data itself will be stored for max 2 weeks after that.. and only 1 admin from the NCC and the HR manager of the NCC will have access to the data, besides myself. As we use the NCC survey monkey account for the questionnaire. All questions can be skipped if you don’t feel like you want to answer a specific question. And feel free to reply here on the list .. or reach out to Mirjam, Eileen (both in CC: ) or myself in private if needed. We are planning a bit larger support group once we are done with the RIPE82 meeting on this. To minimize tracking by Survey Monkey .. You can paste the questionnaire URL in an incognito window.. The questionnaire is here: https://www.surveymonkey.com/r/JPNJG57 Thank you all in advance and see you all at RIPE82. Kind regards, Erik Bais

1 0

Reminder: Register for RIPE 82, Virtual, 17-21 May 2021
by RIPE NCC Event Team 28 Apr '21

28 Apr '21

Dear colleagues, RIPE 82 is getting closer! If you haven't done it yet, you can still register for the meeting at: https://ripe82.ripe.net/attend/register/ The meeting plan and draft programme is available online: https://ripe82.ripe.net/programme/meeting-plan/ More information about RIPE 82 can be found at: https://ripe82.ripe.net/ For updates about the meeting, follow us on Twitter at @ripemeeting and by using the hashtag #RIPE82 . Kind regards, Martina Event Manager RIPE NCC

1 0

Updating the RIPE PDP Appeals Procedure
by Mirjam Kuehne 26 Apr '21

26 Apr '21

Dear colleagues, As mentioned in my previous mail, here you can find the recommendations related to the appeals procedure as currently described in the PDP (https://www.ripe.net/publications/docs/ripe-710). Taking the conversation into account that Daniel Karrenberg initiated on this list last week, we see two ways forward: - We adjust and improve the appeals procedure in the PDP after discussing the recommendations below or - We remove the appeals procedure from the PDP and create a stand-alone RIPE Conflict Resolution Process. Please be aware that the tasks of the RIPE WG Chairs Collective as described in ripe-749 (https://www.ripe.net/publications/docs/ripe-749) define their role in the PDP appeals procedure. Changing that role in the PDP will also require a change to ripe-749. Kind regards, Mirjam Kühne & Niall O'Reilly RIPE Chair Team ----- 1. Recommendations related to recusals from the appeals procedure: - To restore explicit exclusion of the RIPE Chair from the initial stage of the appeal procedure. - To create a non-exhaustive list of categories of individuals having an obligation to be recused from the initial stage of the appeal procedure. - Clarify who count as "interested parties" during an appeals procedure in the PDP. It is recommended that the following list of people shall recuse themselves from any discussion or decision within the WGCC relating to the appeal: - Co-chairs of the relevant WG where the original proposal was discussed - Proposer of the original policy proposal - Appellant - RIPE Chair and RIPE Vice Chair Others who feel that they have a conflict of interest may recuse themselves. However, it is worth considering that the WGCC only reviews the process and not the content of the proposal or the discussion. Question to the community: Do you agree to add this to the PDP document? 2. To add a deadline in the PDP appeals procedure for escalating the appeal to the RIPE Chair. An appeal must be submitted no later than four weeks after the appealable action has occurred. The decision of the WGCC should be reached no later than four weeks of an appeal being made. If the dispute cannot be resolved by the decision of the WGCC, the issue should be brought to the RIPE Chair no later than two weeks after the decision of the WGCC. The RIPE Chair will make a final decision no later than four weeks after the appeal has been escalated to them. Question to the community: Do you agree to add this to the PDP document?

2 1

Apply for RACI Project Funding before 31 May
by Gergana Petrova 26 Apr '21

26 Apr '21

Dear colleagues, RACI provides funding for academics to present their research at events such as the RIPE Meeting and RIPE NCC regional meetings. Due to the COVID-19 pandemic, the funds for this initiative for the year 2021 will instead be used to support research projects relevant to work carried out by the RIPE NCC. We invite universities and research institutes in the RIPE NCC service region to submit proposals to work on projects in these areas: - Apply machine learning and big data analytics to the collected routing data to identify and predict trends. - Apply and customise big data visualisation frameworks to the collected routing data to better display the data to users. More details are available at: https://www.ripe.net/raci-funding If you are interested, please send us a project proposal by 31 May. We encourage you to share this call with anyone who might be interested in applying for RACI funding. If you have any questions, please write to raci(a)ripe.net. Best regards, Gergana -- Gergana Petrova External Relations RIPE NCC

1 0

Re: [ripe-list] Updated Draft RIPE Code of Conduct Published for Community Review
by Hans Petter Holen 21 Apr '21

21 Apr '21

On Mon, 19 Apr 2021 at 19:12, Randy Bush <randy(a)psg.com> wrote: >> The RIPE NCC regularly organizes events for communities which are >> distinct from RIPE. When preparing for such an event, the RIPE NCC >> will ascertain whether the respective community has adopted the >> RIPE Code of Conduct and, if not, also ascertain which Code must >> be applied. my naïve view is that, if the ncc is an organiser, then the coc MUST apply. We strongly believe that all RIPE NCC-organised events should follow the same CoC, and we think this is something the community should be able to agree on. The updated draft provides for this. We understand that it will apply to all RIPE NCC-organised events - including RIPE, MENOG, ENOG, and SEE meetings, as well as things like the Roundtable Meetings, Member Lunches and RIPE NCC Regional Meetings that we organise. Perhaps the CoC TF can look at whether this needs to be made clearer in its draft. Once the community agrees on an updated CoC, the TF will then work to define procedures and how a future CoC Team will handle reports and be constituted. This is where unexpected details or regional differences could become relevant. For example, will members of the CoC Team need to attend every Member Lunch and Regional Meeting, or will an email contact be enough in some cases? Should there be one CoC Team, or would it be better for MENOG, ENOG and SEE to have their own teams with more understanding of local contexts? My understanding is that it was an awareness of these factors that led the TF to include this provision, as well as respecting the autonomy of these communities, as Niall points out. It is my hope and expectation that the outcome of this process should be a single code of conduct that is applied in a more or less uniform way across all of the events that we organise. Regards Hans Petter Holen Managing Director RIPE NCC

2 2

Updated Draft RIPE Code of Conduct Published for Community Review
by Leo Vegoda 21 Apr '21

21 Apr '21

Dear RIPE community, An updated draft RIPE Code of Conduct (CoC) is now published for your review. As this is intended to cover all participation within RIPE, it applies to interactions over the Internet, mailing lists, as well as in-person at RIPE Meetings. You can find the document here: https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-… This draft keeps most of the text in v3.0[1], which was developed by the RIPE Diversity TF. It also draws from CoCs that are in use in other communities, including the Python CoC[2]. The biggest change is that the updated draft covers scope and behaviour only. It doesn’t touch on process or the CoC Team – these aspects will be addressed in two separate documents that are still to come. Please review the draft and share any comments on the RIPE Discussion List by Friday, 2 April 2021. We welcome suggested changes, but if you don’t see problems with the draft then statements of support are also helpful. The RIPE Chair Team will evaluate your comments and determine whether there is consensus on this draft or additional work is needed. While we would prefer comments to be shared on the RIPE Discussion List, we recognise that some people might have feedback that they would like to share in private. If you want to provide feedback in private you can contact members of the CoC TF or the RIPE Chair Team directly. Some key changes in this version: - The goal of “a neutral, transparent and open framework for report handling” has been removed and will be covered in the upcoming document that describes process. - The scope is defined as “all participation in RIPE.” - Groups and events with separate governance from RIPE may adopt this CoC but will need to manage their own implementation. - A new section covers how the CoC relates to national law. - A new section lists desired behaviours along with an updated list of unacceptable behaviours. - Both lists are arranged alphabetically, to avoid suggesting a hierarchy. We look forward to reading your thoughts on the current draft. Kind regards, Leo Vegoda On behalf of the RIPE Code of Conduct TF [1] RIPE Meeting Code of Conduct 3.0 - Draft https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… [2] Python Community Code of Conduct https://www.python.org/psf/conduct/

23 52

Updating the RIPE Policy Development Process (PDP)
by Mirjam Kuehne 20 Apr '21

20 Apr '21

Dear colleagues, The following two documents have now been published as RIPE documents: Review of the RIPE Appeals Procedure (ripe-760) https://www.ripe.net/publications/docs/ripe-760 Evolution of the RIPE Policy Development Process (ripe-761) https://www.ripe.net/publications/docs/ripe-761 The documents contain a number of recommendations, some of them related to the Policy Development Process (https://www.ripe.net/publications/docs/ripe-710). Please find those recommendations below together with a suggested way forward. For more context and background, please refer to the two documents above. We would like to hear your feedback so that we can then update the PDP document accordingly. In a second mail, we will discuss recommendations that are specifically related to the appeals procedure as currently described in the PDP. Kind regards, Mirjam Kühne & Niall O'Reilly RIPE Chair Team ---- 1. To clarify how the policy development process should be amended. The PDP is a community governance document that describes how policy is made within RIPE. Changes to the PDP are presented on the ripe list and discussed during a RIPE Community Plenary. A consensus call is then issued on the ripe-list by the RIPE Chair. Question to the community: Do you agree to add this to the PDP document? 2. To clarify or omit the identification of the RIPE Chair as "author and owner" of the policy development process. The community owns the PDP. The RIPE Chair is listed as the author of the document and oversees the community consensus process. Question to the community: Do you agree with this statement? 3. To discuss an idea for a policy proposal on the relevant mailing list before it is submitted as a formal policy proposal. Since the discussion phase is now part of the PDP, we recommend to add another step before a formal policy is submitted: It is recommended that an idea for a new policy or a change of an existing policy is sent to the relevant mailing list before it enters the formal PDP. Also, the relevant WG chairs are encouraged to work with the proposer in preparing a policy proposal. Question to the community: Do you agree with this approach?

1 0

NRO NC Nominations Deadline
by Hans Petter Holen 20 Apr '21

20 Apr '21

Dear colleagues, The call for nominations from the RIPE NCC service region to fill one seat on the Number Resource Organization (NRO) Number Council (NC) will close on 23 April 2021. Any individual residing within the RIPE NCC service region is eligible for nomination, except Regional Internet Registry (RIR) staff members. Self-nominations are permitted. The nomination process is available at: https://www.ripe.net/nro-nc-nominations-process-may-2021 Please send your nominations to <nominations(a)ripe.net> by 23:59 UTC on 23 April 2021. All confirmed nominations will be listed on the RIPE NCC website by 26 April 2021. The election for this NRO NC seat will take place during the RIPE 82 meeting that will be held virtually from 17-21 May 2021. All members of the Internet community who are attending the RIPE Meeting except Regional Internet Registry (RIR) staff members may vote in the election. All nominees may submit a written statement in support of their nomination for publication on the RIPE NCC website. Other people can express support for nominated individuals by sending an email to <nominations(a)ripe.net>. Expressions of support will also be published on the RIPE NCC website. To find out more about the NRO NC and the election process, please see: https://www.ripe.net/nro-nc-may-2021 Regards, Hans Petter Holen Managing Director RIPE NCC ------------------- Important Dates ------------------- 23 April 2021: Deadline for NRO NC nominations 26 April 2021: Deadline for all confirmed nominations to be published on the RIPE NCC website 17-21 May 2021: Election to fill NRO NC seat during RIPE 82 21 May 2021: Announce successful candidate in closing plenary of RIPE 82

1 0

New on RIPE Labs: Code of Conduct Task Force - Spring 2021 Update
by Alun Davies 16 Apr '21

16 Apr '21

Dear colleagues, The Code of Conduct Task Force published their draft of an updated RIPE Code of Conduct in March this year. In this article on RIPE Labs, Leo Vegoda looks back at why and how the task force came together, shares key feedback on the draft from the community, and discusses plans for a BoF at RIPE 82 and next stages of the TF’s work: https://labs.ripe.net/author/leo_vegoda/code-of-conduct-task-force-spring-2… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0