IETF Logo Mail Archive

Re: A common problem with SLAAC in "renumbering" scenarios

Richard Patterson <richard@helix.net.nz> Wed, 13 February 2019 15:58 UTC

Return-Path: <richard@helix.net.nz>
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 A07EB1286D8 for <ipv6@ietfa.amsl.com>; Wed, 13 Feb 2019 07:58:09 -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 YjzIf40kn6WB for <ipv6@ietfa.amsl.com>; Wed, 13 Feb 2019 07:58:08 -0800 (PST)
Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) (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 F282212426A for <ipv6@ietf.org>; Wed, 13 Feb 2019 07:58:07 -0800 (PST)
Received: by mail-yb1-xb30.google.com with SMTP id b15so1087613ybn.11 for <ipv6@ietf.org>; Wed, 13 Feb 2019 07:58:07 -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=GGNhRUZvOmyecuz5DPTKV+PsQSaFdQccQgE2F6DdduQ=; b=xGv19Jw2ZQa2H0wmKlj1z0QvvU5IfuO6y3ouJ4TcSy9uBqO8mxMV/rdDHM1WrjFzSg 83nKkIzjIkCkSZimNhbN0V2yYY587RZtNfNkU5EJA4j1f7FXEbN51oVXA07I9P9R5QEn BjKT4AsZIaluofOB17CJQQdumvMnHul40QHYDn4jPD9HEVGHnFKbc2ovcRuBbd+XDlIB lUMwWX6gOo0OYAC0eVfMpNPqK3GPI8y3Ob9jL/ZQQUwlwTeVEqZgqKuHRzD3E5Fnyevp hBakuvtkxV6Y9JT+sxTP1A7hLyrjDhTATWfUJQ3kIxgzbNklEVkBlG9vydh9p5ju0GM2 BU0g==
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=GGNhRUZvOmyecuz5DPTKV+PsQSaFdQccQgE2F6DdduQ=; b=jT4rgCGmJ7DHKZPcX2g22IiyMfJOWIy11JrHb37yvH7PR9cZjsXi7EEk9EvAyJTplE zno//g5lJkqjHy+SzLE9pIIcj3wTl7S7y43uMlOtf38rUd8lLzRO383EWG5vFa2Iff2l fcCOEHKvIXOLhqMNNQ9TGpjPtmTeNECMQxpSGydQvd7H5vKl+CTc59eMH8jEzcgmt9kO xhz93HLCEUohYC9Z7f7inULmAqJ3+vnlTS6slA0Hm9T49FlJ8eUFitUhRpwHIK4vj7OX yAHQBCjYpmv110ahwDUuzzuTy9rRKkVyf01o1/yoqwRWdeBWId6DQFi8H6TwTPt3Yx/1 gPaw==
X-Gm-Message-State: AHQUAuZdX3usRbd6J5Uv2Fy4WpkaeNzuV81LeLngWLZWqik8dOxmWkP+ ZpDO64iVSNhJVm/FR7bycOlkz7Bjs1g=
X-Google-Smtp-Source: AHgI3Iabtd4SBJ+chEOKpVBTpjhumZ19N/4ZpG+E9PndtSROBOxcRe9cIkIEDVSIoa6WPmeq+Z7vMg==
X-Received: by 2002:a25:a2c1:: with SMTP id c1mr1172070ybn.246.1550073486698; Wed, 13 Feb 2019 07:58:06 -0800 (PST)
Received: from mail-yb1-f176.google.com (mail-yb1-f176.google.com. [209.85.219.176]) by smtp.gmail.com with ESMTPSA id h205sm1071236ywh.85.2019.02.13.07.58.05 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 07:58:05 -0800 (PST)
Received: by mail-yb1-f176.google.com with SMTP id s5so1101427ybp.6 for <ipv6@ietf.org>; Wed, 13 Feb 2019 07:58:05 -0800 (PST)
X-Received: by 2002:a25:24d3:: with SMTP id k202mr1133626ybk.90.1550073485598; Wed, 13 Feb 2019 07:58:05 -0800 (PST)
MIME-Version: 1.0
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <alpine.DEB.2.20.1901311236320.5601@uplift.swm.pp.se> <m1gpCcz-0000FlC@stereo.hq.phicoh.net> <ddd28787-8905-bafd-3546-2ceef436c8b0@si6networks.com> <m1gptWx-0000G3C@stereo.hq.phicoh.net> <69609C58-7205-4519-B17A-4FBC8AE2EA16@employees.org> <d40b41c3-ff1b-cab4-a8de-16692a78e8fd@go6.si> <D1E45CAD-08D0-43D4-90F7-C4DD44CB32C0@employees.org> <alpine.DEB.2.20.1902041330531.23912@uplift.swm.pp.se> <77ecf321-b46e-4f25-7f68-05b15714a99e@si6networks.com> <CAHL_VyDdHuEAc9UdeiRp9f+c0tdzyoLwPY1rJbZmbWAuq96Uuw@mail.gmail.com> <alpine.DEB.2.20.1902051127510.23912@uplift.swm.pp.se> <7a401098-ef51-86d4-064b-056e061a4472@gmail.com> <CAHL_VyDACS172yQoSiz7s+FvrQWchesGXNx73FkA2T057q0YPQ@mail.gmail.com> <1dda35a9-2dfd-3fad-7a32-47ac0753a6bf@gmail.com>
In-Reply-To: <1dda35a9-2dfd-3fad-7a32-47ac0753a6bf@gmail.com>
From: Richard Patterson <richard@helix.net.nz>
Date: Wed, 13 Feb 2019 15:57:54 +0000
X-Gmail-Original-Message-ID: <CAHL_VyCYqotiZArQgYiROyLMs0W7vNzESPEvhDr5VStoA30W0g@mail.gmail.com>
Message-ID: <CAHL_VyCYqotiZArQgYiROyLMs0W7vNzESPEvhDr5VStoA30W0g@mail.gmail.com>
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/T691UAu4Wute0aqT8qf6bP5zDHc>
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, 13 Feb 2019 15:58:10 -0000

On Wed, 13 Feb 2019 at 15:44, Alexandre Petrescu
<alexandre.petrescu@gmail.com> wrote:

> > Storing the old lease to persistent storage also gives the CPE
> > visibility if the prefix does change.  If it does, it can then send
> > RAs with lifetime 0 to deprecate the old prefix on the LAN side.
>
> Which lifetime?  Prefix Information Option's (PIO's) Valid Lifetime or
> Preferred Lifetime?
>
> I doubt this deprecation work straightforwardly on stacks of user's
> laptops (Windows) on LAN side, unless one tries, of course.
>
> I am saying it because recently confronted with linux absence of visible
> lifetime fields in Neighbor Cache, otherwise urgently needed for other
> contexts.
>

The preferred lifetime of the old prefix in a PIO.
I'm not aware of issues using this method to deprecate an address on
any of the common host implementations.

v2.23.0 | Report a Bug | By Email