Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 28 July 2017 23:53 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C39E1321B0; Fri, 28 Jul 2017 16:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 WVLs73B-kzTG; Fri, 28 Jul 2017 16:53:56 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F173B1321D8; Fri, 28 Jul 2017 16:53:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 47FC4BE2D; Sat, 29 Jul 2017 00:53:52 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2sk00pmspGIF; Sat, 29 Jul 2017 00:53:48 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 3B751BDF9; Sat, 29 Jul 2017 00:53:48 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1501286028; bh=3TlGrMuJugn31QT0CsuaPiLppFEgF6JiZIhsvs7SLCY=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=zAHI1PVJadOrToS5P+8h8jBsnJ6t+DJ9lVc9U52fDjhwKGhZrpx8FntGv63T2wNpv HNp36pCBCkWee8XS5loWjW8heHLcTnBSZsB6pkbWhv91KjZeZGTPqkM1l08FHBNzkp FI5WOiEu+NhU1FAgmxiycoRPvcEmtmws7ANxpMMI=
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Eric Rescorla <ekr@rtfm.com>, "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>, Suresh Krishnan <suresh.krishnan@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <e9095813-b5b5-29ba-34ab-f11c423aea26@cs.tcd.ie>
Date: Sat, 29 Jul 2017 00:53:47 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="qGAEigxUpaDBBmexsXFuqXVt8Dihp8NoV"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IPC52pciCpoNfp307Eu0NkyDodw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jul 2017 23:53:59 -0000


On 28/07/17 21:38, Eric Rescorla wrote:
> I'm not very enthusiastic about this. People come to the IETF to do work
> and having
> to deal with potential bustage from this experiment gets in the way of that.
> 

+1

IIUC correctly this'd also break DNSSEC for some names and has to.
If so, I'd be against it.

S.

> -Ekr
> 
> 
> On Mon, Jul 17, 2017 at 12:33 AM, Brzozowski, John <
> John_Brzozowski@comcast.com> wrote:
> 
>> Apologies, I understand this mail did not make it to the various lists.
>>
>> John
>> +1-484-962-0060
>>
>> -----Original Message-----
>> From: John Brzozowski <John_Brzozowski@Cable.Comcast.com>
>> Date: Sunday, July 16, 2017 at 20:28
>> 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>
>> Subject: Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
>>
>>     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
>>
>>
>>
>>
>>
>>
>>
>