Re: The IESG that can so "no!"

Bernard Aboba <bernard_aboba@hotmail.com> Tue, 10 February 2009 06:34 UTC

Return-Path: <bernard_aboba@hotmail.com>
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 C0BEF3A6C52 for <ietf@core3.amsl.com>; Mon, 9 Feb 2009 22:34:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.394
X-Spam-Level:
X-Spam-Status: No, score=-2.394 tagged_above=-999 required=5 tests=[AWL=0.204, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 IC1wVuXj7Y6R for <ietf@core3.amsl.com>; Mon, 9 Feb 2009 22:34:54 -0800 (PST)
Received: from blu0-omc2-s30.blu0.hotmail.com (blu0-omc2-s30.blu0.hotmail.com [65.55.111.105]) by core3.amsl.com (Postfix) with ESMTP id D0B4A3A6BCF for <ietf@ietf.org>; Mon, 9 Feb 2009 22:34:53 -0800 (PST)
Received: from BLU137-W42 ([65.55.111.72]) by blu0-omc2-s30.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Feb 2009 22:34:57 -0800
Message-ID: <BLU137-W4241A94BEABAA3CB0278AD93BD0@phx.gbl>
Content-Type: multipart/alternative; boundary="_aa419409-fdeb-4011-8dc5-0f76c953352e_"
X-Originating-IP: [24.19.160.53]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: ietf@ietf.org
Subject: Re: The IESG that can so "no!"
Date: Mon, 09 Feb 2009 22:34:56 -0800
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 10 Feb 2009 06:34:57.0120 (UTC) FILETIME=[B0C2CE00:01C98B49]
X-Mailman-Approved-At: Tue, 10 Feb 2009 16:51:21 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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, 10 Feb 2009 06:34:54 -0000

Thomas Narten said:

"At the 20k level, I pretty much agree with everything John has said.
This smells to me mostly of a way for the IESG to have an friendlier
way of shutting down a WG without huring people's feelings. Sorry, but
I think this missed the point. (I would be fine with individual cases
being closed due to OBE, but even then the reasons will be nuanced and
not covered by a broad statement.)

OBE is not well defined, and folk will just start arguing about
whether something really is OBE or not. I.e, we're just moving the
problem elsewhere. In some cases, the problem may be easier to solve
this way, but in others I doubt it."

I agree with this.   The IESG should have the right to close a WG for
a wide variety of reasons, including lack of progress.  Whatever those
reasons might be, they should be subject to a approval by the IESG
as a whole, as well as confirmation by IETF consensus.  

Given this, I don't believe that this draft IESG statement really 
helps much.  If the IESG feels unable to close WGs that
need to be closed, then they should write a document addressing
this issue and bring it to IETF last call.   This doesn't necessarily
require RFC 2026bis (though getting that done is also necessary,
but a subject for another discussion).