- ripe-list - mailman.ripe.net

RIPE Code of Conduct Process - Status
by Leo Vegoda 01 Jun '22

01 Jun '22

Hi, I asked this list in April [1] for input on the draft Code of Conduct Process. We've not had any feedback yet, which makes it difficult to know how our draft should change or whether it is good enough. Please take a look at the draft and either identify areas where we need to improve it or send a simple statement of support. We also held a BoF at RIPE 84. We discussed [2] recruiting for the team that will use this process. The recording has been published and runs slightly over 30 minutes. If you weren't able to attend the BoF but have thoughts to share with the TF, please either send them here or to coc-tf(a)ripe.net. Both lists are publicly archived. Kind regards, Leo Vegoda [1] https://www.ripe.net/ripe/mail/archives/ripe-list/2022-April/002513.html [2] https://ripe84.ripe.net/programme/meeting-plan/bofs/#tues

2 1

AFRINIC vote buying
by Ronald F. Guilmette 01 Jun '22

01 Jun '22

Even though this relates to a whole different Regional Internet Registry, I think that some (many) of you may be interested to watch this video and to learn what's been going on of late down in the AFRINIC region. https://www.youtube.com/watch?v=32xCurWfJo4

1 0

Test
by Engi Gang 31 May '22

31 May '22

test

1 0

ripe-list@ripe.net
by Engi Gang 31 May '22

31 May '22

ripe-list(a)ripe.net

1 0

hola
by Engi Gang 31 May '22

31 May '22

senior

1 0

RIPE Diversity Task Force - Next Steps
by Mirjam Kuehne 30 May '22

30 May '22

Dear colleagues, As announced at the closing plenary of RIPE 84, I discussed the status of the RIPE Diversity Task Force with the original members of the task force. The task force has initiated many activities that have been implemented in the meantime, such as childcare at RIPE Meetings, the Women in Tech sessions, the mentoring programme and the new RIPE Code of Conduct. In agreement with the members of the task force, I proposed to close the task force. This proposal was approved by the RIPE 84 plenary and is now reflected on ripe.net: https://www.ripe.net/participate/ripe/tf/ripe-diversity-task-force This does not mean that our efforts to increase diversity and become more inclusive in the RIPE community are over. But after this topic was successfully kicked off by the task force, it has evolved into a larger community activity and is the responsibility of all of us. The Diversity mailing list has always been open to all and I would like to encourage you to subscribe and participate in this effort: https://lists.ripe.net/mailman/listinfo/diversity There is still a lot to do and I have already heard some good suggestions at RIPE 84: - Take the Women in Tech session to the next level - Continue to collect useful data to measure success - Reach out to students and newcomers and expand the mentoring programme. We will continue this conversation on the Diversity mailing list and I look forward to your ideas and suggestions. Finally, I would like to thank the members of the task force for their hard work on this topic so far. Kind regards, Mirjam Kühne RIPE Chair

1 0

New on RIPE Labs: The RIPE Chair Team Reports - Highlights from RIPE 84
by Mirjam Kuehne 30 May '22

30 May '22

Dear colleagues, It was wonderful to come together as a community again at our first face-to-face meeting since the beginning of the pandemic. Please find a short summary of RIPE 84 along with some personal highlights in this new article on RIPE Labs: https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-highl… Kind regards, Mirjam Kühne RIPE Chair

1 0

Re: [ripe-list] Revised PDP - Draft version 3 for your review
by Mirjam Kuehne 29 May '22

29 May '22

