Re: draft-housley-two-maturity-levels

sob@harvard.edu (Scott O. Bradner) Tue, 26 October 2010 02:46 UTC

Return-Path: <sob@harvard.edu>
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 4A2963A680D for <ietf@core3.amsl.com>; Mon, 25 Oct 2010 19:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level:
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=0.310, 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 c7vzaoXrMbtV for <ietf@core3.amsl.com>; Mon, 25 Oct 2010 19:46:26 -0700 (PDT)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id 0FFA63A68EF for <ietf@ietf.org>; Mon, 25 Oct 2010 19:46:26 -0700 (PDT)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id BD2AD5AC74F; Mon, 25 Oct 2010 22:48:11 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: draft-housley-two-maturity-levels
Message-Id: <20101026024811.BD2AD5AC74F@newdev.eecs.harvard.edu>
Date: Mon, 25 Oct 2010 22:48:11 -0400
From: sob@harvard.edu
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: Tue, 26 Oct 2010 02:46:27 -0000

> I'd like to hear from the community about pushing forward with this
> proposal or dropping it

I do not think this proposal fixes any known problems

the major reason (imo) that technology is not advanced along the
standards track is because there is no need to do so.  

someone labors for a while to get a proposed standard published and
people start to use it (if they did not start at the Internet Draft stage)
soon about anyone that has a need for the technology has implemented it and 
it is being used by customers all over the globe

just what is the reason that someone would take time from working on new 
technology to do the work to advance the proposed standard?  it is unlikely 
that all that many more people will implement or use the technology
so what is the point?

in addition, the IESG acts as if the proposed standard will be the last step
in the publication process (or at least reviews IDs as if this were the case)
so we have all the benefits of the cross area review (this making the proposed standards 
about as good as one could without requiring interoperable implementations at the
first stage (i.e. bringing back running code))

so I say drop it and live with the fact that rfc 2026 does not paint an accurate
picture of the current one step standard process

Scott