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

Keith Moore <moore@network-heretics.com> Tue, 06 September 2011 16:41 UTC

Return-Path: <moore@network-heretics.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 B232021F8770 for <ietf@ietfa.amsl.com>; Tue, 6 Sep 2011 09:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.461
X-Spam-Level:
X-Spam-Status: No, score=-3.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 lFLzZIo7YN75 for <ietf@ietfa.amsl.com>; Tue, 6 Sep 2011 09:41:19 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2F01621F86DE for <ietf@ietf.org>; Tue, 6 Sep 2011 09:41:19 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 7AE30238AD; Tue, 6 Sep 2011 12:43:05 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 06 Sep 2011 12:43:05 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=SM5S53ANMv0V9AM8YObOtfgpsGI=; b=gt mZ8WvJ4sIwSg8O1szHcDsCByuhhVsHyqGcyiMojh1UrdB1FeHAKsJN9t7Q0ufXcZ fZi8Qpriibqjo5t7mNSuGLA39VzCDCpi1lNwFxEABIvaA2kJ/4X3gezdTVEMlp9B CNr2LWLF7DiIAU5V0Y0XclJWP8V001oa+A6lgOmd4=
X-Sasl-enc: Ja5op09vXyY1TD4HUUzlI80iJAMwedwBk5tXXYqbYrMy 1315327384
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 96F868E0260; Tue, 6 Sep 2011 12:43:04 -0400 (EDT)
Subject: Re: Conclusion of the last call on draft-housley-two-maturity-levels
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110906161108.GI31240@shinkuro.com>
Date: Tue, 06 Sep 2011 12:43:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CEDD8840-BE2D-405E-872A-271C25A9A59D@network-heretics.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>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1084)
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 16:41:21 -0000

On Sep 6, 2011, at 12:11 PM, Andrew Sullivan wrote:

> On Tue, Sep 06, 2011 at 11:38:14AM -0400, Ross Callon wrote:
>> 
>> I haven't heard anyone currently on the IESG say that the two step process would require "higher more rigorous document reviews". 
>> 
> 
> That particular refusal to recognize part of reality is the thing that
> annoys me about this draft and about the discussions leading to its
> modification of the official process.
> 
> The causal claim asserted early in the I-D's life was that, since many
> RFCs effectively live forever today at step 1 of the standards track,
> IESG members feel a responsibility to make sure that an I-D is "right"
> before publication as PS even though that requirement is much higher
> than the RFC 2026 process requires.
> 
> As a result, proponents argued, the process would be made less onerous
> by moving to a two-step process in which initial publication at step 1
> is the same as RFC 2026's step 1, except that it is even easier to go
> from that and get the honorific "Internet Standard" than it is today.
> 
> 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.

Keith