Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC

Ted Hardie <ted.ietf@gmail.com> Tue, 08 October 2013 15:39 UTC

Return-Path: <ted.ietf@gmail.com>
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 1808821E818D; Tue, 8 Oct 2013 08:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yWuINqnWP9qE; Tue, 8 Oct 2013 08:39:24 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 78C4421E818C; Tue, 8 Oct 2013 08:39:24 -0700 (PDT)
Received: by mail-ie0-f176.google.com with SMTP id ar20so1921587iec.35 for <multiple recipients>; Tue, 08 Oct 2013 08:39:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OQh76Vcd5i+a01vVT2u+hxzbOkEUjPECvUD1AfLtFts=; b=H5SUGjr0BNfZlAb/CHaYQnQdDL0njDIueVNNlr6ekQf8qeYWZdabEbmM8CWLTMmNi8 eGlvvkjfzzM6EgncTzT4sHWL/4stNNrRUfq4IPYgY5g2EgHOODLss3ibvqNfFy63py65 Bm7E/A83sMR+b088EYgqK0NuW1lnsoXVnU8bIawv3tZQyEPVE53nFVHKvFpsTeSFJBVY dbNmuhk6ysBZRT+ieF3ub76EzHOfnDUDpzNrDZxc66MnhMLHSVrTMEJMSqnfazoDQ3GZ 56AAYHP/Pjop3Y05jLv6n0P1NN2R7kMPsq/ZQ/Map8L3iacv+eGCWS8pDpIRD7atCDaq Xjpw==
MIME-Version: 1.0
X-Received: by 10.43.106.198 with SMTP id dv6mr1527385icc.51.1381246763829; Tue, 08 Oct 2013 08:39:23 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Tue, 8 Oct 2013 08:39:23 -0700 (PDT)
In-Reply-To: <F854C30D-78C6-4FCF-BC48-AB1E7C270164@nominum.com>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com> <52530CCF.8090605@gmail.com> <F854C30D-78C6-4FCF-BC48-AB1E7C270164@nominum.com>
Date: Tue, 08 Oct 2013 08:39:23 -0700
Message-ID: <CA+9kkMDMUjnFwYD2NFjiWx0dMmNOFNerXQtwp6urco+F7-ffTA@mail.gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
From: Ted Hardie <ted.ietf@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary="20cf303344f9b4919404e83c92fb"
Cc: IESG <iesg@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 08 Oct 2013 15:39:25 -0000

On Mon, Oct 7, 2013 at 1:35 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Oct 7, 2013, at 3:34 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
> wrote:
> > So I'd like to dispute Ted's point that by publishing a version of
> > resnick-on-consensus as an RFC, we will engrave its contents in stone.
> > If that's the case, we have an even deeper problem than misunderstandings
> > of rough consensus.
>
> Right, I think what Ted is describing is a BCP, not an Informational RFC.
>
> To be clear here, I did not think Pete's document was going for BCP.  I
remain concerned that the publication of this document as an an
AD-sponsored Informational RFC will impute status to it as a community
conclusion, rather than the start of a conversation (or, rather, the
continuation of one).  Some of the comments of "I've wanted something like
this to hand to..." are part of what cause me to believe that.

And, to re-iterate, I do not think the document is ready, even if the IESG
believes that a document of this type should be published; it needs a much
clearer sense of audience as well as attention to the other points that
have been raised.

regards,

Ted