Skip to main content

RIPE 89 - RIPE Community Plenary Minutes

Date: 31 October 2024, 16:00 – 17:30 (UTC+1)
Location: RIPE 89 Meeting
Chair: Mirjam Kühne, RIPE Chair
Scribe: Ulka Athale
Status of the Minutes: Draft

Links to resources:

Mirjam welcome everyone to the community plenary and wished those celebrating the festival of light a happy Diwali.

1. RIPE Chair Update

Mirjam Kühne, RIPE Chair

The presentation is available at:
https://ripe89.ripe.net/presentations/118-RIPE-89-Community-Plenary-.pdf

Mirjam presented the update from the RIPE Chair team with activities since RIPE 88 including the draft RIPE document on the relationship between RIPE and the RIPE NCC.

Brad Raymo, Zscaler, a newcomer to RIPE, expressed challenges in finding support for first-time attendees, such as mentorship and networking opportunities. Brad said that he had expected to receive a bit more guidance.

Mirjam acknowledged Brad’s feedback and said there is a mentoring programme, but this could be looked into further.

2. Community-Sourced Translations

Fergal Cunningham, Head of Membership Engagement, RIPE NCC

The presentation is available at:
https://ripe89.ripe.net/presentations/134-Community-Sourced-Translations-RIPE-89.pdf

Fergal Cunningham outlined the RIPE NCC’s new language centre, offering materials in six languages on the website. Fergal highlighted the importance of community volunteers for accurate technical translations. He emphasized the complexities of translating technical terms while retaining context, a challenge compounded by the specific jargon used within the technical community.

Piotr Strzyżewski, speaking in a personal capacity, noted the importance of context in translation. He shared an example from his previous efforts assisting the RIPE NCC with translations, he had tested out ChatGPT and Google Translate and they failed to translate the text accurately in the context.

Andreas Harpfer asked whether it would make sense to start with a glossary of technical terms before working on translations.

Fergal replied that a glossary was a great idea, and that the NCC is looking to add more languages.

Lars-Johan Liman, Netnod, suggested building up the glossary over time, so that it doesn’t become a separate task, and that the RIPE NCC should store this.

Marc van der Wal, AFNIC, said that the hardest part with translations is making sure that translated content stays in sync with the original content. He asked if there was a plan to make sure that the translations stay up to date.

Fergal replied that the RIPE NCC doesn’t plan to update content very often but it is likely to be every quarter. The RIPE NCC is looking into software that can keep track of this.

3. 10 Years of the RIPE NCC Academy

Pedro Vaz, RIPE NCC

The presentation is available at:
https://ripe89.ripe.net/presentations/14-RIPE-89-Academy.pdf

Pedro Vaz celebrated the 10th anniversary of the RIPE NCC Academy, recounting its evolution from in-person training to a dynamic online learning platform. He presented the academy’s latest offerings and shared insights on popular courses, such as IPv6 fundamentals and BGP security. Vaz also discussed future plans, including advanced IPv6 courses and learning paths.

Dirk Meyer, Dinoex Servator NCK, participating online, asked about Firefox support in the academy platform. Pedro confirmed that the Academy is compatible with Firefox.

4. Report from the ASO AC and ICP-2 Community Consultation

Hervé Clément and Constanze Bürger

The presentation is available at:
https://ripe89.ripe.net/presentations/126-2024-10-31-ASO-AC-ICP2-RIPE-89.pdf

Hervé Clément and Constanze Burger provided an update on the ASO AC's activities, focusing on the ICP-2 document, which defines criteria for recognizing new Regional Internet Registries (RIRs). Given significant changes since the document’s original drafting, they emphasized the need for community input to refine its criteria.

Lu Heng, Larus, asked if community feedback on the ICP-2 would be summarized and shared. He also asked about a mailing list to have a discussion.

Hervé assured him that the NRO NC would consider all input and planned an additional consultation round. He clarified that there were concerns over potential workload issues with managing community comments, but that the NRO NC would be transparent. He encouraged participants to provide detailed feedback through the questionnaire, assuring that all input would be carefully considered.

Peter Koch, DENIC, asked about the procedural framework guiding the ICP-2 update, and whether it was following the global policy process.

Hervé clarified that the ICP-2 document was not a global policy, but the NRO NC would present the document to the NRO EC and the community for feedback and approval from ICANN at the end.

Hans Petter Holen, RIPE NCC CEO, explained that there had been a long discussion about whether this is a global policy, but it is not. The process being followed is similar to the original process while drafting ICP-2.

Randy Bush, IIJ, asked about the name of the document, suggesting it should be called ICP-3 instead of updating ICP-2.

Hervé responded that the naming of the document was still under consideration, while Hans Petter Holen, NRO EC Chair, provided historical context on the ICP document series, acknowledging the potential for confusion and suggesting a possible new document series under NRO for clarity

