Re: draft-housley-two-maturity-levels

John C Klensin <john-ietf@jck.com> Thu, 27 January 2011 09:07 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 160113A6974 for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 01:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.014
X-Spam-Level:
X-Spam-Status: No, score=-103.014 tagged_above=-999 required=5 tests=[AWL=-0.415, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TRP3CXNhWMt6 for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 01:07:21 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 1DAE13A6951 for <ietf@ietf.org>; Thu, 27 Jan 2011 01:07:21 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PiNry-000Gdq-Ot; Thu, 27 Jan 2011 04:10:22 -0500
Date: Thu, 27 Jan 2011 04:10:22 -0500
From: John C Klensin <john-ietf@jck.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: draft-housley-two-maturity-levels
Message-ID: <A4324E60B4E050068AC29A5E@PST.JCK.COM>
In-Reply-To: <4D4121B9.2060407@ericsson.com>
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu> <C3BAE1E425FB4058C86138DD@PST.JCK.COM> <4D4121B9.2060407@ericsson.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: "Scott O. Bradner" <sob@harvard.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 27 Jan 2011 09:07:22 -0000

--On Thursday, January 27, 2011 09:41 +0200 Gonzalo Camarillo
<Gonzalo.Camarillo@ericsson.com> wrote:

> Hi,
> 
> yes, I also agree the first one is the most important point
> and has not been addressed so far. If we want a system that
> works (and is used), it needs to include incentives to move
> from one level to the next one. I have discussed this issue
> with quite a few people. Some people claim that those
> incentives exist in some areas (e.g., public institutions
> preferring or requiring full standards in their RFQs) but, at
> least in the RAI area, the incentives are not there in the
> vast majority of cases.

Gonzalo,

Suppose we were to succeed in returning Proposed Standard to its
intended purpose --  more or less a good rough sketch of a
protocol, suitable for implementation and testing with the
support of mailing list discussions -- and being completely
clear about what that meant.   I think the incentives to advance
to a more complete specification that represented community
consensus about its being implementable and probably useful
would then be clear.

That change clearly requires our being very clear internally
that Proposed Standard is a lightweight spec with a lightweight
approval process: if we can't get away from the mentality of
"you made me review this, so I have to find at least something
to comment on and ask for changes" in the various review teams
and the IESG, I think it is pretty much hopeless and that
draft-housley-two-maturity-levels will turn out to accomplish
exactly nothing other than to eliminate whatever further
specification refinement occurs in the few documents that now to
to Full Standard.

As long as we apply a very high bar to entry for Proposed
Standard and insist that specifications at that level are
perfectly good standards, there will rarely be an incentive to
move to the second level, no matter what we call it and whether
or not there is a third level.

I think the change, and the incentives, might be reinforced by
renaming "Proposed" to "Rough Preliminary Specification" or
something else without "Standard" in its name, but that is a
separate matter.

best,
    john