Re: [Rfcplusplus] Sunk cost + not about us

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 11 July 2018 02:35 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rfcplusplus@ietfa.amsl.com
Delivered-To: rfcplusplus@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9A5130E30 for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 19:35:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 yqWcd-Q7iFoC for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 19:35:24 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C92DD130E26 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 19:35:24 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id r5-v6so2448960pgv.0 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 19:35:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=KvIHiK3Yww+z8HJ+TN+7EXnE2pIJoq1q8Fl+rilNKZI=; b=ZInSUziQrLt1UBitHT5SdWHctHOBSQDjBxe4k78XWD3zYCWxF2A3TLBW8BzjGC0Uob AxmRs23+0t1ZNoqaxFmDeNcUzGsWI4CbCdzZr1Fe4RFR3CBDgAWtV+rWFg92DTKNACyX V1u3m/Zib8aW8ZFJTiyLkAIKdkQ1FMnFAP42kWSzW1Aw6ZfR/sD1cclEmEwfrthyOhr+ ePIu/IFMDB19XY4vpafNthI7izb/webVCLjI9XW6N4ED/BGjGrzMUAbBXjv+u2MT1kxM z5YfISk12TdNAV9puFXkhoNXy6MApQLv4TcsalPGIsHA8UvrlVEx4OL6dFYBIOzbC1wb G0dw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=KvIHiK3Yww+z8HJ+TN+7EXnE2pIJoq1q8Fl+rilNKZI=; b=jjrKOZAOcIaOt2jPpRwOMaF2wlJHVrz6TptPDfhZou1QFU9xpKlOmtKhfqISI/CDDZ hFcgKjOpMU9MM5NKgfngtSlx5X7HCu6FnCwll71ZoTGA2DypQnQg2dwG7u9igHRs9Sv2 CoH+Sau6pKnGzBLOECwnPJzx+yX1XWgIoo9wIsO1+ivG7oVvPlmvG7KwgoCgUkFirrI6 aT3bL7QCXzMSrdirOXBKYnjRIYCjL0vZpPuWxfqm8edDOUpWmZlkhP8gsuRXl+gQlXlF +gc1mEjXOrLXaEvVz5Id3ye7FYoo8Uxsx1QpO88YBkjFHmEcPU6W0EXBzydBqvSZ438/ z/Vw==
X-Gm-Message-State: APt69E1UTE5huKgFd+Zgt7szF3/yjlPuDfQewydCAImMAN07Qr4BkU1j QfNmV2zOz8qTJSe4OY6ffhoRvg==
X-Google-Smtp-Source: AAOMgpe07ulZ1T84br6VNMnFYMuzLv6N7LBViFvM4Id8dXpzUijX6DgPhOrdDTWvOZ83JneOLME0Kg==
X-Received: by 2002:a62:5613:: with SMTP id k19-v6mr4666787pfb.212.1531276524086; Tue, 10 Jul 2018 19:35:24 -0700 (PDT)
Received: from [192.168.178.38] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id r77-v6sm33335151pfr.117.2018.07.10.19.35.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Jul 2018 19:35:23 -0700 (PDT)
To: Richard Barnes <rlb@ipv.sx>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, rfcplusplus@ietf.org
References: <CAL02cgQbT8s0493SdbM7Gbw2ZiSV1kMHk+6=Z4BdC2Ky664CNg@mail.gmail.com> <d159dd1f-de0b-d6c5-6430-cd5577e266fd@joelhalpern.com> <dc8c30ee-8233-e5cc-3afd-4734c1af8b0b@gmail.com> <CAL02cgT5BtFnMHzxpAx7pV=AiRyzMQV3aON65kAPRnV9kFOgeg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <78e48025-29b0-84c8-01c4-0e0388adb342@gmail.com>
Date: Wed, 11 Jul 2018 14:35:24 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CAL02cgT5BtFnMHzxpAx7pV=AiRyzMQV3aON65kAPRnV9kFOgeg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/y5Rij8dKOthK9eiR_NIfIvb0Whw>
Subject: Re: [Rfcplusplus] Sunk cost + not about us
X-BeenThere: rfcplusplus@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: For discussion of the RFC++ BoF proposal and related ideas <rfcplusplus.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfcplusplus/>
List-Post: <mailto:rfcplusplus@ietf.org>
List-Help: <mailto:rfcplusplus-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2018 02:35:27 -0000

On 11/07/2018 02:34, Richard Barnes wrote:
> On Mon, Jul 9, 2018 at 8:30 PM Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>> On 10/07/2018 10:32, Joel M. Halpern wrote:
>> ...
>>> PS: I do not see how we can draw any conclusion from the very informal
>>> survey.  We have been lectured, with good reason, in the past about the
>>> dangers of drawing conclusions from even carefully formulated and
>>> carefully distributed surveys.
>>
>> It's worse than that. The survey was hastily designed and included
>> at least one ad hominem entry, and I think anyone with experience
>> of surveys and their analysis would simply junk the results. See
>> below for something more concrete on that.
>>
> 
> I'll admit it was hastily conceived; the idea came to me as I was composing
> my message to the list on Friday.  I won't admit it's ad-hominem -- it's
> simply fact that the process entitles Adrian can approve RFCs as he likes.
> 
> But in the real world, when you're trying to make a decision, you either
> work with dirty data or you collect better data.  I don't see anyone here
> doing any better survey work, so throwing out what data we have seems
> counterproductive.
> 
> 
> 
>> On 7/9/18 6:17 PM, Richard Barnes wrote:
>> ...
>>> Based on those observations, I hope it's clear to folks that there is a
>>> problem to be solved here..  The survey data, sketchy as they are, also
>>> point toward the solution, which is to refine the RFC label to have a
>>> much more limited semantic, probably only IETF and possibly only
>> standards.
>>
>> That's a pretty perfect example of confirmation bias.
>>
> 
> If you have another interpretation for the responses to questions 1 and 2,
> I would love to hear it.

That people are confused, or simply don't read the boilerplate, isn't news.

What has not been demonstrated is whether this matters enough to be worth fixing
in a disruptive way.

     Brian

> 
> 
> 
>> I hope that as scientists and engineers, we can do better than this.
>>
> 
> I have no doubt that we could do better, but so far, nobody's done the work.
> 
> 
> By the way, the full results are at
>>
>> https://docs.google.com/forms/d/e/1FAIpQLSeMoeR0TBWkZNpBKXJN3Am6nUL04Vr4-12T2VgEbiRdBwzngQ/viewanalytics
>>
>> The last question is interesting.:
>> "Does an RFC published by the IETF require IETF consensus?"
>> got 58.8% "no", which is the correct answer. However, this
>> seems very unlikely as the preferred response from outsiders.
>> Only insiders know that only some IETF stream RFCs require
>> IETF consensus. So I don't think the data can reasonably be
>> assumed to represent the opinion of outsiders.
>>
> 
> I think this is more likely read as people just not understanding the
> question, and the role consensus plays in our process. If you think the
> respondents were insiders, how do you explain the abundantly "incorrect"
> responses to question 2?
> 
> I actually asked people let me know when they filled out the survey, and
> got around 20 notifications, including some IETF newcomers, several senior
> developers for major projects, and a few newbie developers.  Taking that
> together with the Q2 observation above, I doubt the sample was dominated by
> insiders.
> 
> --Richard
>