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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 07 February 2019 19:46 UTC

Return-Path: <brian.e.carpenter@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 54E3512D4E8 for <ipv6@ietfa.amsl.com>; Thu, 7 Feb 2019 11:46:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ajugjG-tpaJJ for <ipv6@ietfa.amsl.com>; Thu, 7 Feb 2019 11:46:40 -0800 (PST)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FE931293B1 for <ipv6@ietf.org>; Thu, 7 Feb 2019 11:46:40 -0800 (PST)
Received: by mail-pl1-x633.google.com with SMTP id u18so423311plq.7 for <ipv6@ietf.org>; Thu, 07 Feb 2019 11:46:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=9/NcgG3tpuPF1ifOnQZrjulKaGdTVvElhewJ0ICrILg=; b=SgKh2U1Tv1epS/vJ7qlM+QYE9z5LX3lV49acICnB1Yhh73YdPsdGZF28JvZoNZNn+0 i2M2zDmVriqZRpLaqDLQCO4CtWn1NJqsVBK62xc4Iir0G0ILEsxyd9zQRje4UxZjNzR8 4I0biJanen8JRWz87HB1WYvDq+uHaBS6Znv+sThInCseCapfzDA8OYv2tMW4+SW/wZSW ZFIrJ2oItBTRotCNrIEdMAdtd8zhCaL6rrde6O6Hy683o0DiETyegh6sfyH/5BMAIrz2 7QyiM83/yxQl/TCSYOrtCMKOUFxHtIRl4SDIfnjfIzmi5yJoYziiv/pfMF9oXvlDIzv+ T5yw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9/NcgG3tpuPF1ifOnQZrjulKaGdTVvElhewJ0ICrILg=; b=szOTvN2ssryUiFiivCzjMI+4v04ujvd5TN1Spc2/faV1B/gbTjj+qosVMhooJioQeB 96l49bTKiWbr2P7NRa1BBx4tu7zQDpH51spktPJbYf4rWKRcuS5FMSib8AoVkj5RZ2Sn NP50mCA4wBmMzVZxfAzXz4D/q21AdaoEzzTAhxAS6JtcKoDBabvRMAh1eTzPOiblGYrt aD5hEvAvbBHqloLiLX4fMz9+o0keIPsrjOQtSPDG35yUKOmH6CWaqE+4cE5YcQnG2drQ MjpLDXFJacb2xGeLeQcpD/JKWsa39gA8+BgfwJa7fw11gjev1chUYhbcIT2zIyG6cNOm 7dSw==
X-Gm-Message-State: AHQUAuZVRdnG4KnfQrg2HzxboMnCBlrKREMzabP7bRvvHgykGLejBu8O hwlvrZ7MSOUjjXHG77xHWXfieIaS
X-Google-Smtp-Source: AHgI3IbADg16reGqPE+stO0orWWFoMyZ6WOxqlITR5xzdUmHnHq1ZmiPRJ/Q0WEKYBOXbA5fVUhPBA==
X-Received: by 2002:a17:902:8504:: with SMTP id bj4mr9887666plb.200.1549568799010; Thu, 07 Feb 2019 11:46:39 -0800 (PST)
Received: from [192.168.178.30] ([118.148.79.176]) by smtp.gmail.com with ESMTPSA id u66sm80972pfi.115.2019.02.07.11.46.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Feb 2019 11:46:37 -0800 (PST)
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
To: Fernando Gont <fgont@si6networks.com>, Nick Hilliard <nick@foobar.org>, Christian Huitema <huitema@huitema.net>
Cc: ipv6@ietf.org
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <69609C58-7205-4519-B17A-4FBC8AE2EA16@employees.org> <d40b41c3-ff1b-cab4-a8de-16692a78e8fd@go6.si> <D1E45CAD-08D0-43D4-90F7-C4DD44CB32C0@employees.org> <alpine.DEB.2.20.1902041330531.23912@uplift.swm.pp.se> <77ecf321-b46e-4f25-7f68-05b15714a99e@si6networks.com> <CAHL_VyDdHuEAc9UdeiRp9f+c0tdzyoLwPY1rJbZmbWAuq96Uuw@mail.gmail.com> <alpine.DEB.2.20.1902051127510.23912@uplift.swm.pp.se> <m1gqyJC-0000FkC@stereo.hq.phicoh.net> <CAO42Z2wKh-vXmv=dNmr6oEmGnw09ajrr2geYJ=H1DbSYSm=VuQ@mail.gmail.com> <m1gqzYT-0000F5C@stereo.hq.phicoh.net> <e8eabf0f-191a-a293-8051-35268a62a2bd@go6.si> <37ae87fb-93f5-4ec4-6e55-e35ce308f91c@asgard.org> <2aa19534-4856-f01d-8184-6c7ed125ca1b@go6.si> <9cdf8405-e777-6769-4d4f-f123c13a9456@asgard.org> <f4eaaf13-aff3-439f-4426-d32d3722abfe@huitema.net> <d714d577-74f8-6f1a-76a7-94811b615078@foobar.org> <81ab4307-efb8-c04e-7acb-a6f7f0ec839f@gmail.com> <0c79a219-79d4-f7c8-9143-fbdf9ae1b2b1@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <b42dbd6e-692c-ea6a-706c-7177b7741d00@gmail.com>
Date: Fri, 08 Feb 2019 08:46:31 +1300
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: <0c79a219-79d4-f7c8-9143-fbdf9ae1b2b1@si6networks.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6BgnaNbAqXUPViZb2Zgl4uDDDOI>
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: Thu, 07 Feb 2019 19:46:42 -0000

On 2019-02-07 15:46, Fernando Gont wrote:
> On 6/2/19 16:31, Brian E Carpenter wrote:
> [....]
>>> 3) pushing the smarts down to the host layer and detecting / monitoring 
>>> whether any particular prefix is still valid
>>
>> https://tools.ietf.org/html/rfc6059 ?
> 
> Not really. Actually, the tricky part in this case is that the network
> -- from the host pov -- is the same.

The definition of "the same" is: "The combination of the link-layer address
and the link-local IPv6 address of a router is unique" according to RFC6059.

Maybe a CE router should change its own link-local address when it gets
a new prefix? That would automatically break any attempt to use obsolete
RA information.

    Brian
 
> 
>> In any case, because neither of the preceding options is guaranteed,
>> I think there is no choice: hosts must be able to recover from
>> dead addresses.
> 
> Agreed.
> 
> 
>