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

otroan@employees.org Thu, 30 September 2021 17:04 UTC

Return-Path: <otroan@employees.org>
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 3A0E73A0DC5 for <v6ops@ietfa.amsl.com>; Thu, 30 Sep 2021 10:04:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 D2X3kE0wkvTP for <v6ops@ietfa.amsl.com>; Thu, 30 Sep 2021 10:04:23 -0700 (PDT)
Received: from clarinet.employees.org (clarinet.employees.org [198.137.202.74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A163C3A0DCA for <v6ops@ietf.org>; Thu, 30 Sep 2021 10:04:23 -0700 (PDT)
Received: from astfgl.hanazo.no (ti0389q160-5225.bb.online.no [95.34.0.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id C4BF94E11B4A; Thu, 30 Sep 2021 17:04:22 +0000 (UTC)
Received: from smtpclient.apple (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 28E2961FCC9A; Thu, 30 Sep 2021 19:04:19 +0200 (CEST)
From: otroan@employees.org
Message-Id: <7E8C5F52-596F-4CAB-89EB-B0D5BAF5F612@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_890C32C7-02E7-4211-9742-204A37AE41F4"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Thu, 30 Sep 2021 19:04:18 +0200
In-Reply-To: <894BCFE9-0811-4AE6-9941-6183292E4431@delong.com>
Cc: Mark Smith <markzzzsmith@gmail.com>, Jen Linkova <furry@google.com>, V6 Ops List <v6ops@ietf.org>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
To: Owen DeLong <owen=40delong.com@dmarc.ietf.org>
References: <CAN-Dau2in52xSUkqKEXu=2AAiR4O_jLhna7hY-hshYDORfGtcQ@mail.gmail.com> <CAMGpriWFp4JPtqDK5tEj1RkS-SzEfvscfUUnxgK+o6qP2pusRA@mail.gmail.com> <6E95834D-12B3-447B-8326-8EDE9DC6FFB1@delong.com> <CAO42Z2zA-4cK489nxKsWUN8vvU0eAiz-jS0e-_eWPg+OmP8wLw@mail.gmail.com> <DDA36020-90CC-471B-83AD-3D98950F1164@delong.com> <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>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/G2V7Y-pm3LZCSoCZaMMrFmpptLk>
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, 30 Sep 2021 17:04:27 -0000

Owen,

>> What is the main problem IPv6 was designed to solve?
>> 
>> Lack of IPv4 addresses.
> 
> Correct.
> 
>> What problem don't many enterprises have since they're using RFC1918s, and could misuse 100.64/10 if they really need to get more.
>> 
>> Most enterprises don't have the main problem that IPv6 is designed to solve.
> 
> Not entirely true… More accurately, many enterprises are able to pretend they don’t have this problem today because of the above.
> 
> However, eyeball providers DO have this problem and its getting worse. Further, eyeball providers are on some of the thinnest margins
> and consumer IP access is at the low end of the market, so paying for more and more IPv4 addresses and more and more expensive
> (and more complex) IPv4 solutions and higher support costs for those IPv4 solutions becomes a non-starter at some point.
> 
> Either consumer access in general will become significantly more expensive, or eyeball providers will start having to find a way to
> surcharge IPv4 services (whether that’s in the form of an IPv4 surcharge or an overall price increase with an IPv6-only discount
> or whatever).

typically they only use a 1/65535th of an IPv4 address ((one TCP port) although they share it at L7).
it would certainly be possible to improve on that.

> I already know enterprises that are experiencing pain because their outsourced contractors in certain parts of the world are basically
> IPv6-only already and the fact that their contractors can’t interact with the corporate network via IPv6 is causing issues.

would you have more details on that.
last time I tried going IPv6 only, that was completely unworkable.
(while doing IPv4 only is perfectly fine.)

>> For IPv6 to be adopted by many enterprises, there will need to be other reasons that are of business value.
> 
> Employee/contractor connectivity is of vale to most enterprises. There’s a time coming when that’s going to require IPv6 support.

that's what we have been saying for 25 years.
perhaps time to accept reality. ;-)

O.