IETF Logo Mail Archive

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

Markku Savela <msa@moth.iki.fi> Fri, 15 February 2019 10:55 UTC

Return-Path: <msa@moth.iki.fi>
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 87DC4130FA0 for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 02:55:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 NcyLCEZ1r1Pt for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 02:55:29 -0800 (PST)
Received: from moth.iki.fi (moth.iki.fi [IPv6:2a00:1c30:3:2::111:74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61CB4130F82 for <ipv6@ietf.org>; Fri, 15 Feb 2019 02:55:29 -0800 (PST)
Received: from [130.188.13.218] (218.13.vtt.fi [130.188.13.218]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: msa) by moth.iki.fi (Postfix) with ESMTPSA id 2460B2A0053 for <ipv6@ietf.org>; Fri, 15 Feb 2019 12:52:35 +0200 (EET)
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
To: ipv6@ietf.org
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <e56a6e5b-648d-200e-c35d-97f15a31fb2a@asgard.org> <CAO42Z2zh7fKAgQJq9aLCTiFoSSsTeGM=pK3gXitg+gcxH=9fhQ@mail.gmail.com> <d38857c2-6e92-91d6-bb5d-d3eeeb61276a@gmail.com> <CAO42Z2yb47OyXk__Sz-kO00pfcBJgLAhff5DF=mpAddR0iCnAA@mail.gmail.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> <463f 15cf-2754-e2e8-609d-dc0f33448c6c@go6.si> <444A9043-0EDF-4F21-9DCE-BF019B81D078@huitema.net> <a03 6a6a4-26c7-66df-9094-7af67e424711@gmail.com> <9BA9D825-2B75-47FA-999E-2712E151AD01@huitema.net>
From: Markku Savela <msa@moth.iki.fi>
Message-ID: <1b1a78b8-ccba-2085-0fb0-0c957e782146@moth.iki.fi>
Date: Fri, 15 Feb 2019 12:55:16 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <9BA9D825-2B75-47FA-999E-2712E151AD01@huitema.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/3EWngO_DbtlNw0NILfEXepJNjYw>
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 10:55:32 -0000

On 15/02/2019 12:30, Christian Huitema wrote:

> Right now we have the bizarre property of having better privacy in a coffee shop than at home. That doesn't seem right.

On the other hand, I prefer to have have reasonably stable global 
routable IP4/6 addresses at home. Makes peer-to-peer applications easier 
to setup, if your address does not change every minute or hour, or whatever.

However, I'm also very much for privacy. If there is possibility to 
change address, the change trigger control should be on the user, not on 
operator...

v2.23.0 | Report a Bug | By Email