Re: Market forces

otroan@employees.org Mon, 09 November 2020 12:44 UTC

Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CB203A1067 for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 04:44:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 FTirHlb4mYhX for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 04:44:42 -0800 (PST)
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::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 0CDC93A1033 for <ipv6@ietf.org>; Mon, 9 Nov 2020 04:44:41 -0800 (PST)
Received: from astfgl.hanazo.no (201.51-175-101.customer.lyse.net [51.175.101.201]) (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 1D5DC4E11AE5; Mon, 9 Nov 2020 12:44:41 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 535D9439DF10; Mon, 9 Nov 2020 13:44:39 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: Market forces
From: otroan@employees.org
In-Reply-To: <alpine.DEB.2.20.2011091330240.15604@uplift.swm.pp.se>
Date: Mon, 09 Nov 2020 13:44:39 +0100
Cc: Ted Lemon <mellon@fugue.com>, 6man WG <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9A8096F-7DD9-4476-AB32-6A96888F34C1@employees.org>
References: <160409741426.1448.16934303750885888002@ietfa.amsl.com> <3c1c3ab5-5726-b141-e7ed-618984bbbdb1@gmail.com> <CABNhwV1zoZpZNjb54rEys4+49H3vpebZW2g9JbO1_58eR+WnQg@mail.gmail.com> <CAKD1Yr0vvyQnTGRoSh4qa4He1gq5HXXRaKU3pVLtCtDUzcwL_w@mail.gmail.com> <CABNhwV13gggo9XfRvrR31bCUptZuAiosK5ebMmnzDdinKqmrBw@mail.gmail.com> <B7B3091C-92E0-482A-8D16-AD6DCFD1E714@isc.org> <CAD6AjGSCnG_fyorW2-tEqzzTfj897Knf55-0QV9DPcDKt45VOA@mail.gmail.com> <F323E4EB-5AAA-4C34-9EA2-06D4A0839308@thehobsons.co.uk> <77C70939-13F9-4B04-BEF1-F6894EA1C09C@fugue.com> <alpine.DEB.2.20.2011091330240.15604@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike=40swm.pp.se@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/GwnpgzrJw17uO5uAI-y-2Ky4odU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2020 12:44:44 -0000

>> So all this fuss about how to solve the problem of ISPs only giving out /64s is genuinely premature. Market forces will change their behavior. It’s just a matter of time.
> 
> There is an additional requirement here that is also an issue, and that's the lack of DHCPv6-PD support in the RG on its LAN interface, to sub-delegate any space it might have. This is not very common unfortunately, I see people show up weekly on the IRC channels I hang out in, with non-working IPv6 because they hooked up their Openwrt router behind their ISP router and it didn't support PD (even if there actually was a /56 delegated to the ISP-provided RG).
> 
> Other vendors also do not support this, one fairly popular brand is Ubiquiti that I see a lot of, which doesn't support sub-PD.
> 
>> From what I can tell, working as a delegating router within the home is 
> not in RFC7084.
> 
> I use openwrt at home primarily for this reason, as it does support sub-PD.
> 
> Unfortunately I don't think normal users will notice the lack of /64 or larger within the home. Software vendors will have to work around this with IPv4 fallback just like you say, to ensure a good customer experience. They will invisibly to the user workaround the problem to hide this network deficiency. It'll cost everybody time and money without anyone really noticing.
> 
> PS. I still remember my first IETF meeting, in Stockholm where I blundered at the mic about this and made a fool of myself with a "how hard can it be?" comment regarding sub-PD. That was 2009, and we're still not further ahead afaik.

sub-PD aka hierarchical PD only works in very specific topologies.
Which is why the IETF consensus went to another solution instead.

Cheers,
Ole