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

Erik Auerswald <auerswald@fg-networking.de> Mon, 25 April 2022 07:48 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 D5B063A0BE6; Mon, 25 Apr 2022 00:48:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 5Yutvdigmz2G; Mon, 25 Apr 2022 00:48:56 -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 CEE303A1139; Mon, 25 Apr 2022 00:48:37 -0700 (PDT)
Received: from mail.fg-networking.de (mail.fg-networking.de [IPv6:2001:638:208:cd01::23]) by mailgw1.uni-kl.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 23P7mKTT177434 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 25 Apr 2022 09:48:20 +0200
Received: from login.fg-networking.de (login.fg-networking.de [IPv6:2001:638:208:cd01::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 25D342009C; Mon, 25 Apr 2022 09:48:16 +0200 (CEST)
Received: by login.fg-networking.de (Postfix, from userid 11002) id E3B59155; Mon, 25 Apr 2022 09:48:16 +0200 (CEST)
Date: Mon, 25 Apr 2022 09:48:16 +0200
From: Erik Auerswald <auerswald@fg-networking.de>
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>
Cc: Nick Buraglio <buraglio@es.net>, v6ops list <v6ops@ietf.org>, 6man list <ipv6@ietf.org>
Message-ID: <20220425074816.GA67548@fg-networking.de>
References: <CAM5+tA8WvjvWirxqE6kQ9LQAG0NcpWyCLGVooB=G7gZ9ETb2zQ@mail.gmail.com> <20220424172743.GA218999@fg-networking.de> <3bad47a019754cc5a97a33f46da94179@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3bad47a019754cc5a97a33f46da94179@huawei.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/T08bqrbiUvzoPqHTVvcqfPmYjx8>
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:49:01 -0000

Hi Eduard,

On Sun, Apr 24, 2022 at 08:12:29PM +0000, Vasilenko Eduard wrote:
> [...]
> 2. Attach a special Label (redundant action because FC/7 already
> has unique Label=13)

The different label to differentiate between locally used ULA prefix(es)
and the remaining ULA space is intentional.

> Imagine the situation where only one router on the link announces
> ULA PIO, but the other one - GUA PIO.  (Routers are not in sync
> for announcements).

Using different first hop gateways for GUA and ULA is another
problem.  It would be nice if hosts would (optionally) not consider
a gateway announcing a ULA prefix as default gateway, but only for
ULA reachability.

> [...]

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