Re: draft-housley-two-maturity-levels

Dave CROCKER <dhc2@dcrocker.net> Sat, 29 January 2011 20:49 UTC

Return-Path: <dhc2@dcrocker.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 DD0CE3A6880 for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 12:49:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.583
X-Spam-Level:
X-Spam-Status: No, score=-6.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 5bBvIwpjdMtE for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 12:49:22 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id E0D4B3A686D for <ietf@ietf.org>; Sat, 29 Jan 2011 12:49:22 -0800 (PST)
Received: from [192.168.1.4] (adsl-68-122-35-253.dsl.pltn13.pacbell.net [68.122.35.253]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p0TKqQKk006838 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sat, 29 Jan 2011 12:52:31 -0800
Message-ID: <4D447DF8.7040800@dcrocker.net>
Date: Sat, 29 Jan 2011 12:52:08 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-housley-two-maturity-levels
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu> <4D44741A.9070108@gmail.com>
In-Reply-To: <4D44741A.9070108@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 29 Jan 2011 12:52:32 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Sat, 29 Jan 2011 20:49:24 -0000

On 1/29/2011 12:10 PM, Brian E Carpenter wrote:
> On 2011-01-27 16:29, Scott O. Bradner wrote:
>> 4/ as part of #3 - the rules should also specifically deal with
>>     the following pp from 2026
>>
>>        The requirement for at least two independent and interoperable
>>        implementations applies to all of the options and features of the
...
> Actually the draft does not appear to require interoperability testing
> at all:
>
>       "* There are a significant number of implementations with
>          successful operational experience."
>
> Is that intentional? I thought interop was generally regarded as


People are confusing testing with use. Those are two different kinds of 
"interoperability", with the latter being far more stringent.

The new draft specifies the latter.  And it quite intentionally does not specify 
the former.

While "testing" is extremely important for when doing development, there is no 
reason that the IETF should be required to include that very intermediary 
activity within our standards process.

So the new proposal has two phases:

    1) Specification

    2) Use

That there are intermediate real-world phases, such as development, testing and 
deployment is essential, of course.  But there is nothing essential in having 
the IETF mark completion of any of those intermediate phases.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net