Summary

  • RIPE 86 was held in Rotterdam from 22 to 26 May 2023. There was no RIPE meeting in Rotterdam in October 2023; the second-half-2023 meeting was RIPE 87 in Rome, 27 November to 1 December 2023.
  • The meeting's substantive record covers routing-security operationalisation, IPv6 deployment guidance, address-policy simplification proposals, an IXP route-server filtering reform timed for 1 January 2024, and the first Code of Conduct Team at any RIPE meeting.
  • The co-located RIPE NCC General Meeting (24–26 May 2023) adopted the Charging Scheme 2024 Model D, rejected a €50 per-ASN surcharge and a €500 per-transfer-request surcharge, and elected Raymond Jetten, Maria Häll and Harald A. Summa to the Executive Board.
  • The record has stated limits: the General Meeting minutes are labelled draft, several working-group accounts were reviewed through secondary retrieval rather than full-page inspection, and one RIPE 86 page could not be retrieved at all.

The numbering, corrected with dated evidence

The meeting archive lists RIPE 86 as 22–26 May 2023 in Rotterdam, the Netherlands, and places RIPE 85, two numbers earlier, in Belgrade from 24 to 28 October 2022 — an October slot, but a different meeting and a different year Previous RIPE Meetings archive. The archive also places RIPE 87 in Rome from 27 November to 1 December 2023, and the RIPE 87 calendar entry fixes those dates, closing the 2023 calendar with no October meeting between them RIPE 87 calendar entry. The dedicated meeting site carries the same identification — Rotterdam, the Netherlands, 22–26 May 2023 RIPE 86 meeting site — and the RIPE NCC's news item dated 22 May 2023 records Chair Mirjam Kühne opening the meeting that day at 14:00 local time (UTC+2) RIPE 86 Begins Today.

The October association does not survive the record. The RIPE NCC's forward-looking listing shows the meetings that actually followed — Sofia in October 2026, then a May 2027 meeting — and contains no event labelled RIPE 86 Upcoming RIPE Meetings. One RIPE 86 web page could not be retrieved during research for this briefing RIPE 86 participate page; that access limit is recorded here rather than resolved by assumption. BTW's directory record for the entity is linked at the RIPE 86 directory entry.

What the working groups recorded

Routing security was the densest thread. On Wednesday 24 May 2023 (09:00–10:00 UTC+2), the Routing Working Group — chaired by Ignas Bagdonas, Paul Hoogsteder and Job Snijders — heard RIPE NCC's Ties de Kock report that certificates under the RIPE NCC RPKI trust anchor had reached 20,000 Routing WG minutes, RIPE 86. The same update covered Publish in Parent, announced at RIPE 85; an ASPA implementation in the pilot public API; and a public status page. Planned work included rsync capacity, a from-scratch RPKI dashboard rewrite, compliance against the ISAE 3000 control framework, hardware security module replacement, and bringing ASPA into the production API once the standard is ratified. Job Snijders presented RPKIviews, an archive of RPKI data from multiple vantage points, and asked the community for hosting and storage support. Ben Cartwright-Cox presented Realtime bgp.tools, One Year On, covering IXP route collection, comparisons with RIPE RIS, and deployments at NL-IX and South African IXPs. The session also produced a leadership change: Snijders stepped down as co-chair, and Cartwright-Cox was selected as the new co-chair after a humming vote, weighed with RIPE Chair Mirjam Kühne.

The IPv6 session stayed on deployment practice IPv6 Working Group minutes, RIPE 86. RIPE NCC's Learning and Development team sought input for an advanced IPv6 e-learning course. Rinse Kloek (Delta Fiber / Kindes) described the choice between IPv6 and CGNAT deployment from an operator's seat. Wilhelm Boeddinghaus (Route 128) asked the community for clearer IPv6 deployment guidance aimed at enterprise IT departments. Fernando Gont (SI6 Networks) presented remotely on the security challenges that accompany IPv6 deployment. Ondrej Caletka (RIPE NCC) closed with a practical request: test the IPv6-only network, identify issues, and report them to vendors.

