IETF Logo Mail Archive

Re: [v6ops] Why enterprises aren't adopting IPv6 (Re: Implementation Status of PREF64)

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 07 October 2021 14:02 UTC

Return-Path: <alexandre.petrescu@gmail.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 2FD883A05DC for <v6ops@ietfa.amsl.com>; Thu, 7 Oct 2021 07:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.667
X-Spam-Level:
X-Spam-Status: No, score=0.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 GF4WmXnkw36g for <v6ops@ietfa.amsl.com>; Thu, 7 Oct 2021 07:02:30 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 357903A053E for <v6ops@ietf.org>; Thu, 7 Oct 2021 07:02:30 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 197E2SeP045660 for <v6ops@ietf.org>; Thu, 7 Oct 2021 16:02:28 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 22B15201B50 for <v6ops@ietf.org>; Thu, 7 Oct 2021 16:02:28 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 193552053BA for <v6ops@ietf.org>; Thu, 7 Oct 2021 16:02:28 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 197E2RuE005393 for <v6ops@ietf.org>; Thu, 7 Oct 2021 16:02:28 +0200
To: v6ops@ietf.org
References: <CAO42Z2wdoSdJDOB2Zo0=ZK0ecOARRsdg2nbHZGSDOhryPbLfDw@mail.gmail.com> <F2BD0A42-E9AD-45DD-999A-638E73BE1177@delong.com> <CAKD1Yr2K3Gd3JD=NJFOoH6GYgs-8ACxRQB9-sKJ7cbF4_hxsow@mail.gmail.com> <0B533C71-5DB0-410D-A5A3-7E8FD559F214@delong.com> <CAKD1Yr3NoYfNT7+OVJoCCdgdif6AHHw29tNCPttS=-NuRZKv3w@mail.gmail.com> <DM6PR02MB692426B0EEDDC2C4D78D8EC0C3A89@DM6PR02MB6924.namprd02.prod.outlook.com> <CAKD1Yr25dtinLBeJpAuJ17NfLg7-ewM9QPvnXNuEJ8wiBQV9ig@mail.gmail.com> <CAO42Z2zqf=F6OTDK2e8cMYXdPgMZ=SgFJcn7BTKYGgcYsLT2iw@mail.gmail.com> <894BCFE9-0811-4AE6-9941-6183292E4431@delong.com> <7E8C5F52-596F-4CAB-89EB-B0D5BAF5F612@employees.org> <YVXvgS6GDX97sHOW@Space.Net> <46b0b83a-b6cf-f9f2-4686-a6ff695c5d6f@hit.bme.hu> <B310356B-3CD7-4FDB-BF57-E5123E8414B2@employees.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <ff61dedb-8edb-9803-dc63-33b10a5191b1@gmail.com>
Date: Thu, 07 Oct 2021 16:02:27 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <B310356B-3CD7-4FDB-BF57-E5123E8414B2@employees.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/U1KmcwjGEeGk3i3c7UI2S5ZgKBM>
Subject: Re: [v6ops] Why enterprises aren't adopting IPv6 (Re: Implementation Status of PREF64)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 07 Oct 2021 14:02:36 -0000


Le 30/09/2021 à 19:38, otroan@employees.org a écrit :
>>> IPv6-only without a NAT64 gateway is not workable today.
>> Well, it depends on, how you define "IPv6-only". If we are talking about "IPv6-only access and core network", any of the 5 IPv4aaS solutions (464XLAT, DS-Lite, MAP-T, MAP-E, Lw4o6) may be used, and only 464XLAT uses a stateful NAT64 gateway.
> 
> I was referring to IPv6 only as meaning IPv6 end to end.
> Which is the only case where an application would benefit from IPv6.

IPv6 end to end, despite of IPv6-to-IPv4-to-IPv6 like NAT64 is the only
tool that makes work a few visioconference tools which break if NAT64 is
there.

Visoconference braking in presence of NAT64 was the case at an IETF
meeting maybe in Singapour, or so.

Since then, the visioconference tools evolved a lot.

There is one that I would like to try which is this whatsapp web beta on
PC which works apparently without the need of the Android to be
connected (earlier it mandated the Android to be connected even if I was
on PC).

I dont know if you followed recent developments in these visio
multimedia and 2-factor authentications but there was a tendency to
mandate keeping both Android and PC connected if one wanted some
advanced app like like simulators, safe paying, etc.  There seems to be
a nascent tendency where the mandating of the smartphone to be connected
in order for the others to work (PC, etc.) seems to disappear.

That tendency is similar to the tendency where first they required the
smartphone to be connected in order for the smartwatch to work, or the
smartphone to be connected in order to be able to open the car door.
Nowadays the smartphone is no longer mandated to be connected in order
for the watch or the car to work.

It might advance along these lines, or not.

If it advances along these lines, it might that the problem of Android
forbidding DHCPv6 might no longer be that hard.

Alex

> 
> O.
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

v2.23.0 | Report a Bug | By Email