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

Jan Zorz - Go6 <jan@go6.si> Tue, 19 February 2019 09:37 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 1D69D130E81 for <ipv6@ietfa.amsl.com>; Tue, 19 Feb 2019 01:37:30 -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 DtKDI16QLeC8 for <ipv6@ietfa.amsl.com>; Tue, 19 Feb 2019 01:37:28 -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 E9F8A128CF2 for <ipv6@ietf.org>; Tue, 19 Feb 2019 01:37:27 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.go6lab.si (Postfix) with ESMTP id E0E776608B for <ipv6@ietf.org>; Tue, 19 Feb 2019 10:37:21 +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 F7z-NBIAm50I for <ipv6@ietf.org>; Tue, 19 Feb 2019 10:37:21 +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 5CAE465A2D for <ipv6@ietf.org>; Tue, 19 Feb 2019 10:37:20 +0100 (CET)
Received: from haktar.local (unknown [IPv6:2001:67c:27e4:5::2c]) (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 29D6D8054D for <ipv6@ietf.org>; Tue, 19 Feb 2019 10:37:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=go6.si; s=mail; t=1550569040; bh=+cz37JkcetQQuetjbUsXystSkRtYRuAYDxEoYAJKxe0=; h=Subject:To:References:From:Date:In-Reply-To:From; b=ta+KXt4tidtGJKwjWwqlmowQn1vSHYSwLiXCHdOH9YdclfsOd81rbPa6zMLdm/JMK UjFA81E5Ah7j/TsVh9TokJGcQ36PbcZiVeY7oJmzWfyl35kmXaMM4NEUxBc7qwOree 5T+s2RmqflhsR0xTbVAK7jgxg2tRQjvJzPcLRopo=
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> <35adea8e-704a-76f2-857f-a83a9ad689ef@si6networks.com> <CAFU7BAS1_veTu-ZXAF0MF4niJwz149nGipx3ep_6fh1bewOzgg@mail.gmail.com> <d9503983-6524-a13a-2cb0-cdcb95f76ea6@si6networks.com> <CAFU7BAQfg712UfgW9wi9pd3eVeZP9cqJEXd6=FDmchuSdauv+g@mail.gmail.com>
From: Jan Zorz - Go6 <jan@go6.si>
Message-ID: <66687354-5ee1-80f7-2a32-78631530dfb3@go6.si>
Date: Tue, 19 Feb 2019 10:37:19 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <CAFU7BAQfg712UfgW9wi9pd3eVeZP9cqJEXd6=FDmchuSdauv+g@mail.gmail.com>
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/DYcDzhRaFAsk5yXzoWg_IcZ21F0>
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: Tue, 19 Feb 2019 09:37:30 -0000

On 19/02/2019 08:56, Jen Linkova wrote:
> Lets say there are two routers (R1 and R2) on the LAN.
> R1 advertised 2001:db8:1::/64 and 2001:db8:3::/64
> R2 advertised 2001:db8::2::/64 and 2001:db8:3::/64.
> 
> Hosts have addresses from 3 prefixes.
> Now R2 stops advertising 2001:db8:3::/64.
> 
> There is no reason for hosts to deprecate addresses in 2001:db8:3::/64.

Dear Jen,

In theory you are correct.

In practice - at residential home or SOHO environment we rarely see a 
corner case that you described. I'm not saying it's incorrect, but I 
would say - very very rare.

We really need to address the big elephant in the room first and enable 
operators to deploy IPv6 on a massive scale in architectural way that 
they choose. We ignored it for too long now. :)

Cheers and thnx, Jan

P.S: I hope that we can have this discussion at IPv6 WG meeting at RIPE 
in Reykyavik in May and bring some additional operational feedback to 
this mailing list ;)