This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] IPv6-mostly IPv6-only(with dns64/nat64) dual stack at RIPE-meeting
- Previous message (by thread): [ipv6-wg] IPv6-mostly IPv6-only(with dns64/nat64) dual stack at RIPE-meeting
- Next message (by thread): [ipv6-wg] IPv6-mostly IPv6-only(with dns64/nat64) dual stack at RIPE-meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Davids
mdavids at forfun.net
Sat May 27 12:28:24 CEST 2023
Op 27-05-23 om 10:45 schreef Thomas Schäfer: > during the closing plenary were considerations to remove the IPv6-only(with > dns64/nat64) network/ssid the next time. > > I would vote for that. IPv6-mostly covers the traditional IPv6-only. Yes, I agree. > Someone made the proposal to provide a real "ipv6 only" > Let's try it! A lot will break for sure. It's not just websites. The DNS may break as well. I have test domain that can *only* be resolved via IPv6 and it yielded in some interesting findings. If you would like to try: https://42.dnslabs.nl > - VPN, own organisation/company At our company we spent quite some effort is getting this right. And it is fun to open the VPN on an IPv6-only network and still get IPv4-access via the VPN. I guess what I'm trying to say is: it can be done! (but not many companies will have done it) -- Marco
- Previous message (by thread): [ipv6-wg] IPv6-mostly IPv6-only(with dns64/nat64) dual stack at RIPE-meeting
- Next message (by thread): [ipv6-wg] IPv6-mostly IPv6-only(with dns64/nat64) dual stack at RIPE-meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]