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

Brian Candler <brian@nsrc.org> Mon, 15 April 2024 07:17 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 54477C14F5F2 for <v6ops@ietfa.amsl.com>; Mon, 15 Apr 2024 00:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nsrc.org header.b="EDka8azM"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="WrZ4wBBk"
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 QzRKUouMmAAC for <v6ops@ietfa.amsl.com>; Mon, 15 Apr 2024 00:16:57 -0700 (PDT)
Received: from fout7-smtp.messagingengine.com (fout7-smtp.messagingengine.com [103.168.172.150]) (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 8A9F4C14F68C for <v6ops@ietf.org>; Mon, 15 Apr 2024 00:16:57 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfout.nyi.internal (Postfix) with ESMTP id 0728C13800E0; Mon, 15 Apr 2024 03:16:56 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 15 Apr 2024 03:16:56 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nsrc.org; h=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=fm3; t=1713165416; x=1713251816; bh=U7hvllhW9s NBbl1LbEG+WfXNAvsfuYofxfsCum5c2ZQ=; b=EDka8azMep+qr2ltom7jIzYz1Z X1DEbyzw2DwNSOuYFk5K5VRNnjqXDU6KKGjO/oxkS5AtmSag7REK55Q/CSY/vUEa BRAOS1+y/nsU5x+NP9q8PoBFm1KEm0FHHvZuOM4ZWJZZR7fJcvfyXTnkvs63ga4u m2tKDm66+RrmDpNNd81XKJcGYwuctdXiJ3GOM5QV9lfCTuCp2OJNGhbR9LXcvJyT sW8hOAAAJVEtXxBD3r+8b/HUx66cffBGL8p/RAISV8rFY/aLSg3xEfFYqo6Scdk+ q57asNVG9Aj/q2eZdnTHKk58YDfpFP5k+OQEa1GuEswWdHQjHE1+hcLjRYZA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1713165416; x=1713251816; bh=U7hvllhW9sNBbl1LbEG+WfXNAvsf uYofxfsCum5c2ZQ=; b=WrZ4wBBkiT/bA8jr2RQo/JC1VPDoWTJDdn1A0Eo3Rcdl NwFjM+WZg6icay/dWYOq+DrVejXpK6bblijFqaYl43sKCWoG3hFnkD18ZN40iJh5 Yv0pt9KPBSwbuH+js4eCTk3b7nBxFYrEUBhNOxht6KSfBT88oyTA4LDJxezmSVUz Lisf16H+4ef8lC1xePorMqNNTafa+PH00ajfk1A0XL0Ef3Glk+wiBWC9jbrrr/AY Z7uYOwMF0UeVKirmxMLIH+Iumjx9WbHzfehJZLZGVXkNN2PXXTJvBL9umkMB83vx RV3rDJN8QJ1NJvk9MafbVncFsBx223mbTDo04YQ/AA==
X-ME-Sender: <xms:Z9QcZk65CZvi5fiUnb8Rs4Vgp1Wt5wqxvKvrwkrVslivUrgJcvwoFA> <xme:Z9QcZl4Wfn_IhjiLVRJxVpGe0M0_qfTqu6dekRq2UkTJPc47QfBQaUvUtIG4Ustl8 A55amnFubr_NrZXtKc>
X-ME-Received: <xmr:Z9QcZjdS0KriythcETHhvOrNZ7bVWqhfuWdnU3jItxNUKDAvSj1wt86BX9yKkiY>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudejuddgieehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtkfffgggfuffvfhfhjgesrgdtre ertddvjeenucfhrhhomhepuehrihgrnhcuvegrnhgulhgvrhcuoegsrhhirghnsehnshhr tgdrohhrgheqnecuggftrfgrthhtvghrnhepkeekgfevhfevheffiedthfejteeivdfgge dugeffleehleelkeefkeefgfffgfffnecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepsghrihgrnhesnhhsrhgtrdhorhhg
X-ME-Proxy: <xmx:Z9QcZpLXJ6bI1t5_xvndXGSjSKTUTzdiHNPvQjaiBX92moFmn6AaTg> <xmx:Z9QcZoK5fx2jSPMyxntFqcOx7uoIV9N9NKMlfMsBAZUEI-FOlPQYkQ> <xmx:Z9QcZqxky5CZMvtZQppSmwb68DUZW1POur0FWxog8Sw_L6kt1qiXWw> <xmx:Z9QcZsL2Ocxs8nMwvrc9_njAU-Upn6ihe1FbQAYcCfMFBLFvkQCMqQ> <xmx:Z9QcZtHbttDW4mml4_n2Fs3U0zg4RBSNub0n5jeeH8Wm60EDfdE5NR62>
Feedback-ID: i8f09498f:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 15 Apr 2024 03:16:55 -0400 (EDT)
Content-Type: multipart/alternative; boundary="------------fnd8l0Jt9FYi31ES4KRUKKho"
Message-ID: <5e65b7b4-b112-4875-a603-22b5e570619a@nsrc.org>
Date: Mon, 15 Apr 2024 08:16:53 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
To: Vasilenko Eduard <vasilenko.eduard=40huawei.com@dmarc.ietf.org>, "Soni \"They/Them\" L." <fakedme+ipv6@gmail.com>, IPv6 Operations <v6ops@ietf.org>
References: <91ee2782-c98a-4ccf-ae8f-71be571420b6@gmail.com> <7b89e8bd81674a61b364e1fec4176006@huawei.com>
From: Brian Candler <brian@nsrc.org>
In-Reply-To: <7b89e8bd81674a61b364e1fec4176006@huawei.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/8Z7xwvez_CA1fNKDuEPQNkSjP9o>
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: Mon, 15 Apr 2024 07:17:03 -0000

On 15/04/2024 08:03, Vasilenko Eduard wrote:
> The initiative looks strange for me.
> It has an assumption that some*old*  application insists to use IPv4 and this application*could not be changed*  to use IPv6 properly.

No, that's not at all what the underlying driver of this is.

Rather, the issue is what happens when a modern, well-written dual-stack 
application is running on an IPv6-only network, but needs to access an 
IPv4-only resource on the Internet.

The proposed approach allows the application to do DNS lookups, find 
only an A record, open an IPv4 socket and make a connection (as it would 
do on a dual stack network) - but this is transparently rewritten to an 
IPv6 connection to a PLAT with the IPv4 address embedded in the 
destination IPv6 address - i.e. 464XLAT.

This approach is cleaner than DNS64, where you pretend that every 
IPv4-only resource has a AAAA record that points to your local PLAT. It 
also means that an application can make a connection to an IPv4 literal 
address (e.g. 1.1.1.1) and it works.