IPv6-only IXPs Are Coming?#
MORE-IP 2025 digest Program Core pick 4–5 June 2025
Aleksi Suhonen - TREX Tampere Region Exchange Oy
- Why: IPv6-only operations are the concrete form of "IPv4 exhaustion planning," and an IXP is a good forcing function: if an exchange runs v6-only, its members must follow. For a PM whose portfolio includes DC/WAN interconnect and IPAM, this is a preview of a real operational shift rather than a compliance checkbox.
- What: A talk arguing (or asking, per the title's question mark) whether IPv6-only IXPs are imminent, presumably drawing on TREX's experience as a small regional exchange. (No abstract published — from title and speaker only.)
- How: Not stated. TREX is known in the operator community for having run IPv6-only peering experiments; expect the practical mechanics — v6-only peering, translation/NAT64 for stragglers, member readiness — to be the substance.
- Where applicable: Most immediately relevant to small/regional IXPs and their members, where the coordination problem is tractable; the big hub IXes will lag. For enterprise/cloud PMs, it's a leading indicator for when multi-cloud and interconnect products need first-class v6-only paths. Title-level only; the TREX-experiment framing is background context, not program text.
