IETF Logo Mail Archive

Re: Qualitative Analysis of IETF and IESG trends (Re: Measuring IETF and IESG trends)

Lakshminath Dondeti <ldondeti@qualcomm.com> Thu, 26 June 2008 11:38 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 DF9773A6A3C; Thu, 26 Jun 2008 04:38:12 -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 3FFE33A6984 for <ietf@core3.amsl.com>; Thu, 26 Jun 2008 04:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 YpeOa6pIJe4L for <ietf@core3.amsl.com>; Thu, 26 Jun 2008 04:38:10 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id 5A8883A6983 for <ietf@ietf.org>; Thu, 26 Jun 2008 04:38:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=ldondeti@qualcomm.com; q=dns/txt; s=qcdkim; t=1214480293; x=1246016293; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-ironport-av; z=Message-ID:=20<48637FA3.8030407@qualcomm.com>|Date:=20Th u,=2026=20Jun=202008=2004:38:11=20-0700|From:=20Lakshmina th=20Dondeti=20<ldondeti@qualcomm.com>|User-Agent:=20Thun derbird=202.0.0.14=20(Windows/20080421)|MIME-Version:=201 .0|To:=20John=20C=20Klensin=20<john-ietf@jck.com>|CC:=20B rian=20E=20Carpenter=20<brian.e.carpenter@gmail.com>,=0D =0A=20=20=20=20=20=20=20=20Jari=20Arkko=20<jari.arkko@piu ha.net>,=20ietf@ietf.org|Subject:=20Re:=20Qualitative=20A nalysis=20of=20IETF=20and=20IESG=20trends=20(Re:=09Measur ing=20IETF=0D=0A=20and=20IESG=20trends)|References:=20<20 080624203548.D3A8D3A67FD@core3.amsl.com>=09<48622DEB.7060 403@piuha.net>=09<486267E0.8080704@qualcomm.com>=09<48628 ED6.1000800@piuha.net>=20<4862BB84.4070401@gmail.com>=20< 38B2EAB856D35222B4F5A57C@p3.JCK.COM>|In-Reply-To:=20<38B2 EAB856D35222B4F5A57C@p3.JCK.COM>|Content-Type:=20text/pla in=3B=20charset=3DISO-8859-15=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-IronPort-AV:=20E=3DM cAfee=3Bi=3D"5200,2160,5325"=3B=20a=3D"4069371"; bh=RpmOKbesluGgnBNFghCyC3rKy00V2fdYxU9Elmll7s8=; b=ocsdBgAJqJ9y1E8Fev2ZKX23oNQJA6Ci1reEe9vWzYyivqy1m7k2A1xt QGy6J8+/K4mPxZ+baMV4dUm0mqgpxupCyb56OBgsR4loUgbwxLNOdOqFs oQK7W/RXxV3bgtkuRE4f4lSFXVkiNejlBBhrxyOYsJs92j19TnmaT68+x w=;
X-IronPort-AV: E=McAfee;i="5200,2160,5325"; a="4069371"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 26 Jun 2008 04:38:13 -0700
Received: from msgtransport05.qualcomm.com (msgtransport05.qualcomm.com [129.46.61.150]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m5QBcDxb002354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 26 Jun 2008 04:38:13 -0700
Received: from [10.50.65.162] (qconnect-10-50-65-162.qualcomm.com [10.50.65.162]) by msgtransport05.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m5QBc6ll002155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 26 Jun 2008 04:38:11 -0700
Message-ID: <48637FA3.8030407@qualcomm.com>
Date: Thu, 26 Jun 2008 04:38:11 -0700
From: Lakshminath Dondeti <ldondeti@qualcomm.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Qualitative Analysis of IETF and IESG trends (Re: Measuring IETF and IESG trends)
References: <20080624203548.D3A8D3A67FD@core3.amsl.com> <48622DEB.7060403@piuha.net> <486267E0.8080704@qualcomm.com> <48628ED6.1000800@piuha.net> <4862BB84.4070401@gmail.com> <38B2EAB856D35222B4F5A57C@p3.JCK.COM>
In-Reply-To: <38B2EAB856D35222B4F5A57C@p3.JCK.COM>
Cc: Jari Arkko <jari.arkko@piuha.net>, ietf@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

On 6/25/2008 4:28 PM, John C Klensin wrote:
> 
> --On Thursday, 26 June, 2008 09:41 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>> ...
>> And of course, individual ADs
>> have to think carefully whether a given issue is or is not
>> worthy of a DISCUSS, and sometimes they get it wrong. But
>> that will always be true, however we tune the process and
>> procedures.
> 
> Brian,
> 
> While I agree with this, I also believe that there have to be
> effective safeguards against bad judgments prevailing for too
> long.  And I believe that those have largely slipped away from
> us... unless we believe that making changes, unvalidated by WG
> or mailing list consensus, simply to get a DISCUSS removed is
> the right way to get to "high quality, relevant technical and
> engineering documents...".

Indeed that is the issue!

regards,
Lakshminath

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

v2.23.0 | Report a Bug | By Email