IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Sat, 29 July 2017 17:55 UTC

Return-Path: <randy@psg.com>
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 4AD7F131CD5 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 10:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.002
X-Spam-Level:
X-Spam-Status: No, score=-5.002 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 M97tp-2fuul4 for <ietf@ietfa.amsl.com>; Sat, 29 Jul 2017 10:55:26 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48E4F131C88 for <ietf@ietf.org>; Sat, 29 Jul 2017 10:55:26 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dbVxU-0001gu-6a; Sat, 29 Jul 2017 17:55:24 +0000
Date: Sun, 30 Jul 2017 02:55:22 +0900
Message-ID: <m2y3r7gmb9.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <mellon@fugue.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
References: <93C56C4E-8915-4116-B56D-2D623978FF55@cable.comcast.com> <CABcZeBPXC6w5UUee+O4vxsgS7UnKTGMTO=hu2CM+Au0pk4-h=g@mail.gmail.com> <3ECA0AA9-CC0D-420F-97AE-5AD81C81FE7F@fugue.com> <CABcZeBMYaYHrgnfm+7y9MKVXDAXfZk6n=1rCVdCDZUBzS2GanQ@mail.gmail.com> <0F3E8AF3-4302-406A-84D8-37402D14237B@fugue.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Qs_oLJcQDvbyi2pHYhSOw5SaWRw>
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: Sat, 29 Jul 2017 17:55:27 -0000

> The point is that we claim that we have produced something that will
> Just Work for the average user.  If you really think you can't "get
> work done" on an IPv6-only network with working and functional
> transition tech, we have a problem.

bingo!  you are right.  we have a problem.  nat64/dns64 breaks things
people use.  this is known, documented, and extremely annoying this many
years out [0].

the question is how to progress fixing nat64/dns64, given that a lot of
folk come to ietf meetings to simply get work done and not debug a semi-
working transport.  how about a bug bounty?  and maybe a fix bounty a
few times larger!

randy

--

0 - for just how many years, see my plenary rant against 4966 a few
    chicagos back.  it is my $dayjob's customers, the enterprises, who
    are the main target of nat64/dns64, and i am not happy that they can
    not deploy it safely.

v2.41.0 | Report a Bug | By Email | System Status