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

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Mon, 09 November 2020 10:18 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 C4CEA3A0E01 for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 02:18:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.622
X-Spam-Level:
X-Spam-Status: No, score=-1.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.276, 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 AFB1NI1J89T1 for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 02:18:26 -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 2FE673A010A for <ipv6@ietf.org>; Mon, 9 Nov 2020 02:18:25 -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 m1kc4Fh-0000IbC; Mon, 9 Nov 2020 11:18:21 +0100
Message-Id: <m1kc4Fh-0000IbC@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> <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> <21BC970D-8708-4090-A984-02E6E1305B94@gmail.com> <25099A60-8685-4226-8328-AA87376B62D2@ciena.com> <SN6PR02MB4512023A8418FA3BFA79F412C3EB0@SN6PR02MB4512.namprd02.prod.outlook.com> <8bc14b7a-9b4c-6f03-4e11-4fe02947fd31@gmail.com> <321718b8-41c4-8b85-6c0e-7d7cfeea6784@foobar.org> <e1b7bce4-7361-1e81-3496-ea47453d8285@g mail.com>
In-reply-to: Your message of "Mon, 9 Nov 2020 11:05:12 +1300 ." <e1b7bce4-7361-1e81-3496-ea47453d8285@gmail.com>
Date: Mon, 09 Nov 2020 11:18:20 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/hhpAfCi7DGlHms0zHqpCuOLjTdA>
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 10:18:28 -0000

>However, the privacy arguments are fairly strong for not going beyon
>d /80, I think, at any time in the future.

Peronally I'm a lot more worried about collisions. At the moment we have
no operational experience with collisions. Does DAD work? We don't really
know. How does a device recover if it picked an address that is a duplicate
of another.

If we look at /96. That means that more than one in 4 billion addresses
generated is a collision. If IPv6 is adopted worldwide, that will be many
collisions per day. 

A key question here is: do we set a relatively safe limit that allows us
to ignore DAD because duplicates essentially never happen, or do we let 
operator pick a prefix length, spend quite a bit of time trying to deal
with all the collisions that result.

For example, at the moment a low power IoT device could just switch off for
a while and resume. Technically that would be wrong, but in practice it works.
What would we do if IoT devices would randomly renumber do to collisions?

If we set a hard limit, then we are back at the original question, how do you
extend network if you got the longest possible prefix that is supported.