Re: draft-housley-two-maturity-levels

Dave CROCKER <dhc2@dcrocker.net> Tue, 06 July 2010 15:23 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 9B53A3A6934 for <ietf@core3.amsl.com>; Tue, 6 Jul 2010 08:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.392
X-Spam-Level:
X-Spam-Status: No, score=-5.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, 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 ocH8TjK+cXVq for <ietf@core3.amsl.com>; Tue, 6 Jul 2010 08:23:44 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 750353A699E for <ietf@ietf.org>; Tue, 6 Jul 2010 08:23:44 -0700 (PDT)
Received: from [192.168.1.88] (ppp-68-122-72-44.dsl.pltn13.pacbell.net [68.122.72.44]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o66FNWRH019446 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Jul 2010 08:23:39 -0700
Message-ID: <4C334A71.4040109@dcrocker.net>
Date: Tue, 06 Jul 2010 08:23:29 -0700
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.4) Gecko/20100608 Thunderbird/3.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-housley-two-maturity-levels
References: <599DEF8BAF6E7D88746D18C4@[192.168.1.128]> <6.2.5.6.2.20100705121135.0accf848@resistor.net> <4C32BC57.5070605@gmail.com>
In-Reply-To: <4C32BC57.5070605@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]); Tue, 06 Jul 2010 08:23:39 -0700 (PDT)
Cc: SM <sm@resistor.net>, 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: Tue, 06 Jul 2010 15:23:45 -0000

On 7/5/2010 10:17 PM, Brian E Carpenter wrote:
> On 2010-07-06 08:49, SM wrote:
>Although the IETF Chair is also an IETF participant, it can be
>> perceived as problematic when the person writes a non-technical proposal
>> that has to be evaluated by the IESG.
>
> It could be, but if the proposal is a matter of common sense and
> blindingly obvious simplification, it isn't, IMHO. Let's just do it;
> there is no down side. There may be many other issues, as suggested
> by John, but this simplification can only help everybody.


Brian,

I agree that there seems to be quite a bit of blindness in the way this is being 
discussed.  This is something for which there is no urgency, and about both the 
needs and the benefits being offered are squishy, at best.  Added to this is 
unfortunately strong resistance to serious discussion and consideration of 
concerns and questions being raised.

The assertion that it is possible to take a core construct that has been in 
place for 20 years, and that making a change that is certain to have no 
downsides, is an example of the problem in the current process.

This sort of change has costs.  /ANY/ change has costs.  It does not necessarily 
have any benefits. At the least, there should be careful attention to the 
implementation effort and the potential impact on community use of labels.

Also at the least, folks who are promoting this need to produce a compelling 
benefit statement.  So far, that's lacking.

d/

ps.  SM raises a concern that falls under the category of conflict of interest. 
  This is something that does not require bad intent or bad action; it merely 
requires potentially competing goals (interests).  Having a proposal's proponent 
also be in charge of a proposal's approval is the essence of conflict of interest.

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net