[Snac] Re: Why is an AIL prefix with only the "P" flag set suitable?
Ted Lemon <mellon@fugue.com> Fri, 21 November 2025 19:39 UTC
Return-Path: <mellon@fugue.com>
X-Original-To: snac@mail2.ietf.org
Delivered-To: snac@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E44FE8E3824F for <snac@mail2.ietf.org>; Fri, 21 Nov 2025 11:39:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=fugue.com header.b="Di9OaKaO"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="yplQCsew"
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pw3AqNqjYFMU for <snac@mail2.ietf.org>; Fri, 21 Nov 2025 11:39:43 -0800 (PST)
Received: from fout-b8-smtp.messagingengine.com (fout-b8-smtp.messagingengine.com [202.12.124.151]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 0AE9F8E38248 for <snac@ietf.org>; Fri, 21 Nov 2025 11:39:42 -0800 (PST)
Received: from phl-compute-05.internal (phl-compute-05.internal [10.202.2.45]) by mailfout.stl.internal (Postfix) with ESMTP id 73FED1D0013F; Fri, 21 Nov 2025 14:39:36 -0500 (EST)
Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-05.internal (MEProxy); Fri, 21 Nov 2025 14:39:36 -0500
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=fm1; t=1763753976; x=1763840376; bh=W/Bkk5Aq7d 2nNT9t5nl4UgksBa6dQwjTbpf3Ob2gPN0=; b=Di9OaKaO/GUsZBAhSV1QJfcu/s V6VhaZOdiU3k+c69l36tLtRcxTJ5UVN/ql5CDkLxQ1ZanVYf+28LFwRMMaoizzLr Q9rk46PlZ4q57wl+t/3QDD7tnN8QSBFW4kijRaPoHcEWudgMQETVnWUO2MbOSkzO q4lio/HmyE6WZ5UctyRAMlmt9lXiPb16/F2L4VrEIAzFTR/c1V5uj4z0AfoOHDpb E+B5L1meyz3+T1EAo4uW0jdJ2/BuHatAh9YPcZEDGsw1m93Y9yC9Ut6t/gLQlGSf uZ1iLPaRutwvj2+MUpj2qhPjB/L6pF5dMMiqw9oS/31YVqurklcFb5FijxoA==
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=fm3; t= 1763753976; x=1763840376; bh=W/Bkk5Aq7d2nNT9t5nl4UgksBa6dQwjTbpf 3Ob2gPN0=; b=yplQCsewyn5kAMqhaH06K8am3LAdZWY3/6JrV2YfhEHdjSu1Ej8 u0O5JTPVkZdAGDQNNhmd8tq3QqWeSDZ1Z2BFfc+Gassw6JAzUWkHzY4ib6scMYbo mvXELahNJtNmGPwWxAuG8kRUnlzlgXxAXwcGuPfDCLNcInGJWPnqgv5ClR794kUG u/SnB5pXGBbWE+zE7hyR9VJqK8qLwGAEAIh1Y+M9WAgYP1610JKK7dfTggThxYWr BqecFIwncW8i02FCstVGKiXqFGXu4+QRawfmwhNU1xg4220XBQ8E3yWK77Hnz+5H VmxtAIwYAp0TmgpoPJuI6n7Wv+sAUtkmjdw==
X-ME-Sender: <xms:978gaUrBUa12bNQM1H3qW8OBGbDaGYUcNExvYzT5vnyyphNgua6sxQ> <xme:978gae-zRzmmTfD3q5DJ2KjYM_xEenv7qUrTNe6tDUPEmDtT6MQhykeqzGpgvHa6O ouLlUt0wU2fzFBu-Y38ZspuxyPCyXhmNhx6Ti_25zbn6Xnlb1Vpjg>
X-ME-Received: <xmr:978gaYUJGc2z5JSC14n0IOi57lQHjqX_VnKFUOb95EJo8qrjyX17BJ5W3BgWbI22RDMa_nzunk10kPc9gNw5tEfXubI7ExV9XKYq8A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggddvfedtkedvucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhephffktgggufffjgevvfhfofesrgdtmherhhdtjeenucfhrhhomhepvfgvugcunfgv mhhonhcuoehmvghllhhonhesfhhughhuvgdrtghomheqnecuggftrfgrthhtvghrnhepge euveeuhfdtgfejteelvedufeefgedvvdejieeiteekffekjefhvdfgvdegkeefnecuffho mhgrihhnpehivghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmh epmhgrihhlfhhrohhmpehmvghllhhonhesfhhughhuvgdrtghomhdpnhgspghrtghpthht ohepfedpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepmhgtrhdoihgvthhfsehsrg hnuggvlhhmrghnrdgtrgdprhgtphhtthhopegvshhkohdrughijhhksehiohhttghonhhs uhhlthgrnhgthidrnhhlpdhrtghpthhtohepshhnrggtsehivghtfhdrohhrgh
X-ME-Proxy: <xmx:978gaUCDpKCY5EaYQ4oKwZ32mdPkI54IYNJeXI57RtcWId1bXkb8Nw> <xmx:978gaZxqdec0mB1_8Bll1I-_9EvIY75dTqBbGUkO2u2x_BgurG7vFA> <xmx:978gaRAQYYOA04eyzQBjgqCQgY_X2_vMIh3bRtv1s4ZtzeGcaLUKeA> <xmx:978gaWay4z3lCpP-lkb1kMD6dBPrz8blfolaAPYPZ8yRiP7bBxmSsQ> <xmx:-L8gaVlS2-IANqkiFWCNyg8ulsPs3p4bzL6_BBftuJXq0JacCCMLLv_t>
Feedback-ID: i1136489e:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 21 Nov 2025 14:39:35 -0500 (EST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <8F59C774-ACC7-48A8-AE5B-768EE1A5DFC2@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7831C1A4-2BEA-4F20-95BC-39EE2820CF24"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.300.41.1.5\))
Date: Fri, 21 Nov 2025 20:39:24 +0100
In-Reply-To: <21046.1763753344@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <13441f45-57bf-48ea-9814-4d65214113a7@iotconsultancy.nl> <19398.1763653578@obiwan.sandelman.ca> <B0424C42-F02D-42B1-8A1B-A2EFB8F97F13@fugue.com> <15765.1763679273@obiwan.sandelman.ca> <5fbfe856-182d-4eaa-8dac-2fbe271ceb2e@iotconsultancy.nl> <838A5057-520F-4525-BA78-1BC48910F299@fugue.com> <21046.1763753344@obiwan.sandelman.ca>
X-Mailer: Apple Mail (2.3864.300.41.1.5)
Message-ID-Hash: Y4ILCVUPDKJG4YNPL7AOBKNI4SMGQDGH
X-Message-ID-Hash: Y4ILCVUPDKJG4YNPL7AOBKNI4SMGQDGH
X-MailFrom: mellon@fugue.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Esko Dijk <esko.dijk@iotconsultancy.nl>, snac@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Snac] Re: Why is an AIL prefix with only the "P" flag set suitable?
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/R2RhPk8Uy9LACwERupr8tfnFF-I>
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>
On 21 Nov 2025, at 20:29, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> Ted Lemon <mellon@fugue.com> wrote:
>> Consider the bad home router case. In this case, the home router is in violation of RFC7084:
>
>> WAA-1: The IPv6 CE router MUST support Stateless Address
>> Autoconfiguration (SLAAC) [RFC4862].
>
> Support != enable!
> {I think that I can explicitely turn off SLAAC on OpenWRT, relying on DHCPv6-only}
It's pretty clear that the document assumes that SLAAC will be enabled by default. However, you're right that it doesn't say that explicitly. It does say "The A and L flags' ([RFC4861 <https://www.ietf.org/archive/id/draft-ietf-v6ops-rfc7084bis-04.html#RFC4861>]) settings SHOULD be user configurable." which implies that there is a default.
>> So I think we don't need to address this case, because non-conformant
>> home routers should be out of scope. E.g., a home router MUST NOT
>
> I think that word non-conformant is incorrect, but I agree that it probably
> should be out-of-scope.
It should be the case that such a router is non-conformant, and I will mention that on the v6ops mailing list.
> ...
>> It's of course possible that the operator of a home router might turn
>> off SLAAC, but in that case you have a managed network. Which brings us
>> to the second case—a misconfigured or deliberately configured managed
>> network.
>
> Agreed: This might have been done by an incompetent ISP.
> So in this case, we need enough text for an end-user to hit them over the head.
I don't think we can require that the ISP not disable SLAAC, but realistically if they do they are going to get a lot of phone calls. Well, assuming the end user cares about IPv6.
>> If it's deliberately configured this way, then I think it makes sense
>> to follow the operator's intention. Our goal here is not to make every
>> network SNAC-capable, but rather to make sure that when SNAC should
>> work, it does work. In this case, the operator has clearly decided that
>> SNAC shouldn't work for hosts that don't do IA_PA (or possibly
>> IA_NA). I think it's fine for us to not solve this problem.
>
> +1
> The STUB network could well work via PD (or ULA+NAT64 even), but not interact
> with the AIL. We should document this limitation clearly then.
> _It's working as intended_
OK. Send text (to github)?
- [Snac] Re: Why is an AIL prefix with only the "P"… Esko Dijk
- [Snac] Re: Why is an AIL prefix with only the "P"… Ted Lemon
- [Snac] Why is an AIL prefix with only the "P" fla… Esko Dijk
- [Snac] Re: Why is an AIL prefix with only the "P"… Ted Lemon
- [Snac] Re: Why is an AIL prefix with only the "P"… Esko Dijk
- [Snac] Re: Why is an AIL prefix with only the "P"… Ted Lemon
- [Snac] Re: Why is an AIL prefix with only the "P"… Michael Richardson
- [Snac] Re: Why is an AIL prefix with only the "P"… Ted Lemon
- [Snac] Re: Why is an AIL prefix with only the "P"… Michael Richardson
- [Snac] Re: Why is an AIL prefix with only the "P"… Esko Dijk
- [Snac] Re: Why is an AIL prefix with only the "P"… Ted Lemon
- [Snac] Re: Why is an AIL prefix with only the "P"… Michael Richardson
- [Snac] Re: Why is an AIL prefix with only the "P"… Ted Lemon
- [Snac] Re: Why is an AIL prefix with only the "P"… Michael Richardson