- ripe-list - mailman.ripe.net

RIPE 88 Starts Today
by RIPE Meeting 20 May '24

20 May '24

Dear colleagues, RIPE Chair Mirjam Kühne will open the RIPE 88 Meeting in Kraków today at 14:00 local time (UTC+2). You can follow the meeting online via the live webcast: https://ripe88.ripe.net/live/ <https://ripe88.ripe.net/live/main/> If you would like to chat with other RIPE community members and ask questions, you need to register as an online participant. Registration for online participation is free, and you will receive a link to Meetecho, our online platform. Register at: https://ripe88.ripe.net/attend/register/ <https://ripe88.ripe.net/attend/register/> Track #RIPE88 on X(Twitter), Mastodon, Instagram, Facebook, and LinkedIn to stay up-to-date with all RIPE Meeting updates. Best regards, RIPE Meeting Team

2 1

Three Appeals
by Daniel Karrenberg 20 May '24

20 May '24

Web version: https://web.karrenberg.net/krakowappeal.html # Three Appeals I have observed the recent discussions in the community and the RIPE NCC membership. Here are three personal appeals for these discussion as we meet in Krakow and on the Net. ## === Modern Version === ### 1. Be Proud of RIPE Let us be proud! Together we have built a strong community and an exemplary way of self governance. Let us cherish what we have and develop it further by consensus. ### 2. For a Strong RIPE NCC Let us support the RIPE NCC. A strong RIPE NCC is more than just a registry: it is a neutral place where the community does things together. Let us avoid weakening it by exaggerating its shortcomings but rather evolve it in deliberate steps by consensus. A strong RIPE NCC benefits everyone. ### 3. No Fake Solutions Let us not fall for divisive rhetoric and seemingly easy and convenient solutions. Most everyone wants to pay less for the same benefit. More often than not, after deciding to pay less one discovers that the benefit is not quite the same. Let us not focus on the cost first but constructively build consensus to evolve the RIPE NCC in the direction we want and only then decide how we split the costs. ## === Classic Version === ## Who is talking? For those who do not know me well, here is my background so you know where I come from when I speak up: My name is [Daniel Karrenberg](https://en.wikipedia.org/wiki/Daniel_Karrenberg). I have been involved with RIPE and the RIPE NCC from the very beginning. I have [helped to create RIPE in 1989](https://www.ripe.net/membership/meetings/ripe-meetings/ripe-1/) while I was busy bringing the Internet to the region. I helped to create the [proposal for a RIPE NCC](https://www.ripe.net/publications/docs/ripe-019/). In 1992 I took responsibility for [implementing that proposal](https://labs.ripe.net/author/dfk/25-years-of-the-ripe-ncc-the-fir… and became the first employee of the RIPE NCC and its first CEO. I helped to create [the initial versions of many RIPE NCC services](https://www.ripe.net/publications/docs/ripe-062/) including the first two versions of the RIPE Database software. During the first year of the RIPE NCC the first Internet boom hit and the RIPE NCC needed to meet entirely unforeseen demands. I resisted the temptations of the boom and decided to stick with the NCC during this challenging time. At the start of this century I stepped down as CEO and went on to help build new RIPE NCC sevices, such as [RIPE RIS](https://www.ripe.net/analyse/internet-measurements/routing-information…, [RIPE Atlas](https://atlas.ripe.net/) and [RIPEStat](https://stat.ripe.net/). During the following decade I stepped back from operational resposibilities and became an advisor to the RIPE NCC CEO; I still advise him on a part-time basis which makes me the [longest serving RIPE NCC employee](https://www.ripe.net/media/documents/Daniel_Karrenberg_30_Years_a…. Recently I have helped to build consensus about RIPE self governance by authoring documents describing [the role of the RIPE Chair](https://www.ripe.net/publications/docs/ripe-714/) and [the RIPE Chair selection process](https://www.ripe.net/publications/docs/ripe-787/). I have subsequently led the first round of that process as chair of the [2020 RIPE Nominating Committee](https://www.ripe.net/publications/docs/ripe-762/). Currently, on request of the RIPE Chair, I am drafting a document on the community consensus about the current state of the relationship between RIPE and the RIPE NCC. I am also looking forward to advise the next RIPE Nominating Committee in my role as the *previous chair*. So far my history with this community. This should let you draw your own colclusions about my biases and the merit of what I have to say. Now for the longer version of my appeals: ## 1. Be Proud of RIPE Let us be proud! Together we have built a strong community and an exemplary way of self governance. Let us cherish what we have and develop it further by consensus. We are currently facing many challenges such as - renewing our community and bringing in young people, - improving our leadership, f.i. working group chairs, - operating in a climate of raising geopolitical tensions and sanctions, - IPv4 addresses becoming a commodity, - defending against attacks on the RIR system such as the one on AFRINIC, - evolving the relationship between RIPE and RIPE NCC - BoF in Krakow on Tuesday evening -, - . . . At the same time the climate of public discourse in general has become more hostile and divisive. Whole countries are facing a divided population, sometimes close to 50/50. People concentrate more on what divides them rather than on what unites them. Ironically some believe that our very Internet has been a major instrument for this to happen. We should not follow this trend! I fear that significant divisions in our community and a hostile discourse will damage our standing and our credibility as a self governing community. We should be proud of the unique community we have built and the exemplary self governance we have created, especially in the area of Internet Number Resources or as we like to call it *Address Policy* and the *RIPE Registry*. Our community has been leading the world in this and we should be proud of it and build on that success. I do not mean to say that we do not need to evolve. To the contrary! We should do this in our successful tradition of constructive discourse leading to rough consensus. ## 2. For a Strong RIPE NCC Let us support the RIPE NCC. A strong RIPE NCC is more than just a registry: it is a neutral place where the community does things together. Let us avoid weakening it by exaggerating its shortcomings but rather evolve it in deliberate steps by consensus. A strong RIPE NCC benefits everyone. Some argue that the RIPE NCC should be reduced to *just the registry* or that they do not benefit from *all the extra activities*. This is a dangerous view to take. The RIPE NCC is strong and stable just because it is more than a registry. The RIPE NCC was established from the start as a neutral and trustworthy place where the community organises common activities while being fiercely competitive elsewhere. Such a place is worth preserving all by its own. The RIPE NCC is uniquely placed for some of these activities such as neutral Internet measurements and promoting our self governance. It is stronger and less prone to hostile takeovers than just a bookkeeping function. I do not propose that everything the RIPE NCC does should be done forever, including the activities I helped to create. The RIPE NCC does what the community and the membership want. We have always reviewed and updated the RIPE NCC Activity Plan. I fear that weakening the RIPE NCC may destroy the unique resource that we have created and, once weakened, it will be difficult or even impossible to re-build its strength when we need it. We all benefit from a strong and well recognised RIPE NCC whether we individually benefit from all its activities or not. ## 3. No Fake Solutions Let us not fall for divisive rhetoric and seemingly easy and convenient solutions. Most everyone wants to pay less for the same benefit. More often than not, after deciding to pay less one discovers that the benefit is not quite the same. Let us not focus on the cost first but constructively build consensus to evolve the RIPE NCC in the direction we want and only then decide how we split the costs. Of course the RIPE NCC and its activities need to evolve with the changing environment and the changing needs of both the membership and the RIPE community at large. Starting this process by proposing to reduce the costs for individual members however is the completely wrong way around. We should first achieve consensus on what we want from the RIPE NCC and then talk about how we split the cost. Our governance is designed such that RIPE and the RIPE NCC association cooperate. In short it works like this: - RIPE provides guidance to the RIPE NCC, - the RIPE NCC board elected by the paying membership decides on the activities, and - hires the management to get them done. - The management proposes a budget, and - the board decides the budget. - The board proposes a charging scheme to divide the cost, and - the membership votes on that. Evolving the RIPE NCC starts with the RIPE community and with the RIPE NCC membership. We give guidance to the board. The membership elects that board. So we should provide this guidance and elect those people. We should be prudent in this and avoid falling for divisive polemics and seemingly easy solutions. If we screw this up we may very well lose what we have built up over a long time with considerable effort. Let us continue our tradition of constructive discussions leading to rough consensus and the selection of good people. We have shown that we can do that and we will continue to be successful and, importantly, continue to have some fun together.

