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

Nick Buraglio <buraglio@es.net> Fri, 29 April 2022 01:16 UTC

Return-Path: <buraglio@es.net>
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 09882C15ED55 for <v6ops@ietfa.amsl.com>; Thu, 28 Apr 2022 18:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 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, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=es.net
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 y235M9gTOvwn for <v6ops@ietfa.amsl.com>; Thu, 28 Apr 2022 18:15:59 -0700 (PDT)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 ietfa.amsl.com (Postfix) with ESMTPS id DFFFDC15ED4E for <v6ops@ietf.org>; Thu, 28 Apr 2022 18:15:58 -0700 (PDT)
Received: by mail-lf1-x131.google.com with SMTP id p10so11495437lfa.12 for <v6ops@ietf.org>; Thu, 28 Apr 2022 18:15:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=es.net; s=esnet-google; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=4ElZq1QcBslZ/WU6LnWVDNmS+XW2MaZ4kAUDsR5Vtoo=; b=TlmaWWJdAhOcryibSF9UyLdh4DEpbeO0OkhS8/m0eIMKSGQ10uV7n11Ilj7FHAf7Fg C9WlGsW2z8HJJziU9EDXpf0xsNxlTC0JgiSc7gN4+QE1La3cNzuL8rW/lYIHOs68zugR opbLxexapXhIWAwjPClGTjYnfU+lV0wW2Bwf/3fQ4PDMtq9DvPoiMIokrSXGV7uFRu5/ m4FqKXERKTkGXGTKfgGBhCB6Rj8AjCQZFSQAbdmi3hMzOMkxvY/5yAQX30Vq53suRHRB yUOxS6Kdt9pmarb/P8i7wNSeQjEGE+6gVLQdQfJo4+bouqwCsOxFhp2c4xnAs6hMdv39 U8Hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=4ElZq1QcBslZ/WU6LnWVDNmS+XW2MaZ4kAUDsR5Vtoo=; b=v3kdwM/HKD5rgSV32GSTY7DEpuLzXFG7LJdJmScujgS/UudFRmPCjQPn3YX9/btEUP B3OWZbzEf7xZjY550L0ach3smyFrPNHnr3h+iKjhrSh0k0tGR8qcXHq31ZZmGJvqIVfz zU9hv3YxLkMmAByAubnVG+dtmxNyS1c+n91AtKvvKA73eZNFYnkwJ6jwNRTd/Be9Pmf6 e2LJYRK6Fb9br+tBSe3W0BkXcpf7W73MGpklLs8+srDNkcvzRZneY5l3FXqV26JTP0n8 ep00zk4Igm+Q2G4W5osxedF57qw6rmGL8KZDxUDBN/RxFMMErzKH/gdUep3ykE3Z3YNF TiVg==
X-Gm-Message-State: AOAM532jDL9k6TNc5Z0T3LCwkP+xRRql/o+geg4SKPRtvNzEVLgbApFe 1iFrmQ9/pHkjIvbBDGWXDwNeM+gGihQ1DAQ8ucZ3OvFLmwJQO/DSRzEK7tBxavqSugGbq7gEPiP fN9jiouSJiCDpoQRHY+wfIF2XLl+0LIa8Sz4ZtrZkIOCN2yR4dOS6naWToCvH9wITSn61TCjIOY M=
X-Google-Smtp-Source: ABdhPJxjLRrXRgYoJvj5ixFQwfJghpCBWyNorCUmTlp9dBkjzNpqbOYMbQc1mL/vcn3EG8FhTqAnimTRTBiZPEbo8uE=
X-Received: by 2002:a05:6512:1148:b0:448:39c8:89d with SMTP id m8-20020a056512114800b0044839c8089dmr25817695lfg.644.1651194956310; Thu, 28 Apr 2022 18:15:56 -0700 (PDT)
MIME-Version: 1.0
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> <FB031B76-7E88-4824-876F-D1A05F8D2215@thehobsons.co.uk> <CAFU7BAST-oNGpy4JvODDsf=8eS69hV8XCi8OgEHBkkoujRN3Rw@mail.gmail.com> <699f556a3eac41179a80d2cc8749a191@huawei.com> <CAO42Z2wiebCOPmtcEOJ3rOaZEpHE7qFZZTf5KLWybSsL6rOd9Q@mail.gmail.com>
In-Reply-To: <CAO42Z2wiebCOPmtcEOJ3rOaZEpHE7qFZZTf5KLWybSsL6rOd9Q@mail.gmail.com>
Reply-To: buraglio@es.net
From: Nick Buraglio <buraglio@es.net>
Date: Thu, 28 Apr 2022 20:15:44 -0500
Message-ID: <CAM5+tA-PS6m3iD62MtueRKvYTMNyUHj4-4o__MZws8dvQkpAYA@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
Cc: Xipengxiao <xipengxiao=40huawei.com@dmarc.ietf.org>, 6man list <ipv6@ietf.org>, v6ops list <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d3d9ac05ddc0c8c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/AE2Kb9M0sju9JSPHNfwoV1QiS6I>
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 01:16:04 -0000

