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

Stephen Honlue <honlue@gmail.com> Mon, 17 July 2017 08:39 UTC

Return-Path: <honlue@gmail.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 80B2B131B09 for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 01:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ACwrcU2wBLY0 for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 01:39:06 -0700 (PDT)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 A7C88131771 for <v6ops@ietf.org>; Mon, 17 Jul 2017 01:39:05 -0700 (PDT)
Received: by mail-wm0-x241.google.com with SMTP id 65so1860622wmf.0 for <v6ops@ietf.org>; Mon, 17 Jul 2017 01:39:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=SuWI1GZmtvkSwh4nlvKyE/Y8U8c/DMVvtwmhR4c2Tjc=; b=tzM0on8QJz1kEv6cs52gTpcoIHYlD0voy3Rte0cdLgFlCvRQ3gQMFxlJ+ZLNUCajtc wrNhS+zNgZ1wax16V4em/2jCdDD+5qJEH8Eg7OAtZXNRUisADLwmHUF2eaJRO8PTfzTB 5R+qX7SH6nZEK8b8iJ+TtTpBQhyYsSO3Q6cxF7GmLExyiSkRtb1D1qfvaexwYBsj2p8p Z8HQBBtZ0giO8Kx5QaCiEGsNspMDFmBBk+x3zqCcTVl8cq9qHFo4qVgXHWJnj7Pmduct okxiAZZK2T3hVQ9rBaPf/u4ay6NSD+JhMwkmZ7I+d8S7AkaPlHHles+RX5n9iiPmbuDR GLow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=SuWI1GZmtvkSwh4nlvKyE/Y8U8c/DMVvtwmhR4c2Tjc=; b=NJo2FZkX/OvQYKt49TWttwnPaagAaB9Zl7AL+zBp2ns6Bhf/8B9mUjRHw6n59AzxHB 0avj3wDwaKxcAJVYda0SIH+Mg5zabatqazqE5xmuYy6Z4Bz9odbc6zDWrxcD27FrJ5TY rO/aV8AwkRarEv6u03V9xNMOV6zZiL6NpsrTQYsMqWwEEXyHXa+lI+J/UOCASIZMmYD1 4vHUY3UyarKtk+ghZUGIasMKwyjzY+3zTo9IGm/nLYwZIzNLiH8r9Qfid4+ZmXULCIDO v7GeIor5thwh5a/RQFE2I+3PuSILRnbHugVUuLIwR1vYI3k1K1dwDKVCNBxp9lXY7Fwu 1jrQ==
X-Gm-Message-State: AIVw1104B/9mOUa12p6yjgOeTjyIzhSaoizYQg2NWiC5fCxEMwoVxAET YrIObeMjBD29SmornIg=
X-Received: by 10.28.56.198 with SMTP id f189mr3549137wma.88.1500280743928; Mon, 17 Jul 2017 01:39:03 -0700 (PDT)
Received: from CPB-TRN2.dhcp.mu.afrinic.net ([2001:43f8:90:250:edf5:82c3:462e:acb2]) by smtp.gmail.com with ESMTPSA id i136sm9495423wmf.33.2017.07.17.01.39.02 for <v6ops@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Jul 2017 01:39:03 -0700 (PDT)
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> <CAFU7BARahTfH_Uy_t22EthGuFMJ=q-N1zxismNAVkHWWJA-Obw@mail.gmail.com>
From: Stephen Honlue <honlue@gmail.com>
Message-ID: <9a3a454b-d1fa-406c-7f39-5add5f422d16@gmail.com>
Date: Mon, 17 Jul 2017 12:38:57 +0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAFU7BARahTfH_Uy_t22EthGuFMJ=q-N1zxismNAVkHWWJA-Obw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/J9O_VjbVNJpfHW3PZIl397UwCnE>
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:39:15 -0000

My take for this is: IPv6 only per the I-D for the balance of IETF week?

We have been standardizing IPv6 for over twenty years now, it's just so
logical to preach by example.

Regards.


On 17/07/2017 12:34, Jen Linkova wrote:
> On Mon, Jul 17, 2017 at 6:17 PM, JORDI PALET MARTINEZ
> <jordi.palet@consulintel.es> wrote:
>> 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).
> I disagree with this statement. There are networks doing this. Right
> here right now.
>
>> -----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
>
>