[Snac] Re: Handling multiple AIL-interfaces in a single SNAC router

Esko Dijk <esko.dijk@iotconsultancy.nl> Tue, 14 April 2026 08:05 UTC

Return-Path: <esko.dijk@iotconsultancy.nl>
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 64709DBDB6C8 for <snac@mail2.ietf.org>; Tue, 14 Apr 2026 01:05:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776153916; bh=xOK0I+jL6fn0yl/3XVC3EEvqQKmDpDCjtljUDJrbCGk=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=zCC5Qeb+twxJvgvtgOcEZlaWYLeC4nODIpTRvcJh8L1YqeVg20XpwFMdDY1TKsIs/ sK2mdv+Kov0C5UYX1J/9ZyIGyUJoIRSHGzeR4ylKV42K5R3/mmh0IJOcObhXIUv4aP pbBDR1zhXpScjQ8bPtW32vZZ8O0PIRaRAdPX2JZ4=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=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=iotconsultancy.nl
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 Rf0dzMGc856K for <snac@mail2.ietf.org>; Tue, 14 Apr 2026 01:05:12 -0700 (PDT)
Received: from dane.soverin.net (dane.soverin.net [185.233.34.157]) (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 F0B8EDBDAB30 for <snac@ietf.org>; Tue, 14 Apr 2026 01:03:35 -0700 (PDT)
Received: from smtp.soverin.net (unknown [10.10.4.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (No client certificate requested) by dane.soverin.net (Postfix) with ESMTPS id 4fvxc65wYXzjZ; Tue, 14 Apr 2026 08:03:34 +0000 (UTC)
Received: from smtp.soverin.net (smtp.soverin.net [10.10.4.99]) by soverin.net (Postfix) with ESMTPSA id 4fvxc40VJvznt; Tue, 14 Apr 2026 08:03:32 +0000 (UTC)
Authentication-Results: smtp.soverin.net; dkim=pass (2048-bit key; unprotected) header.d=iotconsultancy.nl header.i=@iotconsultancy.nl header.a=rsa-sha256 header.s=soverin1 header.b=HDi69Ywp; dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iotconsultancy.nl; s=soverin1; t=1776153812; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JSrQtWeYBMsxJPS+xKdNEoejGgM/Qc2VwMxqR6K0Wnc=; b=HDi69Ywp6ysaWXAjgilRgkbKz6Ci1/yE2wQzATEMwhOTzCU2cdV/ORWwzcjgPKlLzsz011 0QeDZCfA+JEJP4vJ4Rttp07iiNMqXBIIBUDsSwulmB2Pxx8SumHmZOPRPn2j+TJvvXr22f sphMMPkUut9etcPZA0LYBdYOP8LS2+nUWwp4O8KaZYbPyCNi22xzir4MPvnwD635da2q5h CP0kzTMjEsPpwb5V/w90fb+8iNnwF5hp4/h/IORF1F9s0EGFrrPs59ICFcyqaev2GJGaJf UVoHn4yeqYHNPqz2gfO4w0Wb9J90i2H/zJHAwCpz2OOjAPrZuzEu7ufJjGAKJg==
X-CM-Envelope: MS4xfC1mcsmxY/I5S7rEaMnB7ue0AbDqDHHkNbh8dHPzlX6SyXccALrsl0urVCsTs1FY7irr7fSv5c55bZhAlX/d2fStPW4gUQVVRaniQIRqqg/WSbjdneQn 8fJdTrux8GBBRYjzP1SLq3oVaOexf4pPwqox0SpqbqS3IOOVBDcNzVmuIge9b0HIl7FAtBRQrTc9ZGsYQ7Arh8UybZ0TOVdJv/xhtXbrZm94xPe6Xb0YDnmY wwZdT9iCatfhsbtuXvGUCc2uuzJk5LAijUIQoZrUEGw32kh2RuUFkK03xszaTDjjx0fwIIeyLLCvW95Qk3H3QMZEPmxzUvld+VHebMU+OV2ctjHuZopNaLmT WMcoUy34
X-Soverin-Id: 019d8b04-5c20-7e70-b840-189c28800008
Message-ID: <5110edce-2038-42c8-8d8a-031cedfd22a1@iotconsultancy.nl>
Date: Tue, 14 Apr 2026 10:03:31 +0200
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <ed392ae6-8127-451d-a25d-0f273c49e2b9@iotconsultancy.nl> <3140.1776107801@obiwan.sandelman.ca> <5872bff2-1b82-4f44-9656-544a91d6dc92@iotconsultancy.nl> <7EA1B5EA-198B-454D-874A-9282DD05B13E@fugue.com>
Content-Language: en-US
From: Esko Dijk <esko.dijk@iotconsultancy.nl>
In-Reply-To: <7EA1B5EA-198B-454D-874A-9282DD05B13E@fugue.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Spampanel-Class: ham
Message-ID-Hash: S7PD6IBPBVDM5URG2Z3FRRMVGO3JXYNJ
X-Message-ID-Hash: S7PD6IBPBVDM5URG2Z3FRRMVGO3JXYNJ
X-MailFrom: esko.dijk@iotconsultancy.nl
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: Michael Richardson <mcr+ietf@sandelman.ca>, "snac@ietf.org" <snac@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Snac] Re: Handling multiple AIL-interfaces in a single SNAC router
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/Xp9P9iL471JBriounMz_a2rC70M>
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>

 > But a SNAC router is never a CE router.

Yes, correct! So this case is a SNAC router with an Ethernet port and 
Wi-Fi, with both active; and the CE router is another device. There's a 
single ISP in use.

An example setup:

- SNAC router Ethernet is directly connected to the CE router.

- SNAC router Wi-Fi is connected to a home Wi-Fi AP+router device, in 
router mode, which is in turn connected via Ethernet to the CE router.  
So there's a single ISP, but still two separate AILs.


At first I considered the case of two AILs that are bridged ('bridge 
mode' set for the AP in the example) also as two AILs. But, I think it's 
single AIL case from the IPv4 and IPv6 perspective -- so a single AIL 
for snac-simple purposes, even though it can be accessed via two 
different link technologies.

I'll make a new PR that updates the text to the single-AIL case - then 
we can see how that works out.

Esko