- ripe-list - mailman.ripe.net

The RIPE Chair Team Reports - Looking Forward to RIPE 88
by Mirjam Kuehne 15 May '24

15 May '24

Dear colleagues, Less than a week to go until RIPE 88 kicks off in Kraków. Here are some highlights and topics you can expect to be discussed at the meeting: https://labs.ripe.net/author/mirjam_kuhne/ripe-chair-team-reports-looking-f… Looking forward to seeing many of you there. Kind regards, Mirjam Kühne RIPE Chair

1 0

RIPE Programme Committee - Become a Member @ RIPE88!
by Brian Nisbet 14 May '24

14 May '24

Colleagues, The RIPE Programme Committee is responsible for recruiting and selecting presentations for the RIPE Meeting Plenary sessions. As the term of two RIPE PC members end, we are looking for new members in Spring 2024 who will be elected by the RIPE community at RIPE 88. There are currently two seats up for election to the RIPE PC. Please send nominations, with a biography, statement of interest and photograph, to pc [at] ripe [dot] net. RIPE Meeting Programme Committee: Appointment, Roles and Responsibilities - https://www.ripe.net/publications/docs/ripe-763/ - provides more information about the composition and roles of the RIPE PC. Nominations for the RIPE 88 PC elections can be sent in from today, Tuesday, 14 May, until Tuesday, 21 May, 15:30 CEST (UTC+2). Please include a recent picture and short biography with your nomination. We will announce the PC elections at the RIPE meeting opening sessions, but interested parties can already nominate themselves. If you are nominating someone else, please ensure that the person concerned is willing to be nominated and is copied on emails sent to the PC. The PC will attempt to confirm that nomination with the nominee before proceeding. We will close candidate nominations on Tuesday, 21 May at 15:30 CEST (UTC+2) and publish the biographies on the RIPE Meeting web site. The RIPE PC online voting system will be open from Tuesday, 21 May, 16:00 CEST (UTC+2) until Thursday, 23 May, 17:00 CEST (UTC+2), for community members to cast their votes. The total voting numbers may be public. The official announcement of the elected RIPE PC members will be on the morning of Friday, 24 May, during the closing plenary session. Important Dates and Deadlines Nominations Open: Tuesday, 14 May Nominations Close: Tuesday, 21 May, 15:30 (UTC+2) Voting Begins: Tuesday, 21 May, 16:00 (UTC+2) Voting Closes: Thursday, 23 May, 17:00 (UTC+2) Results Announced: Friday, 24 May, during the Closing Plenary session Questions about the RIPE PC can be sent to pc [at] ripe [dot] net. Regards, Brian On Behalf of the RIPE PC Brian Nisbet (he/him) Service Operations Manager HEAnet CLG, Ireland's National Education and Research Network North Dock Two, 93-94 North Wall Quay, Dublin 1, D01 V8Y6 +35316609040 brian.nisbet(a)heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270

1 0

ASO AC Next Steps
by Mirjam Kuehne 08 May '24

08 May '24

