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

Jan Zorz - Go6 <jan@go6.si> Fri, 01 February 2019 18:19 UTC

Return-Path: <jan@go6.si>
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 BE962131195 for <ipv6@ietfa.amsl.com>; Fri, 1 Feb 2019 10:19:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=go6.si
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 WY_N7oU0Pawq for <ipv6@ietfa.amsl.com>; Fri, 1 Feb 2019 10:19:07 -0800 (PST)
Received: from mx.go6lab.si (mx.go6lab.si [91.239.96.23]) (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 9B3E4131194 for <ipv6@ietf.org>; Fri, 1 Feb 2019 10:19:07 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.go6lab.si (Postfix) with ESMTP id E5C8865FC3 for <ipv6@ietf.org>; Fri, 1 Feb 2019 19:19:04 +0100 (CET)
X-Virus-Scanned: amavisd-new at go6.si
Received: from mx.go6lab.si ([IPv6:::1]) by localhost (mx.go6lab.si [IPv6:::1]) (amavisd-new, port 10024) with LMTP id R_oH0pnR-R7O for <ipv6@ietf.org>; Fri, 1 Feb 2019 19:19:04 +0100 (CET)
Received: from mail.go6.si (mail.go6.si [IPv6:2001:67c:27e4::61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.go6.si", Issuer "Let's Encrypt Authority X3" (not verified)) by mx.go6lab.si (Postfix) with ESMTPS id E9E856143D for <ipv6@ietf.org>; Fri, 1 Feb 2019 19:19:03 +0100 (CET)
Received: from haktar.local (unknown [IPv6:2001:67c:27e4:5::19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Jan Zorz", Issuer "COMODO RSA Client Authentication and Secure Email CA" (not verified)) (Authenticated sender: jan) by mail.go6.si (Postfix) with ESMTPSA id B1DB8809E6 for <ipv6@ietf.org>; Fri, 1 Feb 2019 19:19:03 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=go6.si; s=mail; t=1549045143; bh=GO8/7495WBoZStvEaM55u9G1sFXw9NAuHN8DNNwONZk=; h=Subject:To:References:From:Date:In-Reply-To:From; b=LQpJZJdCjMekX57i1nsRROj3tdHzh5aWcTsywmSgiDnWXFPFcxRsfVDLb+difvvrq 30pNaT7p6jV2jz6rO2C6R6pKXn3BFE0IXcEmZrQLoq6jloiP89/oV/oGDaiwCv8Ko4 Kqb1UkCJDKyW3GSvdCKQPG6aLHPvbfB9Xl7vfojI=
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
To: ipv6@ietf.org
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> <alpine.DEB.2.20.1901311307280.5601@uplift.swm.pp.se>
From: Jan Zorz - Go6 <jan@go6.si>
Message-ID: <57a8ffe6-bb5f-811f-63ac-8be7a3b4ed60@go6.si>
Date: Fri, 01 Feb 2019 19:19:03 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1901311307280.5601@uplift.swm.pp.se>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/F-cg54A6h4YJ0HFKbQodQvzTX5M>
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: Fri, 01 Feb 2019 18:19:09 -0000

On 31/01/2019 13:12, Mikael Abrahamsson wrote:
> 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.

This is basically the idea. Write PD when first received, read when 
received again, compare, if not the same -> send RAs with lifetime 0 and 
write new prefix to that storage. Easy ;)

Cheers, Jan