Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP

Dave CROCKER <dhc2@dcrocker.net> Fri, 28 August 2009 02:13 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 A0DEE3A6C61 for <ietf@core3.amsl.com>; Thu, 27 Aug 2009 19:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.596
X-Spam-Level:
X-Spam-Status: No, score=-1.596 tagged_above=-999 required=5 tests=[AWL=0.204, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 wj6SoCnGCEHx for <ietf@core3.amsl.com>; Thu, 27 Aug 2009 19:13: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 036CE3A6D39 for <ietf@ietf.org>; Thu, 27 Aug 2009 19:13:26 -0700 (PDT)
Received: from [127.0.0.1] (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 n7S2DQMj017798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 27 Aug 2009 19:13:31 -0700
Message-ID: <4A973D42.8030203@dcrocker.net>
Date: Thu, 27 Aug 2009 19:13:22 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP
References: <20090601135553.76CC73A6DB6@core3.amsl.com> <4A23EA07.8030709@piuha.net> <4A23EC17.1010303@piuha.net> <DC08019F-8EAC-40FF-BCE9-66AA0F473DFB@NLnetLabs.nl> <86C717D4-1B08-4155-8B98-FF11EC80501E@cisco.com> <20090827155712.F1FE89A4738@odin.smetech.net> <4A973005.3070506@gmail.com>
In-Reply-To: <4A973005.3070506@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]); Thu, 27 Aug 2009 19:13:31 -0700 (PDT)
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, 28 Aug 2009 02:13:33 -0000

>>>>  I am under
>>> the understanding the the IESG Note in RFC is provided by the IESG not
>>> by the RFC Editor. Is there a document that says otherwise? (I'm
>>> certainly open to the possibility that perhaps these documents should
>>> not have an IESG note but that seems a different issue)
>> My understanding of this text is that the IESG can recommend text,
>> including an IESG Note.  The RFC Editor can accept it or not.  
...
> 
> I'm pretty sure, though, that there has been pushback and negotiation
> on quite a few occasions. It's important that the RFC Editor keeps
> this power, in the general interest of checks and balances. 


+1.

One can debate various details and costs about the RFC Editor function.  But it 
really is quite useful to have the editor exert an independent review of IESG 
efforts to modify an RFC.

Not because the IESG is suspect, but because it is deeply involved in the topics 
it comments on and that could cause misguided decisions.  By contrast, the RFC 
Editor can consider suggested IESG notes with detachment.

My impression, too, is that this has produced revised IESG text.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net