Re: [v6ops] Operational Consensus on deployment

Ca By <cb.list6@gmail.com> Tue, 05 August 2014 03:59 UTC

Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC3D21B280E for <v6ops@ietfa.amsl.com>; Mon, 4 Aug 2014 20:59:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 y3CCOn8hMJjW for <v6ops@ietfa.amsl.com>; Mon, 4 Aug 2014 20:59:46 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D52451B2807 for <v6ops@ietf.org>; Mon, 4 Aug 2014 20:59:45 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id ho1so6211693wib.2 for <v6ops@ietf.org>; Mon, 04 Aug 2014 20:59:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AmQEVJIZI0M/p9vqzShvWJDvra+Kh53dA7U+NFr+eAw=; b=MPO9HTA1dKi3kb2uPA/NDHYrpCEI2mXTTDqVszlcVx1Dhww7vY8xaRIR3CagYQvrgD vlbE/rAkL1g8RErkWYgiRWLk6EFY0libi1CYOW8htm46bvqULZQecSSnTjWMdLUeqSC+ F3WkROfcOwZQ+DkeLq1HKf5MFA7RN47EWgkqZtshXlsNCQeWrYcaRTleRPnTME7fDnYM 6n/0GMdBO71rG6T+3opIHQZIS/C57JpjHhob9+KWQATjIHPJsv0QS0cIz/Fabea3zDaH g0A9fXxEu0vyFKdZiNCu7cA7wV4qurrv5jSSNWml/8cxikpOg6ugOcnJ97AFq2yAFWT8 e9nw==
MIME-Version: 1.0
X-Received: by 10.180.187.141 with SMTP id fs13mr2541033wic.57.1407211184442; Mon, 04 Aug 2014 20:59:44 -0700 (PDT)
Received: by 10.216.49.133 with HTTP; Mon, 4 Aug 2014 20:59:44 -0700 (PDT)
Received: by 10.216.49.133 with HTTP; Mon, 4 Aug 2014 20:59:44 -0700 (PDT)
In-Reply-To: <CAD6AjGSgU5HjQnTvF-T4WU+_+6+f0GZ6jMg89a7=SOv6OBcJMA@mail.gmail.com>
References: <256EAE0B-5C11-42C7-BCA1-CEC7EE6713A7@cisco.com> <28BBAD81-F9FE-43EB-BF49-E5B85C2AB218@cisco.com> <20140804231151.AAAEF1B7AB9F@rock.dv.isc.org> <DDCCBBC8-8F5B-466D-985D-EBC9A1FBD6EB@cisco.com> <CAD6AjGSgU5HjQnTvF-T4WU+_+6+f0GZ6jMg89a7=SOv6OBcJMA@mail.gmail.com>
Date: Mon, 04 Aug 2014 20:59:44 -0700
Message-ID: <CAD6AjGTi+Cta=LktAfTCC5NDUNJaBqeM=NSYp3Jo5Lj09ZREPw@mail.gmail.com>
From: Ca By <cb.list6@gmail.com>
To: Fred Baker <fred@cisco.com>
Content-Type: multipart/alternative; boundary="001a11c381e4c5d51d04ffd9e27c"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/TsVnUd2dF7L8e9P-uur6S7TNNmc
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Operational Consensus on deployment
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Aug 2014 03:59:48 -0000

On Aug 4, 2014 8:44 PM, "Ca By" <cb.list6@gmail.com> wrote:
>
> Allow me to posit that the locus of internet growth is cloud, IoT, and
mobile. Growth areas are important because they drive ip address demand.
Public IPv4 as a unique host ID is dead and will never be used natively in
these high growth edge networks.
>
> Cloud is near 100% nat, the public address is abstracted from the host.
Look at AWS, they dont have a product that gives machines a public ip
address from AWS of any sort at any cost. It is all NAT.  My guess and
Azure and Google are similar, but i dont know.
>
> IoT -- simply cant scale on ipv4.
>
> Mobile -- always has been ipv4 nat in most places, and now approaching
all places.
>
> Even in old world DSL broadband like AT&T DSL, layer 2.75 is private ipv4
that moves the 6RD end to end on top.
>
> The bigger question is -- who thinks real  public dual-stack on every
node is viable for the timescale the ietf or edge network engineering
operates at?  Not T-Mobile US, not facebook, not at&t , not Amazon AWS, not
Terastream. All these networks run at least 1 stack virtually (or
relayed/proxied) and i doubt they see a path to real dual-stack.
>
> The better ietf i-d i would like to read is a post-mortem on why
dual-stack failed in edge networks and what the ietf can learn from this
failure.  It likely has an economic and psychological theme.
>
> Don't get me wrong, the utopian dream of everyone turning ipv6 on over
some period of time and ipv4 slipping off unnoticed into the sunset is
great... But clearly just a dream. It did not and will not happen.
>
> The history of ipv6 transition will not involve a distinct period of time
where a public ipv4 and ipv6 dual-stack internet happened.
>
> CB

Obligatory cross domain reference, although my wife says this theory is
bogus and gets angry when i bring it up

http://en.m.wikipedia.org/wiki/Punctuated_equilibrium