[IPv6]Re: Analysis of Ungleich ULA Registry

Kyle Rose <krose@krose.org> Thu, 23 May 2024 20:49 UTC

Return-Path: <krose@krose.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 5E66FC14F695 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2024 13:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=krose.org
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0wx8kYLLV-SQ for <ipv6@ietfa.amsl.com>; Thu, 23 May 2024 13:49:46 -0700 (PDT)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80E08C14F5FD for <ipv6@ietf.org>; Thu, 23 May 2024 13:49:46 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id 38308e7fff4ca-2e95a60dfcdso1978381fa.1 for <ipv6@ietf.org>; Thu, 23 May 2024 13:49:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; t=1716497384; x=1717102184; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xmGv1fmEYWWmwssMYrQ/YCZEntyV9As1LNsB4sQDyh0=; b=O0nDubUSaZ9F2nlyCGJ2cnT+THinAxRcu35oFYjkTfY5TaSX/x4SAsSFFNkwLE2EZZ 9ikg8vAYAqOnovJoSS5kWjTNiZ76WeCy1TElP9CAO1b9sX2V+pyjY/Gri8v+TALWsYC0 zZ/iC3dIkfAbRyn9ueIwSdh5c4ZniMwc3IdNQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716497384; x=1717102184; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xmGv1fmEYWWmwssMYrQ/YCZEntyV9As1LNsB4sQDyh0=; b=vq21rHsEA7r7h6JplESXmjo26gguDKnNhFts3cl+bv8i5Xso+Q2bU+PsKFaiXpFaga RdCrTgHKyCbZ1GhPrgAjIJnRt9SOBqSRJogbNSXaLXsA+3gVF+3yHfX+RrvQMLLbnLsi I9R2nhQlpFj9cmWAWq9SGE65fLwU9D8siq9T/iMiSnAsCMo9iZPe4lVRjSDS59cwG9gE UA1ELei1QsegEwpgoDii+hVLIzm+uprUjkgl35+Kmh+VJZBpeKnlSziItdUzPMX52a5/ 5kkS/bjnLO5ick/Rke/UKcreM/4EwWPly6aHBGv4NWpET9bTzGwEFNjTwCtEh2iNmSy4 pSJg==
X-Forwarded-Encrypted: i=1; AJvYcCVsN4kLJ+Xg+4Bz5m4bepOMYjXd2o6eFRTeY28zKtq/vjpPL30Dh9f8jRb6oeWihxM2Xu8yHyYsrAOKoy4P
X-Gm-Message-State: AOJu0Ywtb+oVKc+Lzs7wIJul1Q9HBN8kUuEg8qwHaInLO0kp4/NffUso v9ex9l6PebAlPTRxtKk4ddhAAIU0ULV0hzrNxa18mHF8GC5X1go+rTVEYRWeSY+JRiO9XD1DdmZ X1RCU69IAe4sRjsuAM6kP8saTpQauinsHW9mHDg==
X-Google-Smtp-Source: AGHT+IGVFeOdDD/fH1aGVx02NyQRI+4rUij/ygLUZcI9k+nOts5orTlXSlAkc/sKzQb6Z9Rlz5MO9XzTHa8AvwtQohg=
X-Received: by 2002:a19:c50d:0:b0:524:b6ad:c3e with SMTP id 2adb3069b0e04-52966e9aafcmr102137e87.67.1716497384012; Thu, 23 May 2024 13:49:44 -0700 (PDT)
MIME-Version: 1.0
References: <CAN-Dau0J1uqpwnRXYpeSFGUTJ532MmpeGd4BLoAqqf8HzeFTjQ@mail.gmail.com> <CAJU8_nW7Q3WphfgtgnK0E+88R1_nENCy9MBBYhG2G1bkPD9UeQ@mail.gmail.com> <CAN-Dau0Nc0VHMHdRg7MG6yf2X1S_SrYbA6YhKUzBz7XiLkR5cg@mail.gmail.com> <CAJU8_nX4O9hs6R6sOw2+iEL-7urcadNBdBsZfP3-Dn_yUFovLA@mail.gmail.com> <46c161b8-ca0d-4f18-ae3e-22fcb5befb0c@gmail.com> <CAKD1Yr3hTHy+p4nN1mkv4kHb907914gfyxnnzdexy6dYhNmiTw@mail.gmail.com> <7bcaaf7e-4564-4d76-9558-ab005aa70a30@gmail.com>
In-Reply-To: <7bcaaf7e-4564-4d76-9558-ab005aa70a30@gmail.com>
From: Kyle Rose <krose@krose.org>
Date: Thu, 23 May 2024 16:49:32 -0400
Message-ID: <CAJU8_nUkO8mMY0GEZVj_nKN1f0bNxZwfv=oBKLtV6OgD86ZmAg@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000d524930619253001"
Message-ID-Hash: JK7WNC7EBEJZ76TQEIVJRQRJHUD6OI3I
X-Message-ID-Hash: JK7WNC7EBEJZ76TQEIVJRQRJHUD6OI3I
X-MailFrom: krose@krose.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: 6man WG <ipv6@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [IPv6]Re: Analysis of Ungleich ULA Registry
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>

On Thu, May 23, 2024 at 4:42 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 23-May-24 15:25, Lorenzo Colitti wrote:
> > On Thu, May 23, 2024 at 11:36 AM Brian E Carpenter <
> brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> >
> >     Right. If I want to use fd00:bec0::/32 (BEC being my initials), I
> certainly can, and it will disturb nobody.
> >
> >
> > I believe Jen presented some data a few years ago on what prefixes are
> in use, based on backscatter. I don't have the link right now, but I
> remember that what emerged from the data is that people did not commonly
> use their initials. They commonly used fd00:: or fd01::. In other words,
> the chance of collision for human-picked ULA prefixes is very much larger
> than for randomly-assigned prefixes.
> >
> > To use your words... will it "disturb" anyone to pick fd00::? I don't
> know. Networks that picked fd00:: will be disturbed if they ever
> interconnect with other networks that picked fd00::. Do you thik they are
> more likely to try to fix this using renumbering, or via NAT or NPTv6? I'd
> say the latter. If they do that, they will disturb application developers
> and users.
> >
> > Is it "foolish" to pick fd00::? Well, I would say yes. But the people
> who picked it didn't think it was. Or maybe they just didn't know.
> >
> > I don't have an issue when people make unwise or broken deployment
> choices. I just don't like it when people make unwise or broken deployment
> choices, and app developers and users end up paying the price. That's not
> fair.
>
> I completely agree.
>

For the record, so do I; but there's only so much we in the standards
community can do. You can lead a horse to water, yadda yadda yadda. If
someone is intent on violating the spec when it *very clearly indicates*
why something should be done in a particular way, I don't see how there's
anything further we can do to prevent that bad outcome. Thankfully, in this
case the stakes are simply lower because it doesn't have global effect
unlike, say, greedy congestion control algorithms.

Kyle