breaking news
(I have to confess apple is sometimes good)
given a #IPv6only mobile access (like the Deutsche Telekom within Germany, not during roaming)
recent apple #iOS 18.5
makes
#IPv6mostly for clients via hotspot
#dhcpoption108 as well #pref64
I made also the windows test - in case option 108 is not provided by the client, iOS provides IPv4
@goetz @ffhl I needed a while to figure out what practical benefit we would have. One thing that came to my mind: Avoiding #ARP on supporting devices completely if I understand #ipv6mostly correctly. We do have a DHT for ARP in #batman_adv. And could reduce broadcasts a lot with it. But it's still not zero. #IPv6 is so much smarter for Neighbor Discovery as it uses #multicast properly with its solicited mcast addresses and not like broadcasts. And we have #MLD snooping in our #mesh.
@T_X
How about #ipv6mostly ?
@ffhl
@paul_ipv6
As the Google campus network is #IPv6mostly these days, I cannot believe that using #IPv6 printing from #Android is not possible.
@googlepixel
A further talk about #ipv6mostly
Be warned the slides move very fastly.
This draft has now been officially adopted by the v6ops IETF working group and renamed to:
draft-ietf-v6ops-6mops
https://datatracker.ietf.org/doc/draft-ietf-v6ops-6mops/
Also, a related 464XLAT / CLAT draft to keep an eye on:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-claton/
Hat eigentlich schon irgendeine #Freifunk|gemeinde #ipv6mostly oder #ipv6only dauerhaft im Einsatz?
Rejoice, network operators. Windows 11 will be joining the rest of the world soon in supporting CLAT, #NAT64, and #DNS64 natively. (Currently, CLAT only works on cellular connections.)
Supporting two IP versions has been a pain we’ve had to live with for over a decade, but this will allow network operators to forcibly disable clients’ IPv4 stacks via DHCP/RA, finish #IPv6 switchovers, and run true #IPv6mostly or #IPv6only networks.
We’re one big step closer to killing “legacy IP” for good. 
A new v6ops draft from Jen Linkova at Google just dropped:
IPv6-Mostly Networks: Deployment and Operations Considerations
#fosdem
#ipv6mostly by @Oskar456
https://fosdem.org/2024/schedule/event/fosdem-2024-1798-improving-ipv6-only-experience-on-linux/
For me the traditional #IPv6only is good enough on Linux, but...
...the corner cases and DNSSEC.
On the other hand:
https://konecipv4.cz/en/
I prefer dns64 and removing A-Records. (it solves also some corner cases, but it breaks DNSSEC completely )
The recording of my #RIPE87 tutorial about #IPv6mostly on #OpenWRT is already online!
Kudos to RIPE NCC Web Services! https://ripe87.ripe.net/archives/video/1136/
@tschaefer i wouldn’t get too excited, still 22% use this conference 
@pemensik @tschaefer gunna need some citations on how #fedora isn’t #ipv6mostly ready since i’ve used it & other distro’s on #ipv6only networks for years 
most software is #ipv6 capable, the only particular need for nat64 is whether the destinations they interact with have deployed 
Fedora Linux is not yet ready for #ipv6mostly network. I guess we have to improve that. But we do not yet have #ipv6 production connectivity in #redhat offices. Not even dual stack, let alone just ipv6. Where would we test it?
scary ipv6-only networks 
