[IPv6]Re: How are AdvReachableTime and AdvCurHopLimit in RFC4861 used?
Timothy Winters <tim@qacafe.com> Tue, 28 May 2024 12:25 UTC
Return-Path: <tim@qacafe.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 4DC75C14F6A6 for <ipv6@ietfa.amsl.com>; Tue, 28 May 2024 05:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 (1024-bit key) header.d=qacafe.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 P_1FU_wu3B1m for <ipv6@ietfa.amsl.com>; Tue, 28 May 2024 05:25:47 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 5B149C14F6B1 for <6man@ietf.org>; Tue, 28 May 2024 05:25:47 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id d9443c01a7336-1f3469382f2so6168405ad.0 for <6man@ietf.org>; Tue, 28 May 2024 05:25:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qacafe.com; s=google; t=1716899147; x=1717503947; 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=obA4qYqmuO3G8pp3RzA8D9LI93UrLUKeM4ciNDVBc9E=; b=NhmvHFiAJ+Qj3kzLtSPMK3EeDZY9PvWf1D+VGf5Y8z8CfUR8SDZ5Y+2lgGlc2LQNTM e5Rag6XsTxy5WC4aMWJeLl6KcRno1IQ+UIZ9mFN/QZ6Vm1uSSAouae6nStUN2RnE18qS TIdWZzr3XBkiJT0/H57BVbLZu3Bc3IUhdIcjw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716899147; x=1717503947; 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=obA4qYqmuO3G8pp3RzA8D9LI93UrLUKeM4ciNDVBc9E=; b=di2vekBo0ZzwZi8V+pBe4aPTzx+mQDAHXh+MdIxa641bC3UMSNr93oYk2UiEGzqvpg epko4EzG5IPHho4PmBf7nVHVfsDrhRD0q/tfbxxYulgWCAe+zC8nOi5TeRvIeIXkt8vk M2N3lYwJXC1+4ZOSAzrx8st2YweyVErrC9WD2VFHlTmtNlFEd01oLFGyiYJ6L7geicGQ QHMfcemZIX/EbrYrkf8nXmbCks4sA+e76ZhsZY4tMP/aE3GK52sQqmO/PHrsHFocy4gH XBWzBirjENWWX2n0twX2aN1rX0CPrKSdWmCW2+kAD6pTYG8gYAoTScfHlbTIeBy/fGrL Abmw==
X-Forwarded-Encrypted: i=1; AJvYcCVDnL91itDIRtvDHDp0nynY1PoZPtS3EvSK974Oui4lJbTt/0TpkgI4xVFKGnQQL0bVDjFLG1HEapu5sOid
X-Gm-Message-State: AOJu0YxDYKzTAPcx9A+IJOkxnsKFF/R7DeiHMM4KQBj32SqDUjUuaN6R DrO3uExRB7rO8OLExC1XlDkDzBhmdAGoyRts5LnyvveM7lvrv+SnDaMTkuVGqn2F1RAq7Fn/QWx Oezvdl3k/HmiWIYq9Gnug2Hnh1P/7Gk5Ou5YuasddMqcWlKeLAmI=
X-Google-Smtp-Source: AGHT+IFbnjpbEmYuEUMbzpeo9tq18QZZfZ35FLSmwKt7cr4MrBfYHwBtXHk7yo8eXye3qbywxknLom/3zb7H/+ojb64=
X-Received: by 2002:a17:902:eccb:b0:1f4:71c5:c7e with SMTP id d9443c01a7336-1f471c50f85mr116023745ad.38.1716899146720; Tue, 28 May 2024 05:25:46 -0700 (PDT)
MIME-Version: 1.0
References: <CAPt1N1mmiyBSr-jdjxaWVH=hKPq1ty0V+mrBrvHAi6xTgJ2EPQ@mail.gmail.com> <17122E69-0E62-4430-BEDE-84F081734E19@employees.org>
In-Reply-To: <17122E69-0E62-4430-BEDE-84F081734E19@employees.org>
From: Timothy Winters <tim@qacafe.com>
Date: Tue, 28 May 2024 08:25:34 -0400
Message-ID: <CAJgLMKtK6=rFbVuhjwir8BXF_8DoWEz7gs1GH0Qx_W-L848hqw@mail.gmail.com>
To: Ole Trøan <otroan=40employees.org@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c187e9061982bb5f"
Message-ID-Hash: T4GAARA3KWVIROYGHC7MDFOUKIREZ27H
X-Message-ID-Hash: T4GAARA3KWVIROYGHC7MDFOUKIREZ27H
X-MailFrom: tim@qacafe.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/9YzBnzWeNYAbf7Gv_4DOa2T34aA>
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>
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: > -------------------------------------------------------------------- >
- [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