Re: draft-housley-two-maturity-levels

"Bert (IETF) Wijnen" <bertietf@bwijnen.net> Tue, 26 October 2010 08:14 UTC

Return-Path: <bertietf@bwijnen.net>
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 101643A68EE for <ietf@core3.amsl.com>; Tue, 26 Oct 2010 01:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.435
X-Spam-Level:
X-Spam-Status: No, score=-102.435 tagged_above=-999 required=5 tests=[AWL=0.164, 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 3wmYW1jmTszA for <ietf@core3.amsl.com>; Tue, 26 Oct 2010 01:14:47 -0700 (PDT)
Received: from postlady.ripe.net (postlady.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1341]) by core3.amsl.com (Postfix) with ESMTP id 9D3A63A67A2 for <ietf@ietf.org>; Tue, 26 Oct 2010 01:14:46 -0700 (PDT)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postlady.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <bertietf@bwijnen.net>) id 1PAehb-0001to-AL; Tue, 26 Oct 2010 10:16:30 +0200
Received: from dog.ripe.net ([193.0.1.217] helo=BWMACBOOK.local) by ayeaye.ripe.net with esmtp (Exim 4.63) (envelope-from <bertietf@bwijnen.net>) id 1PAeha-0005tw-Ma; Tue, 26 Oct 2010 10:16:14 +0200
Message-ID: <4CC68E4E.9000800@bwijnen.net>
Date: Tue, 26 Oct 2010 10:16:14 +0200
From: "Bert (IETF) Wijnen" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: draft-housley-two-maturity-levels
References: <20101026024811.BD2AD5AC74F@newdev.eecs.harvard.edu>
In-Reply-To: <20101026024811.BD2AD5AC74F@newdev.eecs.harvard.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd46656d8920ff6a5b219e620730f8088e5
X-RIPE-Spam-Level: --
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd46656d8920ff6a5b219e620730f8088e5
Cc: "Scott O. Bradner" <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 08:14:49 -0000

Although I do sort of also agree with Scott, I think it is one step in the right
direction. So please seen a sponsor and get it published.

Bert

On 10/26/10 4:48 AM, Scott O. Bradner wrote:
>> 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
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>