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 17:03 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 235FF131668 for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 10:03:25 -0700 (PDT)
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 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 08FpYcNqj8xy for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 10:03:24 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id D7D3E1300CE for <v6ops@ietf.org>; Mon, 17 Jul 2017 10:03:23 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1dX9QX-0000DnC; Mon, 17 Jul 2017 19:03:21 +0200
Message-Id: <m1dX9QX-0000DnC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
From: Philip Homburg <pch-v6ops-7@u-1.phicoh.com>
Sender: pch-b7900FA3D@u-1.phicoh.com
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>
In-reply-to: Your message of "Tue, 18 Jul 2017 02:06:11 +1000 ." <CAFU7BASxqD1zdqZdoNpUK1KZMx=k8RBf1OF=7oj64nNnNTMqqw@mail.gmail.com>
Date: Mon, 17 Jul 2017 19:03:20 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/UW02mfp4eBJyLEtlREqkvhqgS3w>
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:03:25 -0000

> Let me clarify what I mean by the chicken and egg problem here.
> 'We can not turn off IPv4 because there are IPv4-only endpoints
> there and they are not going away. Why those endpoints are not
> going away? Because there is no demand for them to work on Ipv6-only
> networks. Why there is no demand for them to work on IPv6-only
> networks? Because nobody is turning off IPv4'.

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.