Dear colleagues, Sander Steffann has stepped down from the ASO AC / NRO NC [1], as recently shared on the RIPE Discussion list. I would like to thank Sander for his work over the last two years on the ASO AC. Each region has three members on the ASO AC / NRO NC, which has a total of 15 members. For RIPE, two members are elected by the community and the third is appointed by the RIPE NCC Executive Board. Currently, the elected members are Sander Steffann and Constanze Bürger, while Hervé Clément has been appointed. With Sander's resignation, we have one vacant seat. From a procedural standpoint, there isn't adequate notice to hold an election at RIPE 88 to allow for a sufficient nomination period and to announce confirmed candidates (at least three weeks prior to the election). We will, therefore, hold an election to fill the vacant seat as scheduled at RIPE 89 (28 October - 1 November 2024), for a complete three year term starting in January 2026 until December 2028. The RIPE NCC will send out the call for nominations and follow the regular procedure ahead of RIPE 89. If you're interested in reading more about the election process, please take a look at The NRO NC Election Process (ripe-813). [2] We had considered filling the position temporarily. However, given that the summer break follows not long after RIPE 88, and a subsequent election is scheduled to be held at RIPE 89 in any case, we would be asking a lot of the temporary candidate for only a few weeks. We are considering updating ripe-813 to allow for short-term appointments more easily, if and when required in the future. This is an interesting moment for the ASO AC / NRO NC, which is discussing the criteria to establish new RIRs. Athina Fragkouli, the RIPE NCC's Chief Legal Officer, recently wrote a very insightful article about the process and the role communities like ours need to play in this. You can read the article on RIPE Labs [3]. If you are interested in the discussions, the ASO AC calls are open to observers, so please join in. The call schedule is available at: https://aso.icann.org/aso-ac/meetings/aso-ac-meeting-schedule/ Kind regards, Mirjam Kühne RIPE Chair ---------- [1] ASO AC / NRO NC website https://www.nro.net/about/address-supporting-organization/the-nro-number-co… [2] The NRO NC Election Process https://www.ripe.net/publications/docs/ripe-813/ [3] Criteria for the Accreditation of Regional Internet Registries https://labs.ripe.net/author/athina/criteria-for-the-accreditation-of-regio…

1 0

Seeking Input on the Future of the Anti-Abuse Working Group
by markus＠mxdomain.de 07 May '24

07 May '24

Dear Anti-Abuse Working Group Members, Thank you for your responses and support for both the WG itself and the current Co-Chairs. We are pleased to see that you prefer to keep this WG active. As Co-Chairs, we see an opportunity to broaden our scope (i.e., re-charter). Our main intention is to bring in fresh energy and perspectives by welcoming new faces. Additionally, there are relevant security topics that don't always neatly fit into other WGs. Regarding the question of what a new charter might entail, we have put together a preliminary, high level, draft that we would love to discuss further at RIPE88. — snip — Objective: The Security Working Group is committed to fostering collaboration, sharing best practices, and addressing security challenges within the RIPE community. The primary objective of the WG is to enhance the security, resilience, and stability of the Internet infrastructure within our region. Tackling abuse of Internet infrastructure and resources would remain a goal of the WG. Scope: - Identifying and analyzing emerging security threats and vulnerabilities affecting Internet infrastructure. - Collaborating with stakeholders to develop and advocate for best practices, guidelines, and standards for securing Internet resources. - Facilitating information sharing and cooperation among network operators, law enforcement, and relevant entities to mitigate security risks. - Providing education, training, and outreach initiatives to raise awareness of security issues and promote best practices adoption. - Develop policies and best practices to improve security and response to security incidents and abuse issues. — snap — We are looking forward to your input and comments. Best regards, Brian, Tobias, Markus

1 0

Sander's resignation from the ASO AC
by herve.clement＠orange.com 07 May '24

07 May '24

Dear all, I confirm that the ASO AC<https://aso.icann.org/> has recently received the formal resignation from Sander Steffann and has taken note of it. The Council is now comprised of 11 members (out of the 15 initial ones: there are currently no representatives from the AfriNIC region). Our Operational Procedures<https://aso.icann.org/documents/operational-documents/operating-procedures-…> had been amended last November and the ASO AC is able to fulfil its functions with the remaining councilors. Constanze and I will be happy to present the Council activities during our next RIPE meeting in Krakow, and answer your questions. Looking forward to seeing you very soon (in-person or remotely). Best regards Hervé ASO AC Chair ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

5 5

New Training Modules for (future) RIPE WG Chairs
by Mirjam Kuehne 06 May '24

06 May '24

