IETF Logo Mail Archive

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:33 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 4E07113166B for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 10:33:01 -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 g5yV1sbYEyrq for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 10:33:00 -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 A2EFB131668 for <v6ops@ietf.org>; Mon, 17 Jul 2017 10:32:59 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1dX9tC-0000GJC; Mon, 17 Jul 2017 19:32:58 +0200
Message-Id: <m1dX9tC-0000GJC@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> <m1dX9QX-0000DnC@stereo.hq.phicoh.net> <CAD6AjGTOqKRg3sDogWJPTmkKkqJBnU-DjNj2MxX3KDksUTsBcw@mail.gmail.com>
In-reply-to: Your message of "Mon, 17 Jul 2017 17:17:28 +0000 ." <CAD6AjGTOqKRg3sDogWJPTmkKkqJBnU-DjNj2MxX3KDksUTsBcw@mail.gmail.com>
Date: Mon, 17 Jul 2017 19:32:58 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/RYP7Qwj5mIebFfbI8U00Nquq_gM>
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:33:01 -0000

>User demans is irrelevant. We deploy ipv6only because we are out if ipv4
>(in the real world). It is appropriet for the ietf to design and operate
>real world scenarios instead of living in the legacy world abudent ipv4
>addresses.

If you are truely out of IPv4 address then you cannot deploy NAT64 so
the issue is moot.

If you do have enough public IPv4 addresses to deploy NAT64 then you can
just as well deploy any of the many other CGN techniques. Of course,
you may prefer to break legacy devices to promote IPv6. But that's then just
your choice.

v2.23.0 | Report a Bug | By Email