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

Havard Eidnes <he@uninett.no> Fri, 29 April 2022 08:35 UTC

Return-Path: <he@uninett.no>
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 8E7F6C13A8D0; Fri, 29 Apr 2022 01:35:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uninett.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 f4KC8LkPY0tL; Fri, 29 Apr 2022 01:35:09 -0700 (PDT)
Received: from smistad.uninett.no (smistad.uninett.no [IPv6:2001:700:1:0:eeb1:d7ff:fe59:fbaa]) (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 A9498C13A100; Fri, 29 Apr 2022 01:35:07 -0700 (PDT)
Received: from smistad.uninett.no (smistad.uninett.no [158.38.62.77]) by smistad.uninett.no (Postfix) with ESMTP id ED6FB43F3D7; Fri, 29 Apr 2022 10:35:02 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uninett.no; s=he201803; t=1651221303; bh=HcmanGXHvQ7FFbSftckwpaUv5KLURzJJFxaPrfDXyT8=; h=Date:To:Cc:Subject:From:In-Reply-To:References:From; b=S7oEpiAQ4IuSNqXCJLPyho3wSDYye3VpleIpatYj9+XkyxH6CVkMygKoLzS3P90cP rUn/fbPtH3bTCCH22IsUQMDjx3e/BvHLgr4qHXeQhKy39v8kmypBjnNf+XHtEJmx6c 9EGaISbevKqKoO/rfRPfwywG9IjAryh/JrnkGJY0=
Date: Fri, 29 Apr 2022 10:35:02 +0200
Message-Id: <20220429.103502.2066576388117338604.he@uninett.no>
To: markzzzsmith@gmail.com
Cc: xipengxiao=40huawei.com@dmarc.ietf.org, ipv6@ietf.org, v6ops@ietf.org
From: Havard Eidnes <he@uninett.no>
In-Reply-To: <CAO42Z2wiebCOPmtcEOJ3rOaZEpHE7qFZZTf5KLWybSsL6rOd9Q@mail.gmail.com>
References: <CAFU7BAST-oNGpy4JvODDsf=8eS69hV8XCi8OgEHBkkoujRN3Rw@mail.gmail.com> <699f556a3eac41179a80d2cc8749a191@huawei.com> <CAO42Z2wiebCOPmtcEOJ3rOaZEpHE7qFZZTf5KLWybSsL6rOd9Q@mail.gmail.com>
X-Mailer: Mew version 6.8 on Emacs 26.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/AERMti_sSrMftCcLa4ooLCZcoiM>
Subject: Re: [v6ops] Vicious circle [ULA precedence [Thoughts about wider operational input]]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.34
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, 29 Apr 2022 08:35:12 -0000

>> That said, I very much agree with Kevin Meyer: "If you want
>> more Enterprises participating in the IETF discussions and
>> improving IPv6 uptake, start thinking about meeting them where
>> they are. And to be crystal clear - NAT is where they are and
>> where they will be for quite a while".
>>
>> My point is, given PCI DSS 4.0 (what Jen wrote as PCR DSS
>> 4.0), we should tell enterprises they no longer need NAT. But
>> if some enterprises still insist, respect their decision.
>
> Ignore them. IPv6 doesn't solve any problem they have, and adding NAT
> to IPv6 still won't solve any problem they have, because IPv6 still
> won't solve a problem they have.

I agree.

Some user groups are always going to be the most conservative
when it comes to adopting "new" technologies (I use quotation
marks as I hesitate to describe IPv6 as new...), for whatever
reason.

My guess: this situation will probably not change until a
destination they care about is only reachable via IPv6.  So far,
few if any have gone that route (for good reasons, of course), as
IPv4 is still the "ligua franca" of the Internet.

Regards,

- Håvard