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

Owen DeLong <owen@delong.com> Wed, 04 November 2015 20:13 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 8CA191B33EC for <v6ops@ietfa.amsl.com>; Wed, 4 Nov 2015 12:13:49 -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 m42_HECyBJlA for <v6ops@ietfa.amsl.com>; Wed, 4 Nov 2015 12:13:48 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id 30BAB1B33EB for <v6ops@ietf.org>; Wed, 4 Nov 2015 12:13:47 -0800 (PST)
Received: from [192.168.2.54] (232.149.220.201.itc.com.ar [201.220.149.232] (may be forged)) (authenticated bits=0) by owen.delong.com (8.14.5/8.14.5) with ESMTP id tA4KCdIl020384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 4 Nov 2015 12:12:45 -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: <20151104195254.GW70452@Space.Net>
Date: Wed, 04 Nov 2015 17:12:37 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <307C3852-01BA-425E-A556-1ACAEC646EFC@delong.com>
References: <20151103204237.GJ70452@Space.Net> <CAO42Z2xen4gCfkJphZYKfjff5ZsEn_jOf5V16OtYOYNw2VKVAA@mail.gmail.com> <CAKD1Yr3Qn48eQ1Q4VovCsr_S2+RADRZKzi9qBDoh8G2w6Be+=g@mail.gmail.com> <20151104024731.0DCDE3BC3CBF@rock.dv.isc.org> <D25FB58B.C9B04%Lee.Howard@twcable.com> <20151104104208.GL70452@Space.Net> <0EE48C9B-801D-4670-8D02-248789E2F411@umn.edu> <50027DBA-C4C2-4679-8D1C-2992BE7C3B75@delong.com> <20151104170711.GV70452@Space.Net> <ADA388DF-1E4D-43E4-B2EC-7D3E1B93FCD0@delong.com> <20151104195254.GW70452@Space.Net>
To: Gert Doering <gert@Space.Net>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/1RiayHjuC6WuEAzxW9OlGXJSzNc>
Cc: v6ops list <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: Wed, 04 Nov 2015 20:13:49 -0000

> On Nov 4, 2015, at 4:52 PM, Gert Doering <gert@Space.Net> wrote:
> 
> Hi,
> 
> On Wed, Nov 04, 2015 at 04:37:44PM -0300, Owen DeLong wrote:
>>>> I actually agree with what David says below. However, I???d like to make sure that EVERYWHERE we document any form of IPv6 NAT, we also document that it is considered harmful.
>>> 
>>> "That some people in IETF consider it harmful"
>>> 
>>> Please do not speak for me.
>> 
>> Are you really claiming you can make a case that deployment of NAT is 
>> not harmful? I???m very skeptical that such a case can be made.
> 
> Widen your mind :-) - and indeed, I am making this case.  Multiple
> different scenarios where NAT is making life much easier (or enabling
> a solution at all that might not be otherwise possible).

In IPv6? Such as?

Even in IPv4, each and every one of those cases is actually harmful. It may also come with some  benefits which some people may believe outweigh the harm, but denying that it is also harmful is misguided at best and deceitful at worst.

> And none of this is the trivial case of conflicting RFC1918 IP address 
> usage in enterprise VPN scenarios.

Which doesn’t apply to IPv6. Note that my specific statement was about IPv6 NAT.

> Or the case of destination NAT used for load-balancing...  (still NAT,
> even if not N:1 source NAPT).

Unnecessary in IPv6 and not entirely harmless.

Owen