Transitioning to IPv6 · Tech & Meet

I attended an IPv6-focused Tech & Meet session at Howest University of Applied Sciences, led by Nico Declerck. Networking talks aren't always the most exciting to a security student, but this one landed differently: it reframed IPv6 less as "the protocol we'll all switch to one day" and more as "the operating reality you're already living with, whether or not your stack admits it."

Nico delivered a clear and eye-opening overview of why moving toward IPv6-only networks is no longer optional but essential. He walked through the long-standing limitations of IPv4, the ongoing address shortage, and why leaning on NAT and especially CGNAT isn't a sustainable path forward, particularly when modern cloud environments still depend on legacy IPv4 in oddly ironic ways: shiny new infrastructure propped up by a 1980s scarcity workaround.

What the session covered

• Why IPv6 matters: the long-term benefits, the operational simplifications, the security side-effects of dropping NAT layers, and the urgency to adopt it before policy forces the issue.
• Transitioning to IPv6-only: what organisations should expect when they commit to dropping IPv4, and how to ramp up gradually instead of doing it in one painful weekend.
• Dual stack in practice: why dual stack is an interim strategy and not the end goal, and what it costs to deploy IPv6 today in terms of routing, address planning, firewall posture, and monitoring.

Why this resonated with me

A few angles made the talk feel more relevant than I expected:

• Security implications. IPv6 changes the shape of the perimeter. Native end-to-end addressing means firewall rules and segmentation get more important, not less. That's directly relevant to anyone doing defensive or DFIR work.
• Career relevance. Most enterprise networks I'll touch in the next decade will be running mixed stacks. Knowing the actual transition mechanics, not just the textbook version, is useful capital.
• Avoiding the trap. Dual stack is comfortable, which is exactly why teams stay in it too long. Treating it as a destination is a slow form of debt.

Practical tips Nico shared

• Start with clients and guest networks: it's lower-risk than touching production routing first.
• Build hands-on experience early, even in lab environments, so the muscle memory is there when migration becomes mandatory.
• Treat IPv6 as the new default, not a sidecar. The longer you delay the cognitive switch, the harder the eventual cutover.

As regulations evolve, IPv6 adoption won't just be best practice; it may soon be mandatory. Big thank you to Nico Declerck and Howest for organising such a valuable and future-proofing session.