IETF Logo Mail Archive

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

SM <sm@resistor.net> Fri, 27 June 2008 01:36 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 5E8523A6A80; Thu, 26 Jun 2008 18:36:19 -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 866923A67A8 for <ietf@core3.amsl.com>; Thu, 26 Jun 2008 18:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level:
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=1.650, BAYES_00=-2.599, GB_I_LETTER=-2]
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 ir-mhjFyGfSh for <ietf@core3.amsl.com>; Thu, 26 Jun 2008 18:36:17 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id BFAD23A6A80 for <ietf@ietf.org>; Thu, 26 Jun 2008 18:36:17 -0700 (PDT)
Received: from subman.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.3/8.14.3) with ESMTP id m5R1aB0i028833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 26 Jun 2008 18:36:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1214530579; x=1214616979; bh=L4j0CcUKMDi7+5RapFYp95w5tmYWdRkzHuRW 5JJu66I=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=PwsWg61lcOdyXFcgYwJ/CaD7Or1JcTYEqa X8p1fvpr0w1cDIf0jAn1xiC9TIU3NxNuwwwcGGgcC49ZnkyF53nfBS+Bo6UlgyFrusP g1V5i4VmgvF5jYdkkMiEjvtjvCSBvl99ojB/eJsbczO9vUDBpr9VGoyyEvMtCvyufYC NF8=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=BUC2MtPW3/XvH3Jxi9XXbj5gJgF8y4aOgOzrCuR2Oo2TTnrIcxD54dVUhBbsrI67t giUuHJ0OndvSOkomh3oIn24KxQJFuwIHM2eIknhg+hAQThIwW9TeEEJGolZcPfFXHBb zfRhUecBBFVqNJPhajV6BYDsed18QQT50e77V3Q=
Message-Id: <6.2.5.6.2.20080626175601.02d235b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 26 Jun 2008 18:35:12 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Qualitative Analysis of IETF and IESG trends (Re: Measuring IETF and IESG trends)
In-Reply-To: <486380C4.6000607@qualcomm.com>
References: <20080624203548.D3A8D3A67FD@core3.amsl.com> <48622DEB.7060403@piuha.net> <486267E0.8080704@qualcomm.com> <48628ED6.1000800@piuha.net> <4862BB84.4070401@gmail.com> <486380C4.6000607@qualcomm.com>
Mime-Version: 1.0
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

At 04:43 26-06-2008, Lakshminath Dondeti wrote:
>But, surely the WG consensus counts as part of the overall IETF 
>consensus process, doesn't it?  Please see the example in my 
>response to Jari.  The shepherding AD (or at least the document 
>shepherd) has an idea of the WG consensus as well as the IETF 
>consensus.  We cannot simply weigh the latest opinions more than all 
>the discussions that have happened as part of the WG consensus.

The document may be a product of WG consensus.  It still has to pass 
through the community and the IESG to be published as an IETF document.

The WG knows about the internals of the document and generally have a 
focused view.  The last call allows a wider range of input and to 
gauge the impact the proposal may have in other areas.  It is not 
about weighing the latest opinions more.  The author/shepard can 
always post an explanation.  The participants in the WG should be 
aware that there will be an IETF-wide last call.  You cannot blame 
the process if they choose to remain silent instead of taking part in 
the last call.  Note that letter-writing campaigns in a last call 
have been proven to be ineffective.

Regards,
-sm 

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

v2.23.0 | Report a Bug | By Email