[Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple (ends 2026-09-23)
Ted Lemon <mellon@fugue.com> Fri, 25 September 2026 08:59 UTC
Received: from fhigh-b4-smtp.messagingengine.com (fhigh-b4-smtp.messagingengine.com [202.12.124.155]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 615B03F; Fri, 25 Sep 2026 08:59:30 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=fugue.com header.s=fm2 header.b=ozmiUpJe; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=VkA0ukiT; dmarc=pass (policy=none) header.from=fugue.com; spf=pass (mx.ietf.org: domain of mellon@fugue.com designates 202.12.124.155 as permitted sender) smtp.mailfrom=mellon@fugue.com
Received: from ams-compute-02.internal (ams-compute-02.internal [10.64.2.62]) by mailfhigh.stl.internal (Postfix) with ESMTP id 5E2707A00C2; Fri, 25 Sep 2026 04:59:29 -0400 (EDT)
Received: from ams-imap-01 ([10.64.2.21]) by ams-compute-02.internal (MEProxy); Fri, 25 Sep 2026 04:59:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue.com; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1790326768; x=1790413168; bh=VPsD8c7dLl WQJik7ipJMD0rj5y16T5BhOtj+KK/Vkh4=; b=ozmiUpJefWJBVgsVviNiRocxYe +p0QwT7DFLxH3M8wc9E7BhDCdNJEVXbR2V4JO25v+nYZM0p+V34H7VQOmI2wCeDQ 8sIJh5Vp7GmyJMZBfWHFac6LaBH9dRHPXyx12xXEEfLCzhR/DrzEGDKSlBiX3WWi NIJ49sHioLXi2eWeBSGBrNdBlgknZLIBBAauWehg9xJGKgfQSQOAL6w1V5Co0nEJ U5mn7ahtcsqAYAdz9BnP1C69b5vMpJNZOWP+bZ0U6FNXuQIg6EyHOSYYKHmh8bCQ AGk6/leQszWj0rjVdz9ET7qs4qFPRI/2K+/JbFIeywLT/ehRX0cBELtRDQWA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1790326768; x=1790413168; bh=VPsD8c7dLlWQJik7ipJMD0rj5y16T5BhOtj +KK/Vkh4=; b=VkA0ukiTYYSVVks4L6oqQ6FLXrMCt9e0vD+M/tmiEAeys5BUCDK +hPVbcyrtG1caWgTDd1Rp3GgCKW+usZsOC5w7Cssiac/SkQRI3JSOfYVDFC1QVjN UXui09jP4RpoqwxiQahOnIvrlJUUc7aMRJZGrKllz0CSTXu6L3PgmW7VVEF11beK W5iRi5YGznwEsZciwVzbYotVMRbFMydrMzIPBGqk9IXQzoKFyeqPmfb4/7vyqkJY Yj0hEE66YSXbOQ9itmu+tqYquT6Ki7m35WBXwECpmVCcCfNGyN6V8UM0cg+FTZmy quaBGyd/ELaOgW1QW/FmT2AzcCIMIXEOLVg==
X-ME-Sender: <xms:7je2avivfoJ73lCqPMPJQq5aksvdGpRQA0P-_JKgyrXevezOkV_G3Q> <xme:7je2am2QOIYLoNJf0Ts5y8oW-SWfW1JjSntEwtVe-b3FoxLqQQK_vMrAYJwYBxdYT QhVUlmvfiupcaP2BMH1iUXrzY9sEoA4aywkSaD_Ges2Fg0bTlUtNx26>
X-ME-Proxy-Cause: dmFkZTGnUNpJhbwdJXcj2TpQRQfVJc6iDDaGBTPIK2K7sHsIo1le1LZNZ4OJLFO8RmHK34 Ml443BgM8Q72VobbKWHu0YGDKuqgPQRrtbmFppJpR9iVreRtMdr8+tn/VTl5nUIxj0FHs9 4WfaUI6erMq3jUUAnGD+GBkJzBUO9n3K9tX0sBA7NcG7UDgapwr+/IV+GQnkv62cqZgsSM mMwJQcElZV+3duHwHGVtaGui9SK/RGdKvbGS38UpKAbbjkO7jV8n0ddhzfqGRQkNAasvnM a+Nq1RqTRi+IYB6CpikFPx0oX6DwHoLNRijEqWfepykgAZLP+X18BcYJ7CnFi5RADdeyX8 wzL2c42ny3sfiGvmqe0l7f26qE4fL8X7yr7BaO0P0T9Iq/zVDnAn9eb/rQaw1giN1nei2O GVSYGkrUZrhILAm/1PuNRzl96YIQtNqVkTG5djB85EKYQQMiM86hPrd5pjqQ+SqaLFimPF SfiAA8ivU4BOi/KfsZtNeR/euogqv/9cIG9EXGGBqAQKEO6DTIQmfHGGyz0MWWJAGNQqTX 46nXim/FOnj3RTR079MRDXu3w8vpBUXqKduw2gkZfEV9qS6BdM/EYCywpCuuBlQhVdTv1K L0dQxNHurFOpMTCsbaJjadaZodDGfd3tUmR/s+kuBpxxp5ubl3NHQ88vslXA
X-ME-Proxy: <xmx:7ze2aus0mOZFoppDmEzc674lgg7_3znnL5ES0Y0bkgd5_4dLtFIAUg> <xmx:7ze2asYD-oQOAL0Xj9FNfWaw0JYt0iyfwG7ueA3MEphiGkYVG3rgPQ> <xmx:7ze2alXHmML7nANKXa9DYitQGbg1_KuoLo1sNeNdFGz3y7Ch1sP-fw> <xmx:7ze2apR-8I2Bw6E7Yc5-qibcmN1vkubSbKvEBnwEhBlgRnVulh2dUQ> <xmx:8De2aoy_EGmvpFy-JQ65FLIQHT2HqddW1ZOJg2A8a6DecKGN9mHMczIO>
Feedback-ID: i1136489e:Fastmail
Received: by mailuser.ams.internal (Postfix, from userid 501) id 36CECFA0083; Fri, 25 Sep 2026 04:59:26 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
MIME-Version: 1.0
Date: Fri, 25 Sep 2026 10:59:05 +0200
From: Ted Lemon <mellon@fugue.com>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>, "Andrew Yourtchenko (ayourtch)" <ayourtch=40cisco.com@dmarc.ietf.org>
Message-Id: <9eb608f8-798d-4af8-982c-b859d6495b04@app.fastmail.com>
In-Reply-To: <bf102c56-477d-4676-b622-e5abc90a7fa4@iotconsultancy.nl>
References: <5922305083fc4b799b6ae5551fa2ba93@huawei.com> <FAE16822-FDC0-4FEF-9839-0B0F0A1229C6@cisco.com> <068B87AB-09BE-4ED9-8990-1A0B5EDD4CE9@fugue.com> <bf102c56-477d-4676-b622-e5abc90a7fa4@iotconsultancy.nl>
Content-Type: multipart/alternative; boundary="8bad854e19aedef093aecaf1e35105bc7c297c5d"
X-Spamd-Bar: /
Message-ID-Hash: 4N4GD4K5YHVIUB3SNHLSOOF5CHKFUPEP
X-Message-ID-Hash: 4N4GD4K5YHVIUB3SNHLSOOF5CHKFUPEP
X-MailFrom: mellon@fugue.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Zhe Lou <zhe.lou=40huawei.com@dmarc.ietf.org>, "snac@ietf.org" <snac@ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple (ends 2026-09-23)
List-Id: "Mailing list for discussing problems relating to the automatic connection of stub networks to existing infrastructure networks." <snac.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/snac/QIz__gpurh96T4KM2v2jssDZ6Tw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/snac>
List-Help: <mailto:snac-request@ietf.org?subject=help>
List-Owner: <mailto:snac-owner@ietf.org>
List-Post: <mailto:snac@ietf.org>
List-Subscribe: <mailto:snac-join@ietf.org>
List-Unsubscribe: <mailto:snac-leave@ietf.org>
What's intended there by "recent RA" is exactly what the text you initially quoted is talking about, so it would be worth making this explicit. On Fri, Sep 25, 2026, at 10:45 AM, Esko Dijk wrote: > Hi Andrew, Ted, > > Agree that state of RAs needs to be maintained; this is used in various places in the document. > > However for 5.1.2.2 (STATE-SUITABLE) we put a maximum time cap on received RAs: > > The router MUST NOT consider any Router Advertisement that is older than STALE_RA_TIME to be suitable. > > But in 5.1.2.3 (STATE-BEGIN-ADVERTISING) we don't have any time cap like this. That means that M/O flags seen a month ago from a stray RA (maybe an experiment?), where it had Router Lifetime = 0 (i.e. no default router), will still be copied. > > I'm not sure this was our intention? We do mention: > > If there is no recent RA received from a non-SNAC-router, both 'M' and 'O' flag bits MUST be cleared. > > This implies there's a time/age limit. But it's hard to act on this MUST because we don't declare what "recent" is. > > Esko > > > > On 9/14/26 17:57, Ted Lemon wrote: >> On 10 Sep 2026, at 16:12, Andrew Yourtchenko (ayourtch) <ayourtch=40cisco.com@dmarc.ietf.org> wrote: >>> Scenario: two routers sending RAs, one with zero Router Lifetime, the other with the Router Lifetime > 0, but which expires before the first router sends its next RA. If I were to read the text verbatim, I would need to implement some sort of memory for the values of flags from the first RA, to be able to pick them up in such a scenario ? >>> >>> Otherwise, if I have a naive implementation where I would just store ‘M’/‘O’ flags in a single place, I would not be able to track the Router Lifetime expiration this way. I suppose the way I would have implemented it reading the spec is to remember the flags from a received RA + wind up the timer equal to Router Lifetime to flip them to zero / cancel outstanding timer if I get the Router Lifetime == 0; and if I somehow ended up with just the RA with Router Lifetime == 0 and nothing else, in my naive reading it would result in “sticky” M/O flags remembered value ? >> >> I don't think you can do an implementation of this where you don't main this sort of state, so in practice I don't think this is a problem. Think about how you tell whether or not there is a "suitable prefix" present on the link. >> >> >> _______________________________________________ >> Snac mailing list -- snac@ietf.org >> To unsubscribe send an email to snac-leave@ietf.org > -- > *IoTconsultancy.nl* | Email/Teams: esko.dijk@iotconsultancy.nl | +31 6 2385 8339
- [Snac] 2nd WGLC: draft-ietf-snac-simple (ends 202… Zhe Lou
- [Snac] Re: 2nd WGLC: draft-ietf-snac-simple (ends… Esko Dijk
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Michael Richardson
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Ted Lemon
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Michael Richardson
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Ted Lemon
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Michael Richardson
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Ted Lemon
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Esko Dijk
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Ted Lemon
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Michael Richardson
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Esko Dijk
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Esko Dijk
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Ted Lemon
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Eric Vyncke (evyncke)
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Esko Dijk
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Esko Dijk
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Esko Dijk
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Andrew Yourtchenko (ayourtch)
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Ted Lemon
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Esko Dijk
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Ted Lemon
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Esko Dijk
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Ted Lemon
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Esko Dijk
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Ted Lemon
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Esko Dijk
- [Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple… Ted Lemon
- [Snac] Re: [IPv6]Re: 2nd WGLC: draft-ietf-snac-si… Sebastian Moeller
- [Snac] Re: [IPv6]Re: 2nd WGLC: draft-ietf-snac-si… Ted Lemon
- [Snac] Re: [IPv6]Re: 2nd WGLC: draft-ietf-snac-si… Ted Lemon
- [Snac] Re: [IPv6]Re: 2nd WGLC: draft-ietf-snac-si… Esko Dijk
- [Snac] [SNAC] Conclusion of 2nd WGLC: draft-ietf-… Zhe Lou
- [Snac] Re: 2nd WGLC: draft-ietf-snac-simple (ends… Eric Vyncke (evyncke)
- [Snac] Re: 2nd WGLC: draft-ietf-snac-simple (ends… Esko Dijk
- [Snac] Re: 2nd WGLC: draft-ietf-snac-simple (ends… Ted Lemon
- [Snac] Re: 2nd WGLC: draft-ietf-snac-simple (ends… Esko Dijk
- [Snac] Re: 2nd WGLC: draft-ietf-snac-simple (ends… Jonathan Hui
- [Snac] Re: 2nd WGLC: draft-ietf-snac-simple (ends… Esko Dijk
- [Snac] Re: 2nd WGLC: draft-ietf-snac-simple (ends… Jonathan Hui
- [Snac] Re: 2nd WGLC: draft-ietf-snac-simple (ends… Esko Dijk
- [Snac] Re: 2nd WGLC: draft-ietf-snac-simple (ends… Esko Dijk
- [Snac] Re: 2nd WGLC: draft-ietf-snac-simple (ends… Eric Vyncke (evyncke)
- [Snac] Re: 2nd WGLC: draft-ietf-snac-simple (ends… Ted Lemon