[ipv6-wg] IPv6 only as default for next meeting
- Previous message (by thread): [ipv6-wg] IPv6 only as default for next meeting
- Next message (by thread): [ipv6-wg] Implications of NAT/NAT64 and similar (was: Re: IPv6 only as default for next meeting)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marc Blanchet
marc.blanchet at viagenie.ca
Fri May 15 00:43:04 CEST 2015
On 14 May 2015, at 18:21, Jérôme Fleury wrote: > During WG this afternoon, the idea was submitted that the IPv6 only > experimentation be made the default SSID for the next meeting. > > While this has been working tremendously well for routine internet > usage, I've been unable to use this network mainly because of > incompatibility with my VPN network. > > We have a dual-stack VPN. some of the resources are v4 only though. > The DNS64 converts my v4 VPN resources into v6 resources that are then > routed to the non-VPN interface. While there could be workarounds > (DNS64 on the VPN side, full v6 routing on the VPN, or all VPN > resources available on v6) I don't think the technology is mature > enough I think the technology (v6only-nat64-dns64) is mature enough. The problem is that various applications and services are not compatible with it (usually IPv4 addresses negotiated in the payload) I know it is a variation, but what I’m trying to say is that if we can push more and more to have applications/services ipv6-ready, then that issue will just disappear. Marc. > to make it the default for advanced usage. > > My 0.02$
- Previous message (by thread): [ipv6-wg] IPv6 only as default for next meeting
- Next message (by thread): [ipv6-wg] Implications of NAT/NAT64 and similar (was: Re: IPv6 only as default for next meeting)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]