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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 31 January 2019 13:15 UTC

Return-Path: <prvs=193435552d=jordi.palet@consulintel.es>
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 B82CD129508; Thu, 31 Jan 2019 05:15:57 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 KB0L99711_IZ; Thu, 31 Jan 2019 05:15:55 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5EE7128CB7; Thu, 31 Jan 2019 05:15:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1548940550; x=1549545350; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=bKRBLqvoE2nHV/mel1oAEcMT7u4Y2zr41zItPIi4ieM=; b=U3jBMXBfQPPNW +LXczx8HGYYENYA9bbt+wDvl5UT4k1HexnjaY41EJRQNvDMl7ZHuL/CkDsCbVESQ gb6KbKfxhHbq2h1dIHUr3xVCtmGcdwCopdeZFUaC5lkagauSp1H7oqgZAtuKX1qv urxF/mtVOgJbWgWvaA5MjDYhCjYrBY=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 31 Jan 2019 14:15:50 +0100
X-Spam-Processed: mail.consulintel.es, Thu, 31 Jan 2019 14:15:50 +0100
Received: from [10.10.10.139] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50006135551.msg; Thu, 31 Jan 2019 14:15:50 +0100
X-MDRemoteIP: 2001:470:1f09:495:8509:9a05:69aa:b8d0
X-MDHelo: [10.10.10.139]
X-MDArrival-Date: Thu, 31 Jan 2019 14:15:50 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=193435552d=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
User-Agent: Microsoft-MacOutlook/10.10.6.190114
Date: Thu, 31 Jan 2019 14:15:49 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Fernando Gont <fgont@si6networks.com>, Sander Steffann <sander@steffann.nl>, Mikael Abrahamsson <swmike@swm.pp.se>
CC: IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Message-ID: <703A71D6-0A13-4CCD-B64E-C87DB903AD21@consulintel.es>
Thread-Topic: [v6ops] A common problem with SLAAC in "renumbering" scenarios
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> <44fda109-c84b-4b30-f15b-a8f2a083342c@si6networks.com>
In-Reply-To: <44fda109-c84b-4b30-f15b-a8f2a083342c@si6networks.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/8OhEjRnpmUMJlxuKEtD_bMohoL8>
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: Thu, 31 Jan 2019 13:15:58 -0000

Several times a day in many places!

Regards,
Jordi
 
 

-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Fernando Gont <fgont@si6networks.com>
Fecha: jueves, 31 de enero de 2019, 13:22
Para: Sander Steffann <sander@steffann.nl>, Mikael Abrahamsson <swmike@swm.pp.se>
CC: IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Asunto: Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios

    On 31/1/19 09:04, Sander Steffann wrote:
    >> "   o  A CPE MUST record, on stable storage, the list of prefixes being
    >>      advertised on each LAN segment."
    >>
    >> This is not always doable as some devices have very small flash with no write-leveling, so doing this generally might ruin the flash cells on some devices. This above requirement will drive cost, especially in the low end market of HGWs.
    > 
    > 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.
    
    You don't really know where these boxes are going to be deployed. I know
    of several places where you do experience electric outages several times
    a week.
    
    -- 
    Fernando Gont
    SI6 Networks
    e-mail: fgont@si6networks.com
    PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
    
    
    
    
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.