Re: draft-ietf-6man-slaac-renum: Heuristics to deprecate stale information

Ted Lemon <mellon@fugue.com> Fri, 12 August 2022 22:24 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 818EAC157B52 for <ipv6@ietfa.amsl.com>; Fri, 12 Aug 2022 15:24:00 -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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20210112.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 0m4I1qpzAv0f for <ipv6@ietfa.amsl.com>; Fri, 12 Aug 2022 15:23:55 -0700 (PDT)
Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (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 EDDA9C157B4D for <ipv6@ietf.org>; Fri, 12 Aug 2022 15:23:55 -0700 (PDT)
Received: by mail-ot1-x32c.google.com with SMTP id l5-20020a05683004a500b0063707ff8244so1430502otd.12 for <ipv6@ietf.org>; Fri, 12 Aug 2022 15:23:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=UdKDcLJyXM4n/09xlbSHJh4tyhkHA92/bgfn4ZyJfLI=; b=pIQKWEAJz1rRtBOhcW/zfjqjseMLB6Up6Dz5ADR4JQB61tCOwg2+U97Irxg+AYv40h IGp87onRJEz6Zvo58HHtNC7bdzmvw04aUYC/JkMOg6f+duVRTBw9i+p2GP+fspaB2LJ4 HiuQW9b/u4obq6AuwDjlzihri8AtgFFgzJMkEmxjDz2+8sEXn+Gn07IgHsjyKAKEM/L4 DJGO52JPF7LUqB2N8jWgshHN4O2DQ1XN1kj7+0+MS+L2y9nUyaSUOyyZzuH0ZnSXAWBV STW98YXFfiheNtzkSiRI50C1bwyZlSfLW+r7KhRlpnZ1mYhhFgj8CYX/+/QThzqXeREA LbGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=UdKDcLJyXM4n/09xlbSHJh4tyhkHA92/bgfn4ZyJfLI=; b=X7QZB1giAt1BLvCwtZiVLJ7pgIvRPpf5rcGrcjI15F9tFjk8BI7BLFpnIg0lB3t/tX 0VuUyX7CJZ3t1898wAkmK0EUt2E+sjs2Vsem2vtLRgR5QvfHefTVeNjtr5COMcbeV4wZ znPtqTP3pcpMVMtgPeauC/qfLJkyJlK1Ft5wFe42xVkFsSw7ELBsXBVHCQ02KSf6gs42 TfVz5EA+bAxrQNrVNEJztcZhOFKaWmES+xk6H/Y/s4eLVzGshv/cwdjzCri2KVSlAqUz bX5zK1U+30ZfIUfqgJGPextGLzw3zTCCa/zBWYDPbqNX9Hn240ZVKrtb2ypbyK2akfw0 PsHg==
X-Gm-Message-State: ACgBeo1029uUpDakTBBW8Bh5WN1tJY1f0yN6w+MsOLcR6hWsTtM+HZmx AukF3LY9j/mY57z6bXOMtfxGNRM3fe/wVdMTJlFNMxJbSLA=
X-Google-Smtp-Source: AA6agR6zbI3/nMdYDIlF+oB7/qaEyCIloxJ5+pg/N66WwFtDQcyUwsTGF8p1Z+eADeb8pQ4qWj4xoxGmK9t29skJPTQ=
X-Received: by 2002:a9d:6b13:0:b0:637:749:a0b7 with SMTP id g19-20020a9d6b13000000b006370749a0b7mr2229733otp.163.1660343034672; Fri, 12 Aug 2022 15:23:54 -0700 (PDT)
MIME-Version: 1.0
References: <4d3c116d0461477e9afa4b56c43688fe@huawei.com> <01E08955-E0BF-44B8-839B-4148BD76A819@fugue.com> <ec05eb36-5fe6-8abc-feeb-046f0bcb2bec@si6networks.com>
In-Reply-To: <ec05eb36-5fe6-8abc-feeb-046f0bcb2bec@si6networks.com>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 12 Aug 2022 18:23:44 -0400
Message-ID: <CAPt1N1nhwnT-7X_0r-Kk=7q61UymM9GMXaSQxN0oBB=F+W88_w@mail.gmail.com>
Subject: Re: draft-ietf-6man-slaac-renum: Heuristics to deprecate stale information
To: Fernando Gont <fgont@si6networks.com>
Cc: Vasilenko Eduard <vasilenko.eduard=40huawei.com@dmarc.ietf.org>, ipv6@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c98af505e612bc0e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gh1xGPGDgOBrj0-_9t-sMF0CqU8>
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: Fri, 12 Aug 2022 22:24:00 -0000

On Fri, Aug 12, 2022 at 17:33 Fernando Gont <fgont@si6networks.com> wrote:

> On 12/8/22 13:52, Ted Lemon wrote:
> > FWIW, I would like to see the points made in item 1 addressed in
> > slaac-renum.
>
> Regarding #1, nodes that change their address or that "disappear", I'd
> say that's not really renumbering.


The point is that if the router goes away, we would like to detect that
quickly. A good way to detect it quickly is to notice signals that suggest
the link has changed and probe for known routers. If they don’t answer,
deprecate their information. Does this not make sense?

That said, we could clarify in a separate section noting that, e.g.:
>
>    When the Router Lifetime of a router expires, Neighbor Discovery
>    information advertised by such router should be disassociated with
>    said router -- hence the faith of such information will depend on
>    whether such information is advertised by other routers.
>
> Thoughts?


Sure, but this is not the point Eduard was making.