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

Lee Howard <lee@asgard.org> Wed, 13 February 2019 22:34 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 0375312F1A6 for <ipv6@ietfa.amsl.com>; Wed, 13 Feb 2019 14:34:56 -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 xba27k5L6YQP for <ipv6@ietfa.amsl.com>; Wed, 13 Feb 2019 14:34:54 -0800 (PST)
Received: from atl4mhob21.registeredsite.com (atl4mhob21.registeredsite.com [209.17.115.115]) by ietfa.amsl.com (Postfix) with ESMTP id 7294E128B36 for <ipv6@ietf.org>; Wed, 13 Feb 2019 14:34:54 -0800 (PST)
Received: from mailpod.hostingplatform.com (atl4qobmail03pod6.registeredsite.com [10.30.71.211]) by atl4mhob21.registeredsite.com (8.14.4/8.14.4) with ESMTP id x1DMYpX6047983 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <ipv6@ietf.org>; Wed, 13 Feb 2019 17:34:51 -0500
Received: (qmail 14182 invoked by uid 0); 13 Feb 2019 22:34:51 -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; 13 Feb 2019 22:34:51 -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> <7a401098-ef51-86d4-064b-056e061a4472@gmail.com> <CAHL_VyDACS172yQoSiz7s+FvrQWchesGXNx73FkA2T057q0YPQ@mail.gmail.com> <2ab6bda2-1a8f-47d9-17c1-bd82343e86c5@si6networks.com> <682ab369-3c61-3c63-32be-d59ff445101b@go6.si>
From: Lee Howard <lee@asgard.org>
Message-ID: <cc0388a8-9576-df30-b3a0-cf4449eb95d5@asgard.org>
Date: Wed, 13 Feb 2019 17:34:50 -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: <682ab369-3c61-3c63-32be-d59ff445101b@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/KcAlLxZ1Vs2U_sFE0jDc07P13jM>
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: Wed, 13 Feb 2019 22:34:56 -0000

On 2/13/19 11:38 AM, Jan Zorz - Go6 wrote:
> On 13/02/2019 16:38, Fernando Gont wrote:
>
>
> However, CPE is also an important part of the game here. As said 
> before and as heard from Richard, some huge operators are already 
> deploying this "hack" where they write a PD to persistent storage and 
> compare prefixes after reboots and this solves a lot of problems. Why 
> not making this easy fix a recommended thing to do for everyone?
>
> When talking about the provisioning part - IETF can't tell operators 
> how to run networks (obviously), but what we can do here is to say 
> "when assigning IPv6 prefix to a customer, identified by the same 
> DUID, we must not assign a different prefix to the same DUID before 
> the lifetime of PD that we set doesn't expire, otherwise you are 
> breaking the protocol standards."
"you are breaking the protocol standards" only matters if it breaks 
interoperability. Otherwise you're trying to be protocol police.
>
> If somebody decides (for some bizzare reason) that it's a good idea to 
> make CPEs with randomized DUID after every reboot, then they shall 
> implement memorizing PDs in persistent storage across reboots and send 
> ICMP packets after reboot to deprecate old prefix(es)
Well, CPEs do get some strange ideas of what a DUID should look like. 
When I had the ability to influence CPE features, I told them how to 
build their DUID so it was predictable to me. (I forget which version I 
specified, but it included link layer address). Still didn't help with 
the mass of retail devices.
>
> I think that extending a scope of our I-D to this three "advices" 
> would bring at least some hope for improvement, as currently it can't 
> be worse. Of course, things are easy for huge operators with home-brew 
> CPEs and a lot of knowledge, but there are other, smaller and less 
> deep-tech educated ISPs that could benefit from improved defaults.

My perception is that lack of support for IPv6 at all, followed by lack 
of support for IPv6 transition mechanisms, is a much larger problem in 
CPE. This will simply become another RFC they aren't implementing.

Lee

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