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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 01 July 2008 21:58 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 433DA3A6BEE; Tue, 1 Jul 2008 14:58:13 -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 11FD53A67A5 for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 14:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level:
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[AWL=0.277, BAYES_00=-2.599]
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 U5kmsDYEEe7p for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 14:58:11 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by core3.amsl.com (Postfix) with ESMTP id F23553A6B06 for <ietf@ietf.org>; Tue, 1 Jul 2008 14:58:01 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id k34so57740wah.25 for <ietf@ietf.org>; Tue, 01 Jul 2008 14:58:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Fr5V2hJ3TaQ7n4s6ZxoyYliGrLCiruDHhOvxAzvkC/s=; b=bCQRKw/IcUVWWszSfLfl8vBBcbMUM3fChuYZsOWMbrJdc1FVVMcCZxRhB8wntAN/x5 +sOaia0aycQbch6uoJqksC2BYrISJQ5wuanAGts8PpGZp3N3rlTGcUzhzBqiPuddKPy9 hTvDwIeGWP3MN5ZTm6uobjdmYgzb7zuGSBpHI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=NaqQzuDGu3h6peHZEv0GSOSe9G3+TjYFdY4gyX9DCzo0FMYwi0L41sN/doyHAs9aBU 71uB46BWGwPcjUI2NEfW8/nr2Jvg1xZn2xg4Qa3sMWdq+CnHvPFgT8NxukBP++qpeiHC ec1BMhJM6mB8LQtpSYNEW3sweEyHm3Lz0h9hA=
Received: by 10.115.18.3 with SMTP id v3mr6292675wai.218.1214949492241; Tue, 01 Jul 2008 14:58:12 -0700 (PDT)
Received: from ?130.216.38.124? ( [130.216.38.124]) by mx.google.com with ESMTPS id v35sm11074628wah.12.2008.07.01.14.58.10 (version=SSLv3 cipher=RC4-MD5); Tue, 01 Jul 2008 14:58:12 -0700 (PDT)
Message-ID: <486AA86A.4070801@gmail.com>
Date: Wed, 02 Jul 2008 09:58:02 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.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> <486380C4.6000607@qualcomm.com> <48642503.2000805@gmail.com> <4864F4A4.20103@qualcomm.com> <4868202B.5050408@piuha.net> <p06240604c49047431468@[129.46.226.27]> <486A9C83.8090707@joelhalpern.com>
In-Reply-To: <486A9C83.8090707@joelhalpern.com>
Cc: "ietf@ietf.org" <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-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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On 2008-07-02 09:07, Joel M. Halpern wrote:
> Of course, we also get complaints whenever anyone raises an issue
> without providing text.  So, by a strict reading of the argument, the AD
> is hanged if he provides text (directing the working group) and hanged
> if he does not provide text (you didn't make clear what your problem is,
> and how to fix it.)

There is, I think a big difference between an AD writing

(a) "Here is the fix for my problem"
and
(b) "Here is my proposal for one way to fix this issue; there may of
course be other ways to do so, so please let me know what the WG
prefers to do."

But that takes time to type in, and an overloaded AD (or reviewer)
will be very tempted just to write "Suggested fix:".

Maybe we should assign specific (b) semantics to SUGGESTION and
use that as shorthand?

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