Re: [v6ops] draft-ietf-v6ops-ula-usage-recommendations - work or abandon?

Philip Homburg <pch-v6ops-3@u-1.phicoh.com> Sat, 14 November 2015 11:29 UTC

Return-Path: <pch-bBB316E3E@u-1.phicoh.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 807E81B62AE for <v6ops@ietfa.amsl.com>; Sat, 14 Nov 2015 03:29:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 kqCpFhK5bX8d for <v6ops@ietfa.amsl.com>; Sat, 14 Nov 2015 03:29:44 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo6.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id EEFB41B62AD for <v6ops@ietf.org>; Sat, 14 Nov 2015 03:29:43 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1ZxZ1b-0000CgC; Sat, 14 Nov 2015 12:29:43 +0100
Message-Id: <m1ZxZ1b-0000CgC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
From: Philip Homburg <pch-v6ops-3@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
References: <20151112214819.4EDE63C98D83@rock.dv.isc.org> <CAKD1Yr1jA_PKcjc7tiC9VhQ9yFM=SRzF6fc+fUzk89Jtb4Bvww@mail.gmail.com> <CAKr6gn1uhQhHHQcMj1VyS5+euqEiAQMwtoaF_vsnZQWzqF=MJQ@mail.gmail.com> <alpine.DEB.2.02.1511131342540.24520@uplift.swm.pp.se> <0723DCF1-DE0F-4BBB-9673-17686EB823CD@psc.edu> <5645E9D7.4070009@foobar.org> <alpine.DEB.2.02.1511131448520.24520@uplift.swm.pp.se> <5646589B.7060703@foobar.org> <alpine.DEB.2.02.1511140651020.24520@uplift.swm.pp.se> <m1ZxYeh-0000CkC@stereo.hq.phicoh.net> <20151114111933.GH89490@Space.Net>
In-reply-to: Your message of "Sat, 14 Nov 2015 12:19:33 +0100 ." <20151114111933.GH89490@Space.Net>
Date: Sat, 14 Nov 2015 12:29:38 +0100
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/T8WBT1PWKUcVY91uwumW42mZGpY>
Subject: Re: [v6ops] draft-ietf-v6ops-ula-usage-recommendations - work or abandon?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Nov 2015 11:29:45 -0000

>On Sat, Nov 14, 2015 at 12:05:54PM +0100, Philip Homburg wrote:
>> PI space is EUR 50 per year in the RIPE region, isn't it? Doesn't sound like
>> a barrier to obtaining some.
>
>Having to deal with that every year is a hassle unless you really want
>PI - in which case, it is not.  It's actually a nicely balanced hurdle.
>
>Making it free would encourage everyone and their dog to get a block, 
>whether they need it or not.

It struck me that PI in the RIPE region is similar to getting a DNS domain.
There is a registry (for PI in the RIPE region that would be the RIPE NCC)
and there are registrars (that would be the LIRs in the RIPE region)

For a DNS domain, registrars have completely automated process where you
pick the name, fill in the nameservers, pay, etc. Usually you can pay for
multiple years in advance, so doesn't take too much time.

It seems to me that the same model could apply to PI if it would get 
popular. Though I have to admit, I never bothered to look into the 
actual procedures for getting PI space. Maybe you have to show up in 
person in Amsterdam :-)