Re: [v6ops] Is there a problem? [was: Why enterprises aren't adopting IPv6]

Owen DeLong <owen@delong.com> Sat, 02 October 2021 08:03 UTC

Return-Path: <owen@delong.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 1AD893A0AA4 for <v6ops@ietfa.amsl.com>; Sat, 2 Oct 2021 01:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=delong.com
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 MdIuzVsacX_R for <v6ops@ietfa.amsl.com>; Sat, 2 Oct 2021 01:03:10 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 9CEBC3A0AA3 for <v6ops@ietf.org>; Sat, 2 Oct 2021 01:03:10 -0700 (PDT)
Received: from smtpclient.apple ([IPv6:2607:fb90:2172:f4a8:c0a8:407:1a27:bfd1]) (authenticated bits=0) by owen.delong.com (8.16.1/8.15.2) with ESMTPSA id 19282weo513051 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT); Sat, 2 Oct 2021 01:03:00 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com 19282weo513051
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delong.com; s=mail; t=1633161789; bh=iHdCFo4rjuxiM2YYfIk1VzF1KXlSYQT10mzbwJeW2FQ=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=yfHgv8GkHTgL8+LS7GV5zPf98FKyIWoIh8Gsns8Qu59WUhDCQTVInAhXFD3O4GwhN y2NydoSsa++mXWtEZbhmbvsExoAhMTImLeZ7aJWrmDuQCW7MKyKMoVvQsxVibzaIUZ 9UWiySIwQxL65WV+srwZjd9S6H2nbysvU2I7UY6s=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Owen DeLong <owen@delong.com>
Mime-Version: 1.0 (1.0)
Date: Sat, 02 Oct 2021 01:02:55 -0700
Message-Id: <C7F9DE00-8460-47AA-94BA-91EDCB805813@delong.com>
References: <m1mWPCU-0000JAC@stereo.hq.phicoh.net>
Cc: v6ops@ietf.org
In-Reply-To: <m1mWPCU-0000JAC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-v6ops-10@u-1.phicoh.com>
X-Mailer: iPhone Mail (19A346)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.4 (owen.delong.com [IPv6:2620:0:930:0:0:0:200:2]); Sat, 02 Oct 2021 01:03:09 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/08JsZRiC6eMJTR5W1d4MXH75d3U>
Subject: Re: [v6ops] Is there a problem? [was: Why enterprises aren't adopting IPv6]
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: Sat, 02 Oct 2021 08:03:18 -0000


> On Oct 1, 2021, at 13:32, Philip Homburg <pch-v6ops-10@u-1.phicoh.com> wrote:
> 
> 
>> 
>> Another way to describe it is what economists call "externalities", i.e.
>> costs that an enterprise creates for the community that it does not
>> pay for. The classical example is pollution - my fire pollutes your air,
>> and you pay the price while I use the heat.
>> 
>> The solution is "polluter pays", some way to force the cost of the
>> externality back onto the enterprise that creates it. How can we
>> force the costs back onto IPv4-only enterprises?
> 
> So it seems that you saying that running IPv6 has no net benefit in a 
> world dominated by IPv4. It seems that by now, eyeball providers have found
> some benefit in providing IPv6. 

Eyeball providers are out of IPv4 addresses and acquisition cost exceeds customer value. Eyeball providers need a much larger supply of IPv4 addresses to support IPv4-only content providers than the content providers do. 


Content providers are not (yet) facing shortage and their revenue per address is a much higher ratio than eyeball providers. 

This, like toxic polluters, lazy content providers are externalizing the cost of their laziness onto the eyeball providers. 

> However, we see that, for example, many content providers see no benefit in
> IPv6. Why is it that for them, a direct connection over IPv6 is not worth the
> effort compared to a connection through a CGNAT? 

Because they don’t pay the costs of that CGNAT. They create the cost, but the eyeball providers are forced to pay it. 

> Obviously, there is no way to force anybody to pay anything. We spend decades
> to make sure that internet traffic is cheap.

Major eyeball providers could, actually start demanding higher settlements for IPv4 peering than v6 and use that to start pushing some of the V4 costs back onto the content providers. 

> What can be done is to try find ways to make IPv4-as-a-service cheaper. 

That’s exactly the opposite of a good outcome, TBH. 

Owen

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