Re: Alternative Proposal for Two-Stage IETF Standardization

ned+ietf@mauve.mrochek.com Fri, 12 November 2010 02:10 UTC

Return-Path: <ned+ietf@mauve.mrochek.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 AE35528C10B for <ietf@core3.amsl.com>; Thu, 11 Nov 2010 18:10:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 njyW3E4Z2yR6 for <ietf@core3.amsl.com>; Thu, 11 Nov 2010 18:10:35 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 7C7333A6781 for <ietf@ietf.org>; Thu, 11 Nov 2010 18:10:34 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NU511MNUDC006JTK@mauve.mrochek.com> for ietf@ietf.org; Thu, 11 Nov 2010 18:10:55 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NU4UJ21GTC007CHU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 11 Nov 2010 18:10:48 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01NU511K68DO007CHU@mauve.mrochek.com>
Date: Thu, 11 Nov 2010 18:07:18 -0800
Subject: Re: Alternative Proposal for Two-Stage IETF Standardization
In-reply-to: "Your message dated Thu, 11 Nov 2010 02:44:08 -0600" <2BB7C49F68BA442786EC591F09735823@china.huawei.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format="flowed"
References: <4CD967AD.80605@dcrocker.net> <3486.198.180.150.230.1289445298.squirrel@mail.smetech.net> <4CDB7026.5090903@dcrocker.net> <4CDB918C.8090902@dcrocker.net> <1366.198.180.150.230.1289463839.squirrel@mail.smetech.net> <2BB7C49F68BA442786EC591F09735823@china.huawei.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1289525251; i=@mrochek.com; bh=PTbyVVxsmGeQzy3FHMEXIBHc++Oi/ibRdhn8ps1ySes=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=Hc0IR2WaSv4wrRG9UexYJgMvY6ikjItzsNBYH5DLVMVXwcKhDJpdRxJ51/5Z7MpRv Bf1BHUFl/kRK6x9vXv6KHxT1ZLG/I6VG2XIw6MiSEFP2CvBwMtKSN+JebnpSb4lf5D 0ZkANhwtMaP0XVap0M/BXy1bYS11tLlfWwNRq7eM=
Cc: dcrocker@bbiw.net, IETF Discussion <ietf@ietf.org>
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: Fri, 12 Nov 2010 02:10:38 -0000

> Russ,

> > Dave:
> >
> > This is a significant improvement from my perspective.  We need a
> > mechanism to implement it.  The mechanism does not need to be heavy
> > weight, and it might be as simple as some statements in a Last Call,
> > allowing the community to support or challenge them.
> >
> > Russ

> Thank you for the hallway conversation on this.

> When I counted last week, only 80 implementation reports have been filed
> with the IESG in the history of "ever", so this doesn't seem like the right
> hurdle for advancement.

I assume that figure was arrived at by looking at:

  http://www.ietf.org/iesg/implementation-report.html

If so, it's apropos of nothing, since the list is incomplete. Just as one
example, MIME interop info isn't on it, and that information definitely was
generated.

> I think your suggestion to make assertions at Last Call time and asking for
> supporting/challenging statements sounds very reasonable. The IESG can do
> the right thing based on Last Call comments.

For the record, I am entirely in favor of Russ' proposal but entirely opposed
to this new proposal, because it eliminates the parts of the process that are
working (proposed -> draft criteria) and retains the ones that aren't (draft ->
full).

In fact given a choice between this new proposal and the current process, I
prefer the current process.

				Ned