[IPv6]Re: How are AdvReachableTime and AdvCurHopLimit in RFC4861 used?
Ted Lemon <mellon@fugue.com> Sat, 25 May 2024 14:37 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 70025C14F698 for <ipv6@ietfa.amsl.com>; Sat, 25 May 2024 07:37:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.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_HI=-5, 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 9gnJLy41ohBH for <ipv6@ietfa.amsl.com>; Sat, 25 May 2024 07:37:25 -0700 (PDT)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 6DA1CC14F618 for <6man@ietf.org>; Sat, 25 May 2024 07:37:25 -0700 (PDT)
Received: by mail-qt1-x834.google.com with SMTP id d75a77b69052e-43fb8e911a5so4469241cf.2 for <6man@ietf.org>; Sat, 25 May 2024 07:37:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20230601.gappssmtp.com; s=20230601; t=1716647844; x=1717252644; 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=XhYZ6it6csqLAMIu9MqDZUJhflqnaNPOmwPfaBe7UBY=; b=qQ6w0frOt+8wRtjqYQge90Ixof3C64C21HHe+DVu6QYxpMrIvpNv9jZwWCE6NyTicN CH5QL5y+lXRKTlS5i7t8ss9SD49Szvyvm/ruxtHGiYWppBuOb0/1LyVCav0z426JAH/1 V1S8TpOkFW3Zop9Zx2xnKV4wfTHkxNaz7U0NkUr5N6k3yL0zdO4qDQumNDqXD7F5cZzw wIdfBrjlhWplrfjwHJQpCbu0MfLDUpWXLFapoSQJHxSqpI5c/6Q/Tkmsi92dn0TinOIo H4cmEJu158jmm+CfBwow4Z+Qr7jMLhWiDpmamHwvqCyBsvw3w1xnFc4BYKgfX+CMJDhX IYEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716647844; x=1717252644; 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=XhYZ6it6csqLAMIu9MqDZUJhflqnaNPOmwPfaBe7UBY=; b=iTEayfa2CKR4CCBEF+almAj0qePUSo9G1M+8N0MrHZHcBLM2hNE72b2njjt33oiGi0 WSewQtMeokNN4265nr6rteQ5OpwLEOfjszEEzuYw0JVDhkL4LpjnSsrz12gSqVGZhQu1 xQd1j7XbVzBub5vdROJN53ck7bxzwtoHAZ0VEXTeEtDVrd9LGRPKpRfeeYfvugBq9Kxs +pFPl923aMHPp1jpxnVZaKUbGpyLePjYKyIbIDugBRMy0T7P6f33V0+NWhsYYj4h9UZJ f+5VqhIlKljikU2VNzo9645u6u9cQrTJWkZnJ9r/HNmeiJ+/fe6oGx9uJ0bYYKmwBZwE G9xQ==
X-Gm-Message-State: AOJu0YxOA10+30bZWlIaOgTcQzXmelFcXBaUoWcMmc/2UJt6iuUvDySC Uja3DBYPH7uyRCLXlp+5ev5Md1TRunRI7flfI6HVeKuXdEfjqdQzPErhg0UrkMvv7DdbeirPr+D BHUo8BzJ16v8sOaXAgCGrALsedTBVMUT7aP5IEksZF59HV97p8Fg=
X-Google-Smtp-Source: AGHT+IGY3afhLUlTyNFmBnPqkZYfxnf6LWfdZr4h7UWTfcIgddD8ZGK5qXwxTMJuSorpwsxT9KFSOnUsyOZBHQVBmDg=
X-Received: by 2002:a05:6214:5d11:b0:6ab:9da7:32bd with SMTP id 6a1803df08f44-6abccfa278fmr45565926d6.30.1716647843661; Sat, 25 May 2024 07:37:23 -0700 (PDT)
MIME-Version: 1.0
References: <CAPt1N1kdzWQWDUO8FvM1Bp+B9B9PvvXXsm8F00_ziR4Z735tcA@mail.gmail.com> <CAMGpriWhdYtBVycBoUSYzctM+UPWHzGMGA+-h9cUQ09ftrFBsQ@mail.gmail.com> <CAPt1N1niW4=JkVMbgkzy2O11tHkxYNWq7UKMW7b9TnJOFXx8VA@mail.gmail.com> <CAO42Z2xq4wJT2tGr0Lx0hdHosqTfcbHt44BF_BK-B1_6d3J8dw@mail.gmail.com>
In-Reply-To: <CAO42Z2xq4wJT2tGr0Lx0hdHosqTfcbHt44BF_BK-B1_6d3J8dw@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Sat, 25 May 2024 10:37:12 -0400
Message-ID: <CAPt1N1mmiyBSr-jdjxaWVH=hKPq1ty0V+mrBrvHAi6xTgJ2EPQ@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000ed26dd0619483846"
Message-ID-Hash: POUW5EOTWRBZWZW73PSGUIMFM6ZLKGDQ
X-Message-ID-Hash: POUW5EOTWRBZWZW73PSGUIMFM6ZLKGDQ
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>
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/NU5y0n-29_LjwXwoplnQRkVLYZg>
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>
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: > > -------------------------------------------------------------------- >
- [IPv6]How are AdvReachableTime and AdvCurHopLimit… Ted Lemon
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… David Farmer
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… Ted Lemon
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… David Farmer
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… Ted Lemon
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… David Farmer
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… Ted Lemon
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… Timothy Winters
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… David Farmer
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… Erik Kline
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… Ted Lemon
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… Mark Smith
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… Ted Lemon
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… Ole Trøan
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… Timothy Winters
- [IPv6]Re: How are AdvReachableTime and AdvCurHopL… Ted Lemon