[IPv6]Re: How are AdvReachableTime and AdvCurHopLimit in RFC4861 used?

Ted Lemon <mellon@fugue.com> Tue, 28 May 2024 12:49 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 6594FC14F747 for <ipv6@ietfa.amsl.com>; Tue, 28 May 2024 05:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 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, 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=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 c4o4y1UsKuRf for <ipv6@ietfa.amsl.com>; Tue, 28 May 2024 05:49:26 -0700 (PDT)
Received: from mail-qv1-xf35.google.com (mail-qv1-xf35.google.com [IPv6:2607:f8b0:4864:20::f35]) (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 33D9BC14F73F for <6man@ietf.org>; Tue, 28 May 2024 05:49:25 -0700 (PDT)
Received: by mail-qv1-xf35.google.com with SMTP id 6a1803df08f44-6ab9e011f62so35366486d6.0 for <6man@ietf.org>; Tue, 28 May 2024 05:49:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20230601.gappssmtp.com; s=20230601; t=1716900565; x=1717505365; 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=i0FEQcsuJNb9k/9QgWRByYam+NJIl52WApyxfsl2Kxo=; b=UxyC6sao7r9QzEkt1zNDDjX3zDc0Nlm+JhpvdwAXWTJNeJKZAd4B0P3TNCj0sq9SrZ 0YQlXAI8aF+ZJWk4UXp4hWGDo8ZAQPXHcPmHGi88x+KnMa2Fz+YpPG+ZqLD07Rk/4eOg uXRFT1wmv54HfwPuZDQDirEMgJVuFDVavVlVur3I2HXFWrqWUx145rAPP9tnc1tnouyG XDyc6fH+G/7Yxajz3uKrm/5LHrLD2xIbJSoxSm61097ogexxbRmb/2Ck2OmQwnbDZ6LY mkNyzI2jrVMaI/TuwTo8e5LE196xmz2/VzuqusBy0l2UtPUpg4r7fWY/laPhvK3WU2L/ V2Rw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716900565; x=1717505365; 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=i0FEQcsuJNb9k/9QgWRByYam+NJIl52WApyxfsl2Kxo=; b=lkhfoGG8gD3hc6CZq0TFb8b34TijLojskwMDmOVjI95e0+JPAGleAXiMY8IBE9fJAr MECeBZnqEIVWTiVA9wjaoFF+3IPxXdSCN5nyJb/XSPZMLjk4TcMlhdsVXBYSN//9IUxX iFbZY4TNbKzEm8IYz6uUTXxGEzvPL2FPnFq32c5ygFFCilkOzEkJ+MHa/rkJjmiaxN2g QQ8akrBCpYK+zcrS5A3T10u3bDvkBQII0Dk3eXodBdd5G8fdWZVqyPqPr3vKT+TGmbki Mz41q1JoptvIRH/G4qNEbdumjyFjPUZ99FSWeY71bx7lbMREe4LwCnqiNvacoVo0R+sQ JZ6g==
X-Gm-Message-State: AOJu0YzfYSVv78TPwzMDKCoyO/uXFzVoNoBduVnn9JXy2Jps8PmQxEeB 5E81tLifYwZ6FmkpKhDd2dSQyAcishZaBpp3dSa9+ZHwRLgmo6NEWd2q6pGN4zUiAOxEJriRQBj kfG1KmnFu4yy/sqoIliIoTPl+lSVm6B5sLfn/tQ==
X-Google-Smtp-Source: AGHT+IGLDI33duA46ZqagQYzR9xzqSRvHeRCW1yoUdJXdVk2+ARjVr2kVGr6anoLt74Fg7/oUodP/lq/aybYuuvAlWc=
X-Received: by 2002:a05:6214:29cf:b0:6a9:fdfb:9877 with SMTP id 6a1803df08f44-6ab8f53aa6cmr292713906d6.12.1716900564671; Tue, 28 May 2024 05:49:24 -0700 (PDT)
MIME-Version: 1.0
References: <CAPt1N1mmiyBSr-jdjxaWVH=hKPq1ty0V+mrBrvHAi6xTgJ2EPQ@mail.gmail.com> <17122E69-0E62-4430-BEDE-84F081734E19@employees.org> <CAJgLMKtK6=rFbVuhjwir8BXF_8DoWEz7gs1GH0Qx_W-L848hqw@mail.gmail.com>
In-Reply-To: <CAJgLMKtK6=rFbVuhjwir8BXF_8DoWEz7gs1GH0Qx_W-L848hqw@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 28 May 2024 08:49:13 -0400
Message-ID: <CAPt1N1ms6PkRbRWxH9SEODDgkZdHBXEboF2myHqHHT+DVxQiPw@mail.gmail.com>
To: Timothy Winters <tim@qacafe.com>
Content-Type: multipart/alternative; boundary="00000000000045beac06198310e3"
Message-ID-Hash: 63HFZOXEMPOEEGDMZEDNH7LQADSMLXEI
X-Message-ID-Hash: 63HFZOXEMPOEEGDMZEDNH7LQADSMLXEI
X-MailFrom: mellon@fugue.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: 6MAN <6man@ietf.org>, Ole Trøan <otroan=40employees.org@dmarc.ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [IPv6]Re: How are AdvReachableTime and AdvCurHopLimit in RFC4861 used?
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/nuuNHwjkqLXD0wDHTSoEMHPh7cc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>

Wow. Thanks. This just goes to show that full text searches aren’t
foolproof—I totally missed that!

Op di 28 mei 2024 om 08:25 schreef Timothy Winters <tim@qacafe.com>

> Hi Ted,
>
> 7.3.2 <https://datatracker.ietf.org/doc/html/rfc4861#section-7.3.2>
> defines the state machines that use ReachTime.
>
> ~Tim
>
> On Sat, May 25, 2024 at 1:50 PM Ole Trøan <otroan=
> 40employees.org@dmarc.ietf.org> wrote:
>
>> 20 uses of ReachableTime. 8 uses of “Reachable Time”.
>> Read those sections. But it might be hard to understand ND completely
>> unless you read it all.
>> It’s a long document and the most complicated core IPv6 protocol
>> specification.
>>
>> O.
>>
>> On 25 May 2024, at 16:38, Ted Lemon <mellon@fugue.com> wrote:
>>
>> 
>> Right. My question is, where is the rfc that describes what these
>> variables do? Hop
>> Limit is somewhat straightforward, I guess, but where is the rfc that
>> explains what to do with the reachable time? I’m not saying these things
>> don’t exist, but there is no reference to them in this RFC.
>>
>> Op za 25 mei 2024 om 09:58 schreef Mark Smith <markzzzsmith@gmail.com>
>>
>>> On Sat, 25 May 2024 at 21:22, Ted Lemon <mellon@fugue.com> wrote:
>>> >
>>> > Maybe we should write this down somewhere…
>>> >
>>>
>>> Pretty sure it is in RFC 4861:
>>>
>>> 6.3.4.  Processing Received Router Advertisements
>>> ...
>>>    If the received Cur Hop Limit value is non-zero, the host SHOULD set
>>>    its CurHopLimit variable to the received value.
>>>
>>> ...
>>> If the received Reachable Time value is non-zero, the host SHOULD set
>>>    its BaseReachableTime variable to the received value.  If the new
>>>    value differs from the previous value,...
>>>
>>> > Op za 25 mei 2024 om 02:05 schreef Erik Kline <ek.ietf@gmail.com>
>>> >>
>>> >> I think they update the per-interface ND state defaults, vis.:
>>> >>
>>> >>
>>> https://elixir.bootlin.com/linux/v6.9.1/source/net/ipv6/ndisc.c#L1457
>>> >>
>>> >> and
>>> >>
>>> >>
>>> https://elixir.bootlin.com/linux/v6.9.1/source/net/ipv6/ndisc.c#L1426
>>> >>
>>> >> On Fri, May 24, 2024 at 1:58 PM Ted Lemon <mellon@fugue.com> wrote:
>>> >>>
>>> >>> We've spent the past half hour in the SNAC interim trying to
>>> understand what these do, and we've come up empty. Are they in fact used?
>>> What do they do? We don't know what values to specify for them in SNAC
>>> router RAs.
>>> >>> --------------------------------------------------------------------
>>> >>> IETF IPv6 working group mailing list
>>> >>> ipv6@ietf.org
>>> >>> Administrative Requests:
>>> >>> --------------------------------------------------------------------
>>> >
>>> > --------------------------------------------------------------------
>>> > IETF IPv6 working group mailing list
>>> > ipv6@ietf.org
>>> > Administrative Requests:
>>> > --------------------------------------------------------------------
>>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests:
>> --------------------------------------------------------------------
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests:
>> --------------------------------------------------------------------
>>
>