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

Owen DeLong <owen@delong.com> Thu, 12 November 2015 18:39 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 A2F1C1B2E28 for <v6ops@ietfa.amsl.com>; Thu, 12 Nov 2015 10:39:36 -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 IkaR3tQyE2fu for <v6ops@ietfa.amsl.com>; Thu, 12 Nov 2015 10:39:35 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id BC1651B2E2A for <v6ops@ietf.org>; Thu, 12 Nov 2015 10:39:33 -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 tACIcOhh022140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 12 Nov 2015 10:38:25 -0800
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <563C7DC2.3010704@foobar.org>
Date: Thu, 12 Nov 2015 10:38:24 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B079139D-DD68-41AD-9CD3-75B788E3E928@delong.com>
References: <CAKD1Yr1VvzkSmJo3hu6t_3CUguLN_UkNZjRUqvU_ygPBTyb+8g@mail.gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F45C2319739@nkgeml506-mbx.china.huawei.com> <CAKD1Yr3g-ZV+MkbtDrusbtYaZ_wmCxDG9XbT25Ldma4koGpV6A@mail.gmail.com> <D25E7DDF.C9709%Lee.Howard@twcable.com> <CAKD1Yr3Vsn7Ny_xSCr_=sVCHyU+=ZrRh2iQDUPx-5FWdHajv2w@mail.gmail.com> <D2614A6A.CA099%Lee.Howard@twcable.com> <563B9D1E.4030606@umn.edu> <D261FE8E.CA1FB%Lee.Howard@twcable.com> <563BEBCE.40204@gmail.com> <D2622CC9.CA382%Lee.Howard@twcable.com> <20151106072616.GS70452@Space.Net> <563C7DC2.3010704@foobar.org>
To: Nick Hilliard <nick@foobar.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/c3m1_38Qbu07Iois3QKw8IP9Lq8>
Cc: IPv6 Operations <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:39:36 -0000

> On Nov 6, 2015, at 02:15 , Nick Hilliard <nick@foobar.org> wrote:
> 
> On 06/11/2015 07:26, Gert Doering wrote:
>> On Fri, Nov 06, 2015 at 01:31:02AM +0000, Howard, Lee wrote:
>>> Proposed text:
>>> ... it does have significant implications to applications, as documented
>>> in [RFC6296] Section 5, which may  cause some applications to break.
>>> 
>>> Thus this document does not recommend the use of ULA+NPTv6.
>> 
>> This I can perfectly agree to - it's a different message ("understand 
>> well what you do if you insist on going there"), and clear enough.
> 
> this is verging on "delenda est carthago" territory.

Given the persistent and pestilent nature of NAT externalizing costs onto other parties not choosing to use it, I think that is a perfectly valid approach at this time.

Let us now go forth and destroy Carthage (remove NAT from the public internet) as to eliminate this problem from our collective future.

If you want to use NAT in whatever form on your own network in a manner that does not externalize costs to software vendors, other providers, or pollute the internet with false identifiers, then by all means, do as you wish.

If your use of NAT does not fall within those limitations, then, indeed, it should be destroyed.

Owen