Re: [v6ops] reclassify 464XLAT as standard instead of info

Mikael Abrahamsson <swmike@swm.pp.se> Mon, 25 September 2017 10:19 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 000521332D4 for <v6ops@ietfa.amsl.com>; Mon, 25 Sep 2017 03:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 PvLVNVaRDVT9 for <v6ops@ietfa.amsl.com>; Mon, 25 Sep 2017 03:19:20 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 CE6611332CE for <v6ops@ietf.org>; Mon, 25 Sep 2017 03:19:19 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id BD22DB1; Mon, 25 Sep 2017 12:19:17 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1506334757; bh=rZ0xFdnJV/v4YKusgdT39D3qJM4Z1fmnZitMgYdoCzk=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=0w4w+86ZHB32j8uVQOQ+uqOwi979LEU0hrtzK1BLxEpbvHAy7Ws5qDdPNF4hgsnYy Ps1THBZNBo4hCtmDeWhJcsAaQURSzaOMK62jpoTkdrvyNQvpaE0/HWN2GbyT7kN4Zp /PKquuN09/fxp3rySmLXgE2eA/yFkT/w1EUUN7i0=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A3AC084; Mon, 25 Sep 2017 12:19:17 +0200 (CEST)
Date: Mon, 25 Sep 2017 12:19:17 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
cc: "v6ops@ietf.org" <v6ops@ietf.org>
In-Reply-To: <c0fc3043-d416-aaa7-152e-89b2a7e7c53b@gmail.com>
Message-ID: <alpine.DEB.2.20.1709251214430.18564@uplift.swm.pp.se>
References: <E48DDA04-C058-4992-906E-8C8BC0E102AB@consulintel.es> <de6b9aac-a3cc-0915-77c7-9fb880c3a16a@gmail.com> <20170921223305.B72A8878E716@rock.dv.isc.org> <CAKD1Yr13ijKCB_71_2vMyGurc3-kSraLJycGxZwf121tjp8u1Q@mail.gmail.com> <20170922070719.74AA687A424E@rock.dv.isc.org> <20170922114847.GV45648@Space.Net> <369B3917-D9F3-41D4-A7BD-DAE134310004@employees.org> <20170922122146.GY45648@Space.Net> <20170922212502.E0CFF87B00BA@rock.dv.isc.org> <CAKD1Yr0VdmS0APz-G5VmxMNY1y9Kj+g0VP4Jx0_MXLkqkVyE8Q@mail.gmail.com> <4bf16a40ffd44e9498babf7094b1e526@orange.com> <f8b54014-c5af-d63f-5eed-35f19728b4f7@gmail.com> <0E9B8640-E102-4AB0-8908-28A988795861@consulintel.es> <ba63f464-cf1e-69d1-4d34-c961a8fef286@gmail.com> <CAAedzxqEeh4o4o=ZZbFh62XyjoiiKLPO__7HEE2CZxw9VWcUjw@mail.gmail.com> <9862ff34-8eea-c18a-88e5-d017630efefa@gmail.com> <alpine.DEB.2.20.1709251202500.18564@uplift.swm.pp.se> <c0fc3043-d416-aaa7-152e-89b2a7e7c53b@gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/crlc8SOsDTqGEmiX3ZjBluf3tsU>
Subject: Re: [v6ops] reclassify 464XLAT as standard instead of info
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 25 Sep 2017 10:19:21 -0000

On Mon, 25 Sep 2017, Alexandre Petrescu wrote:

> If it can, then use it.

Some people want to migrate away from IPv4 in their networks. This has to 
be done incrementally, and since encap can be done over IPv4 and IPv6 
without the customer seeing any difference, then this is a good way to do 
things incrementally.

So over time we'll see people migrate from LDPv4 to LDPv6, from GTP over 
IPv4 to GTP over IPv6, from 6PE to 4PE etc.

In the end, IPv4 will be a corner case service tunneled/translated over an 
IPv6 network for most people. We might be up to 20 years out from this 
being done universally, but that's the end goal for most people who have 
actually put serious thought into their long time future. I know people 
who are already trying to do this because they're growing quickly and they 
don't have IPv4 addresses to spare, to waste on infrastructure use, and 
using RFC1918 addresses has lots of operational downsides.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se