Re: Guidelines for authors and reviewers

Suresh Krishnan <suresh.krishnan@ericsson.com> Tue, 03 June 2008 17:55 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 A014028C165; Tue, 3 Jun 2008 10:55:08 -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 CD81B28C165 for <ietf@core3.amsl.com>; Tue, 3 Jun 2008 10:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level:
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, 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 Zu+D8bz-rHMY for <ietf@core3.amsl.com>; Tue, 3 Jun 2008 10:55:07 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id D7BED28C137 for <ietf@ietf.org>; Tue, 3 Jun 2008 10:55:06 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m53Ht5Om000635; Tue, 3 Jun 2008 12:55:08 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 3 Jun 2008 12:55:05 -0500
Received: from [142.133.10.113] ([142.133.10.113]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 3 Jun 2008 12:55:05 -0500
Message-ID: <4845857A.7080004@ericsson.com>
Date: Tue, 03 Jun 2008 13:55:06 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080505)
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Guidelines for authors and reviewers
References: <483F2881.40306@ericsson.com> <g1os0u$3ac$1@ger.gmane.org> <48406BAD.3030706@ericsson.com> <p0624081dc466227168bf@[10.20.30.162]> <4840911C.1090800@ericsson.com> <p06240822c46644a16c0d@[10.20.30.162]>
In-Reply-To: <p06240822c46644a16c0d@[10.20.30.162]>
X-OriginalArrivalTime: 03 Jun 2008 17:55:05.0689 (UTC) FILETIME=[F4774490:01C8C5A2]
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-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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Hi Paul,

Paul Hoffman wrote:
>> Agree. And this topic (the recipient list of the review) is something 
>> I think hard about before I send out any review.
> 
> That's good to hear, but I didn't see it reflected in the document; 
> maybe your co-authors had a different slant. Regardless, my preference 
> is to encourage group communication during reviews for anything other 
> than editorial nits and "I was told to read this; I did; it was fine" 
> reviews. Group communication, in both directions for a review, helps 
> everyone. It also helps prevent a WG hearing that "I changed this thing 
> we had all agreed to because I was told to by { a security person | an 
> IAB member | an ex-AD | ... }". Those kinds of changes tend to make a 
> document weaker if they aren't agreed to and possibly modified by the WG 
> who worked on the document.

I will add the following text regarding this in a new section 4.2 before 
the current section 4.2.

***************************START OF TEXT********************************
4.2 Recipients of the review

The list of recipients of the review is tricky to get right. The main 
idea is to make sure all the relevant people receive the review. The 
recipient list is determined mainly by the following factors

* The timeframe of the review (early vs. late)
* The contents of the review (editorial vs. technical)

Early reviews are usually performed by active participants of a working 
group. The preferred destination for these reviews is the working group 
mailing list since it can be reasonably assumed that the persons 
interested in the document are subscribed to the mailing list. This 
applies for both technical and editorial issues. Alternately editorial 
issues can be resolved using a private mail to the author(s).

Late reviews are usually performed by persons who are not active 
participants of the working group and who usually review the draft from 
a different point of view than the working group. If the contents of the 
review are mainly editorial in nature, the reviews can be sent just to 
the authors, the working group chair(s), the document shepherd(s). If 
the review is of a more technical nature it is considered polite to 
include the working group mailing list and/or the IETF discussion list. 
As it is not reasonable to assume that the reviewer will subscribe to 
the working group mailing list just for discussing this issue, the 
working group chair(s) need to make sure that this review will get past 
any moderation controls imposed on non-subscribers by the working group 
mailing list.
****************************END OF TEXT*********************************

Would this resolve your concern?

Thanks
Suresh

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