IETF Logo Mail Archive

Re: [v6ops] I-D Action: draft-ietf-v6ops-ula-usage-recommendations-02.txt

Owen DeLong <owen@delong.com> Fri, 21 February 2014 09:19 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 D0CB11A0048 for <v6ops@ietfa.amsl.com>; Fri, 21 Feb 2014 01:19:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level:
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, T_DKIM_INVALID=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 vxrxbmgH7SNI for <v6ops@ietfa.amsl.com>; Fri, 21 Feb 2014 01:19:20 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id 4912E1A04FD for <v6ops@ietf.org>; Fri, 21 Feb 2014 01:19:20 -0800 (PST)
Received: from [50.95.222.92] ([50.95.222.92]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id s1L9EVDW027694 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 21 Feb 2014 01:16:17 -0800
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com s1L9EVDW027694
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1392974178; bh=ezYjXHbJqnjCSa0E4LqxkHClwr4=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=Ttnz2oC0ae2tMBMx3GjKSRE/w3xoogeDPQF/bb28iA3qVRFkAAaKerVnnkRHskkef mlIjXRdRgpcqsxe/wL/VvlArZEHoltwhoGetghN+dE8JCL+boiiePO8DHheTgJGMns fVMRI77YJLEsHS2wqXYe5+bUCgYVVMQlGIBHlkrY=
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <20140220015951.2A328FD160B@rock.dv.isc.org>
Date: Fri, 21 Feb 2014 01:16:06 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B276951-478D-49EA-99D8-30E0E0F63B7E@delong.com>
References: <20140214091302.13219.20624.idtracker@ietfa.amsl.com> <m21tz6javn.wl%randy@psg.com> <1442fd6c81e.5859224653900445752.5189762259388794287@internetdraft.org> <52FEBE28.1010006@gmail.com> <8E2A8B56-6F05-4F09-BE7E-651B9CA42458@delong.com> <5300CE32.1050808@gmail.com> <BD473E46-E382-44E6-B474-A56D074318FA@delong.com> <530104B3.3070205@gmail.com> <53010E70.5000401@gmail.com> <20140217110013.GA31822@mushkin> <62FF9B8A-2F21-4FDD-B1D2-82B8C02A21B3@delong.com> <37638184-17C6-4C8B-86B1-C596A5A5504A@nominum.com> <530242C3.4070108@bogus.com> <E91E49CA-7BA6-4DA3-B4F3-46BB0F25F8F1@delong.com> <5303CD3E.1010907@gmail.com> <m2a9dnr4vk.wl%randy@psg.com> <5304BAAF.60608@gmail.com> <53052B43.2070904@gmail.com> <CAKD1Yr2fyZ9FezX5dh=P-PiruiOqKBKO9f5hroD-CHDJS+ZMQQ@mail.gmail.com> <20140220013516.DE278FD134B@rock.dv.isc.org> <CAKD1Yr2nomEgPj4ec8kbEruphe=apu0zZChm7dG37nuT+3gJ3A@mail.gmail.com> <20140220015951.2A328FD160B@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1827)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Fri, 21 Feb 2014 01:16:18 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/6exepE-vQRGo9APtKMXJnFUE7ts
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ula-usage-recommendations-02.txt
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: <http://www.ietf.org/mail-archive/web/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: Fri, 21 Feb 2014 09:19:26 -0000

>> I think it's obvious that the path of least resistance (and thus, the
>> solution that most admins would choose) will be NAT/NPT. After all, if you
>> want to use ULAs to talk to the outside world (And why wouldn't you, right?
>> It's what we do in IPv4, right?), you have to do NAT or NPT anyway.
> 
> It's a matter of education.  Adding "How to deal with a ULA prefix
> collisions" to this document would be a good first step.

No, it’s a good second or third or … step.

A good first step is teaching them that the best way to avoid a ULA collision is to use GUA in most circumstances and only use ULA where GUA is infeasible.

Owen

v2.23.0 | Report a Bug | By Email