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

"Marc Blanchet" <marc.blanchet@viagenie.ca> Mon, 17 July 2017 00:55 UTC

Return-Path: <marc.blanchet@viagenie.ca>
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 59DEC12EC35; Sun, 16 Jul 2017 17:55:47 -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 eGdGx2tK3_Wk; Sun, 16 Jul 2017 17:55:45 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 63DFB12778D; Sun, 16 Jul 2017 17:55:45 -0700 (PDT)
Received: from [206.123.31.198] (unknown [IPv6:2620:0:230:2001::1004]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B551047589; Sun, 16 Jul 2017 20:55:43 -0400 (EDT)
From: Marc Blanchet <marc.blanchet@viagenie.ca>
To: "Brzozowski, John" <John_Brzozowski@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
Date: Mon, 17 Jul 2017 02:55:42 +0200
Message-ID: <54F1DACB-4ED3-46B9-85DE-00C105ED79BA@viagenie.ca>
In-Reply-To: <F73BB5CF-9600-404E-9A25-9DCDD1E2493D@cable.comcast.com>
References: <F73BB5CF-9600-404E-9A25-9DCDD1E2493D@cable.comcast.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sunset4/evJ0N1H4I0Ia5CqWXEp-AfhFMtk>
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 00:55:47 -0000


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