5. IANA Update

Kim Davies, IANA

The presentation is available at:
https://ripe89.ripe.net/presentations/74-iana-ripe89-202410.pdf

Kim Davies shared updates on IANA’s handling of IP resources, DNSSEC, and the upcoming root zone key signing key rollover. He noted the IPv4 resource depletion and clarified IANA’s role in IPv6 allocations, underscoring the extensive availability of IPv6 space. Davies also highlighted new strategic planning initiatives aimed at community alignment.

Shane Kerr, IBM, questioned IANA's preparedness for quantum-safe cryptography given future rollovers.

Kim replied that a community design team established a set of recommendations on how to do algorithm changes in the root zone. IANA’s internal project team was about to start developing the 2029 rollover, including an assessment of algorithms. The 2026 rollover will use the same algorithm but if all goes to plan, 2029 will be the first opportunity to change the algorithm.

Janos Zsako, .hu, asked when IANA plans to have the first post-quantum cryptography. He asked if this would influence the HSM as well and whether the key ceremonies will have to be redesigned.

Kim said the dynamics of how signatures and root zones are used have to be studied, the algorithm change process commits to an assessment every three years of what the landscape looks like.

6. RIPE Code of Conduct Team Community Update

Franziska Lichtblau, RIPE Code of Conduct Team

The presentation is available at:
https://ripe89.ripe.net/presentations/133-RIPE89_CoC_Community_Pleanary-2.pdf

Franziska Lichtblau reviewed the Code of Conduct team’s activities since its formation, emphasizing the team’s commitment to transparency. She detailed the establishment of contact protocols with RIPE NCC for report handling, clarified the team’s relationship with Working Group Chairs, and outlined proposals for procedural changes to streamline operations. Lichtblau also introduced a discussion around the new RIPE Meeting media policy to ensure press interactions are handled appropriately.

Leo Vegoda, chair of the task force that developed the Code of Conduct, said that he had expected that there would be adjustments and that he supported the proposed changes.

Patrick Bussman, Akamai, thanked Franziska and the Code of Conduct team and their work, saying that it is a role model for many NOG communities.

He asked about the media policy allowing for free tickets to the meeting, saying that the RIPE community is proud of sharing the load by paying for their own ticket. He said there should be a bit more discussion about this.

Ulka Athale, RIPE NCC, said that as someone involved in drafting the media policy, the input from the communit was welcome. She clarified that the Code of Conduct applies to accredited media representatives and that their accreditation can be revoked if they fail to abide by the Code of Conduct.

Tina Morris, AWS, said that the community is very open and it’s important that people can stay that way. She said press should be very visible with a different lanyard.

Sander Steffann thanked the Code of Conduct team for the work they are doing.

7. The Next RIPE NomCom Process

Jan Zorz, RIPE NomCom Chair

The presentation is available at:
https://ripe89.ripe.net/presentations/104-RIPE-NOMCOM-call-for-volunteers.pdf

Jan Žorž outlined the NomCom process for selecting the next RIPE Chair and Vice-Chair, discussing the timeline and qualifications for NomCom members. He encouraged community volunteers to participate and reviewed the procedural steps, stressing the importance of adherence to the established timeline.

Kurt Kayser asked why the RIPE NCC Executive Board needed to confirm the NomCom selections.

Daniel Karrenberg clarified the RIPE NCC Board’s role in confirming NomCom selections, emphasizing that it serves as a procedural check and is not a decision on candidates.

Franziska pointed out that RIPE 714 states that RIPE is not formally represented in other organisations, therefore the RIPE Chair does not formally represent RIPE anywhere. However, this is not how things might be perceived by other communities.

Jan said that the role description of the RIPE Chair might need to be updated but it should be done over the coming five years.

Leo Vegoda asked if online attendance at RIPE Meetings counts for the eligibility criteria for the NomCom.

Jan clarified that it does.

Hans Petter Holen, speaking as a former RIPE Chair, pointed out that it might be worth reviewing the RIPE Chair role description before the current selection process with input from the current Chair team.

Christian Kaufmann, former RIPE NCC Executive Board member, said that the NomCom’s task is to find a suitable RIPE Chair. The discussion on the RIPE Chair’s role should take place through a different channel.

Anna Wilson, HEAnet, said, having been involved in several discussions setting up this process, the RIPE Chair selection does provide an opportunity to look at how documents fit RIPE today. Anna reiterated the importance of following the existing process and not changing things midway, and thanked Jan for taking on this important task.

Tobias Fiebig said that he didn’t have a lot of experience on committees but his gut feeling said to start the process with the committee as advised by Jan.

Daniel Karrenberg emphasized that the scope of the NomCom is deliberately narrow and that processes should not change when they are under way.

Mirjam thanked Jan and all the attendees and concluded the session.