IETF Logo Mail Archive

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

Nick Hilliard <nick@foobar.org> Fri, 05 November 2021 10:00 UTC

Return-Path: <nick@foobar.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 807983A073D for <ietf@ietfa.amsl.com>; Fri, 5 Nov 2021 03:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.23
X-Spam-Level:
X-Spam-Status: No, score=-5.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-3.33, 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 G2KM7iUVyy_y for <ietf@ietfa.amsl.com>; Fri, 5 Nov 2021 03:00:39 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B11A3A07CA for <ietf@ietf.org>; Fri, 5 Nov 2021 03:00:38 -0700 (PDT)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.17.1/8.16.1) with ESMTPSA id 1A5A0XOJ011604 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Nov 2021 10:00:34 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
Subject: Re: Accurate history [Re: "professional" in an IETF context]
To: Scott Bradner <sob@sobco.com>
Cc: IETF <ietf@ietf.org>
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>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <513d8f63-78c6-50ca-9d11-ee128af0d202@foobar.org>
Date: Fri, 05 Nov 2021 10:00:31 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.51
MIME-Version: 1.0
In-Reply-To: <7238184A-53D6-42C3-B9C3-E333513A8636@sobco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZqN2es6L6BSaZdzoJbyDG-J5X3Q>
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 10:00:44 -0000

Scott Bradner wrote on 05/11/2021 09:50:
> https://www.google.com/intl/en/ipv6/statistics.html  - total IPv6 at Google 32.41%

I suspect, without direct evidence to hand, that these figures are 
heavily weighted by small numbers of larger carriers pulling content 
from small numbers of larger content networks.  There is a long tail of 
sites and networks that are not ipv6-enabled now, and are likely not to 
ever deploy the protocol, at no particular disadvantage to themselves.

Nick

v2.23.0 | Report a Bug | By Email