Re: Alternative Proposal for Two-Stage IETF Standardization

"Russ Housley" <housley@vigilsec.com> Thu, 11 November 2010 11:09 UTC

Return-Path: <housley@vigilsec.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 86C9F3A69E3 for <ietf@core3.amsl.com>; Thu, 11 Nov 2010 03:09:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level:
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, 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 d1j1YDI8fW0V for <ietf@core3.amsl.com>; Thu, 11 Nov 2010 03:09:42 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 6427A3A69E0 for <ietf@ietf.org>; Thu, 11 Nov 2010 03:09:42 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id B5664F24014; Thu, 11 Nov 2010 06:10:38 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id VNbcGxB5HgO7; Thu, 11 Nov 2010 06:10:06 -0500 (EST)
Received: from mail.smetech.net (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 73C5C9A472B; Thu, 11 Nov 2010 06:10:37 -0500 (EST)
Received: from 198.180.150.230 (SquirrelMail authenticated user housley@vigilsec.com) by mail.smetech.net with HTTP; Thu, 11 Nov 2010 06:10:37 -0500 (EST)
Message-ID: <1654.198.180.150.230.1289473837.squirrel@mail.smetech.net>
In-Reply-To: <4CDBCBAC.2040408@dcrocker.net>
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> <4CDBCBAC.2040408@dcrocker.net>
Date: Thu, 11 Nov 2010 06:10:37 -0500
Subject: Re: Alternative Proposal for Two-Stage IETF Standardization
From: Russ Housley <housley@vigilsec.com>
To: dcrocker@bbiw.net
User-Agent: SquirrelMail/1.4.8-5.el4_8.8
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: 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: Thu, 11 Nov 2010 11:09:43 -0000

>> 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.
>
>
> If I understand both your statement here and your comment in the hallway
> discussion, I suspect that the requirement would be satisfied by having
> various
> folk submit a form with some standard language on it, making an
> attestation
> along the lines of the language I submitted.
>
> Said more plainly:  Some people would need to claim that the developed or
> know
> of an independent implementation that conforms to the spec and works with
> other
> specs.
>
> Forgetting about the task of agreeing on the exact language, would this
> suffice?
>
> I guess the Last Call message would include something like:
>
>      The following individuals and/or organization
>      have stated that [...]:
>
>
> Yes?

I think it would be sufficient to say something like: The following
implementations represent a significant Internet deployment and they are
based on the specification in RFC <n>:

  - <a>
  - <b>
  - <c>
  - ...