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

Simon <linux@thehobsons.co.uk> Thu, 28 April 2022 09:14 UTC

Return-Path: <linux@thehobsons.co.uk>
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 1396AC159821; Thu, 28 Apr 2022 02:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 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] 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 eRl5HEvOL9BU; Thu, 28 Apr 2022 02:14:36 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [80.229.10.150]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9520CC1595FC; Thu, 28 Apr 2022 02:14:34 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from smtpclient.apple (unknown [85.255.235.229]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id A1D13110001; Thu, 28 Apr 2022 09:14:28 +0000 (UTC)
From: Simon <linux@thehobsons.co.uk>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Thu, 28 Apr 2022 10:14:25 +0100
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> <BN8PR07MB70760D9693580F5BDCB61DD995F89@BN8PR07MB7076.namprd07.prod.outlook.com> <CAKD1Yr3Z9wGQ+uiA2WcW00MrOiLyHs+bSoFjHVtrixCi2qp4DA@mail.gmail.com> <BN8PR07MB7076A6456CAB48EF428D6E8695F89@BN8PR07MB7076.namprd07.prod.outlook.com> <65d0d9ac-77fc-c200-09e3-0c3949ca1541@gmail.com> <CAN-Dau2FS99ewfgH8xk-jSJFCnO92CJV9ZC98DUE2UDR7V1Eww@mail.gmail.com> <CANMZLAYbpZBDA8uFnJqfWfWTQ4S9RN4a-DqWe36qzfAfDtXiQA@mail.gmail.com> <CAN-Dau0BjRR2_7xz38DpJsz0Y=Z_8bV5n-=Eh1QUVEDzqVxmaA@mail.gmail.com> <CAPt1N1=H=eAyRu0JcHnLpZEUizDZ4Kj0VwPu=0nM=Wn+y3Ho1w@mail.gmail.com> <CAM5+tA_4rtSkgEuRUFZ2LYr6i8a7vWeKODYieVARF3RbRvgRww@mail.gmail.com> <BN8PR07MB7076DE3E745CB916FB81879595FA9@BN8PR07MB7076.namprd07.prod.outlook.com> <ADAE42CE-448F-42F5-89BE-692F493E2DC8@consulintel.es> <CAM5+tA_ksJ+agY1tze1-zPHLsgYFgjEYtnuPs+ffZbnRqiHytw@mail.gmail.com> <BAD082DA-0958-4926-B3E5-4E4599A75078@consulintel.es> <BN8PR07MB7076564E50C0DAFBFAB950FD95FA9@BN8PR07MB7076.namprd07.prod.outlook.com> <CAPt1N1ncVkekecS=dBHSR3WtaEMruy55Udxy0WSMGTgbN24pKw@mail.gmail.com> <CAM5+tA8-Zqka-vZ9jRL3wn0dtfuJj0ECx_k9prwyS2ypisaPtw@mail.gmail.com>
To: 6man list <ipv6@ietf.org>, v6ops list <v6ops@ietf.org>
In-Reply-To: <CAM5+tA8-Zqka-vZ9jRL3wn0dtfuJj0ECx_k9prwyS2ypisaPtw@mail.gmail.com>
Message-Id: <FB031B76-7E88-4824-876F-D1A05F8D2215@thehobsons.co.uk>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/VYrK8qL1kW66bOE21Py4gcIbGR4>
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: Thu, 28 Apr 2022 09:14:37 -0000

Nick Buraglio <buraglio@es.net> wrote:

> I also find it interesting that "keeping ipv4" is
> even a reasonable choice to entertain. Clearly IPv6 is the long term
> path forward, and it would behoove us to help with that simply from a
> protocol simplification perspective. IPv4 isn't "working for them"
> it's the standard they are evaluated against

Translation (as previously mentioned):
The IPv6 community needs to engage with this other regulatory community to get them to bring their standard into the 21st century.

As long as the PCI standard effectively mandates IPv4 & NAPT then it’s going to be an uphill struggle.


On a much smaller scale I’ve been on the receiving end of this with a previous work hat on. Unknown to us in the IT dept, we would get various audits - insurers, finance auditors, parent company, blah, blah. Often the first we’d know about it would be manglement coming to us and saying “we need to do X because auditors” - no matter whether X is a sensible thing to do or not, or even if the technology we were using at the time supported it. Not running Windows servers would often confuse them !

Unfortunately, we were rarely brought in at the right stage so we could have that discussion where the auditor needs to tick a box, and we could explain “we do it this way, for these reasons - and that supports the objective you are trying to tick a box for”.


Arguing that trying to change the PCI requirements will take a decade, therefore we should bother, is simply kicking the problem down the road. The sooner “someone” starts that conversation, the sooner that 10 years will come round. Leave starting that conversation for another year means it’ll be 11 years, and so on.
As the proverb says "A journey of a thousand miles begins with a single step”.

And I guess the “someone” needs to be a person (or group) who have feet in both camps (IPv6 and PCI).

Simon