Re: draft-housley-two-maturity-levels

Peter Saint-Andre <stpeter@stpeter.im> Wed, 27 October 2010 23:14 UTC

Return-Path: <stpeter@stpeter.im>
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 ADEE73A677D for <ietf@core3.amsl.com>; Wed, 27 Oct 2010 16:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level:
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, 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 bwmsaJ7uNBLI for <ietf@core3.amsl.com>; Wed, 27 Oct 2010 16:14:41 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 3E5C23A6452 for <ietf@ietf.org>; Wed, 27 Oct 2010 16:14:41 -0700 (PDT)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4EC5F40BB9; Wed, 27 Oct 2010 17:24:36 -0600 (MDT)
Message-ID: <4CC8B2CD.6060203@stpeter.im>
Date: Wed, 27 Oct 2010 17:16:29 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
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: dcrocker@bbiw.net
Subject: Re: draft-housley-two-maturity-levels
References: <4B803580-664C-42B3-92A7-712452F12BA3@gmail.com> <01NTJJR8423E000CVY@mauve.mrochek.com> <4CC854D9.2060109@dcrocker.net>
In-Reply-To: <4CC854D9.2060109@dcrocker.net>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms000902050905000501000301"
Cc: Dave CROCKER <dhc2@dcrocker.net>, 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: Wed, 27 Oct 2010 23:14:42 -0000

On 10/27/10 10:35 AM, Dave CROCKER wrote:
> 
> 
> On 10/27/2010 8:53 AM, ned+ietf@mauve.mrochek.com wrote:
>> three level is one level too many. Simplifying things and
>> eliminating process clutter is helpful in and of itself.
> 
> 
> By my reading of the proposal, this means that any spec with a couple of
> interoperable implementations can become a (full) Internet Standard.
> 
> This means that the assignment of that final status has nothing to do
> with real-world deployment and use, or even inclusion in products.
> 
> In other words, it has nothing to do with demonstrated utility.
> 
> Is that really what the IETF community wants?

I think there is a disconnect between the proposal as currently
structured and the core principle that the IETF community has always
professed: "rough consensus and running code".

As I understand it, running code means that the technology has been
deployed across the full breadth of the Internet, in services large and
small, by individuals and companies and service providers and
universities and government agencies and all the other kinds of entities
that are connected to the network. The technology doesn't need to be
universally deployed, but it does need to be widely deployed.

We can't achieve that kind of deployment in 6 months. We might achieve
that kind of deployment in 6 years.

We also can't measure that kind of deployment through rather informal
reports from the producers of two interoperable implementations. And if
we measure the wrong thing, we'll get the wrong results.

I don't think anyone in the IETF community wants to see the term
"Internet Standard" applied to a toy protocol merely because the
original designer just happened to convince one of his friends that it
would be cool to implement that protocol in a second hobby project.

"Internet Standard" is a weighty designation, and I think that to earn
it a technology community needs to show some weighty proof.

So I'm in favor of two maturity levels because it recognizes reality and
simplifies things in a reasonable way, but I think we need to reflect
more carefully and completely on how we determine if something is indeed
an Internet Standard.

And no, I don't yet have text to propose, although I'll get to work on
that...

Peter

-- 
Peter Saint-Andre
https://stpeter.im/