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

"Brzozowski, John" <John_Brzozowski@comcast.com> Mon, 17 July 2017 12:29 UTC

Return-Path: <John_Brzozowski@comcast.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 29906131B58 for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 05:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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, RP_MATCHES_RCVD=-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 3aGKbRekQ0EG for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 05:29:48 -0700 (PDT)
Received: from vaadcmhout02.cable.comcast.com (vaadcmhout02.cable.comcast.com [96.114.28.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DBC1131B3F for <v6ops@ietf.org>; Mon, 17 Jul 2017 05:29:47 -0700 (PDT)
X-AuditID: 60721c4c-001ff70000004e62-d7-596cadb975ca
Received: from VAADCEX16.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by vaadcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id CB.55.20066.9BDAC695; Mon, 17 Jul 2017 08:29:45 -0400 (EDT)
Received: from VAADCEX09.cable.comcast.com (147.191.102.76) by VAADCEX16.cable.comcast.com (147.191.102.83) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Mon, 17 Jul 2017 08:29:44 -0400
Received: from VAADCEX09.cable.comcast.com ([fe80::3aea:a7ff:fe12:e2a0]) by VAADCEX09.cable.comcast.com ([fe80::3aea:a7ff:fe12:e2a0%19]) with mapi id 15.00.1293.002; Mon, 17 Jul 2017 08:29:44 -0400
From: "Brzozowski, John" <John_Brzozowski@comcast.com>
To: Stephen Honlue <honlue@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Index: AQHS/tSiyacM1/hfIEykN3ouQq0Z3w==
Date: Mon, 17 Jul 2017 12:29:44 +0000
Message-ID: <CFBF5CB0-FAA6-4843-A66D-1576DD8902A1@cable.comcast.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> <9a3a454b-d1fa-406c-7f39-5add5f422d16@gmail.com>
In-Reply-To: <9a3a454b-d1fa-406c-7f39-5add5f422d16@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.21.0.170409
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [96.115.73.254]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B9AE4E80719FCB4398832B35645324DD@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA11Uf0wbZRj2u2vpgXzu25W2HycjcokmWzaGP4KN6DJ1idVIpjOZlpiMoz3b rkdL7loY/kjmH+KEGaeZDKoyZoqTMR3RGQrRZXTEjc1FZ4hLBjMqNVm7PzSbKdmI4H13V7j6 1733PN/7Ps/7fJdjaHaxlGNCkZgoRwSJLymzNCtPuzeNfyF56y6+5XZ/cmMQuC98/x29lfKM J67aPMnkLeo5qqnsUb8ohdpFefOW5rLgmSM3qbbkM3v6B3KWvWDU0w1KGYwewn+OjFq7QRnD ojEKH57qovSX0wC//e4irb9MA5z6NWUjLSWoHp+cnFVrhqlAHvzXHw8S2I524IUfLllJXYFe wGNdN216XYvzXy8BUlvQvXjx9j9W0grRNny6d70+fsKKl2f7KHKmFD2GPzj6pnYeICdeOH9c w2nkwlcyhyndNcLJb3+k9dqBs/NLmq5D1frl72GLjm/EFy9ngF7X4W+GThl4Db49MFNCPNBo PT4xsVkvH8HZdKWuVIMP9vyuuYdoLZ7uzxidLnxmKmU9ALiEyVBidVBidVDCNChhGjQIrMdA dbsg+H2twWg8VvdArU9okcRaX7TVJygx8vwKkBuWq55NgRu9njRADODL4fhHkpe1Cu1KZ2sa hBmKd8BLJWEve1dL1N8ZFJTgLjkuiQpfAat61JNwBW6JS2Geg/uOq6h9BY2IHYokxtRPiq+G n5JBrhVOiSttIV8oGld2xWUpDTBDq2OXB8hYv9D5qihHdbE0uJux8C543/huL4sCQkwMi2Kb KBfYDobhMawnymtlMSDueSUkxQq02tfdrzLIzGhm10H3VMjLOs2EyW8NbCA0Z6b/b5liStMg wJSrvvcTeai0Ca1KKGBI2+E7JKTyAqrJVsKNIyrIFkCT5Dq406ZG5CxQxXLnQQ9gEn238hRz cvHcAsVaItGIyLng62QeIk3BeGRlcc4Jp59v9rJrTAQxwFXB/QR3mPBVD9w98BphK01ssY3C jyEHfOoXY4dnyeLl6m9jdW8WPkws3WmA2toYvqRdkIGZtq6CXrK1w2CK1XJqvJQar71Rizcm xMzxzjVq8RqoEe/PjVq8BlgU7yFCOQtUsRK3F2zo2Dpzbv7s0fomas6+lD84O1zRWT2cuZxd /vyz/NyBiYz1w8mZl+cDr53qGmVxaOoKNfHizvhvqX8/9qd+CuZ6hq4PK3DL4HWANznqryZz 6Se+DD61/b1J27b8NdB0ITu0Gz7eN9L7fsOTh4bEHWveGGu844RHGMgeo7v2NfSHp3mLEhTu 30DLivAf0N8tzY4FAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/DMzAHvhJwNnfS-RLCIWdKwTlP_E>
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 12:29:51 -0000

Thank you.

John
+1-484-962-0060

-----Original Message-----
From: v6ops <v6ops-bounces@ietf.org> on behalf of Stephen Honlue <honlue@gmail.com>
Date: Monday, July 17, 2017 at 10:38
To: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

    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
    >
    >
    
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops