Re: IPv4 outage at next IETF in Chicago

Jeffrey Eric Altman <jaltman@secure-endpoints.com> Wed, 25 January 2017 02:48 UTC

Return-Path: <prvs=11982cef5f=jaltman@secure-endpoints.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 2C93112962E for <ietf@ietfa.amsl.com>; Tue, 24 Jan 2017 18:48:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=secure-endpoints.com
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 CP_6cCdxJBX9 for <ietf@ietfa.amsl.com>; Tue, 24 Jan 2017 18:48:41 -0800 (PST)
Received: from sequoia-grove.secure-endpoints.com (sequoia-grove.ad.secure-endpoints.com [208.125.0.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ADFD12962B for <ietf@ietf.org>; Tue, 24 Jan 2017 18:48:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=secure-endpoints.com; s=MDaemon; t=1485312499; x=1485917299; i=jaltman@secure-endpoints.com; q=dns/txt; h=VBR-Info: Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; bh=1B2dEN4Fz Mx5HLB2RyotFx2L5ZyPptY+Y1oI84ekIw0=; b=shwsb1vBPRNLsE6h1lMFswmb8 nwtIhnxHgS1yEdBSoUOYsu+CNpW1VAFco/P2Gdd1c3XQPY91ByKsBU9UTXcIyRH+ YScFRDTQEBcXgQovAp61Am9n3Iai+NqB/oyw6xqI95JpVOpY920Ns1KzjSo6o7yr bCfdHMg+GM6iAjGpL0=
X-MDAV-Result: clean
X-MDAV-Processed: sequoia-grove.secure-endpoints.com, Tue, 24 Jan 2017 21:48:19 -0500
X-Spam-Processed: sequoia-grove.secure-endpoints.com, Tue, 24 Jan 2017 21:48:18 -0500
Received: from [x.x.x.x] by secure-endpoints.com (Cipher TLSv1:AES-SHA:256) (MDaemon PRO v16.5.2) with ESMTPSA id md50001251872.msg for <ietf@ietf.org>; Tue, 24 Jan 2017 21:48:17 -0500
VBR-Info: md=secure-endpoints.com; mc=all; mv=vbr.emailcertification.org;
X-MDRemoteIP: 166.171.184.60
X-MDArrival-Date: Tue, 24 Jan 2017 21:48:17 -0500
X-Authenticated-Sender: jaltman@secure-endpoints.com
X-Return-Path: prvs=11982cef5f=jaltman@secure-endpoints.com
X-Envelope-From: jaltman@secure-endpoints.com
X-MDaemon-Deliver-To: ietf@ietf.org
X-CAV-Result: clean
Content-Type: multipart/signed; boundary=Apple-Mail-14B1554E-C924-4A04-B899-3595B4912D1B; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (1.0)
Subject: Re: IPv4 outage at next IETF in Chicago
From: Jeffrey Eric Altman <jaltman@secure-endpoints.com>
X-Mailer: iPad Mail (14D27)
In-Reply-To: <212835829.114144965.1485306337275.JavaMail.zimbra@peachymango.org>
Date: Tue, 24 Jan 2017 21:48:11 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <B32D096F-11DA-45FF-907B-6DA54CB1AFC2@secure-endpoints.com>
References: <844840869.114000858.1485299485194.JavaMail.zimbra@peachymango.org> <8112f1a6-f63a-e771-f354-206fbb9d684f@gmail.com> <WM!9d8566ee4a667cbd16edab2df707ef7a0c8c696ee92bca1ab194c80d7f9f38afca46538cbe422dcfd43306b1345f3435!@mailstronghold-1.zmailcloud.com> <212835829.114144965.1485306337275.JavaMail.zimbra@peachymango.org>
To: Franck Martin <franck@peachymango.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g_AhXkoz09LCSlkv2rXevNDOJn0>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 25 Jan 2017 02:48:43 -0000

> On Jan 24, 2017, at 8:05 PM, Franck Martin <franck@peachymango.org> wrote:
> 
> 
> ----- Original Message -----
>> From: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
>> To: "Franck Martin" <franck@peachymango.org>rg>, "IETF" <ietf@ietf.org>
>> Sent: Tuesday, January 24, 2017 4:33:22 PM
>> Subject: Re: IPv4 outage at next IETF in Chicago
> 
>>> On 25/01/2017 12:11, Franck Martin wrote:
>>> I think it is time to move to the next level of IPv6 deployment.
>>> 
>>> Ideally the IETF WiFi network should now only provide the following 2 networks:
>>> 1)IPv6-only
>>> 2)IPv6-only with NAT64
>>> 
>>> The later should be the default network.
>>> 
>>> However you would say, well some stuff will break, some non technical people
>>> will use the IETF network and may have a bad experience, etc...
>>> 
>>> So to be conservative but at the same time futurist and like it was done a few
>>> years back, why not create again an IPv4 outage of a few hours where the above
>>> 2 networks would be the only networks available?
>> 
>> That would be a good way of damaging IETF productivity for a few hours.
> 
> Do you have evidence of applications not running in a NAT64 environment? I'm interested to know them.
>> 

AFS

The afs location service returns explicit IPv4 addresses for volume locations not names to be looked up via DNS.

Jeffrey Altman