Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

Philip Homburg <pch-v6ops-7@u-1.phicoh.com> Mon, 17 July 2017 18:20 UTC

Return-Path: <pch-b7900FA3D@u-1.phicoh.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4857130133 for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 11:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 5WR5c-_0g1Vb for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 11:20:23 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id CD8AF12EB96 for <v6ops@ietf.org>; Mon, 17 Jul 2017 11:20:22 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1dXAd4-0000GoC; Mon, 17 Jul 2017 20:20:22 +0200
Message-Id: <m1dXAd4-0000GoC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
Cc: Simon Hobson <linux@thehobsons.co.uk>
X-Cc: "v6ops@ietf.org Operations" <v6ops@ietf.org>
From: Philip Homburg <pch-v6ops-7@u-1.phicoh.com>
Sender: pch-b7900FA3D@u-1.phicoh.com
References: <CAFU7BARz_u92NweYkTizT2=q420sBRh11m9bqWO9+aexCi3ANA@mail.gmail.com> <2A639918-C6AC-44B8-8D66-5293EE13A7BD@consulintel.es> <CAFU7BASrxoroJVHwxFpwwBxCUC62_VZXsUGgfDOj6y+KVWk6tw@mail.gmail.com> <C510C095-B9AB-432F-A050-FD9CD640A6DE@consulintel.es> <CAFU7BAR413hwY_G2Cw-Ab+J158udPDLSFo==EN4LHjWb_YzD5Q@mail.gmail.com> <m1dX7DB-0000FzC@stereo.hq.phicoh.net> <CAFU7BAQ1ML2ARZKozJLFiEw43jmMObKwOpD4pGt9S3VKOwLE4w@mail.gmail.com> <m1dX7nO-0000GTC@stereo.hq.phicoh.net> <20170717152345.GV45648@Space.Net> <m1dX8Uf-0000FkC@stereo.hq.phicoh.net> <20170717172242.GW45648@Space.Net> <m1dXA9Y-0000ChC@stereo.hq.phicoh.net> <ADC7A752-8025-4B71-8E65-080BAC59C02A@thehobsons.co.uk>
In-reply-to: Your message of "Mon, 17 Jul 2017 19:08:32 +0100 ." <ADC7A752-8025-4B71-8E65-080BAC59C02A@thehobsons.co.uk>
Date: Mon, 17 Jul 2017 20:20:21 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/7ARPG0GTXVJfFBQjrJBfPNkFihA>
Subject: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 17 Jul 2017 18:20:25 -0000

In your letter dated Mon, 17 Jul 2017 19:08:32 +0100 you wrote:
>"Break all unmodified hosts ?"
>I was under the impression that many unmodified hosts (and the software runnin
>g on them) was capable of running on an IPv6 only network - but there are spec
>ific, notable exceptions (OpenVPN config specific, and MS Outlook an Mac are t
>wo that have been mentioned), and that the scale is not clearly known.

I'll just assume that with 'IPv6 only' you mean NAT64/DNS64.

So the most obvious example that breaks with DNS64 is a web page that
refers to another http resource using an IPv4 literal. 

Anything that the user has done using IPv4 literals also breaks. Say the
address of a mail server, an ssh host, etc.

Of course, anyone who has manually configured Google's public DNS resolvers
is also in for a surprise.