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

Simon Hobson <linux@thehobsons.co.uk> Mon, 17 July 2017 17:55 UTC

Return-Path: <linux@thehobsons.co.uk>
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 6409412EC1D for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 10:55:23 -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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] 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 qh85HuLCPFUX for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 10:55:21 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [80.229.10.150]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3344412EB5D for <v6ops@ietf.org>; Mon, 17 Jul 2017 10:55:21 -0700 (PDT)
X-Quarantine-ID: <HadF0z75-2gF>
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
X-Amavis-Alert: BAD HEADER SECTION, Header line longer than 998 characters: References: <76[...]
Received: from [192.168.137.111] (unknown [192.168.137.111]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 70C5F1BC37 for <v6ops@ietf.org>; Mon, 17 Jul 2017 17:55:14 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <m1dX9QX-0000DnC@stereo.hq.phicoh.net>
Date: Mon, 17 Jul 2017 18:55:13 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0E1BD32-BC60-497E-9B99-A1ED310B314F@thehobsons.co.uk>
References: <7643C1DC-76A3-4652-9BB1-D0D42801F37E@consulintel.es> <CAEqgTWYOe=jWp=zVZNLx6DjKjNpPTYaq2jmjryudrGZHKZNq6g@mail.gmail.com> <A5D0385C-F755-4B44-86D8-6E618E77193F@consulintel.es> <CAPt1N1kroh2cPkTr8HRfNjLTdG0hkC1oQsUZdhQzQA5tA9-xug@mail.gmail.com> <9AF791E9-1E12-425E-93A4-2913E2D18CBA@consulintel.es> <CAPt1N1kU4cpVCsp7W3XNAZupYqjTWVH+BNp9bwtznnWD_uP2oQ@mail.gmail.com> <CAEqgTWZzZW0wKggDXjY=-aMfDxzd5-GoRqju1829XwY3aHQuYg@mail.gmail.com> <0FAF1E05-DA4B-47BF-95F7-7EFCD1BED9B0@cable.comcast.com> <42188852-BBEB-4D75-967F-4BED79BBBCAE@consulintel.es> <CAFU7BARahTfH_Uy_t22EthGuFMJ=q-N1zxismNAVkHWWJA-Obw@mail.gmail.com> <CBA23B1B-C5A3-413C-B399-93F537C99015@consulintel.es> <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> <6C141215-908F-4AFD-96E9-E99CB4931D7D@consulintel.es> <CAFU7BASxqD1zdqZdoNpUK1KZMx=k8RBf1OF=7oj64nNnNTMqqw@mail.gmail.com> <m1dX9QX-0000DnC@stereo.hq.phicoh.net>
To: "v6ops@ietf.org Operations" <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/p8ypFqBB05ZdGZtiZXCeh89scEM>
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 17:55:23 -0000

Philip Homburg <pch-v6ops-7@u-1.phicoh.com> wrote:

> I find it fascinating that IPv6 is bad at competing with IPv4 even now
> that IPv4 addresses have run out for a while, that you advocate actively
> breaking IPv4.

That's not how I read it.
As I read it, "most" modern software(& systems/configs) will work with IPv4 or IPv6 - and for such software there is no problem as IPv4 gets turned off.
Also, as I read it from various comments, for those that don't, many are due to config issues (such as referencing an IPv4 address in OpenVPN config). It would be useful to identify such issues so that they can be corrected by educating those responsible.
And for those few bits of software where it's the software itself, then making the problem known would allow the developer to fix it "at some point" as they release new versions.

Fixing such problems leads to a situation where IPv6 only will actually work. The alternative that some seem to be advocating is to "do nothing" which means that such problems never get fixed, so IPv4 support stays as a requirement "forever", and progress doesn't happen.

My take on the proposal is that with an IETF shindig you have a self selected group of people with above average technical/networking knowledge - and a common interest in progress. As such it's a perfect group (ie people that won't just whine that "the internet's broken" with no useful information added) to try an experiment with and see whether it is practical to run such a network.



Ca By <cb.list6@gmail.com> wrote:

>   ipv4 has been broken for 10 years now with the mass deployment of NAT. 

Indeed, there seems to be a lot of argument about how to keep it working transparently when for the vast majority it only appears to work because of a lot of work behind the scenes to workaround what NAT breaks. In fact, a lot (not all, but a lot) of the modern complaint about surveillance and dependency on third parties continuing to provide servers (cf Zune and Revolv) is down to the need to workaround NAT.

Unfortunately, people don't believe anything is broken because of all this work that makes it appear as everything is working OK for them.