Re: [IPv6] communicating multiple link (status) to hosts

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 21 March 2024 05:43 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 F3AEAC14F70F for <ipv6@ietfa.amsl.com>; Wed, 20 Mar 2024 22:43:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZB8SKleVJ3l for <ipv6@ietfa.amsl.com>; Wed, 20 Mar 2024 22:43:10 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB2EFC14F5F3 for <ipv6@ietf.org>; Wed, 20 Mar 2024 22:43:10 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [IPv6:2001:67c:370:128:fc45:e748:5ff1:1348]) by relay.sandelman.ca (Postfix) with ESMTPS id 7EC091F4A8; Thu, 21 Mar 2024 05:43:08 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="etPjfaOA"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 4D32BA0C69; Thu, 21 Mar 2024 15:43:05 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1710999785; bh=dyyfd93zVdNQCoczk8rUEaDk2MhXJ/D+CTGex5+qTIk=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=etPjfaOAMDXKy59dMTLKBFVmO84DvTteCGymUsfFYoyyiIJSQZjnaHh8vvcUGW+g5 zZ1imZj3A+dezJZG74bu8kCaw1GZMjZGWCdgiMfVVpuzfuXnudw+gD8PX4KcqrDEiV 8Z+XklVWdnvrSZuz0Auu+WbOONTsV+HN5IfXZPl9viiZ2EQ9yLekCD7I9jAQkcGfgX h8p+/cFf+hjP/Beuuogu9lAJVqf083KklfrU5kEN7FFDbVPXDzS68yvthgCuwfytkO HalCdNUw1N44kkfMmLuqprhqlEFhRX8V+u0sYtBlyzMxlxKo7wcv66or0S2rbVRdam RyKlrTARVYdNQ==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 4A02DA053B; Thu, 21 Mar 2024 15:43:05 +1000 (AEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>
cc: 6man WG <ipv6@ietf.org>
In-reply-to: <CAPt1N1nJR31StrZaPGqbi7=P7vb2xyJF39p8YVdsgaExQVvMdQ@mail.gmail.com>
References: <186314.1710989921@dyas> <CAPt1N1nJR31StrZaPGqbi7=P7vb2xyJF39p8YVdsgaExQVvMdQ@mail.gmail.com>
Comments: In-reply-to Ted Lemon <mellon@fugue.com> message dated "Thu, 21 Mar 2024 13:42:14 +1000."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 21 Mar 2024 15:43:05 +1000
Message-ID: <195905.1710999785@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/1laEnQKlx3ei0U-sBzDgu_gKErg>
Subject: Re: [IPv6] communicating multiple link (status) to hosts
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 21 Mar 2024 05:43:15 -0000

Ted Lemon <mellon@fugue.com> wrote:
    > The whole idea of prefix lifetimes is to avoid flash renumbering. It
    > sounds like you're proposing to standardize flash renumbering.

I'm not saying that some egress died because of renumbering.
It could be a backhoe event.
It could be some router in another building is down because power is out.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*