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

"Brzozowski, John" <John_Brzozowski@comcast.com> Sun, 16 July 2017 18: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 1FD861316C2; Sun, 16 Jul 2017 11:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable 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 aZZ26WHmvCHp; Sun, 16 Jul 2017 11:29:03 -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 40F3A12702E; Sun, 16 Jul 2017 11:29:03 -0700 (PDT)
X-AuditID: 60721c4c-4576e9a000004e62-cc-596bb06c3ee5
Received: from VAADCEX13.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 26.3F.20066.C60BB695; Sun, 16 Jul 2017 14:29:00 -0400 (EDT)
Received: from VAADCEX09.cable.comcast.com (147.191.102.76) by VAADCEX13.cable.comcast.com (147.191.102.80) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Sun, 16 Jul 2017 14:28:58 -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; Sun, 16 Jul 2017 14:28:58 -0400
From: "Brzozowski, John" <John_Brzozowski@comcast.com>
To: "draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org" <draft-jjmb-v6ops-ietf-ipv6-only-incremental@ietf.org>
CC: Randy Bush <randy@psg.com>, Alissa Cooper <alissa@cooperw.in>, Jim Martin <jim@daedelus.com>, Jari Arkko <jari.arkko@piuha.net>, Suresh Krishnan <suresh.krishnan@gmail.com>, Russ Housley <housley@vigilsec.com>
Thread-Topic: Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Index: AQHS/mFjyacM1/hfIEykN3ouQq0Z3w==
Date: Sun, 16 Jul 2017 18:28:57 +0000
Message-ID: <F73BB5CF-9600-404E-9A25-9DCDD1E2493D@cable.comcast.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.252]
Content-Type: text/plain; charset="utf-8"
Content-ID: <81B121D76221E340A120022E53A6DCE2@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA11Uf0wTZxjed3elB/LN46DtRwVib8NkxCFsk3TuR/xDhmYucf8s6RYDRznb o9eW3bUI+5H0H5cFtsQsCxvV+IOAE+JAiPiDsOlqIwNDHJuuOhc3B1F0y2ZcxBgd2/f1rnDd X33ved73eZ737eVYmn+Y62TlUERSQ6Ii5OQxDdoW99PK0YCn6upezn1jeD/jvjX9F+U+e2iU cvePn7a6z5/7it5o2dzb+4DaBt7Me7FJUuRWSV33ckOe/5+JL5iWn8vb7h2essTAr092gFwW cc+h2eFHVAfIY3nuBIUuje1m9IczAB1PPQL6wyRA1wfvATKSw9WgY99ctXYAli3iNHRzlic9 NHcFoLm+LgvpKeQ2ofHUDaD3bEH/XqogcBFXiYbnO9MtDFeORj45ZyU1xO13982n5QFnR/en jlCkpjkH+mluP6Un5VDv+AVar23o1uxiWseGNX+808/o+Fo0nZoDel2FRvu+NnAXWtwzxJA4 NPcUGhpbp8tvQBND3Va9dqFPO68bcQrQZPecMepAZ5MnLbtBcdyUKL6sFDcpxU1KcZPSAWAZ AGWtotjkDfrD0UjVM5VesVGRKr3hoFfUIuR3BJB/WC3ZehLc7dqcABwLhHw40xXw8BaxVWsP JkCApQQbnMnB0OON4aZ2v6j569WoImlCEWx4tdnDwyW4MaoEBCdcM4ibC5fQkLRTU6QIfqWE MthDhBxLnBbVWmSvHI5q9VFVSQDE0lh2w2e4CTaJ7e9Ialg3S4BVLCM44JpT2JHziREpIEkt kpphd7KsgOC+ITxYoEo+qW2HrEQyNJ4bJJk4M5MOWwrdSdnD282EKa8LvkBop5n+f2SKzU0A H5uPc79N7KHWIgY12WdYF8LQWzhyfgZN2xbDYdLKZ0CTZSl8w4ope4bKtpsCnYCNf/5ggWKP Pfz2PsUzoXBIcjrgQno/MuSPhpYWd9rh5OsNHn6liSABnCXwI4LbTPhyBudqOE/YYhObHSPz YbgNvPiNKYS7yDb5+LOxvDcP+0ikFQaYXhvBvQQrMDDT1iXQQ7a2GUy22218Xgqf94NmPzlv RIyYz2sJ+Ml5DdQ472ME5DNg1nnDRMWeobKdnDFw/onuNvuBYG1tf+z96prRX5rl+V3rK0ro 9ReuuLQ9B8Xfr/lWhy729LjurMh5L3ni4kJxPV8wvVC7MlYnf/h82UxqoOZ729RLQl3qj+nG HT+oW1d9/Irt2uWk+vf4tptfbjo68Odva5/t/666bvviodjs8dKy7fCylrTBkYmN5e++dmpM YDS/WF1Bq5r4H+QKnxGOBQAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mOUO7CL5rA2ld6VMVqTlZxMHQ88>
X-Mailman-Approved-At: Sun, 16 Jul 2017 21:22:54 -0700
Subject: [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: Sun, 16 Jul 2017 18:29:05 -0000

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?

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