Re: there should be a ULA prefix?? [was: A common problem with SLAAC in "renumbering" scenarios]

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 27 February 2019 10:12 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41D1E12D4EF for <ipv6@ietfa.amsl.com>; Wed, 27 Feb 2019 02:12:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.632
X-Spam-Level:
X-Spam-Status: No, score=-1.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 bUve6OefsbXA for <ipv6@ietfa.amsl.com>; Wed, 27 Feb 2019 02:12:55 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 065FF1295EC for <ipv6@ietf.org>; Wed, 27 Feb 2019 02:12:54 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x1RACq1G025885 for <ipv6@ietf.org>; Wed, 27 Feb 2019 11:12:52 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 97B04201ACF for <ipv6@ietf.org>; Wed, 27 Feb 2019 11:12:52 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 8BA962019BE for <ipv6@ietf.org>; Wed, 27 Feb 2019 11:12:52 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x1RACqs6002070 for <ipv6@ietf.org>; Wed, 27 Feb 2019 11:12:52 +0100
Subject: Re: there should be a ULA prefix?? [was: A common problem with SLAAC in "renumbering" scenarios]
To: ipv6@ietf.org
References: <6D78F4B2-A30D-4562-AC21-E4D3DE019D90@consulintel.es> <20190221073530.GT71606@Space.Net> <CAO42Z2wmB2W52b4MZ2h9sW5E9cQKm-HRjyf--q8C26jezS7LXQ@mail.gmail.com> <a73818d31db7422b99a524bc431b00ed@boeing.com> <CAO42Z2z9-48Gbb_Exf+oWUqDO=axSLpZBtqeDcxkAoFq5OziGw@mail.gmail.com> <CALx6S3624hnGauG1HaSWPMvQw0t2Q5R3gb8W4R8w3kuK7dcrWQ@mail.gmail.com> <1F07F2BB-2F37-4D12-9731-7892DF4E3D88@consulintel.es> <0a582916-af14-bd82-a4cd-002a36f8830b@huitema.net> <67515a73-26a5-3ed0-da88-1a4ce64550d3@foobar.org> <360afa02-cf23-375c-4876-780d3c2aa5ac@gont.com.ar> <CAHL_VyD34V=TRcsCp0DOO9HJNHyy5xkiMQ_cZoBa7zTE4fe5OA@mail.gmail.com> <ead01e0a-9211-7944-88d6-ae8d037c03a8@si6networks.com> <FB8B77EE-CC16-4418-BB5E-D44EE66D6B72@jisc.ac.uk> <899A1249-D3D9-4824-8B2E-7E950FBB316A@jisc.ac.uk> <m1gya2p-0000HVC@stereo.hq.phicoh.net> <9b7ba4df-41df-2c03-ddca-e15289075bff@gmail.com> <CAO42Z2xq1GNdkopJRwaq=V0UnVGzky7yfCuOy-8mQgHKUw=y1w@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <4da3b5b2-ee8c-7743-9cdf-5d576dcb54a9@gmail.com>
Date: Wed, 27 Feb 2019 11:12:52 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <CAO42Z2xq1GNdkopJRwaq=V0UnVGzky7yfCuOy-8mQgHKUw=y1w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/EIVv9WcYhrG9CUpdvXsG1gK4RAQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2019 10:12:57 -0000


Le 26/02/2019 à 23:10, Mark Smith a écrit :
> 
> 
> On Wed., 27 Feb. 2019, 06:36 Brian E Carpenter, 
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> 
>     Philip,
> 
>     On 26-Feb-19 23:33, Philip Homburg wrote:
>      >> So given that document is 12 years old, with that default copied
>     from one that
>      >> is 21 years old, is an update required?
>      >>
>      >> And if so, to what?
>      >
>      > I think this should be updated.
>      >
>      > A long time ago, the model was that you would get a prefix from
>     your ISP
>      > and that was the only global prefix on the local network.
>      >
>      > So with short lifetimes, if the internet connection would go down
>     for a
>      > relatively long period, there would be no global prefix anymore
>     and hosts
>      > would have to resort to link local to communicate (which
>     obviously fails
>      > if there are multiple subnets).
>      >
>      > Some time in the past, the thinking changed and now there should
>     be a ULA
>      > prefix in addition to any global prefixes.
> 
>     Really? Where do you think that is stated?
> 
>     I happen to run my CPE with ULA enabled, but I'm not aware of any
>     recommendation to do so.
> 
> 
> RFC7084. Was also in its ancestor.
> 
> OpenWRT is enabling ULAs by default (although with infinite lifetimes 
> which is something that should be changed).

YEs I confirm openwrt is enabling ULAs by default.

In recent years I tested several IoT-class cellular router owrt devices 
and they all enable ULAs by default on their WiFi and Ethernet 
interfaces.  In some cases they also enable NAT IPv6.  These owrt dont 
enable 64share nor CLAT; these latter are typical on Android (a 
different OS distribution than owrt, both based on linux kernel) and on 
Apple iOS (OS distribution based on mach kernel?).

While these IoT-class routers are not perfect, their use of ULAs is not 
a culprit.  ULA is fine.

It's their reliance on 64share (an INFORMATIONAL RFC), IPv6 NAT 
(perpetuates the NAT problem) and rigid length 64bit IIDs that are culprits.

A more reasonable IoT-class cellular router would use variable length 
IIDs, and DHCPv6 Prefix Delegation (Stds Track).

> Back in 2010 Fritzboxes were doing ULAs too, although badly. They had 
> all zeros random parts, and were trying to swap them in and out with the 
> PD GUA addresses as the WAN link went up or down. (It seemed they didn't 
> understand the fundamental idea that IPv6 supports multiaddressing.)

Yes I heard of several German cellular router devices enabling ULAs.

Alex

> 
> 
> 
> 
> 
>      > So I think that with a ULA, it makes more sense for a CPE to
>     limit lifetimes
>      > to some multiple of the RA interval.
> 
>     Why? I don't expect my ULA prefix to change ever. Or do you mean the
>     lifetimes
>     for globally routeable prefixes?
> 
> 
>         Brian
> 
>     --------------------------------------------------------------------
>     IETF IPv6 working group mailing list
>     ipv6@ietf.org <mailto:ipv6@ietf.org>
>     Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>     --------------------------------------------------------------------
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>