Re: [v6ops] IPv4 trajectory

Ca By <cb.list6@gmail.com> Wed, 01 April 2015 03:06 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 9B5B21A1EF9 for <v6ops@ietfa.amsl.com>; Tue, 31 Mar 2015 20:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.651
X-Spam-Level:
X-Spam-Status: No, score=0.651 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, 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 wzSh4Dnhy6oq for <v6ops@ietfa.amsl.com>; Tue, 31 Mar 2015 20:06:09 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (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 1F6BB1A1EF5 for <v6ops@ietf.org>; Tue, 31 Mar 2015 20:06:09 -0700 (PDT)
Received: by wixo5 with SMTP id o5so20357339wix.1 for <v6ops@ietf.org>; Tue, 31 Mar 2015 20:06:07 -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=ufZvil0IVB9XLGN7IFR4jZ7LL8XdskcWaOeVY5Uh2Mk=; b=acbAx94urN70QssyzmTvf7T0qcfbmQmIKRNGNUYefE3kZ1jSWQfjAJWId+ZcTHYcvI 2ERXhu4FYsCoNjcFybnpMvYmVyOEw73H3bC0oBHFQlMq8rORXU9xN97J1XhuL2L+aQbu BNEPirr233wyEzseiAdmcIJA+64arhNoi6vzPfQ2xiladIZQOwUS27q7gCKDp+w3RS39 bvDbZhSTRosLvKvfGn6qs9/oKVghTTkiIIckWOHmwqWHV+eeRPag/jD2VUbU8U8KRAqp Y/mBAPavQeX9/ywm5t24ijeYUPBVNz2nA9UwagfjVb9eoUzH3RxyrYkd5CQu9ACXL5t7 UDYg==
MIME-Version: 1.0
X-Received: by 10.180.8.69 with SMTP id p5mr10711631wia.69.1427857567698; Tue, 31 Mar 2015 20:06:07 -0700 (PDT)
Received: by 10.194.93.164 with HTTP; Tue, 31 Mar 2015 20:06:07 -0700 (PDT)
In-Reply-To: <B0D588CB-0448-44FE-BE3F-4D0B890B5756@cisco.com>
References: <D1401A6F.90498%Lee@asgard.org> <551AF135.3060602@gmail.com> <B7AD5376-A2CF-43DF-9A84-B75CFDDBD6FF@cisco.com> <551B37B9.4090400@gmail.com> <B0D588CB-0448-44FE-BE3F-4D0B890B5756@cisco.com>
Date: Tue, 31 Mar 2015 20:06:07 -0700
Message-ID: <CAD6AjGQXt6DwmYkbDKyB-9SJzL5znsHTSJAG8=smPS8yZRpqhA@mail.gmail.com>
From: Ca By <cb.list6@gmail.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: multipart/alternative; boundary="f46d044283b61cd4d70512a0ff55"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/OJ07Xr-Nt9y-GUJGN4iCoj9AERc>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] IPv4 trajectory
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: Wed, 01 Apr 2015 03:06:10 -0000

On Tuesday, March 31, 2015, Fred Baker (fred) <fred@cisco.com> wrote:

>
> > On Mar 31, 2015, at 5:11 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com <javascript:;>> wrote:
> >
> > 5. Therefore, migrate IPv4 support to run over IPv6.
>
> Again, if you want the carrier’s logic, ask the carrier. But to me, that
> doesn’t follow.
>
> Not all core carriers, but a significant number of them, don’t think of
> themselves as carrying IPv4 or IPv6 per se. They think of themselves as
> MPLS houses, using jumboframes so that the addition of that header to
> whatever their payload happens to be (aka IPv4 or IPv6) doesn’t have an MTU
> problem. Whatever comes in, they throw it into the right tunnel (aka LSP)
> to get it to the right egress, MPLS gets it there, and it goes out the
> other door.
>
> You’re arguing about what kind of tunnel they should use. They’re quite
> happy with the one they have, and it’s neither IPv4 nor IPv6.
>

I am not a dfz network operator, but my network has an ipv4 control plane
that is rfc 1918 and only visible to the control plane, for the most
part.  My guess is that most dfz providers are not properly dual-stack,
they are using 6pe or 6vpe.

The forwaring plane is mpls. Full stop.

There is no pressure to ever change the composition of the backbone since
the backbone itself is not scaling quickly in terms of ip address usage.

It is only the edges that scale and sees address pressure: eyeballs, sensor
/ things , cdn, compute ....

So there is no forcing function turning ipv4 off...

Except percentage of 'high value' ipv4 traffic will go down, but dfz routes
will go up. So, this will create an interesting conflict as dfz ipv4 routes
go up, costs go up to support + 1m routes, ddos junk traffic goes up
...ultimately in 5 years the ipv4 dfz will be mostly ddos related udp with
1m+ routes while the ipv6 dfz relatively well aggregated and ddos free (no
win xp, no super legacy cpe, ...)

Knocking on wood the ipv6 stays as clean as it is today.  But, the rate of
decay of 'high value' ipv4 traffic is extreme. Watch this space.  IPv4 is
becoming worse than the back row on $airline

CB