The Address Policy Working Group worked on simplification Address Policy WG minutes, RIPE 86. A review of IPv6 policy named unclear documentation requirements for large allocations, complex language around the HD-ratio, address space handed out off nibble boundaries, and limits on PI assignments. The desired outcomes were predictable documentation requirements, a revisit of the HD-ratio to match how engineers actually plan, nibble-boundary allocations, and PI assignments keyed to the organisation managing the network, with needs requirements eliminated up to /44. The room raised no objections, and a mailing-list recap was proposed to test workable per-topic changes. Two proposals surfaced alongside: a default /26 assignment for new IXPs, with a /24 requestable once more than half is in use — set against an expected IXP IPv4 pool depletion around 2029 — and an AGGREGATED-BY-LIR status for IPv4 PA assignments, discussed amid noted non-compliance by a large share of LIRs. Chair term limits also came up, framed as a stability and rotation question.

The Connect Working Group carried the filtering reform Connect WG minutes, RIPE 86. Stavros Konstantaras presented work by several IXPs toward a common policy for route-server filtering: IXP operators would build and maintain filters only from the AFRINIC, APNIC, ARIN, LACNIC and RIPE databases, effective 1 January 2024, with a twelve-month grace period in which RADB, RIPE-NONAUTH, NTT and LEVEL3 would also be accepted.

Meeting-wide, the Chair Team's report framed regulation, proposed legislation and public policy as recurring themes across plenaries and working groups The RIPE Chair Team Reports: Highlights from RIPE 86. Two parallel Tuesday BoFs covered artificial intelligence and an IETF overview. A BCOP session addressed the DNS Resolver Task Force recommendations and a call to document best practices for keeping networks running through natural disasters or war, work that led to interviews with Ukrainian network operators. A Diversity in Tech session focused on youth and newcomers, after an online student event increased Dutch student participation. Leo Vegoda questioned whether mailing lists remain the right communications channel; Henrik Kramselund proposed a newcomers' guide to the Internet. RIPE 86 also fielded the first Code of Conduct Team at any RIPE meeting; its trained members presented a transparency report at the closing plenary.

The General Meeting outcome

The RIPE NCC General Meeting ran 24–26 May 2023 inside the RIPE 86 week, with voting results announced on Friday 26 May at 10:30 (UTC+2) General Meeting May 2023. The published minutes — labelled draft — record six resolutions Draft minutes of the General Meeting, May 2023: Resolution 1 adopted the 2022 Financial Report; Resolution 2 discharged the Executive Board for its actions under the 2022 Annual Report and Financial Report; Resolution 3 adopted the RIPE NCC Charging Scheme 2024 Model D; Resolution 4, an extra €50 charge per ASN, was not approved; Resolution 5, an extra €500 charge per accepted transfer request, was not approved; and Resolution 6 adopted amendments to the Standard Service Agreement. Raymond Jetten, Maria Häll and Harald A. Summa were elected to the Executive Board. The RIPE NCC Services Working Group session from the same week is also archived RIPE NCC Services WG minutes, RIPE 86.

Where the record is thin

Three limits deserve attention. The General Meeting minutes carry a draft label, and the vote tallies behind the six resolutions are not established in the material reviewed for this briefing. Several working-group accounts were reviewed through secondary retrieval rather than full-page inspection, so this briefing attributes rather than quotes. And the attendance of the meeting cannot be established from the sources cited here; figures in circulation elsewhere were not verifiable against the record above.

What the record does establish — dates, place, chair, working-group decisions, the filtering deadline, the charging outcome and the board election — is enough to anchor RIPE 86 correctly: number 86 is Rotterdam, May 2023; number 87 is Rome, November–December 2023; and the October 2026 meeting that some searches conflate with this number is RIPE 93 in Sofia.