Re: Non routable IPv6 registry proposal
Nico Schottelius <nico.schottelius@ungleich.ch> Thu, 11 March 2021 21:11 UTC
Return-Path: <nico@schottelius.org>
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 CDAE73A0C05 for <ietf@ietfa.amsl.com>; Thu, 11 Mar 2021 13:11:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ungleich.ch
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 uFeycy6eAtSI for <ietf@ietfa.amsl.com>; Thu, 11 Mar 2021 13:11:34 -0800 (PST)
Received: from smtp.ungleich.ch (smtp.ungleich.ch [IPv6:2a0a:e5c0:0:2:400:b3ff:fe39:7956]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 820B53A0C0C for <ietf@ietf.org>; Thu, 11 Mar 2021 13:11:33 -0800 (PST)
Received: from nb2.localdomain (localhost [IPv6:::1]) by smtp.ungleich.ch (Postfix) with ESMTP id E9D9C22C2D; Thu, 11 Mar 2021 22:11:28 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ungleich.ch; s=mail; t=1615497088; bh=9n5272+WzViHaMT7cQaLizKufYqNh8xxzXVDRY8IYFo=; h=References:From:To:Cc:Subject:In-reply-to:Date:From; b=YbAFxxTiInQ1at1N+MWDJ5U1DAaLbD0UlOi9ALBdi64zKs+WpzzPO55pR/r2liy3M PIUaDpIbIZY1eLJ6+1NBm0kzpzEPO7qVqF3sUMIP95/HrjUkVoL8S9qC8MwbdfMWQG sDlWcEBJ1XvViQB8ncKEkOO7YMoyRCYDrHq3HKouXtThu3aY2A1CtEetM7YTYiS3IG YwRvy55Q0MYroHA7INtf9ugR0llU9TYPvSMQ2adva5st1BQjfcZqVsXqQ1C2GIgdoE tiwOcH0EBdosm+SLGoYBsSk+1EoJeMNK9i2YcXdIphHs1DjNfkAw9MMpIdjH/t+oNw fska4kowHE2rA==
Received: by nb2.localdomain (Postfix, from userid 1000) id C856614C051B; Thu, 11 Mar 2021 22:11:30 +0100 (CET)
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> <CAN-Dau2XzkFXiHN0oTEPUksDcT61QDAGPkM886cmMySrCMmpog@mail.gmail.com>
User-agent: mu4e 1.4.15; emacs 27.1
From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: David Farmer <farmer@umn.edu>
Cc: Nico Schottelius <nico.schottelius@ungleich.ch>, Eliot Lear <lear@cisco.com>, Phillip Hallam-Baker <phill@hallambaker.com>, The IAB <iab@iab.org>, The IETF List <ietf@ietf.org>
Subject: Re: Non routable IPv6 registry proposal
In-reply-to: <CAN-Dau2XzkFXiHN0oTEPUksDcT61QDAGPkM886cmMySrCMmpog@mail.gmail.com>
Date: Thu, 11 Mar 2021 22:11:30 +0100
Message-ID: <87v99xpf99.fsf@ungleich.ch>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/u2nVZjkP_VHHEshE7eLzowFu_V0>
X-Mailman-Approved-At: Fri, 12 Mar 2021 08:06:22 -0800
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 21:11:37 -0000
David Farmer <farmer@umn.edu> writes: > On Thu, Mar 11, 2021 at 10:15 AM Nico Schottelius < > nico.schottelius@ungleich.ch> wrote: > >> Eliot Lear <lear@cisco.com> writes: >> >> > ... Also >> > I think there are some tough questions that may need to be resolved >> > around points of contact and relevant laws. These are things that >> > both ICANN and the various RIRs have paid considerable attention to. >> >> They did and they do. However I think the focus has never been on >> enabling (non-profit) commmunities. I am emphasising on this as >> historically when people can spend time (but not money) on something, >> innovation happens. We have not yet addressed this problem properly in >> the IPv6 world. >> > > The ARIN community has put significant effort into reducing the barriers as > low as possible, for IPv6 allocations, all barriers can't be eliminated. > However, the entry point has been lowered to $250 for a /40 IPv6 > allocation, intended for the smallest ISP-like organization, an LIR, > that is an organization that makes assignments to other end-uerser. I believe $250/y is quite a good price tag, indeed. As you mention, it is still not fully inclusive, but I understand the reasoning to at least cover the costs from ARIN side. Given that all RIRs would offer /40's (I'd even go as small as /48 per party) at cost price, this would be a good start. In that case access to IPv6 addresses could be based on a sponsorship / donation model, buy-2-sponsor-1, and/or cross financed by bigger LIRs (for every /32 you sponsor access to 1 /40). I agree with the previously discussed argument "space should not be free" to prevent abuse, but I'd still envision a "pay by time / work" method, because that resource is usually abundant in non-profits. Best regards, Nico -- Sustainable and modern Infrastructures by ungleich.ch
- 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