Re: [sunset4] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
"Brzozowski, John" <John_Brzozowski@comcast.com> Mon, 17 July 2017 08:22 UTC
Return-Path: <John_Brzozowski@comcast.com>
X-Original-To: sunset4@ietfa.amsl.com
Delivered-To: sunset4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8F9131A88; Mon, 17 Jul 2017 01:22:27 -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 ot2jVv_pcWCf; Mon, 17 Jul 2017 01:22:25 -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 81C9C131A83; Mon, 17 Jul 2017 01:22:25 -0700 (PDT)
X-AuditID: 60721c4c-fe5ff70000004e62-4d-596c73bdc9f1
Received: from VAADCEX14.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 E0.23.20066.DB37C695; Mon, 17 Jul 2017 04:22:22 -0400 (EDT)
Received: from VAADCEX09.cable.comcast.com (147.191.102.76) by VAADCEX14.cable.comcast.com (147.191.102.81) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Mon, 17 Jul 2017 04:22:20 -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 04:22:20 -0400
From: "Brzozowski, John" <John_Brzozowski@comcast.com>
To: Marc Blanchet <marc.blanchet@viagenie.ca>
CC: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>, Jim Martin <jim@daedelus.com>, Alissa Cooper <alissa@cooperw.in>, Russ Housley <housley@vigilsec.com>, Randy Bush <randy@psg.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, Jari Arkko <jari.arkko@piuha.net>, "sunset4@ietf.org" <sunset4@ietf.org>
Thread-Topic: [sunset4] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Index: AQHS/mFjyacM1/hfIEykN3ouQq0Z36JXdR8AgAA5uoA=
Date: Mon, 17 Jul 2017 08:22:20 +0000
Message-ID: <06B8C7D0-9806-4180-A6E8-F73B61DCECC1@cable.comcast.com>
References: <F73BB5CF-9600-404E-9A25-9DCDD1E2493D@cable.comcast.com> <54F1DACB-4ED3-46B9-85DE-00C105ED79BA@viagenie.ca>
In-Reply-To: <54F1DACB-4ED3-46B9-85DE-00C105ED79BA@viagenie.ca>
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.253]
Content-Type: text/plain; charset="utf-8"
Content-ID: <40D2836473270548A380542154E8BF9C@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA11UfVAUZRyed+9r7+LVZYG7lwOsW6dmLPkosxb6chr+uBwZczSnqwlZ7jbu ur0Pb+9QqmkYjdE5yaGZFD0aJbxm+DClhABjsAhTNDSJoSK0cSLz+MOgICSz2nfvDpb+2t8+ z/t7nuf3m3deUkWfM5hJlzfIB7ycwGgN6jLxOTa3TxRsBac7stj6r+8CNnydYSdv/qBjD/U1 a9nRARUbbu5VsTdqYgTb0ntGxw60D2nW6a0zEzHCGp7+lrD2RK7qrNHoPGHtjNZrrQcONwDr ianHra3jM5rnyZcMTzp4wVXJB/KfLjM4h8P7df7bhTt7L+3WVINuNgxIElGPoqb9hWFgIGmq i0DD33yviv98DtBswx8g/jMIUMuxLiIM9KSWegx1fPGjDtfpVC5q6GmWO1TULIHGzn4KMJFG bUEffXxRGz/0AppsvAOwXTpVhC7+sh7Daup+dGR3VI1rSBWjXVfqNLimqSq0t6ZJrvXUM2hv 3Q25BpQRzV04LmdQUSY0NnFUrhFFoWjvZVW8zkCxn/+Rz2dQeWh0qkUdx1ejoe8mQLwuQJ0f 9iVwC+qbwvlJSXMVOnk6Py5fhE7sOqmL1xb03r7runjMVDR4eCLRakJfDnRr6kBWRJEosqgU UShFFEoRhVIj0LSCFZUc57B7nL5QsOCRPDtXLvB5dp/HzolB/P0E4NsSyN7QDX4/aO0HFAmY FKjiBBut4SrFKk8/cJMEkwGvaN02elm5z1Hl5ETntkBI4EUmHRYL0km4AJeHBDdjhqUBCU1b QL38DlHgg9L1ZFbAJixkWuDEkOh32V2+kLgtFBD6ASJVkmztZizr4Kpe5wO+uFk/yCLVjAk+ 0POajaYquCDv5nk/H0iyO0iSQfAWdk4N8BX8zlddQjBJS323H5IYSsnIYXMgO+Cy0UYlochr gU9g2qyk/x+ZIPX9oIJMkXKfx/ZQ9HMe0VWRsE6Deo+EpiRR2TYTntougXQSVFjmwK06aUXG JLXU7gLYB8jIofk/CbLjzvk5glZ7fV7ebIJQxPPhJmfIuzC42QgHN5XZ6OUKAgcwZ8NajGco 8MUM5vvgTcxmKtilMZKPzCSwSzcmDY7gwVOkJ2hxbhp+hUe8JwHKYyPYibHUBKaYOhva8NQZ CWap26S0XkJab1qJvN4gF1Sud7xEXm8CTax3uERebwJcst56TBmT1FInczWoteufGnhl+b05 R1a1l67cvubdS38Zrrrf1l3zp1fz1/YYZ963vLXGvCd2amzug7G2lxuHbp07sHb6303PbiBG 2jJHu0qdltX50cvvHC1at3H93bYzsfG/f23On7e1nh2xmD7b6Oo5vnXC3cdsrnH4yPborL84 duzNF9/wLftteu2g/afCXEYtOrmHH1QFRO4/TPCyHdoFAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/sunset4/_PTV4tOwoOhrP0SZ-z4-3xYTxp0>
Subject: Re: [sunset4] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: sunset4 working group discussion list <sunset4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sunset4>, <mailto:sunset4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sunset4/>
List-Post: <mailto:sunset4@ietf.org>
List-Help: <mailto:sunset4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sunset4>, <mailto:sunset4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 08:22:27 -0000
I agree with Marc’s suggestion for IETF 99 and IETF 100. I volunteer to help with messaging and support for IETF 99, for the record. Thanks Marc. John +1-484-962-0060 -----Original Message----- From: Marc Blanchet <marc.blanchet@viagenie.ca> Date: Monday, July 17, 2017 at 02:55 To: John Brzozowski <John_Brzozowski@Cable.Comcast.com> Cc: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>, Jim Martin <jim@daedelus.com>, Alissa Cooper <alissa@cooperw.in>, Russ Housley <housley@vigilsec.com>, Randy Bush <randy@psg.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, Jari Arkko <jari.arkko@piuha.net>, "sunset4@ietf.org" <sunset4@ietf.org> Subject: Re: [sunset4] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings On 16 Jul 2017, at 20:28, Brzozowski, John wrote: > Folks, > > Apologies in advance for the gratuitous cross posting (v6ops, ietf, > ipv6, sunset4, softwires). I hope, to you all, this is worth the > added email. > > The draft below was written to provide the necessary documentation to > enable the IETF (the NOC, participants, etc.) to migrate to an IPv6 > only primary network connection (Wi-Fi and wired) that utilizes > NAT64+DNS64 to access IPv4 only content. The request for IETF 99 has > been to have the primary “ietf” SSID adhere to what is documented > in the I-D below. I trust the motivation is understood. This means > that the main “ietf” SSID would be switched to be IPv6 only with > NAT64+DNS64 (at layer 3) per the I-D below. Given the that IETF99 is > upon us, this may or may not be entirely possible. > > At this stage, the infrastructure preparations for IETF 99 should be > in place to ensure that the IETF has the necessary hardware for > redundancy and performance. > > So, we are all seeking your input. Given the above, what would all > you suggest is tolerable for IETF99 as it pertains to the I-D below? > > • IPv6 only per the I-D for the balance of IETF week? > • IPv6 only per the I-D for one or more days this week? > • IPv6 only per the I-D for the plenary? > • IPv6 only per the I-D for the next IETF meeting? While I’ve been a proponent of IPv6 for a long time, including our own open-source implementation of nat64/dns64, we shall be careful, so I would suggest that for this week, we pick a day for experiment, say wednesday, and then for IETF100, we have it for the whole meeting, great accomplishment for 100! Marc. > > Please send us your feedback. > > Regards, > > John > +1-484-962-0060 > > -----Original Message----- > From: "internet-drafts@ietf.org" <internet-drafts@ietf.org> > Date: Saturday, July 1, 2017 at 03:04 > To: Marcus Keane <marcus.keane@microsoft.com>, Jen Linkova > <furry@google.com>, Lorenzo Colitti <lorenzo@google.com>, John > Brzozowski <John_Brzozowski@Cable.Comcast.com>, Erik Kline > <ek@google.com>, John Brzozowski <John_Brzozowski@Cable.Comcast.com>, > David Schinazi <dschinazi@apple.com>, Stuart Cheshire > <cheshire@apple.com>, Jen Linkova <furry@google.com>, Paul Saab > <ps@fb.com>, David Schinazi <dschinazi@apple.com> > Subject: New Version Notification for > draft-jjmb-v6ops-ietf-ipv6-only-incremental-00.txt > > > A new version of I-D, > draft-jjmb-v6ops-ietf-ipv6-only-incremental-00.txt > has been successfully submitted by John Jason Brzozowski and > posted to the > IETF repository. > > Name: draft-jjmb-v6ops-ietf-ipv6-only-incremental > Revision: 00 > Title: Incremental Deployment of IPv6-only Wi-Fi for IETF > Meetings > Document date: 2017-06-30 > Group: Individual Submission > Pages: 15 > URL: > https://www.ietf.org/internet-drafts/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00.txt > Status: > https://datatracker.ietf.org/doc/draft-jjmb-v6ops-ietf-ipv6-only-incremental/ > Htmlized: > https://tools.ietf.org/html/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00 > Htmlized: > https://datatracker.ietf.org/doc/html/draft-jjmb-v6ops-ietf-ipv6-only-incremental-00 > > > Abstract: > The purpose of this document is to provide a blueprint and > guidance > for deploying IPv6-only Wi-Fi at IETF meetings. This document > outlines infrastructure and operational guidance that operators > should consider when deploying IPv6-only networks using NAT64 > and > DNS64 to support communication to legacy IPv4-only services. > > > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at > tools.ietf.org. > > The IETF Secretariat > > > > > _______________________________________________ > sunset4 mailing list > sunset4@ietf.org > https://www.ietf.org/mailman/listinfo/sunset4
- [sunset4] Incremental Deployment of IPv6-only Wi-… Brzozowski, John
- Re: [sunset4] Incremental Deployment of IPv6-only… Marc Blanchet
- Re: [sunset4] Incremental Deployment of IPv6-only… Brzozowski, John