Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds

Fernando Gont <fgont@si6networks.com> Sat, 26 October 2019 18:24 UTC

Return-Path: <fgont@si6networks.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 77EB31200CC for <v6ops@ietfa.amsl.com>; Sat, 26 Oct 2019 11:24:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.484
X-Spam-Level: **
X-Spam-Status: No, score=2.484 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 NTeDJOY0zNRb for <v6ops@ietfa.amsl.com>; Sat, 26 Oct 2019 11:24:30 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97B561200C5 for <v6ops@ietf.org>; Sat, 26 Oct 2019 11:24:30 -0700 (PDT)
Received: from [10.10.22.143] (mvx-177-92-65-194.mundivox.com [177.92.65.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 75B2F86917; Sat, 26 Oct 2019 20:24:27 +0200 (CEST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Mark Smith <markzzzsmith@gmail.com>
Cc: IPv6 Operations <v6ops@ietf.org>
References: <m1iNIFE-0000IwC@stereo.hq.phicoh.net> <d1b6855d-bde9-7b53-4809-0846bb9772e4@si6networks.com> <CAO42Z2x7vudujw5t++obry56g=VNjQXXTHFK8pBPk0jmk78Bcg@mail.gmail.com> <CAJoHkZ8pTjszP0vw4BjX0HUhmPa6wJONzdy2JEm5iqAfBUvjRg@mail.gmail.com> <CAO42Z2wCYi4KWTEz1hUSPVr9+hu8GaHRkPuvQQ2P00knvnPaaQ@mail.gmail.com> <848BA3B3-36B4-4C42-86D0-88759BC45D5A@employees.org> <A61279DA-4678-4A10-9117-6CA227AE2FA5@cisco.com> <A90AD47E-00E2-4EAB-8BD8-142CC10A6B6F@employees.org> <m1iNv5U-0000KUC@stereo.hq.phicoh.net> <CAO42Z2xUa7n6uUz9gtiZyZR39KFhsQ8mLeiyQdyERGTcJcXWWA@mail.gmail.com> <CADzU5g77cvfZknAzSkkNTP5vT73MZnSdGuOJ4y0Uba8XMgiASA@mail.gmail.com> <CAO42Z2xHYU3y455XsM5grvG0360b9RigCaN=L+cc27_oyxhq0w@mail.gmail.com> <c68e4826-8313-ef4c-86c1-0a45ba7278fd@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <a5c40c94-5c57-10dd-2f75-44fd707b56e1@si6networks.com>
Date: Sat, 26 Oct 2019 00:16:00 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <c68e4826-8313-ef4c-86c1-0a45ba7278fd@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/7gKWU4Kw-f-pUTLIQ-AUVUlZBGQ>
Subject: Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
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: Sat, 26 Oct 2019 18:24:33 -0000

On 25/10/19 22:30, Brian E Carpenter wrote:
>>>     Renumbering is not "common" but it certainly happens.
> ....> People imply it is a regular and routine event...
> 
> Sadly, it is. For example, at my previous apartment there was a badly waterproofed joint somewhere between me and the nearest street cabinet, so for months I frequently lost ADSL synch... and when it came back, I got new IPv6 prefix. After a heavy rainstorm, this would happen many times a day.
> 
> Yes, OK, there was a copper cable fault and it took <unmentionable company> many months to fix it. OK, maybe the ISP shouldn't regenerate a prefix every time. But that's real life and I suspect I am one of millions.

Indeed you are. In fact, I presented this topic at a recent LACNOG
meeting, and we had at least three guys, from different countries,
coming to the mike, noting they have experienced this, noting that they
wished we did something about it. The document itself is a product of a
conversation with an ISP (from a completely different geographical zone).

Particularly when it's the user that experiences the problem, I think we
are not of much help when instead of improving robustness, we complain
about how the world should be a different places.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492