#IPv6 #NAT64 prefix discovery recommendations
via @rfceditor
| pronouns | he/him |
goetz
@goetz@ipv6.social
- 52 Followers
- 111 Following
- 321 Posts
#IPv6 enthusiast
RFC Editorrecommending obtaining the NAT64 prefix from the Router Advertisement option (RFC 8781) when available. This document is a product of the IPv6 Operations Working Group of the IETF. 2/2
RFC 9872: Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis, N. Buraglio, et al., https://www.rfc-editor.org/info/rfc9872 #RFC On networks providing IPv4-IPv6 translation (RFC 7915), hosts and other endpoints need to know the IPv6 prefix(es) used for translation (the NAT64 prefix (RFC 6052)). This document provides guidelines for NAT64 prefix discovery, specifically 1/2
Dan Oachs
GWDGGWDG gewinnt den IT Community Award 2025! 🏆
Wir freuen uns, dass die Gesellschaft für wissenschaftliche Datenverarbeitung Göttingen (GWDG) mit dem IT Community Award 2025 ausgezeichnet wurde – für unser langjähriges Engagement zur Stärkung der IT-Community innerhalb der Max-Planck-Gesellschaft. 💡
Besonders gewürdigt wurden:
✔️ Organisation von Netzwerk-Treffen
✔️ Förderung von Wissensaustausch
✔️ Technische Unterstützung hybrider IT-Meetings
✔️ Beitrag zur digitalen Souveränität
Der Award wird einen Platz im Foyer unseres Rechenzentrums erhalten – als sichtbares Zeichen für Teamarbeit und Zusammenhalt. 🙌
Wir danken allen Kolleg*innen für die starke Zusammenarbeit! 💙
#GWDG #ITCommunityAward #MPG #Digitalisierung #Teamwork #Wissenschaft #ITCommunity
Freifunk MünchenYou should see another Performance improvement now for #DoH, #DoT and #DoQ 🚀
DoH: https://doh.ffmuc.net/dns-query
DoQ: doq.ffmuc.net:853
DoT: dot.ffmuc.net:853
Support us at: https://spende.ffmuc.net
Live Stats:
https://stats.ffmuc.net/d/tlvoghcZk/doh-dot?orgId=1&from=now-2d&to=now&timezone=browser&refresh=1m
Nivex 🐧 📻Yesterday Google announced they would be supporting DHCPv6-PD on Android, essentially requesting a /64 for every device when on WiFi.
https://android-developers.googleblog.com/2025/09/simplifying-advanced-networking-with.html
This has been the topic of fervent discussion on https://ipv6.chat/ . It's an interesting solution to some real world problems I've seen. It also creates a whole new set. I'm mulling a blog post to take a look at the address planning math involved at the scale the article mentions.
I pinged a large electronics online shop from CH, that their store is only reachable with the #legacyprotocol .
They send a well formulated response from the technical department, that #IPv4 is the preferred protocol and they haven't heard any negative feedback from customers so far. Nevertheless, they have placed #IPv6 connectivity on the #backlog for future re-evaluation.
If you are a customer, please make you voice heard.
Erik Nygren 
Android now supports #IPv6 DHCPv6 PD! This means you can assign an IPv6 block to an Android device and it will use as many addresses from there as it needs to. This includes support for reporting on address usage. This creates a path for Enterprise IPv6 deployment of Android, giving them control over which devices are using which addresses, without limiting devices to only a single address as DHCPv6 IA_NA does. Exciting and great to see.
https://android-developers.googleblog.com/2025/09/simplifying-advanced-networking-with.html?m=1
DasSkelett@goetz tried to get it working on my #OPNsense, but there's definitely a bunch of things missing:
- the option to set the PIO P flag for prefixes
- an actually working routing for delegated prefixes in this IA_PD-without-IA_NA scenario (https://github.com/opnsense/core/issues/8682#issuecomment-3300133623)
- a good way to handle delegated prefixes (or at least the general "super-prefix" where they are delegated from), e.g. with automatic aliases, in the firewall rules
- the option to set the PIO P flag for prefixes
- an actually working routing for delegated prefixes in this IA_PD-without-IA_NA scenario (https://github.com/opnsense/core/issues/8682#issuecomment-3300133623)
- a good way to handle delegated prefixes (or at least the general "super-prefix" where they are delegated from), e.g. with automatic aliases, in the firewall rules
