IETF Logo Mail Archive

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

Christian Huitema <huitema@huitema.net> Fri, 15 February 2019 10:30 UTC

Return-Path: <huitema@huitema.net>
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 601A3130F8E for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 02:30:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 7MzDNmHyXJpD for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 02:30:23 -0800 (PST)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 A79E5130E7B for <ipv6@ietf.org>; Fri, 15 Feb 2019 02:30:22 -0800 (PST)
Received: from xsmtp02.mail2web.com ([168.144.250.215]) by mx148.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1gual8-00136g-O0 for ipv6@ietf.org; Fri, 15 Feb 2019 11:30:19 +0100
Received: from [10.5.2.31] (helo=xmail09.myhosting.com) by xsmtp02.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1gual7-0000U1-0N for ipv6@ietf.org; Fri, 15 Feb 2019 05:30:17 -0500
Received: (qmail 9632 invoked from network); 15 Feb 2019 10:30:16 -0000
Received: from unknown (HELO [192.168.200.65]) (Authenticated-user:_huitema@huitema.net@[72.235.197.82]) (envelope-sender <huitema@huitema.net>) by xmail09.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ipv6@ietf.org>; 15 Feb 2019 10:30:16 -0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Christian Huitema <huitema@huitema.net>
X-Mailer: iPhone Mail (16D57)
In-Reply-To: <a036a6a4-26c7-66df-9094-7af67e424711@gmail.com>
Date: Fri, 15 Feb 2019 00:30:15 -1000
Cc: ipv6@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9BA9D825-2B75-47FA-999E-2712E151AD01@huitema.net>
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <c16e0e1f-1ed2-ad88-80f1-070bdd8bccca@go6.si> <1F2C2AEE-1C7D-481C-BBA7-7E507312C53A@employees.org> <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>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
X-Originating-IP: 168.144.250.215
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: ham
X-Spampanel-Outgoing-Evidence: Combined (0.02)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5gYMeifGv86M6Q6HlHfeDZN602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO0+c5LB5+AaOnyUGHzplYThs1ujulqUFmMITHM77eiVihNanwXZfPItb+dN3XDl3Pc7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pBuNKEwKrWwKExVdRofjrCBk5EpHPznVavQp4h 1cyzxbRC4xvs/7iGgDKhZ45D5vihvZAdx4vjUFLh0kXGIOazxFpgLxqZUFZdwbOLffZB9SIbeA2G NaAif0QyGEAJd8kel+zffa+S3paXsykGResyE7dAzbZabvf4+eAvvSn0D5YzxzA4C4+ILjmdkQoL 6F7cCSavQBrPoagEXfZ210Cx8bwqyT5p50x81ZKcmzCu2U1l0pLLr6Q2GfeLeJGF+80DrsibCyBr x+YtCB8oetqRijWKtLT9WR57oxUvRixjadcobnduoQv5Sp6y3SmK1n5SK/lIPtlUiBhTzlv5XU8Y E2iH1Wgh6RAenBR+licROGZo/5bs71XwBmcfZ8NfeEmrIg6PiKVNdhbpls6KZbV3SjmS8t8clATK 5KLleWqGwTJk354Leo8WHhg9Xcph2esmZk4AVtnYApSiFQp1w3dnUjMTi5Xt/sRoctxyu5EZ7wRl sQ6lNTZIrBtlLeoEHaVN0z6bhalFEM/pjPCQA+BAlo4nwaEJvK5+6Pe7PRp6P6hZYSpQQtCkh8qZ SV0LCxteCEYOeoT1sJ+vYeu/v4B5dg33G1sW1AJMTJY6+2ADoXQhu1/rdU1t/SWu+yxj6TsAzBpI RKEYj3P5LT70ZY4uKyB9lEOTMC1CDeyRjdgy1+29UshveVgoiypAicYsWUtdkye6uEH7Y2FUSOL4 rzI+g44cvttr0tmBjeIn/Z/emtVQvYq5Gwe6V5p1dZXUJLl9UHdlPJIlgYKUOVb4Kg3Ivfi62j4u w/K+m8SGihSRsuS3byv3CjhKpQiDxiH2EAzS5xSvMev/h5X3p2+rThvFRg==
X-Report-Abuse-To: spam@quarantine9.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Wiqu3EL4slKDzIdLIlSgzJpcois>
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:30:24 -0000

 

> On Feb 14, 2019, at 11:57 PM, Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
> 
> (I can assure you that changing IP addresses all the time is a nightmare in implementations :-)

The alternative is of course some kind of onion routing for the masses. Or generalized VPN. I wonder about the trade off, in terms of both overhead and management.

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

-- Christian Huitema

v2.23.0 | Report a Bug | By Email