Re: [v6ops] ULA precedence [Thoughts about wider operational input]

Erik Auerswald <auerswald@fg-networking.de> Mon, 25 April 2022 07:53 UTC

Return-Path: <auerswald@fg-networking.de>
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 3DA4F3A0598; Mon, 25 Apr 2022 00:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xgODPH7y9vMR; Mon, 25 Apr 2022 00:53:46 -0700 (PDT)
Received: from mailgw1.uni-kl.de (mailgw1.uni-kl.de [IPv6:2001:638:208:120::220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76F483A041A; Mon, 25 Apr 2022 00:53:44 -0700 (PDT)
Received: from mail.fg-networking.de (mail.fg-networking.de [131.246.197.23]) by mailgw1.uni-kl.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 23P7rYjm182286 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 25 Apr 2022 09:53:34 +0200
Received: from login.fg-networking.de (login.fg-networking.de [131.246.197.41]) (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 mail.fg-networking.de (Postfix) with ESMTPS id 11CBF2009B; Mon, 25 Apr 2022 09:53:28 +0200 (CEST)
Received: by login.fg-networking.de (Postfix, from userid 11002) id E8D91155; Mon, 25 Apr 2022 09:53:27 +0200 (CEST)
Date: Mon, 25 Apr 2022 09:53:27 +0200
From: Erik Auerswald <auerswald@fg-networking.de>
To: Lorenzo Colitti <lorenzo@google.com>
Cc: Ted Lemon <elemon@apple.com>, Nick Buraglio <buraglio@es.net>, v6ops list <v6ops@ietf.org>, 6man list <ipv6@ietf.org>
Message-ID: <20220425075327.GB67548@fg-networking.de>
References: <CAM5+tA8WvjvWirxqE6kQ9LQAG0NcpWyCLGVooB=G7gZ9ETb2zQ@mail.gmail.com> <20220424172743.GA218999@fg-networking.de> <CAKD1Yr1v0Tkh+pWD-ts=PL3gZf7Qj6OHW6Cuvj8iGcSSMibjew@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAKD1Yr1v0Tkh+pWD-ts=PL3gZf7Qj6OHW6Cuvj8iGcSSMibjew@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/BDira3vkbdFxIW-d59Eec-99Oo8>
Subject: Re: [v6ops] ULA precedence [Thoughts about wider operational input]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Apr 2022 07:53:51 -0000

Hi,

On Mon, Apr 25, 2022 at 09:16:14AM +0900, Lorenzo Colitti wrote:
> On Mon, Apr 25, 2022 at 2:28 AM Erik Auerswald <auerswald@fg-networking.de>
> wrote:
> 
> >  "Since ULAs are defined to have a /48 site prefix, an implementation
> >   might choose to add such a row automatically on a machine with
> >   a ULA."
> >
> > The result is that only the local ULA prefix, i.e., exactly the
> > local IPv6 addresses, are preferred over IPv4 (and IPv6 GUA).
> > This should be exactly what is needed to use ULA addresses inside
> > an organization, or for a lab.
> > [...]
> > Implementing the non-normative suggestion from Section 10.6 of RFC
> > 6724 would in all likelihood result in making ULA usable for local
> > tests and even first steps in deploying IPv6.  ULA addresses would
> > only be used locally.  Existing IPv4 based Internet access would not
> > be impaired by adding IPv6 ULA.
> >
> 
> That does seem like it might make ULA more useful, yes.
> 
> Additionally, maybe we could clarify that the longest-prefix match rule
> does not apply to ULAs outside the same /48? I think that would fix
> the issue observed by +Ted Lemon <elemon@apple.com> in home networks:
> https://datatracker.ietf.org/meeting/113/materials/slides-113-6man-source-address-selection-for-foreign-ulas-00
> .

This is the reason for using a different label for the local ULA
/48 prefix.

> [...]

Kind regards,
Erik
-- 
Dipl.-Inform. Erik Auerswald
Gesellschaft für Fundamental Generic Networking mbH
Geschäftsführung: Volker Bauer, Jörg Mayer
Gerichtsstand: Amtsgericht Kaiserslautern - HRB: 3630