Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios

Richard Patterson <richard@helix.net.nz> Tue, 26 February 2019 10:35 UTC

Return-Path: <richard@helix.net.nz>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC9F6130EC0 for <v6ops@ietfa.amsl.com>; Tue, 26 Feb 2019 02:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=helix-net-nz.20150623.gappssmtp.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 udOYpCRHWJVU for <v6ops@ietfa.amsl.com>; Tue, 26 Feb 2019 02:35:34 -0800 (PST)
Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (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 C8A7C130EBC for <v6ops@ietf.org>; Tue, 26 Feb 2019 02:35:34 -0800 (PST)
Received: by mail-yb1-xb2b.google.com with SMTP id d9so5010779ybj.2 for <v6ops@ietf.org>; Tue, 26 Feb 2019 02:35:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=helix-net-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jIv8QrB/ukgD4eKiSDSc3OTuUb+3+ANBywpHfl7MPzs=; b=ptaAHM2QpTIR8lFk3h69N6P+yxG/Erl/z37icwm/GzTCn+Pin6s8oc9MI23iiyH7Kr uVtDD4F6yZQDTlGtm5+3nFnL3YpRfwLJMfLYPKjxpqDAzo7CuuE+IPdJ191T4MMaieUq bPscGkiKc2pipCKd5s1BY3Try2GHUTDtsexQ0Q5BxTYXXwXYiPS9x/N4OqWAjaXixpJU 3GiP8t8e/K3jaHU30CxHlb+XSAY/KYKcxzviy2vx5KwicBsJkyVF1RYMEN905COu3lXX UndiYzvddi6gouFVzTRUxt2+AIVb2hc6yg666L+lNOuuzMRyDVyXLIWp+ElNdCmYZxTx JHOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jIv8QrB/ukgD4eKiSDSc3OTuUb+3+ANBywpHfl7MPzs=; b=MS7GlKRc+Yuw29UPJcFT3NLMKhn1unPgVeIcDZqwhHEFHxQubf8mbB3KLjWzh8VnjZ FDhZg2X27Iaa+87Ru34XQja/Dx9pfQm4j9Qao3If5RPaXyJKCi2HqkLB90QgqhtFcwMN Vv6hEHUj0JDC87mEC2EKRCXfdbRtjaBb6nMwWcz7z+CbFcyX62h4PRBbwO4SA/BbNauF GsRIkXZgyzy6ZGH7WDc3E2qRYhknghGb51Tt3u0UiWfkdo1MR9/6P6L+4W2tVE33/nHF SmBD/O/TpVprTJVknudWDb6WsLC0Quy/M2+GxaVTmEKThX2rLxn079B1QBBkfqE0FaVs IGRg==
X-Gm-Message-State: AHQUAubIcPIwQ1y1WgfSRERNILmImfVcfq7eSx2XXrwa1pjRm45bQwO7 HvmJEfTxl9OoKZnzCweKIwz//EFmgYE=
X-Google-Smtp-Source: AHgI3IaGEOfjBck2f1sDhzy/dE02jNkP8NKOHJZJCefeoti9lALxTUdhb8Yvf7n9LTapwAJuhCKKvg==
X-Received: by 2002:a25:b1a1:: with SMTP id h33mr15989099ybj.270.1551177333806; Tue, 26 Feb 2019 02:35:33 -0800 (PST)
Received: from mail-yb1-f169.google.com (mail-yb1-f169.google.com. [209.85.219.169]) by smtp.gmail.com with ESMTPSA id s186sm5045901yws.13.2019.02.26.02.35.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Feb 2019 02:35:33 -0800 (PST)
Received: by mail-yb1-f169.google.com with SMTP id v63so1782603ybi.1; Tue, 26 Feb 2019 02:35:33 -0800 (PST)
X-Received: by 2002:a25:4d02:: with SMTP id a2mr17656864ybb.90.1551177332859; Tue, 26 Feb 2019 02:35:32 -0800 (PST)
MIME-Version: 1.0
References: <6D78F4B2-A30D-4562-AC21-E4D3DE019D90@consulintel.es> <B6E2EC33-EEAF-40D0-AFCC-BDAFA9134ACD@consulintel.es> <20190220113603.GK71606@Space.Net> <28fbc2c305c640c9afb3704050f6e8d7@boeing.com> <20190220213107.GS71606@Space.Net> <019c552eb1624d348641d6930829fd1f@boeing.com> <CAKD1Yr0HBG+rhyFWg9zh0t3mW486Mjx9umjn+CRqAZg4z9r0dg@mail.gmail.com> <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>
In-Reply-To: <ead01e0a-9211-7944-88d6-ae8d037c03a8@si6networks.com>
From: Richard Patterson <richard@helix.net.nz>
Date: Tue, 26 Feb 2019 10:35:21 +0000
X-Gmail-Original-Message-ID: <CAHL_VyAs2b5pNcrJJRV_ppthLoVN4+X4Axzte0QRxJ3s-bkNHw@mail.gmail.com>
Message-ID: <CAHL_VyAs2b5pNcrJJRV_ppthLoVN4+X4Axzte0QRxJ3s-bkNHw@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: Fernando Gont <fernando@gont.com.ar>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/1bDnxPwYJm5Ew-5BCioSygvKdi4>
Subject: Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 26 Feb 2019 10:35:37 -0000

On Mon, 25 Feb 2019 at 18:37, Fernando Gont <fgont@si6networks.com> wrote:
> Agreed. That said, with the current default lifetime values, things
> become tricky:
> At least in theory, you should be sending such RAs for "Valid Lifetime"
> seconds. With a default of one month, that means that, in theory, you
> should be sending such RAs for a month. And if there are multiple
> crash-and-reboot events, you should advertise each of the stale
> prefixes. (I assume the CPE just records the last one)

I get your reasoning, but I'm not sure if it's quite as dire as that,
a single RA update with PrefLifetime of 0 should in theory suffice,
but then we get in to discussing the reliability of ICMPv6 messaging.
(as you have done in draft-gont-6man-slaac-renum-02 )

In my head, an address with the higher Preferred Lifetime should be
selected over one with a lower value, however I couldn't find any
recommendation as such in RFC6724, is this stipulated anywhere else?
 If not, would an update to 6724 that introduces a Preferred Lifetime
comparison as a tie-breaker help?  i.e. When deciding between multiple
non-deprecated source addresses, always pick the address with the
highest Preferred Lifetime?