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

ned+ietf@mauve.mrochek.com Tue, 06 September 2011 20:08 UTC

Return-Path: <ned+ietf@mauve.mrochek.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 ACBB621F8E55 for <ietf@ietfa.amsl.com>; Tue, 6 Sep 2011 13:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.616
X-Spam-Level:
X-Spam-Status: No, score=-2.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599]
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 cn0J9Sffwfss for <ietf@ietfa.amsl.com>; Tue, 6 Sep 2011 13:08:51 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 011C421F8E52 for <ietf@ietf.org>; Tue, 6 Sep 2011 13:08:51 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5QFMW4LGG010SSV@mauve.mrochek.com> for ietf@ietf.org; Tue, 6 Sep 2011 13:09:13 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5KP14T1K0014O5Z@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 6 Sep 2011 13:09:09 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O5QFMUPV8S014O5Z@mauve.mrochek.com>
Date: Tue, 06 Sep 2011 11:26:55 -0700
Subject: Re: Conclusion of the last call on draft-housley-two-maturity-levels
In-reply-to: "Your message dated Tue, 06 Sep 2011 12:43:03 -0400" <CEDD8840-BE2D-405E-872A-271C25A9A59D@network-heretics.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
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>
To: Keith Moore <moore@network-heretics.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1315339763; i=@mrochek.com; bh=mo7Xosto6qRD4NuP87YtaSKfxxbG271vsU9FaiHvklE=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=TDHl6Cxox2Rl24CI00wBpQzKd7CFSJTpRh49263eRkQpOJ8+l5rvR/vBVe+0hVFAW uJuyQyi/WIQ5XM6vLCcs6bPafwp+IrHUZNnGcNbXW9pzvR3K8Tfxbbzebw5UTvtAGo y61P/zwY8pdlfXfRLxXM/wezNqQzHZY8A5P1K/9o=
Cc: 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, 06 Sep 2011 20:08:51 -0000

> > I find it impossible to believe that this will not result in even more
> > hard-line positions on the part of some IESG members when something
> > with which they disagree is a candidate for PS.  I see no way in which
> > the draft solves this problem, which remains one of its implicit
> > goals.  I said before, I don't care if it is published, because I
> > think it will have little effect.  But I think we'd better be prepared
> > for some IESG members to insist on the same high bar for PS that we
> > have under RFC 2026, regardless of what the RFC says.

> +1

> Best statement of the problem with this document that I've seen so far.

Except for one small problem: It's nonsensical.

Why is it nonsensical? Because you're comparing the status quo with a possible
future course of action. The one thing that's we can be certain of is things
won't remain the same. They never do. So in order to make a reasonable
comparison you have to project what's likely to happen if this document isn't
approved, then compare that with what might happen if it is.

And the future where this isn't approved is fairly easy to predict: As more and
more documents become proposed standards and then fail to progress along the
standards track - and the trend lines for this could not be clearer - we
effectively move more and more to a one-step process. The IESG has only one
rational response to that: Continue to raise the bar on the initial step to
proposed.

Will the imposition of a two step process change this? It certainly won't do so
immediately, so the likely outcome is that yes indeed, the bar will continue to
go up, at least initially, irrespective of whether or not this document is
approved. But if more documents start advancing - and yes, that's an if - that
will lessen the pressure on the initial step, and perhaps break the cycle we're
currently stuck in.

And please don't try trotting out a bunch of additional what ifs about how if
this proposal fails we can then get past this distraction (or however you would
characterize it) and address whatever it is you think the actual problems are.
Given the time that has gone into trying to make this one simple and fairly
obvious change, if it fails, the odds of someone attempting even more
fundamental changes are pretty darned low.

				Ned