Re: [v6ops] IPv4 trajectory

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 01 April 2015 01:12 UTC

Return-Path: <brian.e.carpenter@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 99FB61B2A01 for <v6ops@ietfa.amsl.com>; Tue, 31 Mar 2015 18:12:55 -0700 (PDT)
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, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 i-w8pZVUuqQp for <v6ops@ietfa.amsl.com>; Tue, 31 Mar 2015 18:12:54 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) (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 987621B2BC6 for <v6ops@ietf.org>; Tue, 31 Mar 2015 18:12:47 -0700 (PDT)
Received: by pddn5 with SMTP id n5so37808646pdd.2 for <v6ops@ietf.org>; Tue, 31 Mar 2015 18:12:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Waelq1v+u9bCvPuax6EytIVpH57/AxrF/f5l3Ks6b3I=; b=kUL9Df2BP4gI1fZ1jIMDKZ4w4e/2sgeQp6BAhQXgB0QPmHR+dqyWXWxTmskm8eyUwf KqKUmLo/GPDX7q00NcJPDu3R/7lMLd3tO56Hp+RE7EzxMQC0bKbO+0zg7E7TFWxPZhE9 RDVlKxsk6BKhHiqezraJtg/npu5+TWa0E+t/R0yVMWqLXDcsM9/WizzVW8bZax2fN7I9 vvp6JZbIoiNkWDp1tMp/Mxd28sd4c/FYQZBlQX2cToHeMhmTZnNmZnV3jiqATjZpQjjt dUojFoLPrn8PhyJytLDumTknaLs25X9RTpkb+uOt1v1tDe4gzBBc82ZZzb5lYOGHBqH/ KfgA==
X-Received: by 10.68.200.169 with SMTP id jt9mr73431859pbc.164.1427850767326; Tue, 31 Mar 2015 18:12:47 -0700 (PDT)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by mx.google.com with ESMTPSA id zq6sm196466pac.11.2015.03.31.18.12.44 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Mar 2015 18:12:46 -0700 (PDT)
Message-ID: <551B460E.7040207@gmail.com>
Date: Wed, 01 Apr 2015 14:12:46 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@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>
In-Reply-To: <B0D588CB-0448-44FE-BE3F-4D0B890B5756@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/aiVKqREtocqY5xH1YVtyUKEc2bw>
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 01:12:55 -0000

On 01/04/2015 13:32, Fred Baker (fred) wrote:
> 
>> On Mar 31, 2015, at 5:11 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> 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.

Makes sense. But in that case, ships-in-the-night is the final state
for such providers, as far as IPv4 goes; I have no problem with that.

    Brian