Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt

Dave CROCKER <dhc2@dcrocker.net> Fri, 16 October 2009 01:36 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 3230E3A6805 for <ietf@core3.amsl.com>; Thu, 15 Oct 2009 18:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 bmAPZqEJygYk for <ietf@core3.amsl.com>; Thu, 15 Oct 2009 18:36:32 -0700 (PDT)
Received: from sbh17.songbird.com (unknown [IPv6:2001:470:1:76:0:ffff:4834:7148]) by core3.amsl.com (Postfix) with ESMTP id C48EA3A67AD for <ietf@ietf.org>; Thu, 15 Oct 2009 18:36:31 -0700 (PDT)
Received: from [192.168.1.107] (ppp-68-120-198-98.dsl.pltn13.pacbell.net [68.120.198.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n9G1aOvc003722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Oct 2009 18:36:30 -0700
Message-ID: <4AD7CE0E.1070408@dcrocker.net>
Date: Thu, 15 Oct 2009 18:36:14 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt
References: <339BA895C003819F5F29F909@PST.JCK.COM> <4AD7930D.7000100@piuha.net>
In-Reply-To: <4AD7930D.7000100@piuha.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/9902/Thu Oct 15 11:11:51 2009 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 15 Oct 2009 18:36:31 -0700 (PDT)
Cc: rfc-interest@rfc-editor.org, IETF discussion list <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: Fri, 16 Oct 2009 01:36:33 -0000

Jari,


Jari Arkko wrote:
> It is not news that what we proposed as a compromise position isn't optimal 
> from some people's point of view. But a small number of voices should not 
> drive the entire community's choice.

We agree, yet oddly land on different sides.

A review of the public record shows relatively minimal voiced support for the
IESG insistence that it be able to override the RFC Editor's decision.

That is, my reading of the record says that the small number is on the side of 
terminating the multi-decade RFC Editor independence. Perhaps my reading is 
wrong.  An accounting assessment of community views, justifying claims of rough 
consensus, is the usual approach towards resolving this kind of disparity.


> Also, I believe the first order of priority is to find out what the IETF and 
> the larger community wants to do here.

In the face of a complex problem space, combined with a complex solutions space,
and controversy about both, the first priority should be to establish rough
consensus about the problem that is intended to be solved.

That hasn't been done.

Get us to agree on the nature of the "problem" and its degree of severitym --
and therefore the dangers that come from not "solving" it -- and we might be
able to get some common perspectives on solutions.


d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net