- ripe-list - mailman.ripe.net

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

RIPE 88: Less than four weeks to go!
by RIPE Meeting 29 Apr '24

29 Apr '24

Dear colleagues, RIPE 88 is approaching and we wanted to give you an update about the meeting. You can still register for RIPE 88 if you haven't registered yet: https://ripe88.ripe.net/attend/register/ RIPE 88 will take place at Metropolo Hotel by Golden Tulip in Krakow, Poland from 20-24 May 2024. ------------- Ticket Options ------------- Week ticket: EUR 400 Day ticket: EUR 130 Student (week) ticket: EUR 50 You can find more information about ticket options at: https://ripe88.ripe.net/attend/register/ ------------ Draft Agenda ------------- We have published the draft agenda for the plenary sessions, and Working Group agendas are being added as they come in. Curious about what you can expect at RIPE 88? Take a look at: https://ripe88.ripe.net/programme/meeting-plan/ --------------------- Newcomer's Information --------------------- Is this your first RIPE Meeting? Welcome you to the RIPE community. Please participate in our newcomers’ activities so that you can find your way to things that interest you, and have a productive and fulfilling RIPE Meeting! You will find more information here: https://ripe88.ripe.net/attend/first-ripe-meeting/ ------------- Parallel Events ------------- As always, there are plenty of things going on in parallel with a busy RIPE Meeting week. You can get certified, or join in the Academic and NREN reception. Get the details at: https://ripe88.ripe.net/programme/parallel-events/ ------------- On-site Childcare ------------- Reminder: If you're bringing your little ones to RIPE 88, please make sure that you inform us about your childcare requirements before *5 May*. We have limited spaces. For more information, visit: https://ripe88.ripe.net/attend/diversity/childcare/ ------------- Social Events ------------- Get ready to network and enjoy meeting your fellow attendees. Take a look at our social events: https://ripe88.ripe.net/programme/social-events/ ------------- Safety and Accessibility Information ------------- We want all our attendees to enjoy a safe RIPE Meeting in Krakow. Please take a look at our webpages with information on health, safety and security: https://ripe88.ripe.net/attend/safety-and-security/ And if you have an requirements for accessibility, please get in touch with us. We have published accessibility information, and will add to it as we get closer to the meeting. You can find this information at: https://ripe88.ripe.net/attend/accessibility/ ---------------- Important Dates and Deadlines ---------------- 5 May: Mentoring application deadline 5 May: Childcare application deadline 10 May: Lightning Talk submissions accepted 13 May: Deadline to send recorded presentations to be published on the website 20-24 May 2024: RIPE 88 takes place in Krakow More information on RIPE 88 can be found at: https://ripe88.ripe.net/ Track the #RIPE88 hashtag on social media for the latest updates. See you in Krakow! Kind regards, RIPE 88 Meeting Organisation Team

1 0

Internet: Rewilding vs Climate Change / Environmental Impact
by Vesna Manojlovic ＠ RIPE.net 27 Apr '24

27 Apr '24

Dear colleagues, For this month's news about environmental impact of technology, please find below links to three interesting blog posts, from the members of RIPE & adjacent communities. * We Need To Rewild The Internet, BY MARIA FARRELL AND ROBIN BERJON https://www.noemamag.com/we-need-to-rewild-the-internet > The internet has become an extractive and fragile monoculture. > But we can revitalize it using lessons learned by ecologists. * Blog by Dan York, Director of Internet Technology at ISOC: "The Internet and Climate Change" https://www.internetsociety.org/blog/2024/04/the-internet-and-climate-chang… * Blog by Stéphane Bortzmeyer (in French): "RFC 9547: Report from the IAB Workshop on Environmental Impact of Internet Applications and Systems, 2022" https://www.bortzmeyer.org/9547.html Regards, Vesna -- Senior Community Builder RIPE NCC

1 0

Routine Monitoring of Source Address Validation Deployment by Operators
by Brandon Zhi 26 Apr '24

26 Apr '24

Dear MANRS and RIPE members, My name is Gaoxing Zhang, and I am a computer enthusiast from the High School Competition Team at Hangzhou Dongfang High School. Recently, I've observed that although MANRS requirements mandate Source Address Validation(SAV) for its members, some operators have not fully implemented this practice in their networks. Therefore, I propose to routinely monitor the deployment status of SAV across ASNs to ensure compliance with MANRS guidelines and enhance network security. I am currently unaware of any existing projects with a similar focus. It has come to my attention that operators at IXP facilities, even including major entities like Google, fail to enable SAV. This issue also persists in-home broadband services obtained through PPPoE, which could lead to Infected Home Routers becoming sources of DDoS Attacks and Are Difficult to Trace. In my tests, I announced my IP thought tunnel on a different operator’s network and configured the Next-hop Address to a home broadband gateway obtained via PPPoE. The results indicated that Source Address Validation by China Telecom’s home broadband is only partially implemented in Mainland China, with most IP addresses from the region being accessible through this method. Here are some methods I have considered for ongoing monitoring: 1. Announce a new IP block upstream to receive inbound traffic. 2. Deploy a tunnel on the device connected to the ISP being tested, which will link to the upstream receiving the inbound traffic. 3. The IP block will not be announced to the ISP being tested but only to the upstream used to receive inbound traffic. Check the connectivity to major public DNS servers when the Next-hop address is set to the ISP being tested. 4. If it is reachable, it indicates that the ISP’s device lacks Source Address Validation. I plan to deploy test equipment at major IXPs (currently seeking equipment sponsors) and access points for some residential ISPs (with the assistance of volunteers). The testing environment will be a Linux-based VM, utilizing Python to switch Next-hop based on test targets and assess the accessibility to major public DNS servers, as well as to upload data to a backend system. I would really appreciate it if you could share your valuable suggestions or feedback on this initiative. Best regards, *Brandon Zhang* HUIZE LTD www.huize.asia <https://huize.asia/>| www.ixp.su | Twitter This e-mail and any attachments or any reproduction of this e-mail in whatever manner are confidential and for the use of the addressee(s) only. HUIZE LTD can’t take any liability and guarantee of the text of the email message and virus.

2 1