Re: prerequisite for change (was Re:

Phillip Hallam-Baker <hallam@gmail.com> Wed, 02 February 2011 03:24 UTC

Return-Path: <hallam@gmail.com>
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 2C1983A6A86 for <ietf@core3.amsl.com>; Tue, 1 Feb 2011 19:24:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.477
X-Spam-Level:
X-Spam-Status: No, score=-3.477 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 17xZLmoFoGEd for <ietf@core3.amsl.com>; Tue, 1 Feb 2011 19:24:37 -0800 (PST)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by core3.amsl.com (Postfix) with ESMTP id 99D593A6916 for <ietf@ietf.org>; Tue, 1 Feb 2011 19:24:37 -0800 (PST)
Received: by yie19 with SMTP id 19so3186664yie.31 for <ietf@ietf.org>; Tue, 01 Feb 2011 19:27:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=LuGN3MTf6EOeHDmd4JHcNivLNSfAfUPdk9zHE/n6F6c=; b=UV6r6plaG8hTer1XOynOT918dW/VPQW0CU03Tdx+MSUrkfKnal+5C9/gIvbN2isv7o 2q0C71ctcyvcmXnujUIlu96/IBJiqPj7qRZGISyDKrjKJiP2PoYW7LzhxKn/JTz8DSPP radYq7agQsvC+jY3+12VAE3urV3eMS3nSllSU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=DRzXOwJSJyAU/KbalJeXrC3gahDfnSmegBgfGcOC0kbGIQVRCldiyUxtzIOuVr7tq9 7frESy7auuYFQMDZRx4nzWkQiH0HROkuRhjgVN794m7oEfQtK2HA66/2+64BFWpbwLTZ xSD83PkJVzwiGLkV/GaAYU+rH6iVRnkb8CEP0=
MIME-Version: 1.0
Received: by 10.100.8.9 with SMTP id 9mr5493690anh.120.1296617274128; Tue, 01 Feb 2011 19:27:54 -0800 (PST)
Received: by 10.100.109.16 with HTTP; Tue, 1 Feb 2011 19:27:54 -0800 (PST)
In-Reply-To: <201102020139.p121dl7E005388@fs4113.wdf.sap.corp>
References: <4D44AA6C.8060003@gmail.com> <201102020139.p121dl7E005388@fs4113.wdf.sap.corp>
Date: Tue, 01 Feb 2011 22:27:54 -0500
Message-ID: <AANLkTin-wS02JATw5y=eqc2xRLWbctJ7M4r3iUJUbZdn@mail.gmail.com>
Subject: Re: prerequisite for change (was Re:
From: Phillip Hallam-Baker <hallam@gmail.com>
To: mrex@sap.com
Content-Type: multipart/alternative; boundary="0016e6441dd808b81b049b443c00"
Cc: ietf@ietf.org, 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: Wed, 02 Feb 2011 03:24:39 -0000

What is wrong with using Informational and Experimental for cases where a
lowered bar is required?

If someone is proposing an entirely new protocol, a low bar is appropriate.
But that is only a very small fraction of the work done in IETF today. Most
of the WG effort goes to incremental refinements to existing specs.

If someone is going to propose an extension to HTTP or PKIX or TLS they had
better have a very good document if it is going to go through.


On Tue, Feb 1, 2011 at 8:39 PM, Martin Rex <mrex@sap.com> wrote:

> Brian E Carpenter wrote:
> >
> > The bar for PS has crept up, IMHO, precisely because the bar
> > for DS/STD has appeared too high to be readily attainable.
>
> Lowering the bar will result in the I-Ds on which the first rush of
> implementations are currently being based on becoming the PS document.
>
> But I fail to see how a lowered bar for PS would encourage folks
> to tackle DS.  Frankly, I believe just the opposite is going to happen.
>
> For many vendors, the working model is switched from "development mode"
> to "maintenance mode" as soon as the product is shipped.  And when that
> switch happens, most of the existing resources are reassigned to new
> features, rather than improving stuff that is in maintenance mode.
>
> And when DS/STD are collapsed into one and the requirements for the
> new STD are at least as high as for the old DS, then the gap between
> the new PS and the new STD will be much larger than between old PS
> and old DS, resulting in two problems: more resistence from early
> implementors to change the document, and less resources from the
> vendors to improve a document describing a product that has already
> shipped.  The ones who profit most from an improved document would
> be those vendors that haven't implemented or shipped yet, and many
> of these are not active in the WG or even in the IETF at all.
>
>
> The reliably predictable outcome of lowering the bar for PS is that
> there will be new PS documents with significantly lower quality.
>
> But so far I've not seen any remotely convincing rationale why
> the change of PS would improve the likelihood for PS->STD
> transitions.  Personally, I believe it will have just the
> opposite effect, considering that a non-marginal fraction of
> us work for large organizations and how these usually operate.
>
>
> -Martin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



-- 
Website: http://hallambaker.com/