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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Sun, 16 February 2014 14:42 UTC

Return-Path: <alexandru.petrescu@gmail.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 C25AD1A020A for <v6ops@ietfa.amsl.com>; Sun, 16 Feb 2014 06:42:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 ECtiAMzXzssq for <v6ops@ietfa.amsl.com>; Sun, 16 Feb 2014 06:42:02 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id F34651A0223 for <v6ops@ietf.org>; Sun, 16 Feb 2014 06:42:01 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s1GEfw6u017344 for <v6ops@ietf.org>; Sun, 16 Feb 2014 15:41:58 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5415620777F for <v6ops@ietf.org>; Sun, 16 Feb 2014 15:42:36 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4C73D200D9B for <v6ops@ietf.org>; Sun, 16 Feb 2014 15:42:36 +0100 (CET)
Received: from [127.0.0.1] ([132.166.86.5]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s1GEfsCw009884 for <v6ops@ietf.org>; Sun, 16 Feb 2014 15:41:58 +0100
Message-ID: <5300CE32.1050808@gmail.com>
Date: Sun, 16 Feb 2014 15:41:54 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: v6ops@ietf.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>
In-Reply-To: <8E2A8B56-6F05-4F09-BE7E-651B9CA42458@delong.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/KbNpinTiLOgdFvilufQ4ffGNNDw
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: Sun, 16 Feb 2014 14:42:05 -0000

Le 15/02/2014 19:16, Owen DeLong a écrit :
> Indeed, the situations where ULA usage is detrimental vastly
> outnumbers those where it is actually beneficial.
>
> If we're going to move something like this forward, that really
> should be made clear.

Consider new deployments like IPv6 vehicular networks.

There is an immediate direction to demonstrate an IPv6 vehicle if it 
used ULA.  There is also the alternative to request PI or PA IPv6 
addressing space for these vehicles from some registry, steps which may 
take time.

These two directions are actually head and tail of same snake: it bites 
its end, or otherwise put it's a chicken and egg problem: if the 
deployer sees the prototype works then it may request IPv6 addressing 
space from registry, but not before it sees it works.

At this point I think this draft is good to say that ULAs are useful. 
Later on maybe less so.  But right now that's reflecting real-world 
situation.

That's how I see it, and one's mileage may vary.

But imposing to not do ULA is little reasonable for some test deployments.

Alex
PS:
There are also some intermediary alternatives like IPv4 transitioning 
(6to4 and other tunnels), 64share.  Each has some inconvenients (6to4 
requires both IPv4 and IPv6 on cellular, whereas IPv6-only is easier 
with some operator; 64share only allows one subnet in vehicle).  Also 
one would consider asking the cellular operator to implement DHCPv6 
Prefix Delegation, which may also take time.
>
> Owen
>
> On Feb 14, 2014, at 17:08 , Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>
>> Well, there have always been some people against the existence of
>> ULAs, but we did reach rough consensus to define them, since other
>> people see value in them, for reasons that have been aired many
>> times. So writing words about the best way to use them if you want
>> to use them seems right to me.
>>
>> Brian
>>
>> On 14/02/2014 23:00, ek wrote:
>>> +1
>>>
>>> ---- On Fri, 14 Feb 2014 18:34:36 +0900 Randy
>>> Bush&lt;randy@psg.com&gt; wrote ----
>>>
>>>
>>> i expected this to be a short draft. "Don't"
>>>
>>> randy
>>>
>>> _______________________________________________ v6ops mailing
>>> list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
_______________________________________________
>>> v6ops mailing list v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>
>> _______________________________________________ v6ops mailing list
>> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>
>