IETF Logo Mail Archive

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

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 15 February 2019 13:55 UTC

Return-Path: <swmike@swm.pp.se>
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 D5B3712F1A2 for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 05:55:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 PcRNGg1AWAag for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 05:55:32 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (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 EE49612D4E6 for <ipv6@ietf.org>; Fri, 15 Feb 2019 05:55:30 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 3FABBAF; Fri, 15 Feb 2019 14:55:27 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1550238927; bh=riDUHjvHQPgEQhfFqNZ4ApoSjRH6gWKwZVGdoUJuPQk=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=xUySWeFnByHzrSqUFCogaacI3AEPzE7vvNC6xXs8jk/PgUoCj3Za4MVfAgMSS916D EssthFjJAcVjcQ5Q4JurkOHyAnjuFGi4qc7z2DKpo3zkLsVX2V+qase2IvK/9QMTBd QrS8ABE6LwBYy78tOM0TGI4i199L0fITwIKI4r2E=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 3D17C9F; Fri, 15 Feb 2019 14:55:27 +0100 (CET)
Date: Fri, 15 Feb 2019 14:55:27 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
cc: Richard Patterson <richard@helix.net.nz>, 6man WG <ipv6@ietf.org>
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
In-Reply-To: <65fbfb39-6009-ebc6-3dba-68aa3844153b@gmail.com>
Message-ID: <alpine.DEB.2.20.1902151450230.23912@uplift.swm.pp.se>
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>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/cU2v7BtPf0BHWbArUGoa32TCg8c>
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 13:55:35 -0000

On Fri, 15 Feb 2019, Alexandre Petrescu wrote:

> I speculate that because I've never seen RELEASEing a prefix.  And I did 
> see many other DHCP things working.

It would beneficial for everybody if you stopped speculating so much.

Here you go:

14:54:11.595732 IP6 (hlim 1, next-header UDP (17) payload length: 266) 
fe80::222:7ff:fe6f:1b36.546 > ff02::1:2.547: [udp sum ok] dhcp6 release 
(xid=2fec (elapsed-time 0) (option-request SIP-servers-domain DNS-server 
SNTP-servers NTP-server AFTR-Name opt_67 opt_96 opt_123 opt_198 opt_199 
SIP-servers-domain SIP-servers-address DNS-server DNS-search-list 
server-unicast SNTP-servers NTP-server AFTR-Name opt_67 opt_82 opt_83 
opt_94 opt_95 opt_96) (client-ID hwaddr type 1 0022076f1b36) (server-ID 
hwaddr/time type 1 time 512640186 56847afe6699) (vendor-class) 
(Client-FQDN) (IA_PD IAID:1598115417 T1:0 T2:0 (IA_PD-prefix 
2003:1c09:24:1500::/60 pltime:0 vltime:0)) (IA_PD IAID:1230001238 T1:0 
T2:0 (IA_PD-prefix 2003:1821:24:1500::/60 pltime:0 vltime:0)) (IA_PD 
IAID:1448036688 T1:0 T2:0 (IA_PD-prefix 2003:1831:24:1500::/60 pltime:0 
vltime:0)))

14:54:12.241025 IP6 (class 0xe0, hlim 30, next-header UDP (17) payload 
length: 290) fe80::8678:acff:fe4b:15cc.547 > fe80::222:7ff:fe6f:1b36.546: 
[udp sum ok] dhcp6 reply (xid=2fec (client-ID hwaddr type 1 0022076f1b36) 
(server-ID hwaddr/time type 1 time 512640186 56847afe6699) (status-code 
Success) (IA_PD IAID:1598115417 T1:0 T2:0 (status-code Success)) (IA_PD 
IAID:1230001238 T1:0 T2:0 (status-code Success)) (IA_PD IAID:1448036688 
T1:0 T2:0 (status-code Success)))


-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

v2.23.0 | Report a Bug | By Email