Why IPv6 failed [Re: Accurate history [Re: "professional" in an IETF context]]

otroan@employees.org Fri, 05 November 2021 12:34 UTC

Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D3D33A0E23 for <ietf@ietfa.amsl.com>; Fri, 5 Nov 2021 05:34:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 siCTKHQKbP5O for <ietf@ietfa.amsl.com>; Fri, 5 Nov 2021 05:34:05 -0700 (PDT)
Received: from clarinet.employees.org (clarinet.employees.org [198.137.202.74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AB1B3A0E8C for <ietf@ietf.org>; Fri, 5 Nov 2021 05:34:05 -0700 (PDT)
Received: from astfgl.hanazo.no (77.16.44.104.tmi.telenormobil.no [77.16.44.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 177BD4E11B3F; Fri, 5 Nov 2021 12:34:04 +0000 (UTC)
Received: from smtpclient.apple (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 59D6565495D9; Fri, 5 Nov 2021 13:33:58 +0100 (CET)
From: otroan@employees.org
Message-Id: <A512DF2B-DCD6-40A9-AD34-4BE9CAD2921D@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_8C66888E-7A2C-4DCB-A5BA-CE2D8DA1F6F3"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Subject: Why IPv6 failed [Re: Accurate history [Re: "professional" in an IETF context]]
Date: Fri, 05 Nov 2021 13:33:57 +0100
In-Reply-To: <E285424F-7E21-47BF-8235-BF9710F1593C@gmail.com>
Cc: Vasilenko Eduard <vasilenko.eduard@huawei.com>, IETF <ietf@ietf.org>
To: Stewart Bryant <stewart.bryant@gmail.com>
References: <8F4B97EA-665F-4A59-B99D-791B4AB9F2F7@yahoo.co.uk> <3e685576-a230-a7c4-f371-d66a55aa820d@necom830.hpcl.titech.ac.jp> <7a087707-499f-e3bf-8701-1a58930a8a22@meetinghouse.net> <4ec32d7a-a17b-635b-91bc-4152313d6800@necom830.hpcl.titech.ac.jp> <885e62bf-7d6a-4501-a48a-e7c2cbf20382@joelhalpern.com> <e59adb61-a55c-7f5f-a60a-40bf186c139d@necom830.hpcl.titech.ac.jp> <CAC8QAceMSrfkqGTYcMNr3JargO3gxJqTaEyf02LGHd-KVeUDHw@mail.gmail.com> <6286da3e-2beb-9556-089a-2e1951573b1e@gmail.com> <59c80b60-438f-b10f-ad61-ba839f6e4f95@necom830.hpcl.titech.ac.jp> <e834916e85ea47ef94fce07c23928d2b@huawei.com> <37b299c8-e821-07e5-6240-68fb9d1ca137@gmail.com> <23b450fb11eb4a51bb4ee837b5c52657@huawei.com> <a805b50d-3ccd-dd2a-4931-6c6dc9a8ede3@necom830.hpcl.titech.ac.jp> <CAC8QAceY1gtK5v3WGMd4OB0z826jDiDDw_g1LbjWef7MKTnrcg@mail.gmail.com> <7d6af5bc-9663-7e4e-26ba-23fb1e4dccbe@necom830.hpcl.titech.ac.jp> <7238184A-53D6-42C3-B9C3-E333513A8636@sobco.com> <513d8f63-78c6-50ca-9d11-ee128af0d202@foobar.org> <f6ecd8af8e0040869e152b086e041a42@huawei.com> <E285424F-7E21-47BF-8235-BF9710F1593C@gmail.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ez95bbkLoaRdaheYFtPyS8M1kp8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Nov 2021 12:34:10 -0000

Changed subject to reflect discussion.

>> What is important: Enterprises have no clear sign of IPv6 adoption.
>> ND protocol has a heavy influence on this.
>> Of course, ND is not the only reason. But maybe the biggest one.
> 
> Indeed, and I have had a consistent complaint from a British security conscious large private sector technology savvy company, that IPv6 is so much harder to secure than IPv4 they have no interest in moving. I think that part of this is the conflict between the privacy that IPv6 offers and their need to know that *every* packet on their network is entitled to be there doing what it is doing.

"If we had just one more transition mechanism, or if IPv6 had just behaved this way, then it would have been deployed".

I think that's a fallacy. There are many reasons why IPv6 didn't replace IPv4. Including business models, centralisation of the Internet etc.

Regarding ND, you can operate IPv6 pretty much like you operate an IPv4 network.
Single address to the host, even private address if you so prefer.
(By pushing NAT64 we ensured that all IPv6 applications have to be NAT aware anyway).

O.