Re: the race to the bottom problem

Bob Hinden <bob.hinden@gmail.com> Sat, 07 November 2020 17:41 UTC

Return-Path: <bob.hinden@gmail.com>
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 345D43A0995; Sat, 7 Nov 2020 09:41:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, 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 (2048-bit key) header.d=gmail.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 E15BvdCIiInR; Sat, 7 Nov 2020 09:41:26 -0800 (PST)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B4693A098E; Sat, 7 Nov 2020 09:41:26 -0800 (PST)
Received: by mail-wr1-x42a.google.com with SMTP id 33so4529719wrl.7; Sat, 07 Nov 2020 09:41:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=3++oxIlb0mYoxo1blRkYOiB6aOEXATos+SJ+9yn0jas=; b=WGlbsOglXpDhETSjLKb06BZCCOlooFXKcPe+DC2hdo504qC81GHb4ew5V/66XyJ3RP 0SgfLRTSt7BDMil5KtouGUUi+WLteIipuJrxXeQttzI8AZeSbXlbokvAUTl2EyybxlGe FhO1p5q+FNcNKE8JKcwWXO1dBM5tG3RaZbLfftIRJDUu6R8Mc9YWkfrML+JVJJsx+i+u XttCw5WgCY1/fYlDPlFQbaP93shSRgm+aMG1re75+oKDHEe6gkmREkO0+WmdCpzs1cTl HB7iRm6QcLO2w4TNxDi630Fr48BEA/8/25MFKxz2TGP6MCJZ9YhaE2KSdJATZbEP10gz fVIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=3++oxIlb0mYoxo1blRkYOiB6aOEXATos+SJ+9yn0jas=; b=jSdNfHghnCLmXSIbaHI7vfNFSQqcZOLthzdsCsgTAKKnA0kqfNb5KI9Bt2Ftyikgyw FYZQFf0bxsePuLtSH1trTucxF9L80pixLlo4Knp/U6zb4qxZO1SnGiileshTPotHn53d AM1tZALQDVtOqNjV2IiyCWGlUqzlg2hfCYL+NrOhggXINg1thotuBm+wYX0vhoqRkffi d+q7zm0aUaLUnsVL8MGIeGfVUbKh8dw6am0J/XMgffYEJ6pIHN6FhUstDa5SLdpFMptD cFblc4ggkrGw86DyMnUphs//KVv1SV7cT9zNSeqOSUt4BupOgA6epnK8APagCXTPaUzM /32A==
X-Gm-Message-State: AOAM531RbysG0hqiOoZgO4Y2H+LJjJpGt3OjkCWKka6sMdg3o35DfxGZ 7+kUcPXzJvQVpydODz1iuqU=
X-Google-Smtp-Source: ABdhPJyA9zmzGhUYrqUj5ENtE7IimBInuKR+sk/snO7DB+RCJUiog9fuucGz4a9anILHIP6h2zy0ew==
X-Received: by 2002:a5d:6ca6:: with SMTP id a6mr8822259wra.348.1604770884817; Sat, 07 Nov 2020 09:41:24 -0800 (PST)
Received: from ?IPv6:2601:647:5a00:ef0b:d423:299:1091:776d? ([2601:647:5a00:ef0b:d423:299:1091:776d]) by smtp.gmail.com with ESMTPSA id h62sm7205308wrh.82.2020.11.07.09.41.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 07 Nov 2020 09:41:23 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <E87C175C-C06D-485E-B790-6BC3DB48F101@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_48DEB605-7C03-4146-8437-73B7C714DFE7"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Subject: Re: the race to the bottom problem
Date: Sat, 07 Nov 2020 09:41:20 -0800
In-Reply-To: <CAKD1Yr1yiXR43mL45KbsZkKY7_YVhWFzW82LL6qed6mVPBjxaw@mail.gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Mark Smith <markzzzsmith@gmail.com>, draft-mishra-6man-variable-slaac@ietf.org, IPv6 List <ipv6@ietf.org>, "Mudric, Dusan" <dmudric=40ciena.com@dmarc.ietf.org>
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
References: <160409741426.1448.16934303750885888002@ietfa.amsl.com> <3c1c3ab5-5726-b141-e7ed-618984bbbdb1@gmail.com> <CABNhwV1zoZpZNjb54rEys4+49H3vpebZW2g9JbO1_58eR+WnQg@mail.gmail.com> <CABNhwV3L7kz=cWu8s3X=djVf4MCwewzbEgx09TWaKzCULCjYUQ@mail.gmail.com> <9A9CE8E7-3552-4FD8-A50E-1BDCA2CB813F@employees.org> <CABNhwV0LxM7EuKo2wNtVacjewsVqdhrmSiVBmB_EL-mqJYdU3A@mail.gmail.com> <CD9F9F09-2CBC-4A72-99C0-4A9A470357ED@employees.org> <9e787ed0-a221-e413-e030-ac2553dffc8e@gmail.com> <a21c9447-730b-e2c0-81f6-46deda57f507@gmail.com> <f4635fa9-45ca-f7ec-40a2-41764e1ca74f@si6networks.com> <905bcc26-a223-53d0-6675-c35579b9a8be@gmail.com> <AAE75F7F-F8DF-4B7F-9C50-3D6C91544997@ciena.com> <2b59b2de-3597-8d35-374d-75e9b10d4d83@gmail.com> <CAO42Z2zUvDE2ZSCnZa_525Hj7OthhEoDGZcd0D9xxZVW3D8aeg@mail.gmail.com> <CAKD1Yr1yiXR43mL45KbsZkKY7_YVhWFzW82LL6qed6mVPBjxaw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/q7t2GduJeWUliHsmqYcYCCFQArQ>
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: Sat, 07 Nov 2020 17:41:28 -0000

Lorenzo,

> On Nov 6, 2020, at 11:31 PM, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org> wrote:
> 
> On Sat, 7 Nov 2020, 08:17 Mark Smith, <markzzzsmith@gmail.com> wrote:
> The current bottom is a single /64.
> 
> Any provider who is only giving out a single /64 to customers who might or will need more than one /64 has already raced to the current bottom.
> 
> A "deeper bottom" or longer default allowed prefix length will just facilitate further racing to the deeper bottom. It won't encourage giving out more than one /64 for those who might need them; it'll do the opposite.
> 
> Exactly.
> 
> The fixed 64 bit boundary prevents this by defining the bottom in the *only* way that actually matters: by ensuring that if a network goes below the bottom, many hosts just won't work.
> 
> If it were possible to hand out less than a single /64 and have things work acceptably for their customers, then someone, somewhere, would be doing it already.
> 
> If we change the standards to make this technically possible but ask operators not to do it, some will just do it anyway. After all - if it works for them, why would they do otherwise? Because an RFC they maybe haven't even read says they shouldn't?
> 
> The logical consequence is that we end up at /128. This is particularly risky because any operator with lots of experience with IPv4 will find "one /128 per host" obvious, expected and natural. One device has one IP address, right? And once get to that point, we'll need to bring back NAT in order to extend further. That would pretty much make the entire transition to IPv6 pointless. We might as well have stayed with IPv4.

I agree.

> Personally I think that once there's more industry experience and IPv6 is widely deployed in all network types (say, once we reach 80% of the internet, and many networks are IPv6-only), we might be able to safely move the bottom, once. But it's much too early for that.

From reading this thread, I think if there is a problem to solve now, it is to make it easier for mobile operators to give shorter prefixes to mobiles.   If there are problems with DHCPv6 PD let’s fix that, or if some other mechanism is needed let’s do that.   We should not be going in the other direction.

Bob