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

Lee Howard <lee@asgard.org> Tue, 05 February 2019 21:46 UTC

Return-Path: <lee@asgard.org>
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 B298F1312D1 for <ipv6@ietfa.amsl.com>; Tue, 5 Feb 2019 13:46:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level:
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=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 FSFOmG55URog for <ipv6@ietfa.amsl.com>; Tue, 5 Feb 2019 13:46:45 -0800 (PST)
Received: from atl4mhob12.registeredsite.com (atl4mhob12.registeredsite.com [209.17.115.50]) by ietfa.amsl.com (Postfix) with ESMTP id 17C8B1312A7 for <ipv6@ietf.org>; Tue, 5 Feb 2019 13:46:44 -0800 (PST)
Received: from mailpod.hostingplatform.com (atl4qobmail02pod6.registeredsite.com [10.30.71.210]) by atl4mhob12.registeredsite.com (8.14.4/8.14.4) with ESMTP id x15LkgR6025589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <ipv6@ietf.org>; Tue, 5 Feb 2019 16:46:42 -0500
Received: (qmail 26959 invoked by uid 0); 5 Feb 2019 21:46:42 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 5 Feb 2019 21:46:42 -0000
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
To: ipv6@ietf.org
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> <77ecf321-b46e-4f25-7f68-05b15714a99e@si6networks.com> <CAHL_VyDdHuEAc9UdeiRp9f+c0tdzyoLwPY1rJbZmbWAuq96Uuw@mail.gmail.com> <alpine.DEB.2.20.1902051127510.23912@uplift.swm.pp.se> <m1gqyJC-0000FkC@stereo.hq.phicoh.net> <CAO42Z2wKh-vXmv=dNmr6oEmGnw09ajrr2geYJ=H1DbSYSm=VuQ@mail.gmail.com> <m1gqzYT-0000F5C@stereo.hq.phicoh.net> <e8eabf0f-191a-a293-8051-35268a62a2bd@go6.si> <37ae87fb-93f5-4ec4-6e55-e35ce308f91c@asgard.org> <2aa19534-4856-f01d-8184-6c7ed125ca1b@go6.si>
From: Lee Howard <lee@asgard.org>
Message-ID: <9cdf8405-e777-6769-4d4f-f123c13a9456@asgard.org>
Date: Tue, 05 Feb 2019 16:46:41 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <2aa19534-4856-f01d-8184-6c7ed125ca1b@go6.si>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_u0_H2dOEKte8c9IvLBlULw6i54>
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 21:46:48 -0000

On 2/5/19 3:11 PM, Jan Zorz - Go6 wrote:
> On 05/02/2019 18:54, Lee Howard wrote:
>>>> Ideally every customer just gets a static /48. There is no 
>>>> technical reason
>>>> why this can't be made to work.
>>>
>>> Agreed 100% :)
>>
>>
>> I cordially invite you to go build your own network, so you will 
>> actually be able to tell somebody how to build their network.
>
> I did. Many times.

And yet when somebody says "I built my network for reasons that were 
compelling to me at the time" you tell them they did it wrong. It's 
tiresome.

Even when someone does engage in conversation and begin explaining 
reasons, it always becomes a rathole of all of the unique considerations 
of that network with those vendors and this budget and some other 
requirements at the time in question. Rebuilding a functioning network 
is costly and breaks things.

If you were a network operator reading the latter part of this thread, 
would you be inclined to participate in this working group or in the IETF?

>
> He said "Ideally". I agree with that :)

Static? That was fine when there were few enough nodes that you could 
manually configure changes. Addressing is dynamic, which is why we have 
dynamic routing protocols.

Jan, I'm replying to you because we're friends and I know we will remain 
so. When I say "you" here, I don't just mean you.

Lee


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