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

Mark Smith <markzzzsmith@gmail.com> Thu, 14 February 2019 20:40 UTC

Return-Path: <markzzzsmith@gmail.com>
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 10DD012EB11 for <ipv6@ietfa.amsl.com>; Thu, 14 Feb 2019 12:40:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 bOi1DeiJBn71 for <ipv6@ietfa.amsl.com>; Thu, 14 Feb 2019 12:40:28 -0800 (PST)
Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (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 2F9B3128D52 for <ipv6@ietf.org>; Thu, 14 Feb 2019 12:40:28 -0800 (PST)
Received: by mail-ot1-x335.google.com with SMTP id v62so4036145otb.3 for <ipv6@ietf.org>; Thu, 14 Feb 2019 12:40:28 -0800 (PST)
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=QUalxQcJG3vfB+7yNbBr4z0oBV5EPrR6FnhcqqmWn5c=; b=qJAGbyWIuj3FNEipUceICig5mzAk4IkugrmCc3XAs1M7fuOjv1c7NN39eHVqsA0F3M blGpo/+ADRaCyCnJIIYaKK+Id2TUesvptPg7hV0kfXsgKFl3bJCWUIBYhXbuffxVS4mV KNw6X/gTN9gUdudYLmeo2vu8ovLry3f7OYm1PczRbk9lXToajpvX97LN+50ltkcRJylN 9CirvSmxP42290MWaoIvaTJSbo/bweq8TXYqRCZ4G9ebE3iizoEJ385SYm58YVhGuZCQ 62yB1Ct2W/apSYPbh70/b0jdWhfGhWTFNVOUngu1t8rwtbtMWpa1413LSprc/PkLej2y N8dw==
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=QUalxQcJG3vfB+7yNbBr4z0oBV5EPrR6FnhcqqmWn5c=; b=pDqE3P+Ls39RohbfAUAde1jemHH0NAwdaK+ghqTYQDFBorPjmh4Nqoo5cJMSeVpOVM 4IWHd63gWP7pjLXO/Cg2v6kUTD4EZxgCdpnHtB0La+hdt55GFu5+XB7lLgv0SACYDF+K ASshPUeMOe0fWlYd/GiDLjlkPCEiGZIZAEWHSb+NgSgmuy/XlR9cQCkg/pbKxlPVWY5u AoOlfNnDwZoqa8CXoqTi5E75bDnzvtc97zPPEFIWDbst1ufG3CVXYiJmj7CSAuZZiLzn R/p/QoabhwYwhU7tHHtWUASK2tF1KFAmoCubIShVdHzOhDQ1Jwv87pTOiPi7exGVGUhn 3iKQ==
X-Gm-Message-State: AHQUAuZ+F/NJCscM/cN3+rQsG0NFyCvPjIqH+db15606RASVAUo+8VZ+ FuBackANjfHnMYgOtNXHR9fL9KpAf8HvCaHXV6o/oA==
X-Google-Smtp-Source: AHgI3IZqVN54mTX4x7e1t1vo8jN2LFYAjQuL1PyNiHetJ2TW6mHbWYOi/FATQqfj5kJS2y9+Q5t8wzKQApu2qx+coDA=
X-Received: by 2002:aca:ed06:: with SMTP id l6mr3660019oih.7.1550176827128; Thu, 14 Feb 2019 12:40:27 -0800 (PST)
MIME-Version: 1.0
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <1c7ebabb-d6f6-d877-d4aa-d6c0fc7d5c60@go6.si> <6278.1549471453@dooku.sandelman.ca> <CAO42Z2xdKtLJV11KXELBKca6CWn=B6Avz6bO_94kFFXaKiZ-pQ@mail.gmail.com> <4602.1549908472@localhost> <CAO42Z2w1swQNuwnrOyTCEMXt0NSyrBx7Ww3kUN-7dfEV=fvk3A@mail.gmail.com> <c16e0e1f-1ed2-ad88-80f1-070bdd8bccca@go6.si> <1F2C2AEE-1C7D-481C-BBA7-7E507312C53A@employees.org> <e56a6e5b-648d-200e-c35d-97f15a31fb2a@asgard.org> <CAO42Z2zh7fKAgQJq9aLCTiFoSSsTeGM=pK3gXitg+gcxH=9fhQ@mail.gmail.com> <d38857c2-6e92-91d6-bb5d-d3eeeb61276a@gmail.com> <CAO42Z2yb47OyXk__Sz-kO00pfcBJgLAhff5DF=mpAddR0iCnAA@mail.gmail.com> <2612280f-195a-ae7a-b3b1-9022d9282fa7@foobar.org> <56F813F4-C512-40A9-8A68-1090C76A80F6@consulintel.es> <CAHL_VyCN8kU7qnLOphfGR25-xGBe_p6WeGTkKVXwU5uy5aJ8Dg@mail.gmail.com> <65DB4854-97D2-4C31-A691-2CD93812EF93@consulintel.es> <CAHL_VyCMpCcGkEQu+RV1GRf2QLB-HD0+AOOBV0YhfQ5sbydVzQ@mail.gmail.com> <1e31ec6a-a743-3034-51e4-19d88e379475@go6.si> <CAHL_VyAhbUVLwi2ViwrDNYi-Fy3j1TY2-Aq5SLCPtt5OdiFFdg@mail.gmail.com>
In-Reply-To: <CAHL_VyAhbUVLwi2ViwrDNYi-Fy3j1TY2-Aq5SLCPtt5OdiFFdg@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 15 Feb 2019 07:39:59 +1100
Message-ID: <CAO42Z2yAxcf1uz8B0LZ9JysfAB0Tr+Uzgkj7azaAT9vSgXWvjA@mail.gmail.com>
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
To: Richard Patterson <richard@helix.net.nz>
Cc: Jan Zorz - Go6 <jan@go6.si>, 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Uz6g4FkMnEOxrr41Ndu9UolUKDg>
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: Thu, 14 Feb 2019 20:40:30 -0000

On Thu, 14 Feb 2019 at 23:20, Richard Patterson <richard@helix.net.nz> wrote:
>
> On Thu, 14 Feb 2019 at 11:48, Jan Zorz - Go6 <jan@go6.si> wrote:
> >
> > Hmm... does that mean that also every enterprise network with staff
> > accessing the Internet from their network should have dynamic prefixes
> > and change all the time? I don't think that network people at all those
> > companies would agree.
>
> Bit of a different dynamic there, we have a moral obligation to
> protect our customers, I imagine employers would have a different
> feeling on the matter.
>
> My point was rather that there are often reasons why an operator has
> built things in such a way, and it's not always just because they
> didn't understand IPv6 very well.
>

I don't know about other markets, however dynamic IPv4 addresses on
permanent, always up broadband links in Australia has usually been
because ISPs wanted to charge a price premium for static address
assignments..

Even these IPv4 dynamic addresses may be more stable than most
realise. I'm not sure about other vendors, however Cisco's IOS
remembers these dynamic address assignments and if the customer's new
session lands on the same BNG, they'll get the same dynamic IPv4
address as before.

> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------