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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 02 July 2008 12:47 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 66FB63A690D; Wed, 2 Jul 2008 05:47:24 -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 5C1023A690D for <ietf@core3.amsl.com>; Wed, 2 Jul 2008 05:47:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.423
X-Spam-Level:
X-Spam-Status: No, score=-2.423 tagged_above=-999 required=5 tests=[AWL=0.176, 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 AzSAD7J4wz5H for <ietf@core3.amsl.com>; Wed, 2 Jul 2008 05:47:22 -0700 (PDT)
Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 3617C3A68AF for <ietf@ietf.org>; Wed, 2 Jul 2008 05:47:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,737,1204520400"; d="scan'208";a="125826983"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 02 Jul 2008 08:47:31 -0400
X-IronPort-AV: E=Sophos;i="4.27,737,1204520400"; d="scan'208";a="227815827"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 02 Jul 2008 08:47:30 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: Qualitative Analysis of IETF and IESG trends (Re: Measuring IETF and IESG trends)
Date: Wed, 2 Jul 2008 14:47:28 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04D93A7F@307622ANEX5.global.avaya.com>
In-Reply-To: <486AA86A.4070801@gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Qualitative Analysis of IETF and IESG trends (Re: Measuring IETF and IESG trends)
Thread-Index: AcjbxaL7nOE8yQuLRYWnrGBEDnN6CgAe3mSQ
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> <486AA86A.4070801@gmail.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: 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

Speaking as an individual who has also participated in the work of other
standards organizations - In other SDOs, the IEEE 802 for example,
suggesting a fix for a problem detected in the text at ballot time is
not only welcome, but sometimes the recommended if not mandatory
practice. 

Dan



> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On 
> Behalf Of Brian E Carpenter
> Sent: Wednesday, July 02, 2008 12:58 AM
> To: Joel M. Halpern
> Cc: ietf@ietf.org
> Subject: Re: Qualitative Analysis of IETF and IESG trends 
> (Re: Measuring IETF and IESG trends)
> 
> 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
> 
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf