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

Philip Homburg <pch-v6ops-9@u-1.phicoh.com> Thu, 31 January 2019 16:37 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.com>
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 D2DAC12D84C for <v6ops@ietfa.amsl.com>; Thu, 31 Jan 2019 08:37:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 k7iF5lpei42l for <v6ops@ietfa.amsl.com>; Thu, 31 Jan 2019 08:37:51 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (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 C2C7212D4F0 for <v6ops@ietf.org>; Thu, 31 Jan 2019 08:37:50 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1gpFLa-0000FyC; Thu, 31 Jan 2019 17:37:50 +0100
Message-Id: <m1gpFLa-0000FyC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
From: Philip Homburg <pch-v6ops-9@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <7b77cbfe-2bee-fda0-9751-44f9fb95a553@forthnet.gr> <d9eeb2b7-588b-0ce0-00a7-354960d94400@lanparty.ee>
In-reply-to: Your message of "Thu, 31 Jan 2019 18:26:02 +0200 ." <d9eeb2b7-588b-0ce0-00a7-354960d94400@lanparty.ee>
Date: Thu, 31 Jan 2019 17:37:49 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Co_9ZCHmYJh5sSP8NrInhX_0_-0>
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 16:37:53 -0000

> In reality we have not found the reboot to be a big problem as for
> most residential/SOHO customers the same CPE provides wired LAN
> ports and wifi. Both will be disconnected during reboot and this
> information is visible to OS and OSes will stop using the prefix
> on those interfaces due to that anyway.

There is always the possibility that someone uses a switch or a wifi 
repeater.

In addition, VMs (on a laptop) can be connected using a software bridge on
the host.

Simple setups will be fine, but it may be worth solving this problem.