Dear colleagues, The deadline for comments for the revised PDP documents was set to Friday this week (27 May). Considering that we all have a lot to follow-up with after RIPE 84 and that there is a holiday tomorrow in some countries, I would like to extend the deadline to Monday, 30 May 2022 before 06:00 UTC. Please let us know what you think so we can understand whether the revised version enjoys community consensus. Kind regards, Mirjam Kühne RIPE Chair On 29/04/2022 14:15, Mirjam Kuehne wrote: > Dear colleagues, > > The deadline for comments to the changes we proposed to the revised > Policy Development Process (PDP) document has passed. We reviewed the > suggestions we received and made some adjustments accordingly. > The new version (v3) is here: > > https://www.ripe.net/publications/docs/ripe-documents/other-documents/polic… > > > At the top of the document you will find a link to a page showing the > diff to v2 (and also a diff to ripe-710, the current PDP document). > > Below you find the main considerations and changes we made. In > addition to that, the communication experts at the RIPE NCC cleaned up > and tightened the language throughout the document to avoid > misunderstandings. > > Before issuing a last call, we would like to ask you to review this > new version again carefully and provide any feedback before 27 May > 2022. In order to be able to build consensus, it is also important to > let us know if you are happy with this revised version of the document. > > Kind regards, > Mirjam Kühne > RIPE Chair > ========= > > Main changes and considerations in revised PDP v3: > > 1. Introduction > We removed the distinction between author and owner and the sentence > related to that distinction in the introduction. > > 2. The Process > Based on feedback received for earlier versions of this draft, we kept > the strong suggestion to share an idea with the community before it > enters the formal policy process. We clarified that this is not > mandatory and strengthened the motivation. > > 2.1. Status of a proposal > We reviewed the suggestion to add a fourth status “abandoned” in > addition to open, accepted and withdrawn. We decided not to add > “abandoned” as this case is already covered by "withdrawn" or “open” > (in case someone else picks up the proposal). > > 4. Appeals Process > We did not see enough support for introducing a separate appeals body. > But based on experience with the first appeal, the entire appeals > process is defined a lot more clearly now. > > 5. Changes to the PDP > We received a comment that changes to the PDP should follow the same > process as other documents in RIPE. RIPE documents are typically > agreed by community consensus. While a specific, formal process has > been agreed for development of RIPE policy, enthusiasm in the > community for using this process for other RIPE documents is currently > low. Therefore we kept section 5. that describes how the PDP document > is changed through community consensus. > > >

3 2

Draft Document: RIPE Task Forces - Definition and Guidelines - v3
by Niall O'Reilly 27 May '22

27 May '22

Dear Colleagues, [Please view this message as either plain text or HTML, according to your preference.] In view of significant comments received during what we had expected to be a restricted last call, Mirjam and I have decided to make a fresh draft of the proposed document on RIPE Task Forces and to make this available for your review [here][v3]. An onward link leads to an [alternative presentation][v3chg] of the draft, in which recent changes are highlighted. We are very grateful to Boris Duval and Antony Gollan, who did most of the real work. We plan to close the review period just before 24:00 UTC on Sunday 10 April next, and to announce a two-week last-call period shortly after that. Please let us know what you think, in sufficient numbers so that we can understand whether the draft enjoys community consensus. For your convenience, the table below shows the dates when successive drafts of this proposed RIPE Document were announced. | Date | From | Remarks | |------------:|:-----------|:------------------------------------------------| | 19 Nov 2021 | M.Kuehne | [002363][] Draft; suggestions invited | | 16 Dec 2021 | N.O'Reilly | [002402][] Update; last call closing 14 Jan | | 3 Feb 2022 | N.O'Reilly | [002444][] Update; last call extended to 18 Feb | | 23 Mar 2022 | N.O'Reilly | [v3][] Fresh draft for review until 10 Apr | Best regards, Niall O’Reilly --- [002363]: https://www.ripe.net/ripe/mail/archives/ripe-list/2021-November/002363.html [002402]: https://www.ripe.net/ripe/mail/archives/ripe-list/2021-December/002402.html [002444]: https://www.ripe.net/ripe/mail/archives/ripe-list/2022-February/002444.html [v3]: https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-… [v3chg]: https://ripe.net/publications/docs/ripe-documents/other-documents/ripe-task…

12 19

Gert Döring Receives 2022 Rob Blokzijl Award
by Niall O'Reilly 26 May '22

26 May '22

# Gert Döring Receives 2022 Rob Blokzijl Award On Thursday 19 May at RIPE 84 in Berlin, Gert Döring received the Rob Blokzijl Award for his long-standing contribution to the Address Policy Working Group and the RIPE community and for his work to promote IPv6. The award honours the memory of Rob Blokzijl, the first Chair of RIPE. It recognises individuals who have made substantial technical and operational contributions to the development of the Internet in the RIPE NCC service region and supported or enabled others. Since the beginning of his career, Gert has been sharing knowledge, connecting people, building consensus and helping others to contribute and succeed. He is a role model for working group chairs around the globe. Together with the award, Gert receives EUR 10,000 from the Foundation, and has offered to donate part of this sum to buy a fibre optic splicer to help rebuild networks in Ukraine, with the Foundation making up the remainder. More information on the Rob Blokzijl Foundation is available here: http://rob-blokzijl-foundation.org/ Best regards, Niall O’Reilly On behalf of the Board of the Rob Blokzijl Foundation

4 3