IETF Logo Mail Archive

Re: IPv4 outage at next IETF in Chicago

Mark Andrews <marka@isc.org> Wed, 25 January 2017 04:15 UTC

Return-Path: <marka@isc.org>
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 701121296A8 for <ietf@ietfa.amsl.com>; Tue, 24 Jan 2017 20:15:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.1
X-Spam-Level:
X-Spam-Status: No, score=-10.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-3.199, 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 pipaFUKs4kKE for <ietf@ietfa.amsl.com>; Tue, 24 Jan 2017 20:15:40 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 7CE0A1295E2 for <ietf@ietf.org>; Tue, 24 Jan 2017 20:15:40 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 36FB134930F; Wed, 25 Jan 2017 04:15:38 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 211D3160042; Wed, 25 Jan 2017 04:15:38 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 0E915160067; Wed, 25 Jan 2017 04:15:38 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id r9F1_Luof4fl; Wed, 25 Jan 2017 04:15:37 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id A966F160042; Wed, 25 Jan 2017 04:15:37 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 35CE3608AF46; Wed, 25 Jan 2017 15:15:34 +1100 (EST)
To: Michel Py <michel@arneill-py.sacramento.ca.us>
From: Mark Andrews <marka@isc.org>
References: <844840869.114000858.1485299485194.JavaMail.zimbra@peachymango.org> <20170124235626.042F960836B0@rock.dv.isc.org> <158901d276b3$387d6050$a97820f0$@huitema.net> <F04ED1585899D842B482E7ADCA581B8459489B47@newserver.arneill-py.local> <20170125032702.11D576089F56@rock.dv.isc.org> <F04ED1585899D842B482E7ADCA581B8459489BA1@newserver.arneill-py.local>
Subject: Re: IPv4 outage at next IETF in Chicago
In-reply-to: Your message of "Wed, 25 Jan 2017 03:49:05 -0000." <F04ED1585899D842B482E7ADCA581B8459489BA1@newserver.arneill-py.local>
Date: Wed, 25 Jan 2017 15:15:34 +1100
Message-Id: <20170125041534.35CE3608AF46@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/F-hzSGEPMw4EyuEtgTBSgKQsJ6U>
Cc: Christian Huitema <huitema@huitema.net>, '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 04:15:41 -0000

In message <F04ED1585899D842B482E7ADCA581B8459489BA1@newserver.arneill-py.local
>, Michel Py writes:
> > Mark Andrews wrote :
> > But Microsoft aren't the only ones that are looking to deploy IPv6-only d=
> ue to not
> > having enough IPv4 addresses internally.  There is also Google, Facebook =
> ...
> 
> Your record has a groove. Been reading this for 15 years.
> 
> > The IETF has produced multiple solutions that provide IPv4 as a service w=
> ith IPv6-only to the node.=20
> > All of them require IPv6 nodes and/or applications to be updated to be ge=
> nerally useful.
> 
> I run an IPv4-only network.

And there are IPv4 as a service access solutions for that network.

> I like Brian Carpenter's pragmatism. The IPv6-only dream only exists in
> the IETF ivory tower.

The Mac I'm using is running in IPv6 only mode at the moment (just
turned IPv6 off in network managment panel).  I can get to the
corporate mail servers.  I can get to all the corporate web sites.
Jabber works from it.  I can get to the git repositories.

If my ISP would give me IPv6 I could get away without IPv4 for
almost all my work activities.

Now if Google would give their DNS servers AAAA addresses I could
get to the rest of their servers.  Come on Google your 99.9% of the
way there.

Facebook is reachable.

IPv6 only is definitely achievable.

Mark

> Michel.
>
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

v2.23.0 | Report a Bug | By Email