On 27/11/2023 09:22, Marco Davids (SIDN) via ripe-list wrote:
Good morning from Rome,
Here are two observations from using 'ripemtg-v6onlyexp' SSID.
NAT64: yes, but DNS64: no (solved by using my own DNS64 resolver, but still...)
And no support for RFC8925? [1]
Hello Marco, list, this is correct and expected. We used to have an IPv6-only network with NAT64 and DNS64 for ten years, starting from RIPE 67. Since RIPE 85 we run the main meeting network as IPv6-mostly, which in practice means it is essentially IPv6-only for up to 80 % of connected devices. Therefore we decided that the network called `ripemtg-nat64` has fulfilled its purpose and we announced to shut it down starting this meeting. Over the years we also got comments that people would like to experience a pure IPv6-only network, that is a network where no IPv4 is provided either native nor via NAT64 or any other mechanism. This is what `ripemtg-v6onlyexp` is. There is deliberately no support for IPv4 whatsoever. Technically there is NAT64 present with Well-Known Prefix 64:ff9b::/96, because this prefix is routed in the whole meeting network, but it is not meant to be used in this experimental network - therefore we don't have DNS64 or PREF64 RA option. If you want to experience IPv6-only network with NAT64, the easiest way to do it is to connect to the main meeting network `ripemtg` and turn off IPv4 on your computer. If your computer supports DHCP Option 108 (RFC 8925), this will happen automatically as the main network supports this option. -- Best regards, Ondřej Caletka RIPE NCC