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

Ted Lemon <ted.lemon@nominum.com> Thu, 23 January 2014 01:29 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 094A31A02C8 for <v6ops@ietfa.amsl.com>; Wed, 22 Jan 2014 17:29:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kym0Tkf5fKQp for <v6ops@ietfa.amsl.com>; Wed, 22 Jan 2014 17:29:18 -0800 (PST)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id A87B01A02B9 for <v6ops@ietf.org>; Wed, 22 Jan 2014 17:29:18 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUuBwboOB2nQnobpllrRehGqVjqiAQEsD@postini.com; Wed, 22 Jan 2014 17:29:18 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 75DAD1B82DE for <v6ops@ietf.org>; Wed, 22 Jan 2014 17:29:08 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 037FC190043; Wed, 22 Jan 2014 17:29:08 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 22 Jan 2014 17:29:07 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAD77+gReP-weV3=_hz-rm0KvDbDjkmsZYc0H_rdQ=R9qpcNhJQ@mail.gmail.com>
Date: Wed, 22 Jan 2014 20:29:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <24696EC9-3CC7-4518-A029-E385F1C987DD@nominum.com>
References: <CAD77+gReP-weV3=_hz-rm0KvDbDjkmsZYc0H_rdQ=R9qpcNhJQ@mail.gmail.com>
To: Richard Hartmann <richih.mailinglist@gmail.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] v6-only (with NAT64) as default network during a conference?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 01:29:20 -0000

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.