Re: [apps-review] Feeling kind of confused about draft-merrick-jms-uri-12
SM <sm+ietf@elandsys.com> Thu, 27 January 2011 17:53 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 D5A1E3A69C2 for <apps-review@core3.amsl.com>; Thu, 27 Jan 2011 09:53:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.502
X-Spam-Level:
X-Spam-Status: No, score=-102.502 tagged_above=-999 required=5 tests=[AWL=0.097, 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 eeaCQvCTowEg for <apps-review@core3.amsl.com>; Thu, 27 Jan 2011 09:53:29 -0800 (PST)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by core3.amsl.com (Postfix) with ESMTP id 2AA6C3A69C1 for <apps-review@ietf.org>; Thu, 27 Jan 2011 09:53:29 -0800 (PST)
Received: from SUBMAN.elandsys.com ([41.136.233.251]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id p0RHuNvh026798; Thu, 27 Jan 2011 09:56:29 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1296150992; bh=sGy1nJfVS7DUGf84gLni8eJEnUk=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=Hl7rvM2mp6QDtlDJ78CTVMvYHfehq09Uo2vQDwzNNrHEl5hlZLIjgviWJt6NXLXCt /MWpJKkdzB3aelax0EMGenNvmowxdyIzFHR1I1h5RDmsFVhs8cFwE7dLa1idbR5v3q aiqeSU0SUeXm55W9uWgG8CizvTMsD+/zpazWiZO4=
Message-Id: <6.2.5.6.2.20110127010602.0b515078@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Jan 2011 09:44:03 -0800
To: John C Klensin <john@jck.com>
From: SM <sm+ietf@elandsys.com>
In-Reply-To: <5869A181BE49612A2C0C7836@PST.JCK.COM>
References: <AANLkTikaHw7GKiAn1B4Uu5sytyzmi97ExejzfDT82UzO@mail.gmail.com> <6.2.5.6.2.20110126212046.0c26cae8@resistor.net> <5869A181BE49612A2C0C7836@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: apps-review@ietf.org
Subject: Re: [apps-review] Feeling kind of confused about draft-merrick-jms-uri-12
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: Thu, 27 Jan 2011 17:53:34 -0000
Hi John, [following up on apps-review] At 23:20 26-01-11, John C Klensin wrote: >Remember too that, as Mark has already pointed out in a >different way, the main point of a provisional registration is >to lower the odds that the same protocol identifier string will >be used to designate two different protocols. Mark and you have commented on this case. There was a comment from Larry ( http://www.ietf.org/mail-archive/web/apps-discuss/current/msg02096.html ). >I am not advising this in any way and I personally don't think >it would be worth the effort, but, in the interest of procedural >knowledge and consistency, RFC 2026 does give anyone who feels >strongly about this decision the right to appeal it. I suggest talking to the Apps Area Directors before taking that path. When a request for review come from the Apps Area Directors, I pick a reviewer for the assignment. There was a case where the document was over 300 pages and there was a short deadline. I mentioned to the ADs that it would be too much work and they agreed not to request a review by the team. The assignment task generally works like this: (a) Receive request for review (b) Verify whether the document is relevant to the Apps Area and that there is a team member with the expertise to perform the review (c) Assign the review to a team member (d) Add the document to the Apps Area Review tracker (e) Send out reminders to the reviewer (f) Update the Apps Area Review tracker once the review is submitted I think that the Apps Area Directors find the reviews useful or else they would not have asked for it. Some authors respond to the reviews. For example: http://www.ietf.org/mail-archive/web/apps-discuss/current/msg01740.html http://www.ietf.org/mail-archive/web/apps-discuss/current/msg01814.html http://www.ietf.org/mail-archive/web/apps-discuss/current/msg01828.html http://www.ietf.org/mail-archive/web/apps-discuss/current/msg01835.html http://www.ietf.org/mail-archive/web/apps-discuss/current/msg02124.html The Apps Area Team reviews are also copied to the IESG as an AD asked for that after he read one of the Apps Area reviews. The reviews are also read by future authors and it can help them when they write an Internet-Draft. It has been difficult to get all the reviews done. I value the contributions made by Tim and all members of the team. I may voice my discontent to the Apps Area ADs if a reviewer mentions that his/her work is not given any consideration. Best regards, -sm
- Re: [apps-review] Feeling kind of confused about … SM
- Re: [apps-review] Feeling kind of confused about … SM
- Re: [apps-review] Feeling kind of confused about … Mark Nottingham
- Re: [apps-review] Feeling kind of confused about … John C Klensin
- [apps-review] The importance of Apps Review team … Alexey Melnikov