Re: [v6ops] Our IPv6-only home network and future experiments

Brian Candler <brian@nsrc.org> Sat, 13 April 2024 17:56 UTC

Return-Path: <brian@nsrc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5342C14F5FA for <v6ops@ietfa.amsl.com>; Sat, 13 Apr 2024 10:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_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 (2048-bit key) header.d=nsrc.org header.b="GVIUILB3"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="PzKFW2lU"
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 nfWfRN-0RY5T for <v6ops@ietfa.amsl.com>; Sat, 13 Apr 2024 10:56:19 -0700 (PDT)
Received: from wfout1-smtp.messagingengine.com (wfout1-smtp.messagingengine.com [64.147.123.144]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 93583C14F5EA for <v6ops@ietf.org>; Sat, 13 Apr 2024 10:56:19 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailfout.west.internal (Postfix) with ESMTP id 4F9CE1C0007F; Sat, 13 Apr 2024 13:56:18 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sat, 13 Apr 2024 13:56:18 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nsrc.org; h=cc :content-transfer-encoding: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=fm3; t=1713030977; x=1713117377; bh=bk5CIiQFexC030KvcQOVVYO6wpkQ2qi7gExIM/aotws=; b= GVIUILB39o5OtCPCDgtaT6GNo05ekgOENwz44qNj2ILs37S8cGLTBqaM5kmB9oMJ 5PHKrZrzAjE4ughaJNh7W+HkIr3Gi4TuK+g22BT6teoQwFqn5S1yr9t9nFDwQNep vxh/JPJ/m3lGC/rAlPig5JA0LR7paEFj5teueZxDLSxJFto3HZyoPv9z+u8kWfp7 sx8Pw/UeEgGPtYzTP8v5Vc62HU559ahP3i5uoKzE5fF8bsZAtoPDl4h9znc0Y0U0 saglA3GsgpLGYj6Etwq+EcmIYHet+XWnnwaOy1jupLlV3cVzAV3hkXvPW5TrtP5E SwZlBOpJWAWBhTPeS2v+8g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1713030977; x= 1713117377; bh=bk5CIiQFexC030KvcQOVVYO6wpkQ2qi7gExIM/aotws=; b=P zKFW2lU0jKik4z11vHg2bPNXIWD/V7kzoCBcgfIlX02tszamRpijUHRhFKnRr9/O IVALLf/8gF6LoTf0ZJfwfWLxNSAU31AlUrMtF5NBSbWFrPUFGHIlxNXiR1eCejb7 fV9B7dVHnA4Qky7FKGdkPvCf/jhqAUMQygLO3piTYgmt6NDiiKRuGP8dnwwJLIZB J3Fbqgz8I9Gi+7Mv3GksWKHiaPZOdaUrQN7KnlRKWe1GVKTC9ACKQT1TjmeWbgP+ w5VtI3ooLQdkgB66XfE7l8+vOxJGmaz0RrNbMPfNFg2+uGX2xT8hAlW2oiyhLuU4 7oFN7xC+BfWnEoP4R4Ovw==
X-ME-Sender: <xms:QMcaZq_-jTfm48wSmGFwBgjkRNV_eOGFdOaSUb0g3xv49bAWqJRYBw> <xme:QMcaZqvGkA2ELD-FsQhLyuf2n4hiUlsbXeOedjzkwscCTmQMugedKN9f8BCCD37M0 miOIn4wxJeMVd-dWtw>
X-ME-Received: <xmr:QMcaZgCRJkCDvuA2_1yoA9yvQNM6ka7yo6dXv7AwPJcHG3XgKyTrJz2TFjQYbek>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudeiiedguddvudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpeeurhhi rghnucevrghnughlvghruceosghrihgrnhesnhhsrhgtrdhorhhgqeenucggtffrrghtth gvrhhnpeevhfekjeeuueeutefgheejheekteeltdevtddvhfevhfefveejvdfgfeeiteet heenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrh hirghnsehnshhrtgdrohhrgh
X-ME-Proxy: <xmx:QMcaZicpleflPjpIHtcDfhqejBmBexp9YSxmWyOFz6Z0IBhomxPWhQ> <xmx:QMcaZvNTs5vCwmUFxefnZa6ZRoQniAjVTt34FN0ZNXb7TcXPoQmjWQ> <xmx:QMcaZsmssQfCiasr0dyvDmVIf5wKTUJUV21YmcCqZW4KnAm0pAl8qg> <xmx:QMcaZhu5zPFCDRZXysA6iSsWwqioTBAyWmDFwW4AaqK87mOsfULadg> <xmx:QccaZkowNC3cy4SnAmzQnAgvdhPy9BGq-slsxWs4p5r2bqC7X7yRRsnz>
Feedback-ID: i8f09498f:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 13 Apr 2024 13:56:16 -0400 (EDT)
Message-ID: <6912930d-54b8-449f-bfec-577d2a97658a@nsrc.org>
Date: Sat, 13 Apr 2024 18:56:14 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
To: "Soni \"They/Them\" L." <fakedme+ipv6@gmail.com>, Tore Anderson <tore@fud.no>, IPv6 Operations <v6ops@ietf.org>
References: <91ee2782-c98a-4ccf-ae8f-71be571420b6@gmail.com> <3c1e1f55-555f-42f2-b472-5f3a3a0c40a6@fud.no> <547145b0-21c0-457a-af58-2eeb8f44422d@nsrc.org> <b081fb6a-116c-4012-878b-636282d8cf9a@gmail.com>
From: Brian Candler <brian@nsrc.org>
In-Reply-To: <b081fb6a-116c-4012-878b-636282d8cf9a@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/TiAtC_AtRteS24UABQyBqxoh9dE>
Subject: Re: [v6ops] Our IPv6-only home network and future experiments
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Apr 2024 17:56:24 -0000

On 13/04/2024 18:44, Soni "They/Them" L. wrote:
> Oh. That makes sense. So the extra IPv6(s) would only be necessary for 
> providing services to IPv4-only and CLATless dual-stack hosts, we're 
> guessing? 

If you mean a CLAT sitting in a router, providing CLAT service to 
downstream hosts (IPv4/dual-stack), then yes.

However, the libc-based CLAT is a essentially a CLAT embedded in the 
endpoint application, and provides service only to that application.