Re: [v6ops] draft-buraglio-v6ops-ula discussion

Fernando Gont <fgont@si6networks.com> Fri, 05 August 2022 10:08 UTC

Return-Path: <fgont@si6networks.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 D9E49C15948E for <v6ops@ietfa.amsl.com>; Fri, 5 Aug 2022 03:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 BTFXgTQTVIN4 for <v6ops@ietfa.amsl.com>; Fri, 5 Aug 2022 03:08:42 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (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 E4C08C14CF10 for <v6ops@ietf.org>; Fri, 5 Aug 2022 03:08:41 -0700 (PDT)
Received: from [IPV6:2001:67c:27e4:c::1001] (unknown [IPv6:2001:67c:27e4:c::1001]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id ACF4D280261; Fri, 5 Aug 2022 10:08:34 +0000 (UTC)
Message-ID: <d69fe9b4-7a15-6c87-7cf6-32eb9a86df29@si6networks.com>
Date: Fri, 05 Aug 2022 07:08:31 -0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1
Content-Language: en-US
To: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>, Fred Baker <fredbaker.ietf@gmail.com>, v6ops list <v6ops@ietf.org>
References: <CABKBHweedb9Cmefy3M+jBkX3P_ML++a2N7SpSKVcZ0gL2U5K8w@mail.gmail.com> <D28DC500-06C3-41EE-BB07-0B9DF630B288@cisco.com>
From: Fernando Gont <fgont@si6networks.com>
In-Reply-To: <D28DC500-06C3-41EE-BB07-0B9DF630B288@cisco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_a7msaRX_8KmTWzpUePC348bKnI>
Subject: Re: [v6ops] draft-buraglio-v6ops-ula discussion
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, 05 Aug 2022 10:08:43 -0000

Hi, Eric,

On 5/8/22 06:45, Eric Vyncke (evyncke) wrote:
> [Wearing no special hat in this reply]
> 
> I would prefer NOT adopting this I-D in his current state for the 
> reasons listed below:
> 
> This may be an unexpected behavior, but I still prefer using global IPv4 
> addresses (not RFC 1918) rather than ULA. The I-D should cover this.

Adoption question aside, I believe the I-D should probably keep its 
focus on the narrow/specific issue it is meant to solve.. (Unfotunately, 
we don't have  a good track record discussing ULAs :-) )



> In section 3, there is:
> 
>    “necessitate the immediate update to [RFC6724] to better reflect
>     the original intent of the RFC.”
> 
> The “immediate update” kinds of contradict the current intended status 
> of “informational”. Moreover, I am unsure whether this I-D authors and 
> the V6OPS WG can declare anything about the “original intent of RFC 
> 6724” as it was a 6MAN WG document ;-)

If the intent is to provide a problem statement -- as I believe it was 
-- I'd definitely focus on the probably statement, or at most hint 
solutions, rather than require them (agree with you on this one).




> Finally, with free IPv6 GUA, I wonder why the IETF should spend time on ULA.

Well, my rule of thumb in this respect is: fix-it, or ditch it ;-).
I do believe there's value in ULAs for some scenarios/cases.
However, i there was consensus that they are just useless, I'd rather 
formally deprecate them that keep them lying around.

They are indeed used here and there. e.g., coincidentially just a few 
minutes ago:

fgont@laptop:~/code/ipv6toolkit/tools$ sudo blackhole6 www.google.com 
do8 icmp
SI6 Networks IPv6 Toolkit (current)
blackhole6: A tool to find IPv6 blackholes
Tracing www.google.com (2800:3f0:4002:810::2004)...

Dst. IPv6 address: 2800:3f0:4002:810::2004 (AS15169 - GOOGLE, US)
Last node (no EHs): 2800:3f0:4002:810::2004 (AS15169 - GOOGLE, US) (8 
hop(s))
Last node (DO 8): fc00:0:200:6c::1 (AS Unknown - Unknown organization) 
(3 hop(s))
Dropping node could not be determined (you may want to try again)

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494