IETF Logo Mail Archive

Re: [v6ops] [EXTERNAL] Re: FYI: Microsoft's latest on CLAT

Ole Troan <otroan@employees.org> Mon, 11 March 2024 07:30 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 7DC07C14F5F3 for <v6ops@ietfa.amsl.com>; Mon, 11 Mar 2024 00:30:12 -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 JNeZJn4J7law for <v6ops@ietfa.amsl.com>; Mon, 11 Mar 2024 00:30:08 -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 E70BCC14F5E4 for <v6ops@ietf.org>; Mon, 11 Mar 2024 00:30:08 -0700 (PDT)
Received: from proxmox01.kjsl.com (localhost.localdomain [127.0.0.1]) by proxmox01.kjsl.com (Proxmox) with ESMTP id 5139EE724B; Mon, 11 Mar 2024 07:30:08 +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=w2viIbZehjpd1FvY zZPlXWEvVJ969KpUHea/l+4/6mA=; b=QN+BHReCkkTupeyLup0Hs+5ti/zPKcXm 5tD8etiuen4Lh8WnMntOEQOgUcTY90ut1ImyQUUHAlvzL36GlKON1EIMrH0plrHY qN9wxADuT4rAQrPf/VjkuNAmCRmj9q+NFN5sakbCng/OxWR/zl+jblRdgeeBvNVr tr7d/GnQox1OyCT7B1eEujbPKjBPiWqiARFvDpkTRoPEecycYaOXAd1HfTauOGFA msGyDeQHvQ8xaMk7KFWZiDtuDh+c9rKNMvqS6am7zWCvDk69+HQmUK5xgjpKV9ve igfbXanQKXcNKNfy6mfAVK4n3QfCBnI4mSDWvYY4Fbsr0C+KCHV5Sw==
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by proxmox01.kjsl.com (Proxmox) with ESMTPS id 304D7E7246; Mon, 11 Mar 2024 07:30:08 +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 51D124E11B45; Mon, 11 Mar 2024 07:30:07 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <SA1PR00MB134236D88803AC93AD95181AFA252@SA1PR00MB1342.namprd00.prod.outlook.com>
Date: Mon, 11 Mar 2024 08:29:53 +0100
Cc: Tore Anderson <tore@fud.no>, Jen Linkova <furry13@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <07DF9F54-BEF4-48BC-9096-840A5B839DDA@employees.org>
References: <CAFU7BAQsnionnO_VZoxAnqAKad_cuQbyHzFKK4XMai_Hw8-Kyg@mail.gmail.com> <56FFAFE7-94B4-47BD-9139-1A1FA83FB472@employees.org> <1113ad66-424a-4c49-bbab-713916fe357a@fud.no> <SA1PR00MB134236D88803AC93AD95181AFA252@SA1PR00MB1342.namprd00.prod.outlook.com>
To: Tommy Jensen <Jensen.Thomas=40microsoft.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/uGwjeWfpV8DBR3Mlnhp72IKpB7o>
Subject: Re: [v6ops] [EXTERNAL] Re: FYI: Microsoft's latest on CLAT
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, 11 Mar 2024 07:30:12 -0000

Tommy,

I think it’s a bad idea to tie the IPv6 addressing model to the IPv6 mostly/XLAT mechanism.
In an enterprise that requires centralized management of addressing for policy purposes, how do you foresee that Enterprise doing IPv6 mostly?

It would nice if we could position IPv6 mostly as a mechanism for all Enterprises, and not get ourselves into a situation where transitioning off IPv6 mostly to IPv6 only would be awkward either.

O.


> On 10 Mar 2024, at 18:43, Tommy Jensen <Jensen.Thomas=40microsoft.com@dmarc.ietf.org> wrote:
> 
> >>> IPv6 mostly in itself is not incompatible with a single IPv6 address. That’s an implementation choice....interesting to see where Microsoft lands on this one.
> >>I believe Tommy already mentioned...
> 
> Jen is correct in linking to our draft, as we are endeavoring for our proposed text and future product to be in alignment. Deploying IPv6 but allowing only a single /128 per client does not seem like a scenario we should be designing for going forward.
> 
> >...e.g., by ensuring that an outbound TCP/UDP connection assigned 192.0.2.1:portX claims [2001:db8::1]:portX automatically... [2001:db8::1]:portY may be used by a regular native IPv6 socket simultaneously.
> 
> Note that port collision will occur if an IPv4 socket and an IPv6 socket wish to use the same port, where they should not have to worry about that (it would be a regression from dual stack networking introduced by the implementation choice).
> 
> Thanks,
> Tommy
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email