[apps-review] Suggested changes for Applications Area Review Team

SM <sm+ietf@elandsys.com> Sat, 19 March 2011 07:49 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: apps-review@core3.amsl.com
Delivered-To: apps-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A1C0A3A6A0D for <apps-review@core3.amsl.com>; Sat, 19 Mar 2011 00:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 2kKGQsIYGir8 for <apps-review@core3.amsl.com>; Sat, 19 Mar 2011 00:49:44 -0700 (PDT)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by core3.amsl.com (Postfix) with ESMTP id EB3A63A69BE for <apps-review@ietf.org>; Sat, 19 Mar 2011 00:49:44 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.235.103]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id p2J7p6nY026080; Sat, 19 Mar 2011 00:51:11 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1300521073; bh=+iF/WcUpFfUigPBHi7uTPkfjrgg=; h=Message-Id:Date:To:From:Subject:Cc:Mime-Version:Content-Type; b=NMwIWHNWkCUakO7yufKqQzVgFrftOB3qyq4pZMgJ2uYNWVj9mkOS38qIYryA+EWuH C42RyFypmMDjbmi59dMHJvem5qkf0zl4zFx/uWguuhm2DSLmWxNKnFJ+Lab9bwIC2s KYBhd2vE33CjEpFD45zPjh3/l1QRVWmsj0+BqIlU=
Message-Id: <6.2.5.6.2.20110318165117.0d43e6e0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 19 Mar 2011 00:50:46 -0700
To: apps-review@ietf.org
From: SM <sm+ietf@elandsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Pete Resnick <presnick@qualcomm.com>
Subject: [apps-review] Suggested changes for Applications Area Review Team
X-BeenThere: apps-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Apps Area Review List <apps-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-review>
List-Post: <mailto:apps-review@ietf.org>
List-Help: <mailto:apps-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Mar 2011 07:49:47 -0000

Hello,

I have been acting as Applications Area Review Team Lead for nearly a 
year.  My assessment is that the team is still not fully 
functional.  Alexey made some suggestions.  Please comment on the 
following suggested changes:

There are three kinds of requests:

  (a) Early reviews requested by the Apps Area ADs

  (b) Review of a document in Last Call

  (c) Document on the IESG Agenda

I would like to minimize requests for (c) as it would mean a short 
deadline for assignments.

Reviews requested by Apps Area ADs could include a list of issues to 
look for when specific reviewer expertize is required.

When an assignment is made, the review can:

  (i)   acknowledge that he or she can perform the review before the deadline

  (ii)  acknowledge that he or she can perform the review but he or 
she requires more time

  (iii) decline the assignment

If a reply is not provided within 24 hours of the request for review, 
it is assumed that the reviewer will be able to perform the review 
before the deadline.

Team members that have been unable to perform three assignments over 
a six month period can be dropped from the team.

The review template at 
http://www.apps.ietf.org/content/apps-review-template suggests that 
the review should provide a one-sentence summary, e.g.:

  (i)   This draft is ready for publication as an Experimental RFC

  (ii)  This draft is almost ready for publication as an Informational RFC but
        has a few issues that should be fixed before publication

  (iii) This draft is not ready for publication as a Proposed Standard and
        should be revised before publication

followed by major issues, minor issues and nits.

Major issues are the type of concerns that will result in the 
document being blocked until they are resolved.

Minor issues are concerns about clarity or technical accuracy that 
should be discussed and resolved before publication, but which would 
normally be resolved between the authors and the reviewers.

Nits are editorial or layout items.  They would ideally be resolved 
before publication to make the document more readable.  Usually a 
reviewer will not be looking for this type of issue, but may find 
some in the course of the review.

If you have any other suggestions, please send them to the list.

Best regards,
-sm