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

Ted Lemon <mellon@fugue.com> Thu, 21 March 2024 05:47 UTC

Return-Path: <mellon@fugue.com>
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 7ADE2C1519A6 for <ipv6@ietfa.amsl.com>; Wed, 20 Mar 2024 22:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20230601.gappssmtp.com
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 yBoJDvGqMCrf for <ipv6@ietfa.amsl.com>; Wed, 20 Mar 2024 22:47:30 -0700 (PDT)
Received: from mail-qv1-xf31.google.com (mail-qv1-xf31.google.com [IPv6:2607:f8b0:4864:20::f31]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 15E89C15198F for <ipv6@ietf.org>; Wed, 20 Mar 2024 22:47:17 -0700 (PDT)
Received: by mail-qv1-xf31.google.com with SMTP id 6a1803df08f44-6918781a913so5110566d6.3 for <ipv6@ietf.org>; Wed, 20 Mar 2024 22:47:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20230601.gappssmtp.com; s=20230601; t=1711000036; x=1711604836; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=cJEdd+/LCH2zqNKgE7nJJletkoF8yHM1vi/U+1hPc8c=; b=wP59pSharvgEB6q0LRJw1GGqK0juBfH3e6cCz2m3T4pNKPUnhtVV+G0FAe0+yD26xv /X9jhyzHgGac7EkV3wjS0YaJ4/clVnF8VPP1DHCMH8PyR1DBtBlrQcnQFIpUIplrin7P VJpqShy1PBfNYujnvuo1brX2jqgVT99LlQcqGyYKQk8gazGTO0llB0YtmjIAwnCf0cIY 5jlZ+iwcNqKAs63t8vLLD7++wJ8J1sADyLfUcGPqznzXLDbGleAbzp3PZLWMrqvbWSD3 cvEsxM4ngBEg8LT8up9SZDtl0kIz2k3g0fCHUp+zlsNx/m66yGm4baN6BtK33jN5S9YL Q8vA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711000036; x=1711604836; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=cJEdd+/LCH2zqNKgE7nJJletkoF8yHM1vi/U+1hPc8c=; b=dO31bZgWi6vpAtBRQT4OigmIwJiZFNC6ituMtZj2zI4kQ4pSFXg/nmiPSllaT6/n7V AU7nv4pnnsnwotO7aTXRY3/YsdW6DyQZY/K2BFG6DCF+AW8GXjqav2e978RUNbMeVcKP HODU/B193M+OcG9eL/3cxd53QJ+LcVmQzCsjVFte89XZT4fBPzXg+t+SLldS+kW3uZ27 W1Nc4yRuHvK+NvqWrJwW6/AoAXHnDFFCUSERkCL64XQHGXx4DFp7VfaMAVsvohfOHbo1 YbvxEGDR6gl+oIzGMJeM/cqSPBpgsktCqn/aSATOC/3kignzM43l4xPq/vuhqeU+PQ81 uBsA==
X-Gm-Message-State: AOJu0YzTdUoFXsKexQuRjO8e8toTDw+sLgFUAi5yKib7WiyawzlEVare SRxFgU/Pve1SbZCxoAKyjZ0Ls7sciK3MeTHqbXKAyX3la382FHzopCnaZGec+Q+uVICTopD+cTJ 0b0cGNFwIJVXt9WysRoq2WclxMkbrrLxIHf1wR2M+IQhHNXqluco=
X-Google-Smtp-Source: AGHT+IHvVxoNoPlpS04MyqOPBiiVOSCusFesePajlsKwcAs5kpZA51Xja5lYr9AnMUUaKi2Y9mNKU49eZkPXATctsWc=
X-Received: by 2002:a05:6214:2401:b0:690:c13f:ebc5 with SMTP id fv1-20020a056214240100b00690c13febc5mr997483qvb.63.1711000035741; Wed, 20 Mar 2024 22:47:15 -0700 (PDT)
MIME-Version: 1.0
References: <186314.1710989921@dyas> <CAPt1N1nJR31StrZaPGqbi7=P7vb2xyJF39p8YVdsgaExQVvMdQ@mail.gmail.com> <195905.1710999785@dyas>
In-Reply-To: <195905.1710999785@dyas>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 21 Mar 2024 15:47:04 +1000
Message-ID: <CAPt1N1kV12OG76CUNXm7AOrhdu+310E9BbaMJgKbw6Mw4=Ziew@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000576dac0614253d72"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/jEUbNMCSLecqCw9g57YgYYdaFvA>
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:47:31 -0000

Hm. The way we generally handle this at the host level is to notice icmp
messages. On Apple devices if you use network framework it tracks this
stuff for you, at least for QUIC and TCP.

Unfortunately we don’t standardize APIs in the IETF these days…. :)

Op do 21 mrt 2024 om 15:43 schreef Michael Richardson <mcr+ietf@sandelman.ca
>

>
> 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*
>
>
>
>