Dear colleagues, As announced earlier this year, together with the RIPE NCC, we developed a second set of training modules for RIPE Working Group Chairs and those who consider volunteering for such a role in the future. The additional modules are: Module 5: How are RIPE policies made? Module 6: Building consensus Module 7: Making Sure Everyone Is Respected And Included Module 8: How do I Become a Working Group Chair? As a reminder, the other modules are: Module 1: The RIPE Community and its Structure Module 2: The Role of the RIPE WG Chair Module 3: How is Work done in RIPE Working Groups? Module 4: How do you keep a WG working? I am very pleased with the result and I would like to thank the RIPE NCC Learning & Development Team for producing such an interactive, engaging and fun course. You can access all modules here: https://academy.ripe.net/ripe-wg-chairs (You will need an SSO (RIPE NCC Access) account.) Please let me know if you have any feedback. Kind regards, Mirjam Kühne RIPE Chair

1 0

ASO AC activities / ICP-2
by herve.clement＠orange.com 05 May '24

05 May '24

Dear all, Please find below the link to the ASO AC activities report slides which have been presented during the last ARIN meeting: https://www.arin.net/participate/meetings/ARIN53/materials/monday/arin53_as… ICP-2 related activities are mentioned in pages 8 and 10 to 13. Such a presentation will be held during RIPE 88 (Address Policy Working Group on Wednesday and RIPE Community Plenary on Thursday - Meeting Plan - RIPE 88<https://ripe88.ripe.net/programme/meeting-plan/> ). Looking forward to seeing you there (on-site or remotely). Best regards Hervé ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 2

RIPE Labs article: Reflecting on the Past Decade of RIPE Meetings
by hmi＠ripe.net 02 May '24

02 May '24

Dear all, As the secretariat of the RIPE community, the RIPE NCC has had the privilege of observing and facilitating the evolution of RIPE Meetings over time. Each decision made, from the selection of venues to the design of the badges to the structuring of the Fellowship programme encapsulates, a deeper reflection of the RIPE community's core values: openness inclusion collaboration and transparency. Getting this right requires continuous dialogue, adaptability and innovative thinking within our community. I reflect on this in a RIPE Labs article which looks back at the past decade of RIPE Meetings: https://labs.ripe.net/author/hisham_ibrahim/reflecting-on-the-past-decade-o… Let's discuss more on this mailing list, at RIPE 88, or on the RIPE NCC Forum: https://forum.ripe.net/t/reflecting-on-the-past-decade-of-ripe-meetings/948 Regards Hisham Ibrahim RIPE NCC

1 0

Mastodon for the RIPE Community
by Ulka Athale 02 May '24

02 May '24

Dear all, At the last RIPE Meeting, I presented at the RIPE Community Plenary on Mastodon, asking if the RIPE NCC should run a server that would be open to community members. The presentation is at: https://ripe87.ripe.net/archives/video/1251/ The feedback we got was that this was not something we should do, or at least not right away. The main concerns were about the work involved and the difficulties in moderating a public server. Given this feedback, and considering the costs and maintenance required from our technical staff, we will not provide a server this year. However, there were also suggestions that we should dip our toe in the water. So we have started a RIPE NCC account on Mastodon that community members can follow. We hope to connect with people and also learn more about the Mastodon ecosystem. We can then revisit this question at a later date once we are familiar with the platform and we can better assess whether there is appetite for us to provide a server for the community. If you’re already on Mastodon, you can follow us at: https://mastodon.social/@ripencc. See you there! Best regards, Ulka Athale RIPE NCC

7 7

DNS Resolver Recommendations Published (ripe-823)
by Mirjam Kuehne 01 May '24

01 May '24

Dear colleagues, I am happy to inform you that the RIPE DNS Resolver Best Common Practice Task Force [1] finished its work and published a set of recommendations and best current practices for operators of DNS resolvers - now available as RIPE Document 823: https://www.ripe.net/publications/docs/ripe-823/ I would like to take this opportunity to thank all task force members for their contributions to this document and especially Shane Kerr who chaired the group and ensured that progress was made and that all feedback was heard and considered by the task force. Kind regards, Mirjam Kühne RIPE Chair [1] The RIPE DNS Resolver Best Common Practice Task Force https://www.ripe.net/community/tf/dns-resolver-best-common-practice-task-fo…

1 0