IETF Logo Mail Archive

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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 15 February 2019 15:00 UTC

Return-Path: <alexandre.petrescu@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 E39491310A0 for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 07:00:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, 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 DURK_NjizG4K for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 07:00:06 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 778321310FA for <ipv6@ietf.org>; Fri, 15 Feb 2019 07:00:06 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x1FF00KX034065; Fri, 15 Feb 2019 16:00:00 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C2F69202723; Fri, 15 Feb 2019 16:00:00 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B290A2017FE; Fri, 15 Feb 2019 16:00:00 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x1FF00t1019911; Fri, 15 Feb 2019 16:00:00 +0100
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, Richard Patterson <richard@helix.net.nz>
Cc: 6man WG <ipv6@ietf.org>
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <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> <8CE7A0CD-97D9-46A0-814D-CAF8788F9964@consulintel.es> <e3e0bf2273e04f15b792665d0f66dfe5@boeing.com> <4c5fab33-2bff-e5b5-fc1d-8f60a01a146d@go6.si> <b4525832-9151-20bf-7136-31d87ba6c88d@huitema.net> <444A9043-0EDF-4F21-9DCE-BF019B81D078@huitema.net> <9BA9D825-2B75-47FA-999E-2712E151AD01@huitema.net> <1b1a78b8-ccba-2085-0fb0-0c957e782146@moth.iki.fi> <7bab7a8a-1136-9b53-56b1-6401e62947d5@go6.si> <CAHL_VyDKh+R4UC5qicbEk-qVkYi8wxkXabPRn_mw9fi_1QHZ9g@mail.gmail.com> <98eb2f0c-7f13-e024-147e-dc2b2876a248@gmail.com> <CAHL_VyCiHUTfaqQV9E82GtSQwpr9A2ByeF+dvzazp2j1NT_2sQ@mail.gmail.com> <65fbfb39-6009-ebc6-3dba-68aa3844153b@gmail.com> <33beee588f994cd1adf3c19438e241b1@boeing.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <5cd314f4-7662-2c6c-75c2-a751406c8fba@gmail.com>
Date: Fri, 15 Feb 2019 16:00:00 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <33beee588f994cd1adf3c19438e241b1@boeing.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/URHODTDE7bP5jImc8gupU2Xcs-A>
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: Fri, 15 Feb 2019 15:00:14 -0000


Le 15/02/2019 à 15:47, Templin (US), Fred L a écrit :
> Alex,
> 
>> -----Original Message-----
>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Alexandre Petrescu
>> Sent: Friday, February 15, 2019 5:03 AM
>> To: Richard Patterson <richard@helix.net.nz>
>> Cc: 6man WG <ipv6@ietf.org>
>> Subject: Re: A common problem with SLAAC in "renumbering" scenarios
>>
>>
>>
>> Le 15/02/2019 à 13:58, Richard Patterson a écrit :
>>> On Fri, 15 Feb 2019 at 12:29, Alexandre Petrescu
>>> <alexandre.petrescu@gmail.com> wrote:
>>>> Le 15/02/2019 à 13:20, Richard Patterson a écrit :
>>>>> And that mechanism already exists in the form of a DHCPv6 RELEASE, but
>>>>> not if the assignment authority has been removed from the DHCPv6
>>>>> Server, and placed within RADIUS instead.
>>>>
>>>> I speculate RELEASE does not work with prefixes (like it does work with
>>>> IA_NA addresses, but not with IA_PD prefixes).
>>>
>>> I'm not sure why you'd speculate that, but it does IME.
>>
>> I speculate that because I've never seen RELEASEing a prefix.  And I did
>> see many other DHCP things working.
> 
> DHCPv6 Release for IA_PD is no different than for IA_NA and others; it
> works the same way.

I agree - the packet dump showed IPv6 message RELEASE with IA_PD for 
prefixes.  My speculation was wrong.

> Please also remember that RFC8415 is the new standard; RFCs 3315 and
> 3633 are obsoleted.

Noted, and congratulations for the new DHCP RFC.

Alex

> 
> Thanks - Fred
> 
>> I dont know what you mean by IME.
>>
>> Alex
>>
>>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email