Re: Disabling temporary addresses by default?

Jared Mauch <jared@puck.nether.net> Sun, 02 February 2020 08:04 UTC

Return-Path: <jared@puck.nether.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 78B60120048 for <ipv6@ietfa.amsl.com>; Sun, 2 Feb 2020 00:04:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 RiUtBKsqWEoF for <ipv6@ietfa.amsl.com>; Sun, 2 Feb 2020 00:04:56 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56ABA120044 for <ipv6@ietf.org>; Sun, 2 Feb 2020 00:04:56 -0800 (PST)
Received: from [10.0.0.155] (c-68-32-79-179.hsd1.mi.comcast.net [68.32.79.179]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 1948654017B; Sun, 2 Feb 2020 03:04:52 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: Disabling temporary addresses by default?
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CABNhwV2=TPU+CQ1zBu58DmRD7i3=tBsdZvuOxuaS_jQLZ-ebBw@mail.gmail.com>
Date: Sun, 02 Feb 2020 03:04:50 -0500
Cc: Lorenzo Colitti <lorenzo@google.com>, Christian Huitema <huitema@huitema.net>, 6man WG <ipv6@ietf.org>, Fernando Gont <fgont@si6networks.com>
Message-Id: <2E8EF340-72CD-46BC-A634-22571BC5E705@puck.nether.net>
References: <CABNhwV2=TPU+CQ1zBu58DmRD7i3=tBsdZvuOxuaS_jQLZ-ebBw@mail.gmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
X-Mailer: iPhone Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6Da5v42WqnPgQ_OUUSABhHA4yCs>
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: Sun, 02 Feb 2020 08:04:57 -0000

They are also useful and needed when debugging hashing or 802.3ad related issues. To debug the flow hash you often need stable addresses which are not easily changed or provided by the average user who just expects the technology to work. 

Sent from my iCar

> On Feb 1, 2020, at 4:24 PM, Gyan Mishra <hayabusagsm@gmail.com> wrote:
> 
> Stable random IPv6 address works best to meet the objective of an enterprise.