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

Mark Andrews <marka@isc.org> Thu, 20 February 2014 01:35 UTC

Return-Path: <marka@isc.org>
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 ECB4F1A0423 for <v6ops@ietfa.amsl.com>; Wed, 19 Feb 2014 17:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] 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 Piilc5s4my8p for <v6ops@ietfa.amsl.com>; Wed, 19 Feb 2014 17:35:35 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 4D3441A00FA for <v6ops@ietf.org>; Wed, 19 Feb 2014 17:35:35 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 16A8E2383D2; Thu, 20 Feb 2014 01:35:20 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id E943E160060; Thu, 20 Feb 2014 01:36:07 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id B316816005D; Thu, 20 Feb 2014 01:36:07 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id DE278FD134B; Thu, 20 Feb 2014 12:35:16 +1100 (EST)
To: Lorenzo Colitti <lorenzo@google.com>
From: Mark Andrews <marka@isc.org>
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>
In-reply-to: Your message of "Thu, 20 Feb 2014 10:17:48 +0900." <CAKD1Yr2fyZ9FezX5dh=P-PiruiOqKBKO9f5hroD-CHDJS+ZMQQ@mail.gmail.com>
Date: Thu, 20 Feb 2014 12:35:16 +1100
Message-Id: <20140220013516.DE278FD134B@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/I6dM3jIyeFakRgQJxgIC7erAvOo
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: Thu, 20 Feb 2014 01:35:37 -0000

In message <CAKD1Yr2fyZ9FezX5dh=P-PiruiOqKBKO9f5hroD-CHDJS+ZMQQ@mail.gmail.com>, Lorenzo Colitti writes:
> 
> On Thu, Feb 20, 2014 at 7:08 AM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
> > 1. More than one party not following the spec on how to generate
> > a ULA prefix - so they will be punished for their own mistakes.
> >
> 
> How are they punished? And what will they do when they are punished? I
> guarantee that renumbering will not be the solution, NAT will be the
> solution.

Both sites just generate a NEW ULA prefixes.  They can continue to
use the collision prefix until the heat death of the universe if
they wish to or they can migrate to the new prefix.  IPv6 is NOT
IPv4.  Running parallel prefixes is *standard* proceedure.  They
just need to talk to each other using the NEW prefixes which should
be no more complicated than pushing new address selection tables.

If they really want to they can choose to use the same new prefix
and create a site that covers both of the old sites splitting the
address space.  If they do that they don't even need to push new
address selection tables.

> 2. A piece of remarkably bad luck, rather less likely than
> > winning any lottery I'm aware of.
> >
> 
> You assume that people will actually follow the rules instead of saying
> "let's just do this like IPv4, and use NAT at the border".
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org