[Snac] Re: [IPv6]2nd WGLC: draft-ietf-snac-simple (ends 2026-09-23)

Ted Lemon <mellon@fugue.com> Fri, 25 September 2026 11:51 UTC

Received: from fhigh-b6-smtp.messagingengine.com (fhigh-b6-smtp.messagingengine.com [202.12.124.157]) (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 7A36E31; Fri, 25 Sep 2026 11:51:28 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=fugue.com header.s=fm2 header.b=lkXbphQY; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="SG/divZ9"; dmarc=pass (policy=none) header.from=fugue.com; spf=pass (mx.ietf.org: domain of mellon@fugue.com designates 202.12.124.157 as permitted sender) smtp.mailfrom=mellon@fugue.com
Received: from phl-compute-03.internal (phl-compute-03.internal [10.202.2.43]) by mailfhigh.stl.internal (Postfix) with ESMTP id B9AB67A0120; Fri, 25 Sep 2026 07:51:22 -0400 (EDT)
Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-03.internal (MEProxy); Fri, 25 Sep 2026 07:51:22 -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=1790337082; x=1790423482; bh=7wRKnVDDyI ZkxDLg4fQgYZv3XmtgWg228za+vAWEOkU=; b=lkXbphQYnngSyMiLQLenF5Rbxf Gyj30ejed8n4iM5fAE0uhaFV/VCTUOb66g6zm6cKICkCcJQepFGyFUXvOU0gAX2P hZ0JBYzzNV/8+UC4PC1xj4EFmmrZuS6D4LKJBSwUcJVKOTbr7QwNvha8QWnMMpUX AIbgnhmx7CykaqF9e9WxhXGRcIF1rDYapXvJ8w93aMdMPDmqCUc20WoEirhrwN6U aYs1IVanqJzt2rsoNpn5dv3bvvxKKJZricBPzPUjdnpW8X67HT8r1QCNDEkUoWvq cKihW9dkQAl0vwJNQCGidZWE9JJJdSqwW/91Q1ff0UxLAFVpSuh2gdyx9yIQ==
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= 1790337082; x=1790423482; bh=7wRKnVDDyIZkxDLg4fQgYZv3XmtgWg228za +vAWEOkU=; b=SG/divZ9PkAbnqNxNfGSe3habAxEMkFgHQTL7t4E2O36aOiBDae mO9UWGB8qhlgJ/nuSJJgE9rhZK67Yw6IiRQ9PPlIOnaqzR+fOq/c09z5Q2eEGApE yRNNqlUK5E7+XDx1+/pxI64xiT2YoF5BoMgbjmFJUd0t7u9OItpyy+JQuHBI8qcO OaidQny6VYIdHUyMeL9zdkbmpwQYQoXZ8wgVYqArkdA7885W2RA6K/120u9Otv95 gnQRdAbPc2TmKqL7UK77iFIEGRIJRMG+EFrV8rq7hq3LnISc4j1pBg5umMrT80kU cmbB8/N9XF0qC0TFATIa8qoDqIHVvbpQkEA==
X-ME-Sender: <xms:OmC2akqXpOxyIfYJ8av8mZG7quIUawaCWBL4DG8_eb08Ah_IAspGFg> <xme:OmC2am_T4wffyTmHfrjGA5gQpUtgu6jtQCqaYSORRXixjR-MT58w757n3fnNOCcDw XRMVWOK5_tC4n9MmsZgZXhzzPaxbp_EDw0t9fXQyEcwFMni3cnB6D8Z>
X-ME-Received: <xmr:OmC2ar_JSUfiiB9XHwuzgDylZOCqLoHfUvQvN_tcfziO23PG76ZeZM2xngf0ApFuouAc_DalFtPI4cY6K6hYqwzcXmPb8cuprAtUoR5n>
X-ME-Proxy-Cause: dmFkZTFnHGnTHBTNGchEncoW4IkrToW3qbRuGlkU0HKwOAKdWLdbu4FaP/xhipjjo7n70s 8XYc3w52K+f5E0NvMcyGMDofKgYYQji5Ia/xMlLNnlB5TnPwepgBuS0gkapOuhSwbXp0VK Dj6C9+IzYXnTyhhxR/D1nWwBUkhHrSxMsq8z1p6pTrAMmwTsVN3p/BZOPQ1h/h8FbCoHUa jD7UnMrnfTCTwnByVu2RclpKhcDUmMTdNxM++cX1jWVbY0zDbQ0kghazKfiKfCHih14hVA wbUdbgTOHRgXZ/3HKT+b4d23pYbbWe4kZmr77cVjM2yUzXPN6VBxW1q5LJWgR7iG5+gVi+ UrvJCEwbUZHxIa+5a2Qa6dAs+DJGHNXZ8+MXBDpQOpyMGgC8qc+Ig1PnyK4eEEFEBczBke DusXi/Qr9DAEMj0SJTuVBtNE1BY3mMie605Gl/jplpk/bPwi4DLqFscTPLIya97Fj0uvJ+ K6SmUt4uDuq11K0QMpmhEt/F3UmPkESUuZDCbKQeI7itM0D90jz02QVEQRnANppTq4H7Dy FTxT73jI51NuzabHFEPcRBcxp3Lo4AX8iE0wOqUZpg2HxTsk5Arb6PgbtIPVX2+amsmo6O 6GVscQ8SWKwz6SDZC5qwO8HzeuZZK9iqCwoO/lIKkXQcVzbL+yBbhByZjj6A
X-ME-Proxy: <xmx:OmC2atsfVByqK4VlWGnaQrN96lEAHKlt8K-aQJxUxZOd-N4MX4douQ> <xmx:OmC2ampInSCmcrgz0v02rQftYBgCJ7m2m_iMFFU3OUyhcIZuZwGHDQ> <xmx:OmC2ailamQcIe7H78gSinMozjbH3h8R9Rp5BNr29v27qjtnOgayYuA> <xmx:OmC2aiy33pjvmfeYnyEQkX659NPJeaQXyIZzaEcG6Or8f71faylyEA> <xmx:OmC2agztzTb8bo_ZFREhFW7-YMdCvDCLunCsi0oNNGKfCc5o_skPSReM>
Feedback-ID: i1136489e:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 25 Sep 2026 07:51:21 -0400 (EDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <06C5C1E1-DD3E-4BA8-871C-8F3A699F67C9@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E9D62B08-EF16-4118-BAA7-5E324D986DA0"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3901.200.54\))
Date: Fri, 25 Sep 2026 13:51:09 +0200
In-Reply-To: <FAE16822-FDC0-4FEF-9839-0B0F0A1229C6@cisco.com>
To: "snac@ietf.org" <snac@ietf.org>
References: <5922305083fc4b799b6ae5551fa2ba93@huawei.com> <FAE16822-FDC0-4FEF-9839-0B0F0A1229C6@cisco.com>
X-Mailer: Apple Mail (2.3901.200.54)
X-Spamd-Bar: -
Message-ID-Hash: VWS5TMLYQIEAFLKO5A62G4NDQTXVUH6M
X-Message-ID-Hash: VWS5TMLYQIEAFLKO5A62G4NDQTXVUH6M
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: "ipv6@ietf.org" <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/tr8cIqX11a4Rm4d2qvPYGNWtR3c>
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 10 Sep 2026, at 16:12, Andrew Yourtchenko (ayourtch) <ayourtch=40cisco.com@dmarc.ietf.org> wrote:
> Technically, an enthusiastic implementer of a SNAC router could front its NAT64 with a CLAT-like function towards the infrastructure NAT64, thus achieving IPv4 connectivity with no IPv6 connectivity. This would create a capability disparity between the stacks, so is clearly not the best idea. 
> 
> Is it worth forbidding this case explicitly, or do we assume nobody goes in that direction, or we don’t care if they do ? 

We can't forbid this. It's just not SNAC. If somebody wants to take a SNAC router and do something with it that they consider useful but that is out of the scope of the specification, that's great! Why should we tell them not to?