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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 26 February 2019 23:58 UTC

Return-Path: <brian.e.carpenter@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 4F5FB12D827 for <ipv6@ietfa.amsl.com>; Tue, 26 Feb 2019 15:58:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 adXJUHeGuR6H for <ipv6@ietfa.amsl.com>; Tue, 26 Feb 2019 15:57:59 -0800 (PST)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 919E712D4EA for <ipv6@ietf.org>; Tue, 26 Feb 2019 15:57:59 -0800 (PST)
Received: by mail-pl1-x62a.google.com with SMTP id v11so1605929plg.9 for <ipv6@ietf.org>; Tue, 26 Feb 2019 15:57:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=cpuSuAGQtdXH9xOqAIi3vr9Hi1NeA6vpbphSZwCFdWQ=; b=tFQaIqJ5CEGOwTQoZVLfNVUZSuBfpvtwCKN5lMY63hgPXH5zfmy8WAuPGy4FuWSaNn SEELIF5/QMiOIxUTqQWX1ijPd19Kfe0bWaWIph1oteEyVjMb/c1bJxVA/cASDuTor5Kn iMT9R3bZzlPMVNsNw7v9oW/oeR7hUHKW2RHA7kfjskPnx4uELI3jrxoPdKOFCR2z+kXR bDAj0u8nX5P7/0+bpqOWYTEb2l6q1VXcLiHGZ0wveif0plP8UI6D8aP7aolp5OaRnhzE l+BECGDta12yxcxj6/WkzXXmtWkeG145rfCv8+p/uqJWZXP+gPzzmqIkmAvcyklSeGlT +AKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=cpuSuAGQtdXH9xOqAIi3vr9Hi1NeA6vpbphSZwCFdWQ=; b=qbSQ5pIDnMaOBmsXkpH77QISN0Ayx1bQDLZ7YcPLS00KvsEQwtRfdj5R30TvYVeEd4 gKtnPeJ3lCeu6o8WUnq0PEvCNWVH07NKyRJ14M5rvxVgj8+2thL0EvOBWYXqF4GNQ+FG 8XuLTXeqpYAOo07fnAMw2kf0SJM6qM4KKqnFzDkv6WTRL3fQZkDIMsjMwStt/4Q/VQg6 H62tlzPM81H9Mqc8XsuWIfqWaUdqc960xJIGonZLZBO8MaoC+FbTnfeMUs/EbZXw4bYK XkL8h/gO1QRBcoZnIet/jvnR6X4JIvDbLslHM8naE1xQBQdKn7VRm6v4eqN0Xl8na2H+ gYGw==
X-Gm-Message-State: AHQUAuYr5sDCpaKorhOFEDVS/KjTvr7b98SP2oI3Of9KQYf4r7Lek5ak BoXb6cuQODWlfO/IoDC/Iqe+cGvP
X-Google-Smtp-Source: AHgI3IbhFoqSFO37H9eyFDChq06IV6sFcqAJZCOuSGVFDGAAZ0t1r0yUS3hLnxg8d/r/AFMH2P4jCw==
X-Received: by 2002:a17:902:1e6:: with SMTP id b93mr20429373plb.325.1551225478477; Tue, 26 Feb 2019 15:57:58 -0800 (PST)
Received: from [192.168.178.30] ([118.148.79.176]) by smtp.gmail.com with ESMTPSA id z12sm16436193pgv.0.2019.02.26.15.57.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Feb 2019 15:57:57 -0800 (PST)
Subject: Re: there should be a ULA prefix?? [was: A common problem with SLAAC in "renumbering" scenarios]
To: Mark Smith <markzzzsmith@gmail.com>
Cc: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, 6man WG <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: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <e44c03a5-64b7-973a-0c03-503f58bb122e@gmail.com>
Date: Wed, 27 Feb 2019 12:57:57 +1300
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"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/mloZ0_2yVAUwamQf_2njxKlyhx8>
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: Tue, 26 Feb 2019 23:58:02 -0000

On 27-Feb-19 11:10, Mark Smith wrote:
> On Wed., 27 Feb. 2019, 06:36 Brian E Carpenter, <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.

Not so. All it says is:

   ULA-1:  The IPv6 CE router SHOULD be capable of generating a ULA
           prefix [RFC4193].

Unless I've missed something, nowhere does it recommend that ULA
should be enabled by default, and even though I'm a strong advocate
of ULAs, it isn't obvious that they should be on by default as a
general recommendation.
 
> OpenWRT is enabling ULAs by default (although with infinite lifetimes which
> is something that should be changed).

And for homenets that is a reasonable default IMHO, and is advocated
by RFC7368. However, https://tools.ietf.org/html/rfc7788#section-6.5
doesn't make it mandatory.

> 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.)

My 2013-vintage FritzBox does better than that.

   Brian> 
>>> 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
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>