Re: Disabling temporary addresses by default?

Christian Huitema <huitema@huitema.net> Tue, 28 January 2020 16:27 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 1E09E120251 for <ipv6@ietfa.amsl.com>; Tue, 28 Jan 2020 08:27:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 j6xkUTQtqja2 for <ipv6@ietfa.amsl.com>; Tue, 28 Jan 2020 08:27:37 -0800 (PST)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.30]) (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 CCBF91209D5 for <ipv6@ietf.org>; Tue, 28 Jan 2020 08:27:37 -0800 (PST)
Received: from xse244.mail2web.com ([66.113.196.244] helo=xse.mail2web.com) by mx37.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1iwTiB-0007dH-Qs for ipv6@ietf.org; Tue, 28 Jan 2020 17:27:36 +0100
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 486X8Q2ggvz24Lm for <ipv6@ietf.org>; Tue, 28 Jan 2020 08:27:34 -0800 (PST)
Received: from [10.5.2.16] (helo=xmail06.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1iwTiA-0001dC-8E for ipv6@ietf.org; Tue, 28 Jan 2020 08:27:34 -0800
Received: (qmail 10429 invoked from network); 28 Jan 2020 16:27:33 -0000
Received: from unknown (HELO [192.168.1.104]) (Authenticated-user:_huitema@huitema.net@[172.58.46.251]) (envelope-sender <huitema@huitema.net>) by xmail06.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ipv6@ietf.org>; 28 Jan 2020 16:27:33 -0000
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
From: Christian Huitema <huitema@huitema.net>
Mime-Version: 1.0 (1.0)
Subject: Re: Disabling temporary addresses by default?
Date: Tue, 28 Jan 2020 08:27:32 -0800
Message-Id: <751D59E0-F60B-4FE1-840F-3FEAB82F618F@huitema.net>
References: <CAKD1Yr11_SSUkCBuQ3-h+eRg0LPZQdhe+h7f0YZy9TiyRWj6mw@mail.gmail.com>
Cc: Ole Troan <otroan@employees.org>, 6man WG <ipv6@ietf.org>
In-Reply-To: <CAKD1Yr11_SSUkCBuQ3-h+eRg0LPZQdhe+h7f0YZy9TiyRWj6mw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (17C54)
X-Originating-IP: 66.113.196.244
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.244/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.244/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: ham
X-Spampanel-Outgoing-Evidence: Combined (0.06)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0YfsolMNZcEgL2mqy3zzv3mpSDasLI4SayDByyq9LIhVFJxv2/0hhDPH AJ7NggnyhkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDMPcu82DWGPPvLRplVChEZLgN zB/4Jkrw1eDLcif59ftemBFg9+DdqPy+AmIaWR/xU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+7KJix/R2qbtdH2ZflMjNgfMm/JD3cPBOX47Hg3FEpDo46jSvfpO+1kZkomjtjB6X7/nuj3 koRhn2BlE7dXoT0pGVmhMAaQ/AfCRwRe7yHm5oY+NYmsSGn+svMubxnbgm1cr18FZBEPC2/c16Xd 7sC9aC4xteE1WLqGS9YoqrsZ2DyteN0e+ECCv9/f+GPymkgDVo7QBKA4MctKq4ifYPcXFRL2K3LA EfDXVOdt7wDbusYnuEVWSxKMHbU0zkNM3EElFDaoLuOPKc8gc82pKfhB7T02ZXdoQxMs//iOE4Fl hiCv9TR+UxzLZWL8hwGBjhoI3W+YcuHfP5PkZb5A+wE5qGdpH54Oa3V8I76VOEvlwB+XPdEXquZ7 t0MUOMrNUB3Qwv97DaU24YqVtkGlysE2ew4Tm6caFX9Dc2quOQjMQveybnFw0rwBWUthlyazKK1U PVcmx1QL+XiKf76y/BgKwpwsC8Fmnlfgf4Cu051IgPKY2AXNZGS5G93aGyH8MqMlOQRMVMd0HCeT skOZ5TL8s3mBJMNu8dMsv3x/Dm+M8jXg724gFzhHYUe+7aKm0vUpO3icu5Unr9tFMTAR0mniTi+J 2sBvM/O0p+zizleC4va6FPcpDHjXMKZJK8+chibxsi78+E01STiOlNq8tEEK7cTs80/2FnZg/IMs IAdedSzLrjsyfTPCYbMCLdmf5h2vfxw3Qvb2Glio5Cia/9Kfg4kJ0WtAYbrpe3OOAtQNb87OBHCz Hbokiue7PjVB1S6AQRz4SqXhOP5fdiQt7lu5Jm5nk4BSgYHOJJgUtm67rBRli6kULE5BQDZnPvvF VsQ=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0AbCKe-lBp4B3-rbSoYIuIbUIys>
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: Tue, 28 Jan 2020 16:27:39 -0000

On Jan 28, 2020, at 6:59 AM, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org> wrote:
> 
> Instead of disabling, why not change the default of the number of addresses maintained? For example, instead of maintaining 1 permanent + 1 valid + 7 deprecated, why not just default to maintaining 1 permanent + 1 valid + 1 deprecated. That means that applications would have to re-establish their connections once a day instead of once every 7 days. But if they use privacy addresses, they already need to re-establish connections after 7 days. And they can always use not to use privacy addresses via the appropriate socket option.

That seems plausible, but how about going one step further and for clients just have one temporary and one deprecated address, without any stable address? If the client is not running any server, that makes address management much simpler.

-- Christian Huitema