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

Mark Smith <markzzzsmith@gmail.com> Sat, 26 October 2019 01:59 UTC

Return-Path: <markzzzsmith@gmail.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 F1F051200B9 for <v6ops@ietfa.amsl.com>; Fri, 25 Oct 2019 18:59:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.497
X-Spam-Level:
X-Spam-Status: No, score=-0.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 E4uNxgK7Q5cD for <v6ops@ietfa.amsl.com>; Fri, 25 Oct 2019 18:59:44 -0700 (PDT)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78FFF12001A for <v6ops@ietf.org>; Fri, 25 Oct 2019 18:59:44 -0700 (PDT)
Received: by mail-ot1-x330.google.com with SMTP id z6so3354126otb.2 for <v6ops@ietf.org>; Fri, 25 Oct 2019 18:59:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Hb994jUUHwNXCsT21HJjIkVENUCzAXg6uvvWPI5FdRM=; b=Og9ERwMG1wiiBUtY4io2u5XvAdP24NG8lUlMBvQN2z3dVuXnY8777y6CQT4fBNCdKO JPFJ2/9M5J3OIsKxgIGD7HsMcTfWsEs7WtJvdt6b0cKG82OMfqgCTQTAcfXBX5pWG4Yr L7DwUQjK1crLh1SdPJM2AHiUE7/AClcIsdg2IRtazp5HHeG04n0aeGR5ivejwAT0Jdq8 3c27AIf4tsbxZFQ8habIjP7MWJZgk3Vqkwh1WlUxuxTjhseNPoTDB4nEf5YHNoKAibeN EKyNi1uTF/4ANjpNkY8aQEmpEoZdkLg+dAuLfat5gwJjpR0cnLED3JBj50++YsoOFXb+ lZ0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Hb994jUUHwNXCsT21HJjIkVENUCzAXg6uvvWPI5FdRM=; b=iF6lIzw/KE+mhFGPm654X4bLJsivNAZ6vyKa2x5chJb/z5ixcn1uAR1uULk77rS3ro X+4zoCsuLX2h6qxPG/E5cuHXOhdaoOOlAtDN0wBehaUCEXo+oXYFlOLbKe7dMIBx8QXb LwXtFH2dPnQOK4qf4D8fjympwioQ3jui7cmz1ZWs0Jq74TK/cuGZHzYgS0z2QYcvyYOp MQukyb3Jsere9k23HukIxDGq9tYF6srLrlE+75Pbbsrqnp/kE4f6na3/zG0JdVY4gxYl uYLo4V64CF+4BNzzn7q2PzVQ/kSP27wqO6EunsKmp3xrNtNmImxso9FLh50ddKsW3DWj rmIw==
X-Gm-Message-State: APjAAAWm+c1ulp9yFu7mZ/7tfsiIbXjcF4ZRpamZC4VGWchsD9+qdxNN K24WGy9ud5gDdsCgr7eAyZJcfux6NoheuOrMFTA=
X-Google-Smtp-Source: APXvYqx1W6Wm38nn+iX6Z0XoEfPcDQZ5omXUt1fGxgnwSuF7aoZjaLOKgGR46l1eLKxf0jLxMf0LV5rQE6aL6V38HNk=
X-Received: by 2002:a9d:6c85:: with SMTP id c5mr4948620otr.257.1572055183821; Fri, 25 Oct 2019 18:59:43 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <c68e4826-8313-ef4c-86c1-0a45ba7278fd@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sat, 26 Oct 2019 12:59:32 +1100
Message-ID: <CAO42Z2wPsr9iT1JtJPeFxJFmuhy_sckHB5_AJMo61zxakeC5OQ@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: v6ops list <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cc909f0595c69ecb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/n8jyZTpLdEx84iCwOVKLZ8FhV8M>
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 01:59:46 -0000

On Sat, 26 Oct 2019, 12:30 Brian E Carpenter, <brian.e.carpenter@gmail.com>
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.
>

This smells of the local BRAS pool dial up model.  In the same situation,
that wouldn't happen to me because I have a stable /56 associated with my
user account.

If you're using PPPoE, you can specify the access concentrator you want to
(re)attach to.

One common AC/BRAS/NAS implementation caches IPv4 pool assignments to user
accounts, so that if the same account re-attaches, the same IPv4 pool
address is given back to it. I wouldn't be surprised if that also occurs
with IPv6 pool delegated prefix assignments.





> Regards
>    Brian
>