Re: draft-housley-two-maturity-levels

sob@harvard.edu (Scott O. Bradner) Thu, 28 July 2011 12:19 UTC

Return-Path: <sob@harvard.edu>
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 C614E21F8C2C for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 05:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9-q-Ikepghlo for <ietf@ietfa.amsl.com>; Thu, 28 Jul 2011 05:19:05 -0700 (PDT)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by ietfa.amsl.com (Postfix) with ESMTP id 4DEDE21F8C29 for <ietf@ietf.org>; Thu, 28 Jul 2011 05:19:05 -0700 (PDT)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 2D22AD7A76F; Thu, 28 Jul 2011 08:19:04 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: draft-housley-two-maturity-levels
Message-Id: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu>
Date: Thu, 28 Jul 2011 08:19:04 -0400
From: sob@harvard.edu
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: Thu, 28 Jul 2011 12:19:05 -0000

this is better than the last version but

1/ I still see no reason to think that this change will cause any
significant change in the percent of Proposed Standards that move up the
(shorter) standards track since the proposal does nothing to change the
underlying reasons that people do not expend the effort needed to
advance documents

2/ one of the big issues with the PS->DS step is understanding what
documentation is needed to show that there are the interoperable
implementations and to list the unused features - it would help a lot to
provide some guidance (which I did not do in 2026 - as I have been
reminded a number of times :-) ) as to just what process is to be
followed

could be
	a spread sheet showing features & implementations
	an assertion by the person proposing the advancement that the
requirements have been met
or something in between

Scott