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

Owen DeLong <owen@delong.com> Wed, 04 November 2015 15:02 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 010CB1B30FF for <v6ops@ietfa.amsl.com>; Wed, 4 Nov 2015 07:02:23 -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 IHGu4gKR20qC for <v6ops@ietfa.amsl.com>; Wed, 4 Nov 2015 07:02:21 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1D71B30EB for <v6ops@ietf.org>; Wed, 4 Nov 2015 07:02:21 -0800 (PST)
Received: from [192.168.88.235] (host226-63.122-190.riotel.com.ar [190.122.63.226] (may be forged)) (authenticated bits=0) by owen.delong.com (8.14.5/8.14.5) with ESMTP id tA4F1GrC016683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 4 Nov 2015 07:01:19 -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: <0EE48C9B-801D-4670-8D02-248789E2F411@umn.edu>
Date: Wed, 04 Nov 2015 12:01:13 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <50027DBA-C4C2-4679-8D1C-2992BE7C3B75@delong.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F45C231921A@nkgeml506-mbx.china.huawei.com> <5637D854.2090203@bogus.com> <5637E84B.5090001@gmail.com> <5637EB69.1080608@umn.edu> <03358859-8078-489E-835D-3B4D324381BE@delong.com> <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>
To: David Farmer <farmer@umn.edu>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/v5kwySz55sZtwjhxd-Q5eu42Y2Y>
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 15:02:23 -0000

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.

Owen

> On Nov 4, 2015, at 11:40 AM, David Farmer <farmer@umn.edu> wrote:
> 
> 
>> On Nov 4, 2015, at 04:42, Gert Doering <gert@space.net> wrote:
>> 
>> Hi,
>> 
>>> On Wed, Nov 04, 2015 at 04:36:05AM +0000, Howard, Lee wrote:
>>> 2. There is consensus that NPT66 is bad, for some of the reasons give in
>>> various NAT44/CGN documents. It might be slightly less bad than NAT66,
>>> since it has slightly fewer of the problems given in those documents.
>> 
>> I don't think there is consensus on that... otherwise we wouldn't have
>> published NTP66.
> 
> Please don't mistake support for publishing a document as support for a technology.
> 
> The only thing I think is worse than NAT66, and the slightly less objectionable NPT66, are a 1000 slightly and subtly different versions of NAT66.  Not publishing a document can ensure we will have those 1000 different versions of NAT66, it will not ensure that NAT66 is not deployed.
> 
> I believe our only hope of a world without NAT66 deployed all over the place is to define the beast and explain why we think it is a bad idea.  Until we charter the IEP (the Internet Engineering Police) and/or the IEA (the Internet Engineering Army) the only weapons we have are words and their power to persuade.  
> 
> We could try to holding or breath until NAT66 goes away, but all that will lead too is a bunch of passed-out network engineers on the carpet at the IETF Plenary. 
> 
> To explain why we think NAT66 is a bad idea, we have to acknowledge it exists.  Just a with IPv4 our failure to define a standard form of NAT, will not prevent the deployment of NAT, it will ensure the deployment of subtly incompatible and worse versions of NAT.  Our only useful way forward is to define NAT66 and explain why we think it is a bad idea.
> 
> Thanks.
> 
>> Gert Doering
>>       -- NetMaster
>> -- 
>> have you enabled IPv6 on something today...?
> 
> -- 
> ===============================================
> David Farmer                          Email: farmer@umn.edu
> Office of Information Technology
> University of Minnesota    
> 2218 University Ave SE         Phone: +1-612-626-0815
> Minneapolis, MN 55414-3029   Cell: +1-612-812-9952
> ===============================================
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops