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

Fernando Gont <fgont@si6networks.com> Thu, 31 October 2019 19:58 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D528D1200C5 for <v6ops@ietfa.amsl.com>; Thu, 31 Oct 2019 12:58:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 tduVQXYtK2Yr for <v6ops@ietfa.amsl.com>; Thu, 31 Oct 2019 12:58:41 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE43E12006A for <v6ops@ietf.org>; Thu, 31 Oct 2019 12:58:41 -0700 (PDT)
Received: from [192.168.1.36] (unknown [177.27.208.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id A4C828669B; Thu, 31 Oct 2019 20:58:38 +0100 (CET)
To: "Bernie Volz (volz)" <volz@cisco.com>, Owen DeLong <owen@delong.com>, Ted Lemon <mellon@fugue.com>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
References: <CAO42Z2yQ_6PT3nQrXGD-mKO1bjsW6V3jZ_2kNGC2x586EMiNZg@mail.gmail.com> <B53CE471-C6E8-4DC1-8A72-C6E23154544F@fugue.com> <e67f597d-93a7-3882-3a12-69519178893d@foobar.org> <m1iOinq-0000J3C@stereo.hq.phicoh.net> <DC2F31E2-8CA4-483A-B1A1-6730A904BA32@fugue.com> <A96A5C76-93AE-40E4-BA52-776F9277C382@delong.com> <74875D36-6A96-4FB2-853F-86875833470D@cisco.com>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <d45a39b2-cbad-3fbb-3e92-7fb85c3fa088@si6networks.com>
Date: Thu, 31 Oct 2019 16:47:43 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <74875D36-6A96-4FB2-853F-86875833470D@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/u-36MKo3nT3guzW4BznxUHMddPg>
Subject: Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2019 19:58:44 -0000

On 27/10/19 19:03, Bernie Volz (volz) wrote:
>>I don’t know of a single DHCPv6 server which operates that way
> currently. Can you point to a working example?
> 
>  
> 
> That is actually the RFC8415 specified behavior … the DHCP server I work
> on (Cisco Prime Network Registrar) will do this if steps are taken to
> “invalidate” a lease.
> 
>  
> 
> See RFC 8415, Section 18.3.4:
> 
>  
> 
>    If the server finds that any of the addresses in the IA are not
> 
>    appropriate for the link to which the client is attached, the server
> 
>    returns the address to the client with lifetimes of 0.
> 
>  
> 
>    If the server finds that any of the delegated prefixes in the IA are
> 
>    not appropriate for the link to which the client is attached, the
> 
>    server returns the delegated prefix to the client with lifetimes
> 
>    of 0.

Doesn't the above imply that the client remembers the addresses?


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492