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

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 31 January 2019 12:12 UTC

Return-Path: <swmike@swm.pp.se>
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 BC15D131041; Thu, 31 Jan 2019 04:12:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 jjAXnoZtdiAh; Thu, 31 Jan 2019 04:12:34 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 E3EA4131023; Thu, 31 Jan 2019 04:12:33 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id B5AD7B3; Thu, 31 Jan 2019 13:12:31 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1548936751; bh=7ocGnQIoXipVhXz7UsNmOWwJlop9Qc1hlVXpJ99sEYY=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=Ca/a8/VyLYcfECz7Ytpbt3o8hhqdBhv4av2oTKeHaGfra+vy4/6y11jdtQ3IqLdgG EiY0z0h19RqtJYe2gmHPxJ2IF3FL0kWJKNjOvSbQUgnHHnudkDpRNcbHWswMqYBDLW ueMkiXv06JASwSvT48qIdnT1HhFlxXXHnAJnkvo8=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id B3C94B0; Thu, 31 Jan 2019 13:12:31 +0100 (CET)
Date: Thu, 31 Jan 2019 13:12:31 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Sander Steffann <sander@steffann.nl>
cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
In-Reply-To: <F1C19A2F-F397-4164-BFBC-D1410407E63A@steffann.nl>
Message-ID: <alpine.DEB.2.20.1901311307280.5601@uplift.swm.pp.se>
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <alpine.DEB.2.20.1901311236320.5601@uplift.swm.pp.se> <F1C19A2F-F397-4164-BFBC-D1410407E63A@steffann.nl>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/rsxwCTzsLstnnRJKPX1vBE7RABI>
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: Thu, 31 Jan 2019 12:12:40 -0000

On Thu, 31 Jan 2019, Sander Steffann wrote:

> A flash cell is at least capable of 1000 to 3000 erase/write cycles. 
> Even if the prefix would change every single day that gives a lifetime 
> of 3 to 9 years. And prefixes shouldn't change that often anyway. When 
> looking at more realistic estimates line a change on average once a week 
> you'l get to 20 years. Seems more than enough for low end extra cheap 
> devices. I don't see this driving cost up, except for spending a few 
> hours on properly engineering this.

There are places where they flap your WAN (PPPoE session for instance) 
every day to renumber you. I have personally experienced this.

So it might be possible to do what you're saying but only writing partial 
information of the prefix, so skip writing lifetimes, and just keep the 
actual prefix. This is not what a typical DHCP server/client does today, 
it re-writes the file every time the lease is renewed so it knows about 
it. Some kind of compromise might be where a "hint" file is written and 
the only time this is re-written is when the prefix is changed.

OpenWrt today stores most volatile things in /tmp which is just /tmpfs. 
This has the added disadvantage that after a reboot the LAN lease file is 
empty.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se