IETF Logo Mail Archive

Re: Disabling temporary addresses by default?

Jared Mauch <jared@puck.nether.net> Sun, 02 February 2020 16:33 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 1293C12008D for <ipv6@ietfa.amsl.com>; Sun, 2 Feb 2020 08:33:13 -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 goEmXT_PMtV1 for <ipv6@ietfa.amsl.com>; Sun, 2 Feb 2020 08:33:11 -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 AB51B12003F for <ipv6@ietf.org>; Sun, 2 Feb 2020 08:33:11 -0800 (PST)
Received: from [100.71.204.31] (ip65-46-187-134.z187-46-65.customer.algx.net [65.46.187.134]) (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 5210F5401DB; Sun, 2 Feb 2020 11:33:10 -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: <CABNhwV1vLM3LJnb=HSBtwoBz+4BtL9aYKmWpUqE4tGumKGhA3w@mail.gmail.com>
Date: Sun, 02 Feb 2020 11:33:09 -0500
Cc: Mark Smith <markzzzsmith@gmail.com>, 6man WG <ipv6@ietf.org>, Christian Huitema <huitema@huitema.net>, Fernando Gont <fgont@si6networks.com>
Message-Id: <4FB732F8-069B-4B14-A310-133832B5F9BE@puck.nether.net>
References: <CABNhwV1vLM3LJnb=HSBtwoBz+4BtL9aYKmWpUqE4tGumKGhA3w@mail.gmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
X-Mailer: iPhone Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Rly4bZqcRvwKn_XmjnDSheXN298>
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 16:33:13 -0000

I've experienced it on most, cisco, juniper and the BCM based silicon as well. 

Finding which port or LC is having issues without just playing a search method of taking things out of service is always painful. 

Hopefully there is a syslog or hardware counter that tells us what's happening but that's not always the case. 

At $dayjob we have constant measurements to detect some of this but it doesn't make it much easier for the humans. 

Sent from my iCar

> On Feb 2, 2020, at 11:12 AM, Gyan Mishra <hayabusagsm@gmail.com> wrote:
> 
> Which vendor are you referring to regarding software bug or programming issue?

v2.23.0 | Report a Bug | By Email