1 0

BoF session at RIPE 88 - Building a stable future for the RIPE NCC
by Remco van Mook 16 May '24

16 May '24

Dear colleagues, Following up on my email from April about the RIPE Labs article about this topic, I’d like to draw your attention to the fact that the program committee has approved a BoF session at RIPE 88, on Tuesday May 21st between 1800 and 1900 CEST. I’m very much looking forward to see you there and listen to your ideas. In order to have a bit of structure in our discussion I have prepared a slide deck, which you can find linked from this page: https://ripe88.ripe.net/programme/meeting-plan/bof/ Kind regards, Remco van Mook

1 0

ICANN/IANA FY25 Operating Plan and Budget and ICANN FY25-29 Operating and Financial Plan
by Ulka Athale 16 May '24

16 May '24

This message is sent on behalf of the Number Resource Organization -------------------------------- Summary -------------------------------- ICANN has approved and published the operating plan and budget for ICANN and IANA for the financial year 2025, as well as the ICANN 25-29 Operating and Financial Plan. As a Decisional Participant, the Address Supporting Organisation (ASO) is required to inform its community about these documents. Further, anyone who objects to these can submit a Rejection Action Petition during the Rejection Action Petition Period. This petition period will end on 31 May 2024 at 06:59 UTC. The announcement is available at: https://www.nro.net/notice-to-the-aso-community-on-rejection-action-petitio… -------------------------------- ICANN/IANA FY25 Operating Plan and Budget and ICANN FY25-29 Operating and Financial Plan -------------------------------- ICANN has approved the following budgets: - IANA FY25 Operating Plan and Budget - ICANN FY25 Operating Plan and Budget - ICANN FY25-29 Operating and Financial Plan The resolutions approving the Operating Plans and Budgets are available at: https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… The IANA FY25 Operating Plan and Budget is available at: https://www.icann.org/en/system/files/files/adopted-iana-op-budget-fy25-202… The ICANN FY25-29 Operating and Financial Plan (pages 1-126) and FY2025 Operating Plan and Budget (pages 127-245) are available at: https://www.icann.org/en/system/files/files/adopted-fy25-29-operating-finan… Under the ICANN Bylaws, the Empowered Community now has the opportunity to consider whether it will reject the Board’s approval. During Rejection Action Petition Periods any individual may submit a petition to any Decisional Participant, seeking to reject the Board action. This petition period will end on 31 May 2024 at 06:59 UTC Please refer to Article 2, Annex D of the ICANN Bylaws for additional details on the Rejection Process, including all pertinent deadlines and requirements for Rejection Action Petitions: https://www.icann.org/resources/pages/governance/bylaws-en/#annexD Any Rejection Action Petition should be sent to the ASO Secretariat ( secretariat(a)aso.icann.org ) before the deadline. Regards, ASO Secretariat -------------------------------- Kind regards, Ulka Athale Senior Communications Officer RIPE NCC

1 0

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