Re: IPv6 Adoption Curve (was Re: Last Call: RFC 6346 successful: moving to Proposed Standard)

Randy Bush <randy@psg.com> Thu, 04 December 2014 09:44 UTC

Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47E361A0137 for <ietf@ietfa.amsl.com>; Thu, 4 Dec 2014 01:44:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 9Q3b9txcavkX for <ietf@ietfa.amsl.com>; Thu, 4 Dec 2014 01:43:58 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [198.180.150.18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9713A1A00DF for <ietf@ietf.org>; Thu, 4 Dec 2014 01:43:58 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1XwSx2-0000pW-2b; Thu, 04 Dec 2014 09:43:56 +0000
Date: Thu, 04 Dec 2014 18:43:55 +0900
Message-ID: <m2fvcvbvhg.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Olivier MJ Crepin-Leblond <ocl@gih.com>
Subject: Re: IPv6 Adoption Curve (was Re: Last Call: RFC 6346 successful: moving to Proposed Standard)
In-Reply-To: <54801F8E.6060302@gih.com>
References: <20141201223832.20448.34524.idtracker@ietfa.amsl.com> <A4CFF3FB-A9C5-47EA-A1CA-B900CDBF776E@gmail.com> <547F451C.3010507@dcrocker.net> <89433C24-5E69-463B-804B-62F73E0DFB12@istaff.org> <547FE8E6.4090103@dcrocker.net> <54801F8E.6060302@gih.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/e7zp6v0ihm2_F47bQO5GpDu708Y
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 04 Dec 2014 09:44:00 -0000

> What I am nervous about on the other hand, is that the lack of IPv6
> adoption is making the alternative growth scenarios using Carrier
> Grade NAT ever more attractive for some ISPs. CGN breaks the key end
> to end principle that we have on the Internet and many mobile networks
> are using CGN. Some non-mobile TelCos are now saying "hey we do not
> need to roll out IPv6 - just look how happy customers are in using
> their mobile networks with CGN!"

thanks for understanding what the enemy is.

at the dublin meeting, cgn could be seen on the horizon, and i was
sufficiently unhappy to stand up in plenary and rant against it.  russ
and a few others said "that's nice, put your money where your mouth is.
what's the alternative?"  this was the impetus for a+p, as the document
states right up front.

for a broader view than 6346, see

    Nejc Skoberne, Olaf Maennel, Iain Phillips, Randy Bush, Jan Zorz,
    and Mojca Ciglaric, "IPv4 Address Sharing Mechanism Classification
    and Tradeoff Analysis," IEEE/ACM Transactions On Networking April
    2014.  http://archive.psg.com/130419.ton-v4-sharing.pdf

some of the alternatives sure make stateless a+p look pretty good, eh?
my favorite may be ds-blight; nat in the core and you get to fork-lift
your cpe, a double win there.

ipv4 has pretty much run out; the iana free pool ran out long ago, along
with apnic and ripe.  arin will very soon.  like it or not, ipv6 is
depressingly poorly deployed; and our major forward strategy seems to be
denial as so well demonstrated in this thread.  the stonewalling and
denial have distracted from reducing the friction of deploying ipv6, so
have helped drive cgn deployment; so it *really* pisses me off [0].

the paragraph to which bob hinden objected

   We are facing the exhaustion of the IANA IPv4 free IP address pool.
   Unfortunately, IPv6 is not yet deployed widely enough to fully
   replace IPv4, and it is unrealistic to expect that this is going to
   change before the depletion of IPv4 addresses.  Letting hosts
   seamlessly communicate in an IPv4 world without assigning a unique
   globally routable IPv4 address to each of them is a challenging
   problem.

is tragically true; please point out a single untruth.  get over it.

and i like the situation less than most folk here, and with good reason.
my employer has thrown money at real ipv6 deployment for over 15 years,
wrote a lot of the stack many implementations still use today, ...

randy

---

[0] - i still feel the bruises and broken bones of the multiple years it
      took to get the tla/nla crap removed.  and that was just one of
      the battles.