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

Philip Homburg <pch-v6ops-10@u-1.phicoh.com> Sat, 02 October 2021 10:14 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 F39C73A1004 for <v6ops@ietfa.amsl.com>; Sat, 2 Oct 2021 03:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 NLPphXq-cezi for <v6ops@ietfa.amsl.com>; Sat, 2 Oct 2021 03:14:42 -0700 (PDT)
Received: from stereo.hq.phicoh.net (pch.xs4all.nl [83.160.102.151]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14C1E3A0FFD for <v6ops@ietf.org>; Sat, 2 Oct 2021 03:14:40 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #158) id m1mWc20-0000IcC; Sat, 2 Oct 2021 12:14:12 +0200
Message-Id: <m1mWc20-0000IcC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
From: Philip Homburg <pch-v6ops-10@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <m1mWPCU-0000JAC@stereo.hq.phicoh.net> <C7F9DE00-8460-47AA-94BA-91EDCB805813@delong.com>
In-reply-to: Your message of "Sat, 2 Oct 2021 01:02:55 -0700 ." <C7F9DE00-8460-47AA-94BA-91EDCB805813@delong.com>
Date: Sat, 02 Oct 2021 12:14:10 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/lqjUQopKIDzCnllQQLgjiDVYCcA>
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 10:14:46 -0000

> 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.

As far as I know, eyeball providers have waited until the last possible
moment with offering IPv6 to customers. For example, my phone got IPv6 address
(on mobile) just weeks ago.

Even then, most countries have less than 50% adoption of IPv6 by eyeball
providers.

So it seems like eyeball providers didn't do IPv6 when they had enough 
IPv4 addresses. And that they are out of address suddenly everybody has
to do IPv6.

Of course, I'm happy that my phone now finally has an IPv6 address.

> 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.

I think for a long time, the internet community at large has argued against
eyeball providers demanding money from content providers.

However, in the cases where an eyeball provider is already collecting
money from content providers, what is stopping them from offloading the
cost of the CGNAT and IPv4 addresses to the content providers? That seems like
an easy way out.

The classical argument again this is that the customers of the eyeball ISP
should pay for access to IPv4. They are the ones that want the content.