Re: [v6ops] IPREF as a transitioning tool

"jordi.palet@consulintel.es" <jordi.palet@consulintel.es> Fri, 10 November 2023 08:56 UTC

Return-Path: <prvs=1678a27eb0=jordi.palet@consulintel.es>
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 84F63C1522CB for <v6ops@ietfa.amsl.com>; Fri, 10 Nov 2023 00:56:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.005
X-Spam-Level:
X-Spam-Status: No, score=-7.005 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nQr3A8UTGR9Q for <v6ops@ietfa.amsl.com>; Fri, 10 Nov 2023 00:55:59 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B67DC187724 for <v6ops@ietf.org>; Fri, 10 Nov 2023 00:55:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1699606556; x=1700211356; i=jordi.palet@consulintel.es; q=dns/txt; h=From:Content-Type: Content-Transfer-Encoding:Mime-Version:Subject:Date:References: To:In-Reply-To:Message-Id; bh=Y3tgFUAhdvHv8OfEN+0prWsGJRnm/eMtfk K+h7WcTNQ=; b=KFvheULf56S9NCDrsqw1zopvEhZIiGbBGgqNEHbYkCdCCQoKjR 7XY7k0BLTz9fyeLgD1b7JyC0Cx3WgzjI2xd7ZY3lu6+qtpNryW6v0M7l3FtggASR B6W6xJmpQDWHe1tZH3Dw+daxgB1pNo7H7+bXIaq8PrCd52swwnQDMLjmw=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Fri, 10 Nov 2023 09:55:56 +0100
X-Spam-Processed: mail.consulintel.es, Fri, 10 Nov 2023 09:55:55 +0100
Received: from smtpclient.apple by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50001292495.msg for <v6ops@ietf.org>; Fri, 10 Nov 2023 09:55:54 +0100
X-MDRemoteIP: 10.8.10.10
X-MDHelo: smtpclient.apple
X-MDArrival-Date: Fri, 10 Nov 2023 09:55:54 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1678a27eb0=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
From: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
Date: Fri, 10 Nov 2023 09:55:40 +0100
References: <90f07ffa-1f44-8fa6-a6eb-b35c14fcf655@wdmsys.com> <11220775.0j3nEXixpK@asclepius.adm.tul.cz> <df800110-7ee4-23d8-e11f-c6e1e32e8edc@wdmsys.com> <33892F6F-A2AF-4BAA-BB33-1ED99F9FD674@isc.org> <442536ba-f736-5106-615c-7fcc0b8dc2a1@wdmsys.com>
To: V6 Ops List <v6ops@ietf.org>
In-Reply-To: <442536ba-f736-5106-615c-7fcc0b8dc2a1@wdmsys.com>
Message-Id: <BB43DD2A-97A7-4D46-BDB4-9AE52AE8A008@consulintel.es>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/GC1Y5zcE9vd06ZMLdeqAIW4CsKc>
Subject: Re: [v6ops] IPREF as a transitioning tool
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 10 Nov 2023 08:56:04 -0000

>> We already have the ability for IPv6 to connect to IPv6 to IPv4 using NAT64.  This can be run
>> with initiating traffic coming from both directions at the same time.  IPv6 on the public side
>> to IPv4 on the private side with static mapping and AAAA records in the DNS as well as the more
>> common use of dynamic mappings when running IPv6 only on the private side.  This has been done
>> for many years now.
> 
> ...thereby reinforcing IPv4. You will never do away with IPv4 Internet this way.
> 

I observe the contrary. Every time I enable IPv6 in an ISP or enterprise network, the amount of IPv6 traffic is bigger and bigger. In a residential ISP, it comes often to 85% of IPv6 traffic. In fact we see that with measurements from Google, Meta, Akamai, etc.

Also if I understood correctly, your mechanism requires an IPv4 option, and that’s not easy to deploy, actually this is the reason we have IPv6 instead of "IPv4+”, because the effort to deploy one or the other is the same, and IPv6 provides a better feature set in the long term, that if we just had “upgraded IPv4”.


> For as long as IPv4 Internet exists, the transition to IPv6 will never be completed.  Are you concerned at all that this may happen? Has there ever been a doubt in your mind that IPv4 might survive?  Is the fight over transition tools worth risking IPv6? IPREF transitions only to pure IPv6, it uses only pure IPv6 Internet. It removes IPv4 addresses.


Yes, of course, there will be some IPv4 traffic remaining in some networks, until some “un-updated” devices or apps are being used, but with IPv6-only with IPv4aaS, this is a no-brainer for most of the networks.



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.