Re: Conclusion of the last call on draft-housley-two-maturity-levels

Keith Moore <moore@network-heretics.com> Sat, 10 September 2011 15:12 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEB6721F84E5 for <ietf@ietfa.amsl.com>; Sat, 10 Sep 2011 08:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.471
X-Spam-Level:
X-Spam-Status: No, score=-3.471 tagged_above=-999 required=5 tests=[AWL=0.127, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SFacR9qyQr4m for <ietf@ietfa.amsl.com>; Sat, 10 Sep 2011 08:12:13 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id A142421F84E1 for <ietf@ietf.org>; Sat, 10 Sep 2011 08:12:13 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 3377424F78; Sat, 10 Sep 2011 11:14:11 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute6.internal (MEProxy); Sat, 10 Sep 2011 11:14:11 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=wMt OD8oLdMIvlJFVkEZmw+WB17o=; b=uhtNRZGL2BfuvgHVxTq1NV+8SxGR2IM9TSX Ye75tTLuyZEMP2yHZxbyWeoYuiVuc+Ohp2p28Ey/GlXZjjSyhJbceczGGdiGIlhh 4aF7pQ1SWjG5BOdpEhlZtTvnZgrMrkriAs37h6zYiNrc3blV4TG2AEjb8eSb3DMo 0puPUuJg=
X-Sasl-enc: mfEIVrwHT89HFaOUrs7FPTHFff0QBAlh5yyuYxETq6Dl 1315667650
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 148E154059D; Sat, 10 Sep 2011 11:14:09 -0400 (EDT)
Subject: Re: Conclusion of the last call on draft-housley-two-maturity-levels
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary="Apple-Mail-1-205508223"
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <2E8B54A8-A024-4869-9E50-1377F48AAA80@vigilsec.com>
Date: Sat, 10 Sep 2011 11:14:00 -0400
Message-Id: <94D40572-03D0-4E35-8C1C-F62537F2798D@network-heretics.com>
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu> <4E5D4570.9080108@piuha.net> <4E6AEBDC.60002@gmail.com> <2E8B54A8-A024-4869-9E50-1377F48AAA80@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 10 Sep 2011 15:12:15 -0000

On Sep 10, 2011, at 10:44 AM, Russ Housley wrote:

> That said, at the plenary at IETF 81, Harald suggested that we have waited so long that incremental improvements may not be the right approach, rather it was time for 2026bis.  I agree that it is needed, but I am not sure the IETF community is willing to tackle a project of that size and complexity.

I suspect that there are two underlying problems, both significant.

1. Many people would see an attempt to change the process as a "threat" of one kind or another, feeling like the result of such change under current circumstances would likely be worse than the status quo.

2. There seems to be wide perceptual variation among IETF participants as to the organization's purpose and/or what's wrong with the current process.

I think there's a need for consensus-building around these two topics (and perhaps others) before even considering whether and how to revise 2026.  In the first case, we need to find out what people see as threats and use that to bound the charter of the rewrite effort so that people won't feel like they have to be in damage control mode.  But the second topic is even more important.   

Keith