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

Mark Elkins <mje@posix.co.za> Mon, 17 July 2017 08:36 UTC

Return-Path: <mje@posix.co.za>
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 6DC5913179D for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 01:36:37 -0700 (PDT)
X-Quarantine-ID: <TeyGXKtRGXbf>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-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 TeyGXKtRGXbf for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 01:36:34 -0700 (PDT)
Received: from relay.vweb.co.za (relay.vweb.co.za [IPv6:2001:43f8:790:61::200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2DB0131771 for <v6ops@ietf.org>; Mon, 17 Jul 2017 01:36:33 -0700 (PDT)
Received: from [165.255.159.95] (port=52526 helo=mjelap.posix.co.za) by relay.vweb.co.za with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.87) (envelope-from <mje@posix.co.za>) id 1dX1W1-0002T9-30 for v6ops@ietf.org; Mon, 17 Jul 2017 10:36:29 +0200
Reply-To: mje@posix.co.za
To: v6ops@ietf.org
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>
From: Mark Elkins <mje@posix.co.za>
Organization: Posix Systems
Message-ID: <d0181f3b-9729-4dab-57f1-3d16e1694da8@posix.co.za>
Date: Mon, 17 Jul 2017 10:35:48 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <42188852-BBEB-4D75-967F-4BED79BBBCAE@consulintel.es>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/K0l77AI4UpjLERiCYibQ-LiOOJo>
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 08:36:37 -0000

For what its worth, we've had successful IPv6 only days in past AfriNIC
meetings (using NAT64+DNS64). I also personally ran IPv6 only at a
SAFNOG (Southern African NOG) in Swaziland with no ill effects (I broke
dhcp on my Laptop and just had to once configured the IPv6 Nameservers
by hand).

I'm personally advocating having future "IPv6 only" AfriNIC meetings
though this may end up being just for a single day.


On 17/07/2017 10:17, JORDI PALET MARTINEZ wrote:
> However, we have different ways for doing the same, and we should go for the one that has less impact and it is more realistic.
>
> In the real world, you will not disable IPv4 in the LANs of end-users or enterprise customers (at least not now, may be in 3-5 years from now). This is what IETF need to test now. IPv6 only with IPv4 as a service (which is 464XLAT).
>
> Again, and I’m for-IPv6, but being realistic, not considering sci-fi of turning down IPv4 in our customer networks (now).
>
> Regards,
> Jordi
>  
>
> -----Mensaje original-----
> De: v6ops <v6ops-bounces@ietf.org> en nombre de "Brzozowski, John" <John_Brzozowski@comcast.com>
> Responder a: <John_Brzozowski@comcast.com>
> Fecha: lunes, 17 de julio de 2017, 10:14
> Para: Noah <noah@neo.co.tz>, Ted Lemon <mellon@fugue.com>
> CC: Jim Martin <jim@daedelus.com>, IPv6 Ops WG <v6ops@ietf.org>, Alissa Cooper <alissa@cooperw.in>, Russ Housley <housley@vigilsec.com>, Randy Bush <randy@psg.com>, Suresh Krishnan <suresh.krishnan@gmail.com>
> Asunto: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
>
>     Agree with Noah and Ted.
>      
>     Note the I-D explicitly documents that a fallback, dual stack SSID must remain available as Noah mentions below.
>      
>     I fail to see how doing this will harm or discriminate.
>      
>     We do need to eat our own dogfood, otherwise we are hypocrites.
>      
>     John
>     
>     +1-484-962-0060
>      
>     From:
>     v6ops <v6ops-bounces@ietf.org> on behalf of Noah <noah@neo.co.tz>
>     Date: Monday, July 17, 2017 at 09:01
>     To: Ted Lemon <mellon@fugue.com>
>     Cc: Randy Bush <randy@psg.com>, v6ops <v6ops@ietf.org>, Alissa Cooper <alissa@cooperw.in>, Russ Housley <housley@vigilsec.com>, Jim Martin <jim@daedelus.com>, Suresh Krishnan <suresh.krishnan@gmail.com>
>     Subject: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
>     
>      
>     
>     FWIW and to cater for all, would a fallback dual stack SSID work for the status quo while this 2nd v6 SSID is also experimented upon which is a great idea considering this is IETF.
>     
>      
>     
>     Noah
>     
>     
>      
>     On 17 Jul 2017 9:54 a.m., "Ted Lemon" <mellon@fugue.com> wrote:
>     
>     I don't think this is a social justice issue.   Does the IETF think that IPv6 works, or not?   If we think it works, and we have been working for what, 20 years, to make it work, and we have designed all this great
>      transition tech, then why on earth would we not want to use it?   This isn't "one draft."   This is roughly half the work of the IETF for the past two decades.
>     
>      
>     On Mon, Jul 17, 2017 at 8:51 AM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
>     
>     So we agree to change the rules so that we use this network for every ID that want to experiment with it? Otherwise we discriminate among different authors …
>     
>     I think is a really bad precedent.
>     
>     Regards,
>     Jordi
>     
>     
>     -----Mensaje original-----
>     De: Ted Lemon <mellon@fugue.com>
>     Responder a: <mellon@fugue.com>
>     Fecha: lunes, 17 de julio de 2017, 8:48
>     Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
>     CC: IPv6 Ops WG <v6ops@ietf.org>, Jim Martin <jim@daedelus.com>, Randy Bush <randy@psg.com>, Suresh
>      Krishnan <suresh.krishnan@gmail.com>, Russ Housley <housley@vigilsec.com>, Alissa Cooper <alissa@cooperw.in>
>     Asunto: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
>     
>         I don't actually know what the goal of the IETF network is other than to provide connectivity.   Because of the vicissitudes of hotel topology, it is often the case that IETF participants experience issues with the
>      network at least once or twice per IETF despite the best efforts (and they are quite exceptional) of the NOC team.   I do not really see what the damage is that you are hoping to protect against here.   Users who don't read the NOC announcement?   No sympathy. 
>       Sorry.
>     
>     
>     
>     
>     
>     **********************************************
>     IPv4 is over
>     Are you ready for the new Internet ?
>     http://www.consulintel.es
>     The IPv6 Company
>     
>     This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or
>      use of the contents of this information, including attached files, is prohibited.
>     
>     
>     
>     _______________________________________________
>     v6ops mailing list
>     v6ops@ietf.org
>     https://www.ietf.org/mailman/listinfo/v6ops
>     
>     
>     
>     
>     
>      
>     
>     
>     _______________________________________________
>     v6ops mailing list
>     v6ops@ietf.org
>     https://www.ietf.org/mailman/listinfo/v6ops
>     
>     
>     
>     
>     
>     
>     
>     _______________________________________________
>     v6ops mailing list
>     v6ops@ietf.org
>     https://www.ietf.org/mailman/listinfo/v6ops
>     
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

-- 
Mark James ELKINS  -  Posix Systems - (South) Africa
mje@posix.co.za       Tel: +27.128070590  Cell: +27.826010496
For fast, reliable, low cost Internet in ZA: https://ftth.posix.co.za