Summary

  • RIPE NCC’s June member update listed an IPv6 Security Training Course in Oslo for Friday 14 August 2026.
  • The course page describes a one-day, member-only programme with theory and hands-on work for people who already have advanced IPv6 knowledge.
  • Its published scope spans IPv6 protocol surfaces, filtering, denial-of-service considerations and transition mechanisms; the sources do not report attendance, delivery or outcomes.

A scheduled operating exercise, not an incident report

RIPE NCC listed the Oslo course in its public June member update as an upcoming activity for Friday 14 August. That is the event the sources establish: a scheduled, RIPE NCC-presented training day in Oslo. Neither official page says how many people registered, whether the class ran as scheduled, what operators changed afterwards, or whether any particular network was assessed.

The distinction matters. A course listing is useful evidence that a registry sees an operating subject as worth teaching to its member community. It is not evidence of a newly disclosed IPv6 vulnerability, an outage, a compliance obligation or a measured weakness in a named operator.

The published curriculum points to control surfaces

The course description calls for advanced IPv6 experience and combines theory with practical work. Its listed material covers IPv6 headers, extension headers and addressing; ICMPv6, NDP, MLD, DNS and DHCPv6; and operational areas including filtering, denial-of-service issues and transition technologies.

These are not interchangeable controls. Addressing and extension-header handling concern how traffic is interpreted. ICMPv6, NDP and MLD place neighbour and multicast behaviour at the network edge. DNS and DHCPv6 add service dependencies. Filtering and DDoS planning concern the point at which a team converts that protocol knowledge into a repeatable protection and recovery practice. RIPE NCC’s description also names the intended audience broadly: staff at LIRs with IPv6 experience, network or system administration responsibilities, consulting roles or policy-writing responsibilities.

Why a one-day course still deserves a bounded watch

For NOG readers, the relevant signal is the connection between protocol literacy and operational change control. A team can have IPv6 address space in service while still carrying older assumptions about filtering, neighbour discovery or transition paths. Training cannot prove those assumptions were corrected, but it can provide a common vocabulary for testing them.

The official material sets an equally important boundary. It explains the course’s aims — recognising threats, understanding associated protocols and applying filtering approaches — but it does not publish a course-specific checklist, a participant assessment, configuration guidance for a named network or an incident dataset. Readers should treat it as a scheduled capacity-building event, not as a substitute for their own architecture review.

Evidence boundary

The date, location, organiser, member restriction and course outline come from RIPE NCC. The pages do not establish completion, attendance, participant identity, local timezone beyond the listed date, or effects on any deployment. A stronger assessment would require a post-course record from RIPE NCC or independently attributable operational evidence.

Sources