Re: Guidelines for authors and reviewers
Paul Hoffman <paul.hoffman@vpnc.org> Fri, 30 May 2008 22:01 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 D928F3A67EE; Fri, 30 May 2008 15:01:27 -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 2B67C3A67B6 for <ietf@core3.amsl.com>; Fri, 30 May 2008 15:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level:
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553]
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 rD5Pb7TabG16 for <ietf@core3.amsl.com>; Fri, 30 May 2008 15:01:25 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 274FE3A69CC for <ietf@ietf.org>; Fri, 30 May 2008 15:01:25 -0700 (PDT)
Received: from [10.20.30.162] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m4UM08GQ004674 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 30 May 2008 15:00:09 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624081dc466227168bf@[10.20.30.162]>
In-Reply-To: <48406BAD.3030706@ericsson.com>
References: <483F2881.40306@ericsson.com> <g1os0u$3ac$1@ger.gmane.org> <48406BAD.3030706@ericsson.com>
Date: Fri, 30 May 2008 14:59:01 -0700
To: ietf@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Guidelines for authors and reviewers
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
At 5:03 PM -0400 5/30/08, Suresh Krishnan wrote: >I'm not sure if > > that needs a separate "review netiquette RFC", IMO it should be >> a part of the "Tao", or the next Tao if it is not already clear. > >Paul Hoffman is working on the TAObis. Maybe he can chime in on this. <ching!> The past few editions of the Tao do indeed talk about taking reviews with an open mind. The Tao doesn't talk much about *giving* reviews, mostly because the intended audience (IETF newcomers) are mostly interested in learning how to be in the normal IETF structures, like WGs. Having said that, I agree with some of what Ted Hardie said about the tone of the document. It sounds like there are instructions to document authors on how they are supposed to act when they get reviews. That's bordering on a revision to RFC 2026, which I don't think is what you intended. "It is polite to" and "some document authors like to" are quite different than "are expected to" and "needs to". This document emphasizes reviews going to authors instead of reviews going to WGs or, in the case of individual submissions, reviews going to mailing lists. In the Tao, we emphasize the value of communications to groups so that the group can agree, amplify, show disinterest, or disagree. In the WGs I have co-chaired, the WG got good value out of some of the GenART and SecDir reviews in that it made the whole WG think about the topics brought up. This may be a fundamental difference in view between this document's authors and my preferences, but I think the discussion of where reviewers should be sending their reviews is an important one for the IETF community to have. --Paul Hoffman, Director --VPN Consortium _______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Guidelines for authors and reviewers Suresh Krishnan
- Re: Guidelines for authors and reviewers Frank Ellermann
- Re: Guidelines for authors and reviewers Ted Hardie
- Re: Guidelines for authors and reviewers Suresh Krishnan
- Re: Guidelines for authors and reviewers Suresh Krishnan
- Re: Guidelines for authors and reviewers Paul Hoffman
- Re: Guidelines for authors and reviewers Ted Hardie
- Re: Guidelines for authors and reviewers Joel M. Halpern
- Re: Guidelines for authors and reviewers Suresh Krishnan
- Re: Guidelines for authors and reviewers Suresh Krishnan
- Re: Guidelines for authors and reviewers Ted Hardie
- Re: Guidelines for authors and reviewers Paul Hoffman
- Re: Guidelines for authors and reviewers Joel M. Halpern
- Re: Guidelines for authors and reviewers Brian E Carpenter
- Re: Guidelines for authors and reviewers SM
- Re: Guidelines for authors and reviewers Frank Ellermann
- Re: Guidelines for authors and reviewers SM
- RE: Guidelines for authors and reviewers Romascanu, Dan (Dan)
- Re: Guidelines for authors and reviewers Ted Hardie
- Re: Guidelines for authors and reviewers Joel M. Halpern
- Re: Guidelines for authors and reviewers Scott Brim
- Re: Guidelines for authors and reviewers Suresh Krishnan
- Re: Guidelines for authors and reviewers Ted Hardie
- Re: Guidelines for authors and reviewers Suresh Krishnan
- Re: Guidelines for authors and reviewers Pekka Savola