Re: Non routable IPv6 registry proposal
David Farmer <farmer@umn.edu> Thu, 11 March 2021 19:19 UTC
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18A3A3A0E59 for <ietf@ietfa.amsl.com>; Thu, 11 Mar 2021 11:19:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level:
X-Spam-Status: No, score=-2.118 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_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=umn.edu
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 qBmM1f3LNbqx for <ietf@ietfa.amsl.com>; Thu, 11 Mar 2021 11:19:30 -0800 (PST)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98D5E3A0E55 for <ietf@ietf.org>; Thu, 11 Mar 2021 11:19:30 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id 4DxJfV0yQSz9vCHk for <ietf@ietf.org>; Thu, 11 Mar 2021 19:19:30 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fyhJ0-qyr3AN for <ietf@ietf.org>; Thu, 11 Mar 2021 13:19:29 -0600 (CST)
Received: from mail-ed1-f70.google.com (mail-ed1-f70.google.com [209.85.208.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id 4DxJfT4Zc5z9vCGP for <ietf@ietf.org>; Thu, 11 Mar 2021 13:19:29 -0600 (CST)
DMARC-Filter: OpenDMARC Filter v1.3.2 mta-p8.oit.umn.edu 4DxJfT4Zc5z9vCGP
DKIM-Filter: OpenDKIM Filter v2.11.0 mta-p8.oit.umn.edu 4DxJfT4Zc5z9vCGP
Received: by mail-ed1-f70.google.com with SMTP id a2so10362856edx.0 for <ietf@ietf.org>; Thu, 11 Mar 2021 11:19:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=W5s+vH4tb1Iqw7Lw3GK6zpIqiCCTgdviFouwbjW+U+w=; b=RbSq08URTKUImSMP4h7rO42v5WR1H37mnH+VjWQIPRBJq44OELAk1hUALhAn2XuMpT q/FjtQxZte/qTe6fjFwrZVrCb6wRHhrqUSnvB7xPfMYaw1Dc5Um6Pn3RZpIRstLJsRB9 sZnCixP05vhMNCwIdvvRSefzcfMaIsDjphUo5PgIwitPiDnudJaYc17u9G+jSsVlWBSa gwnxMc0PZV7BfJkEMi+/i/AsldxEqSuQWDPHbgfaKm8aOk4viApA0gMh/JMQ6NF21kZz t+c5aK6RY+AOC9OW6HeDbrSF0N0oMyrhqtjfFRg0MNF+lM7K5Y55z3XTTCdnqrbVW1yC Zjeg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=W5s+vH4tb1Iqw7Lw3GK6zpIqiCCTgdviFouwbjW+U+w=; b=PXiA9ruqdPeAsEO+dmb8ygjQxc3tN87o+/yFmACj0BXRcOp9qSUSn70mPP8GgNzT9S u3hGeh1aQSTvNONd5/2I7BDw6ARleiVKw/h5jtoDDB3uz94Iv05q/laetbTEtT6/CW// IZZtzF8Se/aixse3+i1G+wu4xz0TQKCAsGd9OEMzABb2P984zSUOSoAMmREG/8eYfsCn D7GVJDTESNa/ybeQgNlrb/EOxc607DgoCDdgElJ+RyXFIlbvYJOQ4Vaw6eecCTSL9nFe 3ObxzFmnrBiX6bVLZ/MU9utjg9hGgEMUb+ERzPlbBB1UfTUEk3z0P/E3w37HGPLHQa1L eskw==
X-Gm-Message-State: AOAM533CncEtbXIaQOK6BwVgm06mLMhDrctUyyKTnSMTLqu4Hklaq/Yf euLCY53ztEXWOzLCkayMthLgJFpF2J4e1l04N7+b7kDgDETdznntJsgAGjDw8NDjakXoYJmcZvC 3/QKfYo4GXN8FIwJCsIQ84Kk1
X-Received: by 2002:aa7:dc15:: with SMTP id b21mr10165803edu.350.1615490367511; Thu, 11 Mar 2021 11:19:27 -0800 (PST)
X-Google-Smtp-Source: ABdhPJzZRtzoukD5TBxPHZla4WSnKzGjaCbFNM1kwbm/SqOFnUUIIlX/CbJ2JDrjNQPiKNgQ0b4U59sOMFV7IWWiUnk=
X-Received: by 2002:aa7:dc15:: with SMTP id b21mr10165786edu.350.1615490367185; Thu, 11 Mar 2021 11:19:27 -0800 (PST)
MIME-Version: 1.0
References: <CAMm+LwjNiE0P7RAVqzKMypNbh3=9BeqiWn_hGv3E=zX7-YmSXQ@mail.gmail.com> <72F969A9-AF94-47B6-B48C-B3CD4D9A7C72@strayalpha.com> <7cc9e38c-5a00-ec59-a8c2-10503cc40d50@si6networks.com> <CB1A6DF0-8CDD-495D-9F7B-80BF72F08C1E@strayalpha.com> <53d7190a-3e1f-66b3-0574-8e8fbb3a7a5e@si6networks.com> <90718D2A-3483-45D2-A5FB-205659D4DCDB@cisco.com> <87h7li0z2t.fsf@line.ungleich.ch> <253e084c-6ced-7f94-c909-bd44f7c53529@network-heretics.com>
In-Reply-To: <253e084c-6ced-7f94-c909-bd44f7c53529@network-heretics.com>
From: David Farmer <farmer@umn.edu>
Date: Thu, 11 Mar 2021 13:19:11 -0600
Message-ID: <CAN-Dau2YCvCfWmPwGhF8q2c5fMDCbMhNBDA180x1o1Y9ZQga7Q@mail.gmail.com>
Subject: Re: Non routable IPv6 registry proposal
To: Keith Moore <moore@network-heretics.com>
Cc: IETF-Discussion Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000797d2b05bd47a9a8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9EPF0yuD_jpBxzRYQeQCjcbgijg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2021 19:19:32 -0000
On Thu, Mar 11, 2021 at 10:49 AM Keith Moore <moore@network-heretics.com> wrote: > On 3/11/21 5:22 AM, Nico Schottelius wrote: > > Another question I have is whether such ULA allocations > will realistically remain local. > > ULAs are unlikely staying local, as we have seen with radio networks in > Germany. Tunnels are being used to interconnect remote cities and > non-collision (not necessarily public routing) are a primary concern. > > Despite the name, there's no reason that ULAs should stay local. As long > as they are properly chosen, it's perfectly reasonable to route them > privately between cooperating networks, and IMO this is part of their > design. One of the problems with RFC 1918 addresses in IPv4 was that > enterprises had a need to route traffic between networks each using that > space. The resulting address collisions generally required explicit NAT > configurations to work around, and these were failure-prone and difficult > to manage. ULAs were intended in part to remedy this problem. > > Keith > The "L" for Local isn't intended to have a strict definition of Local. However, similarly, the "U" for Unique isn't intended to have a strict definition of Unique either, especially a mathematical definition of Unique. You can easily interconnect thousands or even tens of thousands of ULA prefixes without much chance of an address collision, as long as the random assignment process is actually used. Whereas, if you try to interconnect billions of ULA prefixes, you will probably start running into the birthday paradox. So the interconnection of ULA prefixes, the route-ability of them, is not intended to be unlimited. There are limits to the number of ULA prefixes that SHOULD be interconnected to each other; nevertheless, this limit is extremely generous for the intended use cases. If you disregard the intended use cases and use them outside the intended use cases, then address collisions could become an issue. Thanks -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================
- Re: Non routable IPv6 registry proposal Nick Hilliard
- Non routable IPv6 registry proposal Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Joe Touch
- Re: Non routable IPv6 registry proposal John Levine
- Re: Non routable IPv6 registry proposal Brian E Carpenter
- Re: Non routable IPv6 registry proposal Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Nick Hilliard
- Re: Non routable IPv6 registry proposal Fernando Gont
- Re: Non routable IPv6 registry proposal Fernando Gont
- Re: Non routable IPv6 registry proposal Fernando Gont
- Re: Non routable IPv6 registry proposal John R Levine
- Re: Non routable IPv6 registry proposal Christopher Morrow
- Re: Non routable IPv6 registry proposal George Michaelson
- Re: Non routable IPv6 registry proposal Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Michael Richardson
- Re: Non routable IPv6 registry proposal Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Brian E Carpenter
- Re: Non routable IPv6 registry proposal Brian E Carpenter
- Re: Non routable IPv6 registry proposal John R Levine
- Re: Non routable IPv6 registry proposal Nick Hilliard
- Re: Non routable IPv6 registry proposal Masataka Ohta
- Re: Non routable IPv6 registry proposal Michael Richardson
- Re: Non routable IPv6 registry proposal Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Joseph Touch
- Re: Non routable IPv6 registry proposal Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Nick Hilliard
- Re: Non routable IPv6 registry proposal Brian E Carpenter
- Re: Non routable IPv6 registry proposal Nick Hilliard
- Re: Non routable IPv6 registry proposal Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Christian Huitema
- Re: Non routable IPv6 registry proposal Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Christian Huitema
- Re: Non routable IPv6 registry proposal Nick Hilliard
- Re: Non routable IPv6 registry proposal Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Fernando Gont
- Re: Non routable IPv6 registry proposal Eliot Lear
- Re: Non routable IPv6 registry proposal Masataka Ohta
- Re: Non routable IPv6 registry proposal Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Joe Touch
- Re: Non routable IPv6 registry proposal Fernando Gont
- e2e [was: Non routable IPv6 registry proposal] Brian E Carpenter
- Re: Non routable IPv6 registry proposal Fernando Gont
- Re: Non routable IPv6 registry proposal Joe Touch
- Re: Non routable IPv6 registry proposal Fernando Gont
- Re: e2e [was: Non routable IPv6 registry proposal] Fernando Gont
- Re: Non routable IPv6 registry proposal Joel M. Halpern
- Re: e2e [was: Non routable IPv6 registry proposal] Joseph Touch
- Re: e2e [was: Non routable IPv6 registry proposal] Phillip Hallam-Baker
- Unique 128 bit identifiers. Was: Non routable IPvā¦ Phillip Hallam-Baker
- Re: Non routable IPv6 registry proposal Nico Schottelius
- Re: Non routable IPv6 registry proposal Keith Moore
- Re: Non routable IPv6 registry proposal David Farmer
- Re: Non routable IPv6 registry proposal David Farmer
- Re: Non routable IPv6 registry proposal Brian E Carpenter
- Re: Non routable IPv6 registry proposal David Farmer
- Re: Non routable IPv6 registry proposal Fred Baker
- Re: Non routable IPv6 registry proposal David Farmer
- Re: Non routable IPv6 registry proposal Brian E Carpenter
- Re: Non routable IPv6 registry proposal David Farmer
- Re: Non routable IPv6 registry proposal Bob Hinden
- Re: Non routable IPv6 registry proposal David Farmer
- Re: Non routable IPv6 registry proposal Nico Schottelius
- Re: Non routable IPv6 registry proposal Brian E Carpenter
- Re: Non routable IPv6 registry proposal Nico Schottelius
- Re: Non routable IPv6 registry proposal Bob Hinden
- Re: Non routable IPv6 registry proposal Keith Moore
- Re: Non routable IPv6 registry proposal Nick Hilliard
- Re: Non routable IPv6 registry proposal Bob Hinden
- Re: Non routable IPv6 registry proposal David Farmer
- Re: Non routable IPv6 registry proposal Nick Hilliard