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

Owen DeLong <owen@delong.com> Thu, 12 November 2015 18:34 UTC

Return-Path: <owen@delong.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 6494E1B2DDD for <v6ops@ietfa.amsl.com>; Thu, 12 Nov 2015 10:34:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.111
X-Spam-Level:
X-Spam-Status: No, score=-6.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 fLUpHJHW5ZUz for <v6ops@ietfa.amsl.com>; Thu, 12 Nov 2015 10:34:37 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id 1298E1B2DDF for <v6ops@ietf.org>; Thu, 12 Nov 2015 10:34:37 -0800 (PST)
Received: from delong-dhcp229.delong.com (delong-dhcp29 [192.159.10.229]) (authenticated bits=0) by owen.delong.com (8.14.5/8.14.5) with ESMTP id tACIWZkx021579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 12 Nov 2015 10:32:35 -0800
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <20151106.081425.74651560.sthaug@nethelp.no>
Date: Thu, 12 Nov 2015 10:32:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6ED54502-C5D1-4D09-877C-FE283E3EF142@delong.com>
References: <Pine.LNX.4.64.1511050424410.1055@moonbase.nullrouteit.net> <20151106.063106.74659839.sthaug@nethelp.no> <CAO42Z2x3O8A1XKqN3PTcvM=xpF8W_WNSL1rVhHQ4ZY5HbVG=OQ@mail.gmail.com> <20151106.081425.74651560.sthaug@nethelp.no>
To: sthaug@nethelp.no
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/J1mpoHSLAsAIq9iDhVY5eN4o4Ww>
Cc: v6ops@ietf.org
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: Thu, 12 Nov 2015 18:34:38 -0000

> On Nov 5, 2015, at 23:14 , sthaug@nethelp.no wrote:
> 
>>> Okay, one more operator then. I want to have NPT66 (and ULA) available
>>> in the toolbox.
>>> 
>> 
>> Why would a recommendation against it prevent you using it on your network
>> if you wanted to? How is the IETF recommending against it stopping you from
>> using it?
> 
> I would of course carefully consider the alternatives. But you're right
> that it probably wouldn't stop me if I concluded that NPT66 was the best
> solution.
> 
>> A recommendation not to do something is for people who fundamentally don't
>> know better.
> 
> Which leaves the people who would like to be provider independent in a
> slightly difficult situation. Recommend /48 PI for everybody? Still too
> difficult to acquire for many companies, and with significant scaling
> problems if enough people start using it. NPT66? "Harmful", as some
> people here would like the documents to say.

How is a /48 PI hard to acquire? Where?

I know it’s utterly simple in the ARIN region.
To the best of my knowledge, it is fairly simple in RIPE.
It’s utterly easy in APNIC, though somewhat expensive IMHO.
I believe it is fairly easy in LACNIC.
To the best of my knowledge, it is not difficult or expensive in AfriNIC.

Please explain exactly what circumstances make it too difficult for any company
to acquire a /48 PI as I would consider this a brokenness in the relevant RIR’s
policy and would happily work to resolve the issue.

Owen