Re: [Rfcplusplus] Sunk cost + not about us

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 10 July 2018 00:30 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 22FB7130EB3 for <rfcplusplus@ietfa.amsl.com>; Mon, 9 Jul 2018 17:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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 44NfoR0b2V2W for <rfcplusplus@ietfa.amsl.com>; Mon, 9 Jul 2018 17:30:42 -0700 (PDT)
Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com [IPv6:2607:f8b0:400e:c00::242]) (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 18A42130EB0 for <rfcplusplus@ietf.org>; Mon, 9 Jul 2018 17:30:42 -0700 (PDT)
Received: by mail-pf0-x242.google.com with SMTP id j3-v6so14797959pfh.11 for <rfcplusplus@ietf.org>; Mon, 09 Jul 2018 17:30:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=PlXAEHp3oEYeSdDpDp3NbFZXApRVuXabDR6JU+ECb54=; b=FClv0e+R6CtkGCh6aFnf42uprWyle+ovEQLu9bFPzECRYTR/jAnCRudTYmHUeLgSCx unJbG2VFeHg37lyvzGWYw2V/Njth+2PKXk3uYE8ZyybiFJdkNWc5R2BN3EZVaoB0TMuI ldijNWWqv+mTzfTHsZrcGeyPihRXSxUACRtMJkz5yDqROdWywZh+ArZ8QCpg8/ocszDn JH9TZrazLU+NP1ivWdbxwKzR4QzNZuGJ6P7OMpBvmONEPCW0ZuwI+3cEyrcwgyex2Z+M bOtYVLeKtiOwk0tuS3w4oQkwWg6ot25eXSSMnM758pwsKNymm+koa2rxBfPfBdb0hAcM 0/BA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=PlXAEHp3oEYeSdDpDp3NbFZXApRVuXabDR6JU+ECb54=; b=UN3X3hcky6fqXU5r0W3qIduclxqd8OcHFV8t/23Ty1QzD6uT5R6r/9UPcZOTUAEd4e 6MC7ELW7ViXYwxu0Xvg5ESKwYRrhhQNyGBZY4p5DS/yyF7a//cKK9yiMffWfI5jqR5/s XW/fK6/XnZ0fAneu51xrL/4qF/M/XK4I6WFF5oJUE6oiZMwsG6G3waiajRoVXAyhMOjj 1MrNFKgxSoZ3vVKnY1r0eEzXvQ+tcQbpLrEUHvfgY0FQGm+SjbpXcdYFXfA5KZxgWG2T /11BfrerzbwgjnXcmYI3pTbAjpkKuv7UdMnfRAIGvBJv4ebP2BJXjrDBM1KtNP9eM0qT LNyA==
X-Gm-Message-State: APt69E3Yp/xaNMvNJv3EFmeWk3hoAGnJlFoySiEkGujg9NzGBxbryKnY 49eb4fRgzwAntm/brlc33gtcnQ==
X-Google-Smtp-Source: AAOMgpclKD/k8KcIo+DPUZVl3KlOGjYZojErfr/ua1Y2z79UM+QJXl+pla6HLVAoaS7UlSl18Rqk8A==
X-Received: by 2002:a63:fc44:: with SMTP id r4-v6mr20736473pgk.169.1531182641444; Mon, 09 Jul 2018 17:30:41 -0700 (PDT)
Received: from [130.216.38.4] (sc-cs-316971.cs.auckland.ac.nz. [130.216.38.4]) by smtp.gmail.com with ESMTPSA id h7-v6sm3774552pfd.155.2018.07.09.17.30.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Jul 2018 17:30:40 -0700 (PDT)
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Richard Barnes <rlb@ipv.sx>, rfcplusplus@ietf.org
References: <CAL02cgQbT8s0493SdbM7Gbw2ZiSV1kMHk+6=Z4BdC2Ky664CNg@mail.gmail.com> <d159dd1f-de0b-d6c5-6430-cd5577e266fd@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <dc8c30ee-8233-e5cc-3afd-4734c1af8b0b@gmail.com>
Date: Tue, 10 Jul 2018 12:30:39 +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: <d159dd1f-de0b-d6c5-6430-cd5577e266fd@joelhalpern.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/kilNRYQzK--ITBLUP7xImxchAkg>
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: Tue, 10 Jul 2018 00:30:44 -0000

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.

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. Sorry, but
even if we accept that there's a problem worth solving, the "data"
don't point to any particular solution.

I hope that as scientists and engineers, we can do better than this.

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.

    Brian