IETF Logo Mail Archive

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

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Fri, 15 February 2019 14:47 UTC

Return-Path: <Fred.L.Templin@boeing.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 38AAD124D68 for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 06:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 VNOvoIkuD023 for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 06:47:17 -0800 (PST)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (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 008C512008F for <ipv6@ietf.org>; Fri, 15 Feb 2019 06:47:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id x1FElEIK004476; Fri, 15 Feb 2019 09:47:14 -0500
Received: from XCH16-07-08.nos.boeing.com (xch16-07-08.nos.boeing.com [144.115.66.110]) by clt-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id x1FElDUE004461 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Fri, 15 Feb 2019 09:47:13 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-08.nos.boeing.com (144.115.66.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1591.10; Fri, 15 Feb 2019 06:47:12 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.1591.014; Fri, 15 Feb 2019 06:47:12 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, Richard Patterson <richard@helix.net.nz>
CC: 6man WG <ipv6@ietf.org>
Subject: RE: A common problem with SLAAC in "renumbering" scenarios
Thread-Topic: A common problem with SLAAC in "renumbering" scenarios
Thread-Index: AQHUxS7RlfA3ltjHmkmVDEct8Kbv/6Xg76vw
Date: Fri, 15 Feb 2019 14:47:12 +0000
Message-ID: <33beee588f994cd1adf3c19438e241b1@boeing.com>
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <2612280f-195a-ae7a-b3b1-9022d9282fa7@foobar.org> <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>
In-Reply-To: <65fbfb39-6009-ebc6-3dba-68aa3844153b@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 315CE6E6DC1739E97A4ED75339643B812B012D1138337F015B747BCAFCA658CC2000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vwMKSEIDYxkSJT1h07MECICbQkI>
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 14:47:19 -0000

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.

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

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