Re: [v6ops] IPREF as a transitioning tool

Vasilenko Eduard <vasilenko.eduard@huawei.com> Fri, 10 November 2023 11:36 UTC

Return-Path: <vasilenko.eduard@huawei.com>
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 A9D27C16F3EC for <v6ops@ietfa.amsl.com>; Fri, 10 Nov 2023 03:36:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
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 Gzd6S5REstoN for <v6ops@ietfa.amsl.com>; Fri, 10 Nov 2023 03:36:24 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 683E5C15C2BA for <v6ops@ietf.org>; Fri, 10 Nov 2023 03:36:24 -0800 (PST)
Received: from mscpeml100001.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4SRcBQ33n8z67ZTF; Fri, 10 Nov 2023 19:32:46 +0800 (CST)
Received: from mscpeml500001.china.huawei.com (7.188.26.142) by mscpeml100001.china.huawei.com (7.188.26.227) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Fri, 10 Nov 2023 14:36:20 +0300
Received: from mscpeml500001.china.huawei.com ([7.188.26.142]) by mscpeml500001.china.huawei.com ([7.188.26.142]) with mapi id 15.01.2507.031; Fri, 10 Nov 2023 14:36:20 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: "jordi.palet@consulintel.es" <jordi.palet=40consulintel.es@dmarc.ietf.org>, V6 Ops List <v6ops@ietf.org>
Thread-Topic: [v6ops] IPREF as a transitioning tool
Thread-Index: AQHaE3MJIXnk3bdf8EyI+pPG83c+frByrooAgAAyFACAACZvAIAABx4AgABe7+A=
Date: Fri, 10 Nov 2023 11:36:20 +0000
Message-ID: <0bdf98fd6c694256872bd47175d222f3@huawei.com>
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> <BB43DD2A-97A7-4D46-BDB4-9AE52AE8A008@consulintel.es>
In-Reply-To: <BB43DD2A-97A7-4D46-BDB4-9AE52AE8A008@consulintel.es>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.191.128]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/rQ9Qt8lzFbPOIRGbVjb5kNelP8U>
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 11:36:28 -0000

IPv4 has chances to be "for business" for decades.
Internet would probably transition to IPv6.
Ed/
> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of
> jordi.palet@consulintel.es
> Sent: Friday, November 10, 2023 11:56 AM
> To: V6 Ops List <v6ops@ietf.org>
> Subject: Re: [v6ops] IPREF as a transitioning tool
> 
> 
> >> 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.
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops