Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis

Eliot Lear <lear@cisco.com> Thu, 19 June 2008 20:33 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3DD853A69D3; Thu, 19 Jun 2008 13:33:09 -0700 (PDT)
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 C3AC73A69DC; Thu, 19 Jun 2008 13:33:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level:
X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[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 jDryFXZjFYde; Thu, 19 Jun 2008 13:33:06 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 2DED13A69B8; Thu, 19 Jun 2008 13:33:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,674,1204498800"; d="scan'208";a="12171719"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 19 Jun 2008 22:33:00 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m5JKX0H2000992; Thu, 19 Jun 2008 22:33:00 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m5JKX0f8015099; Thu, 19 Jun 2008 20:33:00 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Jun 2008 22:33:00 +0200
Received: from adsl-247-5-fixip.tiscali.ch ([10.61.81.179]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Jun 2008 22:32:59 +0200
Message-ID: <485AC27B.6070206@cisco.com>
Date: Thu, 19 Jun 2008 22:32:59 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 3.0a2pre (Macintosh/2008061703)
MIME-Version: 1.0
To: Ted Hardie <hardie@qualcomm.com>
Subject: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
References: <8832006D4D21836CBE6DB469@klensin-asus.vbn.inter-touch.net> <485590E2.3080107@gmail.com> <p06250116c47c330c7dd0@[75.145.176.242]> <4856DE3A.3090804@gmail.com> <C122F91B-59B0-49AC-ABBC-6752217C4E47@NOKIA.COM> <20080619024147.9146C3A6938@core3.amsl.com> <485A353B.30403@dcrocker.net> <20080619175645.0CA443A68C2@core3.amsl.com> <p06240601c480518c107f@[10.0.1.196]>
In-Reply-To: <p06240601c480518c107f@[10.0.1.196]>
X-OriginalArrivalTime: 19 Jun 2008 20:33:00.0192 (UTC) FILETIME=[AA51B200:01C8D24B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1730; t=1213907580; x=1214771580; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20Appeal=20against=20IESG=20blocking=20DI SCUSS=20on=20draft-klensin-rfc2821bis |Sender:=20; bh=zA0NqrcBZ2Nl2CXLr9oXdgscMdwQAuDJtjdPKKKssio=; b=qYves/LMQJTW/5JHEn+1bwSyJp525KloFmtAmPF6fVSMteT3ToQAK6jMuh /X2kECGEUbXAyLLU+nGcu2s00g7iua3vV4rzPHNTvnq+iZDaOf/GV9aXztKG 8Frb3WOEFC;
Authentication-Results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );
Cc: IETF Discussion <ietf@ietf.org>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "iesg@ietf.org" <iesg@ietf.org>
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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Ted Hardie wrote:
>   	There are very few cases where that is okay.  It applies when
> there is a documented, larger community consensus that the WG or
> submission group decision ignores (a working group decision that
> congestion control wasn't important would get pushback on this
> front, for example).  It applies when the Area Director can demonstrate
> harm to the Internet as a result of the decision; the "can demonstrate"
> there, though, is to the *community* not just to himself or the IESG.
> It applies when the Area Director can demonstrate that the proposal
> simply *does not work* to the satisfaction of the larger community, no
> matter what the proposers believe.
>    

Isn't the IESG is meant to serve two roles?  The first is to be the 
arbiter of community consensus.  The second is to be a judge on the 
quality of the work before them, as to whether it is ready to move 
forward.  The threat of the IESG saying, "jeez what a {dumb|complex|...} 
approach" separates us from other standards organizations (or at least 
it did).  The most famous example of all of this is still the 
ETHERNET-MIB WG where they were upset that Jon Postel reset a counter 
size in the final copy of the MIB to match the IEEE specification, and 
those folks were rip roaring upset that he did so.  I don't want the 
IESG to author the docs like Jon did but I do want them to stand in the 
way of dumb ideas.

In this case they should be there to apply our *evolving* standards.  To 
hogtie those folk to me just begs for others to attempt to make use of 
those knots to get their dumb standards.

Shouldn't the response to John's appeal demonstrate the balance between 
their two roles?

Eliot

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf