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

Philip Homburg <> Sun, 27 October 2019 14:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 035F612012C for <>; Sun, 27 Oct 2019 07:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NkK1PPmvUiML for <>; Sun, 27 Oct 2019 07:07:35 -0700 (PDT)
Received: from ( [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 171DE12012A for <>; Sun, 27 Oct 2019 07:07:35 -0700 (PDT)
Received: from (localhost [::ffff:]) by with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1iOjCf-0000L9C; Sun, 27 Oct 2019 15:07:33 +0100
Message-Id: <>
From: Philip Homburg <>
References: <> <> <> <> <>
In-reply-to: Your message of "Sun, 27 Oct 2019 09:54:36 -0400 ." <>
Date: Sun, 27 Oct 2019 15:07:26 +0100
Archived-At: <>
Subject: Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 27 Oct 2019 14:07:36 -0000

>    Actually I do not believe this is correct behavior.   Let us
>    assume prefix delegation.   If we have prefix delegation, then
>    when the CPE comes back from a power cycle, it should reconfirm
>    the prefix it had previously; the assumption is that that prefix
>    is still valid.  

This is not required behavior for a DHCP client. Traditionally, a client
does not have to write a lease it received in persistent storage. In 
fact, in the case of DHCPv6-PD in some cases that actually triggers bugs
on the ISP side and delays obtaining a new lease.

Now I'm not opposed to trying to renew the previous lease. It makes the
whole thing more complex and probably more fragile, but it is the right
thing to do.

However, the thing that actuualy makes it work (and no need for SEND there)
is to have the CPE to advertise a stale prefix with lifetimes zero to
inform hosts that this prefix no long works.