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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 21 February 2019 10:07 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 39612129619 for <ipv6@ietfa.amsl.com>; Thu, 21 Feb 2019 02:07:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 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] 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 4lht-Qdn8XQ1 for <ipv6@ietfa.amsl.com>; Thu, 21 Feb 2019 02:07:09 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 061861276D0 for <ipv6@ietf.org>; Thu, 21 Feb 2019 02:07:08 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x1LA773q038410 for <ipv6@ietf.org>; Thu, 21 Feb 2019 11:07:07 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id F0A43203DA7 for <ipv6@ietf.org>; Thu, 21 Feb 2019 11:07:06 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E77E6203DD0 for <ipv6@ietf.org>; Thu, 21 Feb 2019 11:07:06 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x1LA76eW024030 for <ipv6@ietf.org>; Thu, 21 Feb 2019 11:07:06 +0100
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
To: ipv6@ietf.org
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <e3e0bf2273e04f15b792665d0f66dfe5@boeing.com> <4c5fab33-2bff-e5b5-fc1d-8f60a01a146d@go6.si> <b4525832-9151-20bf-7136-31d87ba6c88d@huitema.net> <463f15cf-2754-e2e8-609d-dc0f33448c6c@go6.si> <ff649810-7242-7bc2-d36f-3f998f7bdd71@asgard.org> <9CDF41CA-83B4-4FC4-B995-EF79727C5458@steffann.nl> <CAO42Z2wA+vLmU7+sU6xLK7TO6pWfNQA5shs9zp=PqANCihLmBQ@mail.gmail.com> <BAB3061A-1808-4C0E-AA1B-2D7DD5BA63FC@employees.org> <bbd8b761-403a-5b3f-3f04-dc3bfdea116e@foobar.org> <6F3036C6-50A1-43C6-B554-31293B69E59D@employees.org> <433607c1-dbc6-a42e-cb17-dc209e33bdaa@si6networks.com> <12EA4FAE-BE3D-4CFE-9837-DF052F79A998@employees.org> <5bc3eaf0-3ef0-d954-b228-00a7faac7f4c@si6networks.com> <CAO42Z2wa9gWoB_bWrYt79urHF8ihmMAbjDSZCBoZa8dn8SCNFw@mail.gmail.com> <cfe8d901-b1db-78fc-2a80-ae85ccf0c0d3@si6networks.com> <CAO42Z2yAXnFRViCZ7Wf27twUAanuSLA30jcHZZPa30HJsg7adQ@mail.gmail.com> <a3854d79-f661-4363-c910-31e6a08179a1@si6networks.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <897ff121-ff3d-56c7-25bb-2d46043ade05@gmail.com>
Date: Thu, 21 Feb 2019 11:07:06 +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: <a3854d79-f661-4363-c910-31e6a08179a1@si6networks.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/bru9Eve2dfpdNVHioI5G9AlEm0A>
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, 21 Feb 2019 10:07:11 -0000


Le 20/02/2019 à 10:59, Fernando Gont a écrit :
> On 20/2/19 06:32, Mark Smith wrote:
[...]
>> What I am saying is that they are and have been foundation design and
>> implementation assumptions that have been in place for multiple
>> decades. I think the longer a foundation assumption has been in place,
>> the more care and consideration you need to give to changing it,
>> because there can be unexpected impacts. Given those impacts, it may
>> be better to preserve them and design around them, compared to trying
>> to change them ("boiling the ocean"). The Mobile IP people, for
>> example, took this approach.
> 
> Based on the deployment level of Mobile IP, I'm not sure we want to
> follow that road ;-)

But do not take an even worse road, even less implementations.

(Mobile IP implementations are available widely on Cisco and other 
platforms; Mobile IPv4, Mobile IPv6 and DS-MIP are distinct; numerous 
trials featured it; Mobile IP went even into Space on a shuttle)

The SLAAC problem with non-expiring prefixes and addresses that you talk 
about in your draft is valid, and solving it could be valuable in some 
context.

Alex

[...]