Re: [Rfcplusplus] Sunk cost + not about us

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 10 July 2018 14:45 UTC

Return-Path: <ajs@anvilwalrusden.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 2DACF130E0D for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 07:45:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=l58/Rqre; dkim=pass (1024-bit key) header.d=yitter.info header.b=dhLkXnsB
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 nSGu1pNuVRii for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 07:45:29 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A1DA130E79 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 07:45:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id DB132BEBEB for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 14:45:28 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1531233928; bh=sq/S06zieWiXPCcccZPb75Ac+1LQKN8HrE2zVP0paQI=; h=Date:From:To:Subject:References:In-Reply-To:From; b=l58/Rqre5aUwnJ0VYthQSR0QqKsejvgJm14Yb668jXvjDkZHSfQCy5gUCp3Y5BoeQ iQLm0UCS5Rf5PIkAvBfr0InlJw+YMvwSQPBg+F83Ajz1eh30YNJLJ6E9hXPPXUOh6U BDUBN8d/lTmAnFocSXu0KmSycvxzrm7n4CjA16w0=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rix_cBodHkx0 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 14:45:27 +0000 (UTC)
Date: Tue, 10 Jul 2018 10:45:25 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1531233927; bh=sq/S06zieWiXPCcccZPb75Ac+1LQKN8HrE2zVP0paQI=; h=Date:From:To:Subject:References:In-Reply-To:From; b=dhLkXnsBimckoDMs9WgG+FKjYgxbr6NxixdgKJGFu3YNhKeRcRiUeg5eYRyiF7Mjg /BEBUvEQlyqYWmVtZ3aDPoR/bwchEMK6naJ1k+YDixfuKkFaOeyJ92wkAQfx180dKB ++3c5OtmoUW1qVjs1vCmfc1I2mrBI4dq5itYh8Zo=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: rfcplusplus@ietf.org
Message-ID: <20180710144525.GE20282@mx4.yitter.info>
References: <CAL02cgQbT8s0493SdbM7Gbw2ZiSV1kMHk+6=Z4BdC2Ky664CNg@mail.gmail.com> <d159dd1f-de0b-d6c5-6430-cd5577e266fd@joelhalpern.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <d159dd1f-de0b-d6c5-6430-cd5577e266fd@joelhalpern.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/v438hp6w3Ff69mem87Um4kT-Ft0>
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 14:45:31 -0000

Hi,

On Mon, Jul 09, 2018 at 06:32:28PM -0400, Joel M. Halpern wrote:
> This formulation assumes that change does not have a cost.  It does.  I
> agree that not changing has some cost.  However, absent indication that the
> changes will actually address the claimed problem, paying the various direct
> and indirect costs of changing things is not inherently a good thing.

I think this argument would be stronger if we understood what your
estimation of the costs are.  The analysis underpinning the proposal
(in the BoF request), as near as I can tell, is that the costs are the
using up of a few letters (for new series names) plus the cost of
possibly reserving RFC numbers for the alternative series publications
(in case they turn out not to work after 3 or more years), plus the
costs to tooling changes.  Are there other costs you can think of?

Keep in mind, the proposal is for an experiment.  Experiments do
indeed result in some costs, and I think it is entirely reasonable to
ask what those costs really would be.  But I also think we ought to
keep in mind the potential benefit of the experiment, which is to do
an empirical evaluation of whether the long-debated confusion can be
clarified (at least, in this way).

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com