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

Philip Homburg <pch-v6ops-11@u-1.phicoh.com> Mon, 25 April 2022 11:10 UTC

Return-Path: <pch-b28DE43C2@u-1.phicoh.com>
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 408173A1785; Mon, 25 Apr 2022 04:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 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] autolearn=unavailable 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 F64_F2ND9DUl; Mon, 25 Apr 2022 04:10:24 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [IPv6:2a10:3781:2413:1:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 076523A1786; Mon, 25 Apr 2022 04:10:23 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #158) id m1niwbi-0000JyC; Mon, 25 Apr 2022 13:10:18 +0200
Message-Id: <m1niwbi-0000JyC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
Cc: Vasilenko Eduard <vasilenko.eduard=40huawei.com@dmarc.ietf.org>, 6man list <ipv6@ietf.org>
From: Philip Homburg <pch-v6ops-11@u-1.phicoh.com>
Sender: pch-b28DE43C2@u-1.phicoh.com
References: <CAM5+tA8WvjvWirxqE6kQ9LQAG0NcpWyCLGVooB=G7gZ9ETb2zQ@mail.gmail.com> <20220424172743.GA218999@fg-networking.de> <CAKD1Yr1v0Tkh+pWD-ts=PL3gZf7Qj6OHW6Cuvj8iGcSSMibjew@mail.gmail.com> <0afe25f5-52b7-a438-0696-cf8b0a83c2dc@gmail.com> <m1niw9v-0000JkC@stereo.hq.phicoh.net> <81d1bfa5857d4558adaea9da2ef94bdc@huawei.com>
In-reply-to: Your message of "Mon, 25 Apr 2022 11:00:20 +0000 ." <81d1bfa5857d4558adaea9da2ef94bdc@huawei.com>
Date: Mon, 25 Apr 2022 13:10:11 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/8BD3XVEOuSFNSiTakVGG2_JDfBo>
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 11:10:27 -0000

In your letter dated Mon, 25 Apr 2022 11:00:20 +0000 you wrote:
>What you proposed (separate ULA prefix for NAT) is robust and solid but very h
>eavy - it would need a big change for many RFCs (new address type).

Why would that change many RFCs? The introduction of ULA didn't touch
many RFCs.

We would need an RFC that defines the new space and update the policy
table (if it needs updating at all).

>Would you agree to the tradeoff: assume that GUA PIO is absent for ULA+NPT cas
>e.
>Then I do not see a problem in the implementation: just ULA priority about IPv
>4 (it is not mandatory to put it in priority above GUA) would be enough.
>This is the minimal change for RFC 6724 only.

This a good example of something that is not robust. And why we need a
good description of use cases.

You imply that ULA+NPT only happens in networks that do not have GUA. A
counter example would a be network that wants to use ULA+NPT for all 
outgoing traffic, but has GUAs on servers to receive requests.