Re: [v6ops] IPv6 mostly for DS-Lite

Ole Troan <otroan@employees.org> Fri, 22 March 2024 07:03 UTC

Return-Path: <otroan@employees.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 9237BC14F60E for <v6ops@ietfa.amsl.com>; Fri, 22 Mar 2024 00:03:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, T_SCC_BODY_TEXT_LINE=-0.01, 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=employees.org
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 RPg_7iZT1r2F for <v6ops@ietfa.amsl.com>; Fri, 22 Mar 2024 00:03:36 -0700 (PDT)
Received: from proxmox01.kjsl.com (proxmox01.kjsl.com [204.87.183.6]) (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 C1BC2C14F5EF for <v6ops@ietf.org>; Fri, 22 Mar 2024 00:03:36 -0700 (PDT)
Received: from proxmox01.kjsl.com (localhost.localdomain [127.0.0.1]) by proxmox01.kjsl.com (Proxmox) with ESMTP id 4A948E3549; Fri, 22 Mar 2024 07:03:36 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=employees.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:from:from:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to; s=prox2023; bh=cfKgvYZu7hs1dOi7 9o2iZG8vrJiyVrjTzLL+obcurQA=; b=HawC8Kwm28S+j3fYv5c05IM4GeNfam89 RF6sbzaRE+4GDQAosNPbrIk1wKVM3+k5XMnCu41ToQbYsaGXknJpQYFpNwkMCM+q 6lI/kxVzWRMkW0FLevbgeCo2dyNTQS2SYOdDRZ3VG1ZkICwEnxmACRNsT80imGye 2+D0+JcT2i+/ws7oXCd9oFwj6H+CkUY9ijSepS+ZTd9Xd65rpBdhXjkKSDBb2iAs mvjkrouxVaxQluu/HlrvYJEoPA7fJn9fpUJ0PmzWXKF3Fesy627DKfE8uqiKlM5A bX06ShAWutkg46x5BYPvXbKpBjSu/Z2erF7wtSSNOcYEYL632g74DQ==
Received: from clarinet.employees.org (clarinet.employees.org [198.137.202.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by proxmox01.kjsl.com (Proxmox) with ESMTPS id 2C798E3545; Fri, 22 Mar 2024 07:03:36 +0000 (UTC)
Received: from smtpclient.apple (unknown [IPv6:2001:4650:c3ed:37a:1e9f:54b:1ba9:d468]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 6EAE94E11BF1; Fri, 22 Mar 2024 07:03:35 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <9b0b43fc-739e-4296-801e-b08553787de3@gmail.com>
Date: Fri, 22 Mar 2024 08:03:22 +0100
Cc: Mark Andrews <marka@isc.org>, v6ops <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D06D056-DF9D-4BE7-9206-0D4613E4D640@employees.org>
References: <63a002b6-e3e8-4846-a0bf-2792b04eff56@gmail.com> <C02015A8-7553-49DA-8418-26362286B5EE@isc.org> <9b0b43fc-739e-4296-801e-b08553787de3@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/DpYnjFfDLCqf0Sl7EthSN29K2n8>
Subject: Re: [v6ops] IPv6 mostly for DS-Lite
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: Fri, 22 Mar 2024 07:03:40 -0000

>> The market has picked both DS-lite and DNS64/NAT64. Both are deployed by ISPs.  One actually worked. The other required a series of corrections to be put out making it more visible to the IETF.
> 
> I don't think anyone is saying "switch them off". It's a question of where we spend IETF effort.
> 
>> Daisy chaining DS-lite and 464XLAT will be a real mess as both use the same IPv4 address rage for source addresses.  
> 
> That is... unfortunate.

In the example where the hosts gets IPv4 via 464XLAT and the site gets IPv4 access via DS-lite, then it should be better if the host used the ISP NAT64 instance instead of the CPE NAT64 instance.


> 
>> Or are you saying only those that can get full dual stack can deploy IPv6-mostly.
> 
> I'm not sure I can parse that. The end point must be that applications *see* a full dual stack whatever mechanism is deployed on the wire. That applies to every host on an IPv6-mostly network (unless there is such a thing as an IPv4-only host, I suppose).

464XLAT in itself has 2-3 NATs. Chain it with DS-lite, you would have another 2? Nice! :-)
_If_ all hosts (very unlikely of course) supported 464XLAT then the CPE could of course be IPv6 only.
Alternatively, the CPE could act as a CLAT and proxy for those IPv4 only nodes that don’t.
At least that’s a path to a single mechanism.

Cheers,
Ole