Re: [**EXTERNAL**] Re: the race to the bottom problem

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Fri, 06 November 2020 16:36 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 F287E3A08B8 for <ipv6@ietfa.amsl.com>; Fri, 6 Nov 2020 08:36:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.623
X-Spam-Level:
X-Spam-Status: No, score=-1.623 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.275, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 YVi39mVJ8ucp for <ipv6@ietfa.amsl.com>; Fri, 6 Nov 2020 08:36:27 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 658483A08AF for <ipv6@ietf.org>; Fri, 6 Nov 2020 08:36:27 -0800 (PST)
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 #157) id m1kb4ir-0000KIC; Fri, 6 Nov 2020 17:36:21 +0100
Message-Id: <m1kb4ir-0000KIC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: [**EXTERNAL**] Re: the race to the bottom problem
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
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> <SN6PR02MB45129EE49060E5DBFEC9FBD0C3ED0@SN6PR02MB4512.namprd02.prod.outlook.com>
In-reply-to: Your message of "Fri, 6 Nov 2020 16:19:26 +0000 ." <SN6PR02MB45129EE49060E5DBFEC9FBD0C3ED0@SN6PR02MB4512.namprd02.prod.outlook.com>
Date: Fri, 06 Nov 2020 17:36:19 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/r-oR67wOfLJyhrCedHizIVC75jI>
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: Fri, 06 Nov 2020 16:36:29 -0000

> I'm thinking it might be reasonable to impose a requirement on CE
> routers (and devices in similar roles) that it MUST NOT accept
> delegation of a prefix longer than 64 bits on any interface using
> a technology that only exists on WAN links (e.g., DSL, PON, DOCSIS).
> This doesn't fully solve the problem. But if it's hard to get
> routers that will accept such delegations on WAN-only links, it
> will discourage most operators from doing them. From a business
> analysis case, the cost of providing prefixes with length <= 64
> would be less than the cost of making sure all their customers have
> CE routers in place that do not have this limitation.  Barbara

We can also impose a requirement on CE routers and phones, etc. that if they
don't get a suitable prefix (using DHCPv6 PD or homenet) to number all of
their downstream interfaces using /64s, then they should drop the WAN link.

Is such a requirement going to have any effect? Probably not.