Re: [v6ops] v6-only (with NAT64) as default network during a conference?

On Jan 22, 2014 5:29 PM, "Ted Lemon" <ted.lemon@nominum.com> wrote:
>
> We've had a production quality NAT64 network at the past two IETFs, and
it's worked wonderfully.   However, some things do break.   In particular,
Skype doesn't work, and I've heard reports that some Cisco VPN
implementation doesn't work.   I've found that OpenVPN does work, but needs
to be configured differently because it can't automatically switch to IPv6
when IPv4 isn't available—it has to be configured to do one or the other.
>
> If it were up to me, I'd make NAT64 the default and let people switch
away if they can't make it work, because particularly at an open source
conference I would expect this to generate a lot of frenetic bug fixing
rather than a sad migration.   In theory free operating systems ought to do
IPv6 better, but your milage may, unfortunately, vary.
>
>

+1 for nat64 default with another ssid for dual-stack.  This should be a
good practice for ietf, nanog, rirs, and so on.

This is the obvious way of things to come given the post ipv4 run out
situation we are currently living.

CB _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops