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

Richard Patterson <richard@helix.net.nz> Tue, 05 February 2019 17:28 UTC

Return-Path: <richard@helix.net.nz>
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 277CF130EA5 for <ipv6@ietfa.amsl.com>; Tue, 5 Feb 2019 09:28:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.042
X-Spam-Level:
X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=helix-net-nz.20150623.gappssmtp.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 96JkrNviw3_E for <ipv6@ietfa.amsl.com>; Tue, 5 Feb 2019 09:28:25 -0800 (PST)
Received: from mail-yw1-xc2e.google.com (mail-yw1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) (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 126C3124BAA for <ipv6@ietf.org>; Tue, 5 Feb 2019 09:28:24 -0800 (PST)
Received: by mail-yw1-xc2e.google.com with SMTP id x21so693122ywx.11 for <ipv6@ietf.org>; Tue, 05 Feb 2019 09:28:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=helix-net-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gSuJHYSziMBNefV/H/a8jJS8VoOpjbUlJDGqW8cvkh4=; b=KE04x6gEfmBJpfe4JEhEx/xMZ1j56Ly0h2f0+MBWT/RxwG5CXXyYTR3463AJ8pkdkS Jl4XhMKaQmN8iX4nkaNvngeFltUfAgv2IUkkcG0qrIYEb6OLg57jR0ZmASyDQRtNzWlK 5QJR6lMy8ZwNSmPUjIdzZSeta1DrfRCAXlaEXhs0x5/wHX+6x24CaXeOdjYhnnZOcsDx vXsri83HDQNlzi34EgmS22Zab3aB7GNp2hATJxw23omx+0kq1KuTz/T5Lz6KCFBYwbri RlN0X80NV8chYKHDwPi5ff9jecq8g1ORRVeaopD5BKnqzc5bxSrcGcEitlC01efIML6l WYiQ==
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=gSuJHYSziMBNefV/H/a8jJS8VoOpjbUlJDGqW8cvkh4=; b=Oz9COi9xa5RJpYKc3eqHhoSun3UZQF/jAyAEiYr7LO1DMF0sBT8wI/B1bcZ3cHBmFf sI05zW+/HWrow5ZTnbHXEGJ2jEEpBhlV5nShHPqBrWYcY0VoyEbxr6lRlqwMXaaChM/B jo0ZVcRsR0AqJlqCn4T5uD9ipRa6hkgeVcNTb7vfqT276QeVvqktHCtBbooN6zRMvXuA GXVGg01kI5EVYTYpbP1ROQr8lt+OTMRnq16ieRY0n+afGYe/UqMVxaAd1fdUTKMPeUTv en0htgXo7LQSb0PTURqcLLi9oiNuKZlAjOa3ViqwzlTDMFYXKxKv/hO1nOHXyTOfMTwg Mf3Q==
X-Gm-Message-State: AHQUAubBVH4I6OZ9E/9MCrRO2DcDnS7AL2Smjsm5y3JuXr+1FSD7h5it f8vWymcOfTHDe89r4CEMskIEI0L/bK0=
X-Google-Smtp-Source: AHgI3IbAehC/lYzXtx7En9FM1UvLiQXeLcWoCXNgb4l2g2goPnKipROWlDO9gO2yGZNqwXueX+CRxA==
X-Received: by 2002:a81:2c09:: with SMTP id s9mr4803334yws.165.1549387703747; Tue, 05 Feb 2019 09:28:23 -0800 (PST)
Received: from mail-yb1-f182.google.com (mail-yb1-f182.google.com. [209.85.219.182]) by smtp.gmail.com with ESMTPSA id w2sm1283990ywe.62.2019.02.05.09.28.22 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Feb 2019 09:28:22 -0800 (PST)
Received: by mail-yb1-f182.google.com with SMTP id s17so1318629ybp.6 for <ipv6@ietf.org>; Tue, 05 Feb 2019 09:28:22 -0800 (PST)
X-Received: by 2002:a25:8108:: with SMTP id o8mr4896360ybk.83.1549387702551; Tue, 05 Feb 2019 09:28:22 -0800 (PST)
MIME-Version: 1.0
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <alpine.DEB.2.20.1901311236320.5601@uplift.swm.pp.se> <m1gpCcz-0000FlC@stereo.hq.phicoh.net> <ddd28787-8905-bafd-3546-2ceef436c8b0@si6networks.com> <m1gptWx-0000G3C@stereo.hq.phicoh.net> <69609C58-7205-4519-B17A-4FBC8AE2EA16@employees.org> <d40b41c3-ff1b-cab4-a8de-16692a78e8fd@go6.si> <D1E45CAD-08D0-43D4-90F7-C4DD44CB32C0@employees.org> <alpine.DEB.2.20.1902041330531.23912@uplift.swm.pp.se> <62b74cf1-9cb0-bba3-b078-cb6f48e90145@foobar.org> <m1gqeb9-0000GCC@stereo.hq.phicoh.net> <bc8c0ef9-2c24-1c2a-9822-8580e6e1858c@go6.si> <CAO42Z2w2FdcumHTY6S2GuUi4pfbHrc6dihKvDtL3mHUykkOPZw@mail.gmail.com> <6dc0dbea-44fc-96df-c9dd-313d4385d19a@go6.si>
In-Reply-To: <6dc0dbea-44fc-96df-c9dd-313d4385d19a@go6.si>
From: Richard Patterson <richard@helix.net.nz>
Date: Tue, 05 Feb 2019 17:28:11 +0000
X-Gmail-Original-Message-ID: <CAHL_VyBxSFXK-t723nFjHLB1GmuZEZzgS6k9oJ4v1qVJn=D1aQ@mail.gmail.com>
Message-ID: <CAHL_VyBxSFXK-t723nFjHLB1GmuZEZzgS6k9oJ4v1qVJn=D1aQ@mail.gmail.com>
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
To: Jan Zorz - Go6 <jan@go6.si>
Cc: Mark Smith <markzzzsmith@gmail.com>, 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/w4m5re-KVulfLd3S9r2uDfxfu70>
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, 05 Feb 2019 17:28:27 -0000

On Tue, 5 Feb 2019 at 15:41, Jan Zorz - Go6 <jan@go6.si> wrote:

> simply assigns a big IPv6 prefix to that BNG/BRAS as a "pool" where
> BNG/BRAS allocates prefixes to customers "at it's will". It's fast, it's
> simple and works in a lab environment.
>
> That's the behaviour that needs to stop.

Why?