Again, we're focusing on the wrong thing that is a tangent out of an
example used to describe *why* we need the thing. We need something that is
usable in a dual stacked environment that has similar attributes to ULA. If
everyone here thinks ULA is fine (which I do not believe is the consensus),
great. Let's say that. If not, let's think about how to fix it - or at the
very least update the draft to reflect its limitations. Ideological
soapboxing about the merits or detriment of NAT isn't really gaining any
ground either way. It is a tool in the toolbox. Some folks use it.
Vilifying it is like hating an earthmover because it's not a Ferrari.

nb



ᐧ

On Thu, Apr 28, 2022 at 6:03 PM Mark Smith <markzzzsmith@gmail.com> wrote:

> On Fri, 29 Apr 2022 at 07:37, Xipengxiao
> <xipengxiao=40huawei.com@dmarc.ietf.org> wrote:
> >
> > Hi Jen,
> >
> > Thank you for bringing this useful piece of information to light.  I
> hope more people see it:
> >
> > > PCR DSS 4.0 (published in March 2022) does not mandate NAT for IPv6.
> The text has been updated.
> >
> > 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.
>
>
> Earth moving equipment manufacturer: "We think you should buy an earth
> moving front end loader from us. They're great!"
>
> An Enterprise: "We don't need an earth moving front end loader, we're
> an accountancy firm. It doesn't solve any problems we have."
>
> Earth moving equipment manufacturer: "What if we add a backhoe to it?"
>
> An Enterprise: "We're still an accountancy firm, we still won't need
> it. We don't need to move dirt or dig holes. It still doesn't solve
> any problem we have."
>
> Earth moving equipment manufacturer: "Oh, come on! You really should
> buy one! We love our front end loaders. Everybody needs one. What if
> we paint it green too?"
>
> An Enterprise: "Nope. Even though our corporate colours are green,
> we're still an accountancy firm and we still won't need it. We've got
> better things to spend $100K on."
>
>
> Even government mandates to get enterprises to adopt a networking
> protocol don't work - the Internet is supposed to be running CLNS by
> now as mandated by governments around the world. (I expect Vint Cerf
> was being nice while working on this rather than truly believing OSI
> would take over.)
>
> Explaining the Role of GOSIP
> https://www.rfc-editor.org/rfc/rfc1169.html
>
>
>  It's more important to get enterprises to use IPv6 ASAP, than to
> insist that they use the "right" IPv6 solution.
> >
>
> Why is it important to get enterprises to use IPv6 ASAP?
>
>
> Regards,
> Mark.
>
>
> > XiPeng
> >
> > -----Original Message-----
> > From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Jen Linkova
> > Sent: Thursday, April 28, 2022 12:53 PM
> > To: Simon <linux@thehobsons.co.uk>
> > Cc: 6man list <ipv6@ietf.org>; v6ops list <v6ops@ietf.org>
> > Subject: Re: [v6ops] Vicious circle [ULA precedence [Thoughts about
> wider operational input]]
> >
> > On Thu, Apr 28, 2022 at 11:15 AM Simon <linux@thehobsons.co.uk> wrote:
> > > 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.
> >
> > See my email I sent yesterday. PCR DSS 4.0 (published in March 2022)
> does not mandate NAT for IPv6. The text has been updated.
> >
> > --
> > SY, Jen Linkova aka Furry
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>