Thomas Schäfer <tschaefer@t-online.de> wrote: > during the ripe90 meeting I made (and collected) different experiences > with WLAN-call (a built in feature for "native" phoning via WIFI > instead of via 4G/ 5G). My conclusion is, it strongly depends. (even > it does not work reliable in IPv4-only networks). Nevertheless, I don't > expect wonders, when using IMS/SIP via ipsec via 464xlat. As long the > providers only provide A-Records here: > epdg.epc.mnc0XX.mcc262.pub.3gppnetwork.org (for Germany XX That's an interesting and useful observation. I understood that the WLAN-call is sometimes managed entirely by the broadband CPU on some phones, so it would be entirely under the 464xlat? Maybe that information is dated though. It's been more than a decade since WLAN calling went "mainstream" at the 2012 Olympics, and I believe that it's critical at pretty much every major sporting event/concert. > 01,02,03/07,23) I think it won't get better. Does anybody know if 3gpp > has also IPv6/IPv6 defined ipsec connections for it? (instead of > IPv6(payload) via IPv4(transport)) The IPsec part should work fine, but of course, the 3GPP providers have to have v6 connectivity. > After the meeting another built in function came in to my mind: > printing > Do people print in android and iOS? Does it work out of the box - > "zeorconf" via mDNS/airprint in IPv6-only/mostly? People sometimes print boarding passes and the like from their phones. I find that the number of people with working printers at home is now diminishingly small. (Sure, they exist, but they are poor inkjets with permanent shortages of cyan ink). So the instance of people randomly printing stuff has gone done. > A test in my home environment (cups/avahi) showed: > It can work, but only with the alternative print service by mopria. > The default/standard print service in android did not work at all. Do > you have any experiences with that? I don't let me home laser printer talk to wifi, so any printing from my phone would have to be via routed IPv6. Alas, my brother multimode printer has extensive ACLs for IPv4, and none for IPv6. I tried to build a MUD file for it once, but I couldn't determine how it finds it's firmware updates when there are ones. That is essentially what leads to: https://www.rfc-editor.org/rfc/rfc9726.html#name-use-of-ip-address-literals Where in charge of printing in the world, I'd remove all the ethernet and wifi interfaces on printers, leaving them with USB-C OTG only. And then have a smarter, more easily upgraded, (open source) device (RPI-sized, USB powered) with the right network interfaces. A LCD display on the unit would allow each spooled job to be released when the person who printed arrived. Then we could do all the IPv6 stuff that really need. (I've seen the same thing at many university computer labs for decades) -- Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide