Re: ULA clashes don't matter [Re: ULA Registration]

Erik Kline <ek@google.com> Sun, 26 March 2017 21:21 UTC

Return-Path: <ek@google.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 5D0941296A4 for <ipv6@ietfa.amsl.com>; Sun, 26 Mar 2017 14:21:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 uNKP27Tb-bcw for <ipv6@ietfa.amsl.com>; Sun, 26 Mar 2017 14:21:24 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (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 2EF29126BF0 for <ipv6@ietf.org>; Sun, 26 Mar 2017 14:21:24 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id v76so20033740ywg.0 for <ipv6@ietf.org>; Sun, 26 Mar 2017 14:21:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2cCcikgyLuGqSJZgXF5zLi/QJ8Lq9v2KLLnksThu2yI=; b=oi77QRlLOlLHnkHZXvuiIN+WjuKEnp750/mOuhMhDENKtNWk+4AN8tcS6P5ZaCxyD+ 3RkXjadHFp0hTYa+xVeZ3vW4tFTrfSjn+T9ujBpih9GehzvslCAf2VauF94opcrajt5H aXk08UfDgqG7NyKP1j7GT9LmFU0movkMoFkmdzRavzopLOKE3NHuZ2NjylvqkD0Z6foC ii/e8Ff5/cmI4DZyrBYsnODZzLkVQd9BtqDxxVQwrjTbSmf7NC9sfbdSFZrkQ1vcq6Ds +OqYk4tXQDOVOouMXO6cZiUH71Plz4bt3OWAVtTPcEiqwhBcwisIvG0TvLJg40DdTqls FlxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2cCcikgyLuGqSJZgXF5zLi/QJ8Lq9v2KLLnksThu2yI=; b=OcXMip96iFAEq0pIrmMh/1t4pZjIi06aHQb2dj63iLWwtOLQrbu6T1PGoIL/UWugLK S6kB0AZ9mbIRoMp6XDnap3UTtw/Hgil2XB7IEXgE4QA1SYVpSmTvBEzT+mFx+HOUOlE7 SqXZNqXEnASlzc1p+pHoFpojjBtvHHLdb4Q/XDVw+a8hiBBdA7noWds8Y2j0cyXrgbg4 ZE5x1zluZsY0TMkguf9R8VASektz5Ikx6EsxiT5qfCeFOBWED6Xm7yrR68I+PCx1zkzr /CzlTU7ahSKNXcnPNB5ffxqqe0RuohlLJ49wVR/n2K/MLutBICYTKlAaDELSPIVkdrwM VR0g==
X-Gm-Message-State: AFeK/H0whw0lLX6PBNxK2btHZ7a9YCdm2l8mM4vuktBjJ+rGDuihRNgmH1A26cBNszQKJ5pQYc0vlQwyfPBqbnqo
X-Received: by 10.37.88.212 with SMTP id m203mr14673666ybb.27.1490563283002; Sun, 26 Mar 2017 14:21:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.50.7 with HTTP; Sun, 26 Mar 2017 14:21:02 -0700 (PDT)
In-Reply-To: <1E2BE958-3186-4201-92B6-FB7A5EB59D5C@google.com>
References: <CAN-Dau132Jg0SsRjgcrxzGfbUEx_KPES9wMgDMg_++-zwY+0dw@mail.gmail.com> <7c4412a4-6494-961d-165b-9c5d267015a7@gmail.com> <39db830bd4d04faca308c01d0d39b8ae@XCH15-06-11.nw.nos.boeing.com> <bc58c4d5-68b9-9651-1c4e-657c6d07c61d@gmail.com> <1E2BE958-3186-4201-92B6-FB7A5EB59D5C@google.com>
From: Erik Kline <ek@google.com>
Date: Sun, 26 Mar 2017 14:21:02 -0700
Message-ID: <CAAedzxp6TjfPWLR=ud_zw8kW16kR8ikKAKhkeH1Ldd-pg2CDdw@mail.gmail.com>
Subject: Re: ULA clashes don't matter [Re: ULA Registration]
To: james woodyatt <jhw@google.com>
Cc: 6man WG <ipv6@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="001a113fc6b8083683054ba8cf06"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/WaTA7VqOzh0CzftdotWvROmdI-c>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 26 Mar 2017 21:21:26 -0000

Agreed.

The doc is clear about what is required in order to minimize the chance of
collision.

In the inevitable event two non-randomly generated fd00:: networks merge,
that's their problem.  If this situation were to be cited as a motivation
for standards action, the correct answer IMHO is "they're doing it wrong;
not the IETF's problem".

On 24 March 2017 at 13:31, james woodyatt <jhw@google.com> wrote:

> On Mar 24, 2017, at 11:37, Brian E Carpenter <brian.e.carpenter@gmail.com>
> wrote:
>
>
> Do I need to justify that? Oh, OK: […]
>
>
> 4. In the event of the simultaneous merge of a sufficient number of
> ULA-numbered networks that the statistical chance of Global ID collisions
> arising would approach a significant level, the entity performing that
> merge can make its own private arrangements to manage the numbering
> requirements for the merge. For one thing, there is no apparent and
> immediate need for a public service to do it, and for another, establishing
> a registry is not obviously the best way to construct such a service in the
> event the need arises for one in the unforeseeable future.
>
> --james woodyatt <jhw@google.com>
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>