Re: Conclusion of the last call on draft-housley-two-maturity-levels

John C Klensin <john-ietf@jck.com> Sun, 11 September 2011 02:25 UTC

Return-Path: <john-ietf@jck.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 A69CD21F86A6 for <ietf@ietfa.amsl.com>; Sat, 10 Sep 2011 19:25:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level:
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 xD1CA5zUhX6y for <ietf@ietfa.amsl.com>; Sat, 10 Sep 2011 19:25:02 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 04AE421F84CB for <ietf@ietf.org>; Sat, 10 Sep 2011 19:25:02 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1R2Zkz-000IIT-Av; Sat, 10 Sep 2011 22:26:53 -0400
X-Vipre-Scanned: 00E2C21C0028C400E2C369-TDI
Date: Sat, 10 Sep 2011 22:26:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eric Burger <eburger-l@standardstrack.com>, Thomas Narten <narten@us.ibm.com>
Subject: Re: Conclusion of the last call on draft-housley-two-maturity-levels
Message-ID: <126AE4FDE4FE115A77CDE6B7@[192.168.1.128]>
In-Reply-To: <3E9E22D3-9C4B-48CF-A0F1-BACD219AF582@standardstrack.com>
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu> <4E5D4570.9080108@piuha.net> <6.2.5.6.2.20110902090159.09e97af0@resistor.net> <4E6147D4.2020204@santronics.com> <DF7F294AF4153D498141CBEFADB17704C352657343@EMBX01-WF.jnpr.net> <20110906161108.GI31240@shinkuro.com> <CEDD8840-BE2D-405E-872A-271C25A9A59D@network-heretics.com> <01O5QFMUPV8S014O5Z@mauve.mrochek.com> <96633252-503F-4DCD-B6FD-B6B9DEA1FC66@network-heretics.com> <01O5RIOBEGP0014O5Z@mauve.mrochek.com> <201109100133.p8A1XFvS003894@cichlid.raleigh.ibm.com> <3E9E22D3-9C4B-48CF-A0F1-BACD219AF582@standardstrack.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: IETF list discussion <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: Sun, 11 Sep 2011 02:25:02 -0000

Eric,

Thomas may well have a different answer but, speaking
personally, if we have a choice between a nominal three-step
process that is actually one-step with a few exceptions and a
nominal two-step process that is actually one-step with a few
exceptions, I think we would be much better off with a one-step
process.   Ideally, we should be able to annotate that one-step
process with how mature we think a spec is, but the "facing
reality" situation is that, unless we can change how we and the
marketplace do things, we have a one-step process today and
trying to cut things from unused-three to unused-two
accomplishes nothing other than giving us an extra opportunity
to confirm our failure to be able to use a multi-step process.

I'd find a change to one-step a lot easier to support than a
change to two-step, if only because moving to one-step is not
only closer to present reality but also would give us a starting
part for new work to express maturity (if we still care).
Two-step neither gets us to present reality nor gets us away
from the idea that the multistep model actually expresses
maturity and other useful information.

    john


--On Saturday, September 10, 2011 21:26 -0400 Eric Burger
<eburger-l@standardstrack.com> wrote:

> So should we move to a one-step process?
> 
> On Sep 9, 2011, at 9:33 PM, Thomas Narten wrote:
> 
>> Advancing a spec is done for marketing, political, process
>> and other reasons. E.g., to give a spec more legitimacy. Or
>> to more clear replace an older one. Nothing wrong with that.