ULA Registration (Was: Re: IETF: SixXS is shutting down)

David Farmer <farmer@umn.edu> Fri, 24 March 2017 15:24 UTC

Return-Path: <farmer@umn.edu>
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 340A5129484 for <ipv6@ietfa.amsl.com>; Fri, 24 Mar 2017 08:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 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_MED=-2.3, 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=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 Bn3e6qHnXKTG for <ipv6@ietfa.amsl.com>; Fri, 24 Mar 2017 08:24:17 -0700 (PDT)
Received: from mta-p7.oit.umn.edu (mta-p7.oit.umn.edu [134.84.196.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 959461293E0 for <ipv6@ietf.org>; Fri, 24 Mar 2017 08:24:17 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p7.oit.umn.edu (Postfix) with ESMTP id D9DCB836 for <ipv6@ietf.org>; Fri, 24 Mar 2017 15:24:16 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p7.oit.umn.edu ([127.0.0.1]) by localhost (mta-p7.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p5HyEzmBQi3U for <ipv6@ietf.org>; Fri, 24 Mar 2017 10:24:16 -0500 (CDT)
Received: from mail-vk0-f71.google.com (mail-vk0-f71.google.com [209.85.213.71]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p7.oit.umn.edu (Postfix) with ESMTPS id 9A3457CD for <ipv6@ietf.org>; Fri, 24 Mar 2017 10:24:16 -0500 (CDT)
Received: by mail-vk0-f71.google.com with SMTP id b202so5775012vka.7 for <ipv6@ietf.org>; Fri, 24 Mar 2017 08:24:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=JO4EK7+yHin/+Iuz4yB5dkoyyDTSZxWz1Tsk71GoNEA=; b=mzUGItkjnidZCla2ihLpeQbTACjt0fQPc8YyHhB4ojTCrqHHkFKq2EjSiOwGLvAml5 e9dcMI4R9oAie92gGtCk91ONy3lRhWWYoSEhvPo2X6WRVgHCA4yZ52bjdZxjaOJ5AHLh 8Jb5nJUoTNIYU2HloqPULJ78+37blu4VsDiNbARKTIbP1RiLd8CmV77IJKGmlPRotcDO cv6l+8Kk8+pvG69FKNqPjRIoJeI9T/p7gV6bTN8jg9bM9Q5wkR6CTV+M6kBgGXzlZ0GE IoHSu4kpvZGhsAxZ6mr5AItADXE4uYbPIiZRmUpzdcQ5GeCoqYY8bOBO2RTRPJsH4EAD MFpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=JO4EK7+yHin/+Iuz4yB5dkoyyDTSZxWz1Tsk71GoNEA=; b=nDbXPn/mhlUhro6S0olZ61f6+AoyYmCSAXM6dPG0gDwtjxC7Z9C/VcLTFNePK6V0wh oW0Kw3etSpzTLw+HbExdeQ1cy0NKyrO7HH4AkaMUpYxXpffUmj5lJFlK4IojoN/KeycP p8Oy61D1EkYTe+jCkvgevFC26fnPGt/zCmDlFh2WH7UjRwFD+JT0pAQvdUi1j8v+kh5n gwA3JE4z4SYLaD+klC3mjTk8w2AcTgmQWO/tTJvd4adkhvmb61HhX/W1bNjtcz5ruVMz aSGKBP25T6gqKVQoNRH4I4U3oZAaC17IFR/B1nXpk54bsTmoK1xbQeUHnCdmX1AYlc8B Qchw==
X-Gm-Message-State: AFeK/H3cbHKlqbfCczN5YIEwR6seZ/oWSAYwvQF0KX3VJCuKRQ5qqKKClTEMEvon5yEbj8tsmzL1i9WB7Pi4VRVDw1vbfr09FxYqsv5BYEtVGQalOuWH8Uxjpk7atdSho/SJGTqcRKpikh1XzZo=
X-Received: by 10.176.3.107 with SMTP id 98mr3641825uat.163.1490369055835; Fri, 24 Mar 2017 08:24:15 -0700 (PDT)
X-Received: by 10.176.3.107 with SMTP id 98mr3641813uat.163.1490369055559; Fri, 24 Mar 2017 08:24:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.138.136 with HTTP; Fri, 24 Mar 2017 08:24:14 -0700 (PDT)
From: David Farmer <farmer@umn.edu>
Date: Fri, 24 Mar 2017 10:24:14 -0500
Message-ID: <CAN-Dau132Jg0SsRjgcrxzGfbUEx_KPES9wMgDMg_++-zwY+0dw@mail.gmail.com>
Subject: ULA Registration (Was: Re: IETF: SixXS is shutting down)
To: Pim van Pelt <pim@ipng.nl>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="001a113ee5022425dc054b7b96dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Mc2Z_mDHSVRoDEu1LePdtgNh4lY>
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: Fri, 24 Mar 2017 15:24:20 -0000

On Fri, Mar 24, 2017 at 9:14 AM, Pim van Pelt <pim@ipng.nl> wrote:

> Hoi Alex,
>
> On Fri, Mar 24, 2017 at 3:05 PM, Alexandre Petrescu
> <alexandre.petrescu@gmail.com> wrote:
> > Congratulations for past achievements!
> Thank you.
>
> > Tunnelbroker ok, but how about ULA generation and registration at
> sixxs.  Is
> > it shut down tombstone too?
> > https://www.sixxs.net/tools/grh/ula/
> TL/DR: Plan of record is that it will cease to exist.
>
> This registry was for educational purposes, and has no official
> status. Importantly, as ULA is random per definition, the chance of
> collisions is extremely low. It is fairly straight forward to get a
> prefix from one of the RIRs. While that does cost some money, it is an
> activity that is not the main charter of SixXS and will be expected to
> continue with the RIRs.
>

There are other purposes for registration than just uniqueness, with ULA
such as identification of leaked traffic for instance, but more generally
registration facilitates many forms of operational coordination.  We have
the RIRs use registries because we want more than just a guarantee of
uniqueness, we also want to facilitate operational coordination on many
fronts.

Further, ULA prefixes provide something that RIR allocated GUA prefixes
don't, that is a presumption that they are not routed(or reachable) between
administrative domains.  While they can be routed between administrative
domains, this is really only suppose to happen with one-on-one
coordination. Were as RIR allocated GUA prefixes are presumed to be routed
between all administrative domains.  Their is no guarantee they are
actually routed between any two administrative domains, but it is presumed
to be the case.  And, ULA is presumed to be the exact opposite that.

While ULAs are presumed to not be routed between administrative domains,
that doesn't mean they are not use cases where registration can provide
advantages, especially when ULAs are used for enterprise use cases.  There
are probably much less advantages of ULA registration when all you are
looking for is a semi-stable prefix that isn't dependent on a service
provider, like in typical residential use case, but these are not the only
use cases for ULA.

> And what happens to the registrations?
> Can't quite parse the question - so let me offer three answers (maybe
> the answer you're looking for is among them):
>

I think he means the ULA registrations.  As I mention above, there are
other advantages to registration than just uniqueness.

>From this discussion on another list, here is the count of ULA
registrations in the SixXS database.
+------+-------+
| Year | Count |
+------+-------+
| 2007 |    63 |
| 2008 |   140 |
| 2009 |   321 |
| 2010 |   611 |
| 2011 |   835 |
| 2012 |   742 |
| 2013 |   724 |
| 2014 |  1096 |
| 2015 |  1303 |
| 2016 |   640 |
| 2017 |   143 |
+------+-------+

That is 6618 ULA block that were registered, that seems like that's more
than just a fad. Does this make a case for resurrecting the discussions of
ULA-C? I think it does.  But, what do others think?

Thanks.

Happy to discuss this or other things further as we near the lights-out
> date.
>
> groet,
> Pim
>
> --
> Pim van Pelt <pim@ipng.nl>
> PBVP1-RIPE - http://www.ipng.nl/
>

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
===============================================