Re: [apps-review] apps-team review of draft-ietf-speechsc-mrcpv2-24

Eric Burger <eburger@standardstrack.com> Thu, 28 April 2011 00:36 UTC

Return-Path: <eburger@standardstrack.com>
X-Original-To: apps-review@ietfa.amsl.com
Delivered-To: apps-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 673BEE07EB for <apps-review@ietfa.amsl.com>; Wed, 27 Apr 2011 17:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level:
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ApFqKQvWY0gI for <apps-review@ietfa.amsl.com>; Wed, 27 Apr 2011 17:36:15 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [66.117.3.189]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB2EE0691 for <apps-review@ietf.org>; Wed, 27 Apr 2011 17:36:15 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Message-Id:References:To:X-Mailer; b=njH36jgg6eqVSRS4Q9qLKBba4SlMSKJ8KUcl9FBtBODsftUW7vQsTYQwNJw9WAqsGQJrkjaxX0x3llBx0iawFu5wf7BhnDVoOsloO78qUMX2fKfO0JxHkuao3Bne3aFZ;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.126]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QFFCs-00076Z-5h; Wed, 27 Apr 2011 17:35:46 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-151--773742168; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <6.2.5.6.2.20110427142718.03163040@elandnews.com>
Date: Wed, 27 Apr 2011 20:36:12 -0400
Message-Id: <07E0ECE1-4CD0-4559-A703-DFFE6FD03AF8@standardstrack.com>
References: <C68CB012D9182D408CED7B884F441D4D05A089B718@nambxv01a.corp.adobe.com> <6.2.5.6.2.20110426092800.0304c710@elandnews.com> <C68CB012D9182D408CED7B884F441D4D05A089B783@nambxv01a.corp.adobe.com> <6.2.5.6.2.20110427091204.05694848@elandnews.com> <C68CB012D9182D408CED7B884F441D4D05A089BA17@nambxv01a.corp.adobe.com> <6.2.5.6.2.20110427142718.03163040@elandnews.com>
To: apps-review@ietf.org
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
Cc: Sparks Robert <RjS@nostrum.com>, Worley Dale <dworley@avaya.com>
Subject: Re: [apps-review] apps-team review of draft-ietf-speechsc-mrcpv2-24
X-BeenThere: apps-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Apps Area Review List <apps-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 28 Apr 2011 00:36:16 -0000

I would offer that after this long and our third editor, the only hope for editorial cleanup would be to have professionals do the cleaning, i.e., the RFC Editor.

The normative requirements issue is potentially a substantial issue that we will look into.

As SM says, Larry has already gone beyond the call of duty given the length and detail of this document.

On Apr 27, 2011, at 6:21 PM, SM wrote:

> Hi Larry,
> At 13:30 27-04-2011, Larry Masinter wrote:
>> I'm willing to put more time into reviewing and working with the authors if I get feedback that my review comments will be considered.
> 
> The document contains 221 pages.  I am aware that you have already spent eight hours on this assignment.  I could say "thanks for putting in more time in the review" as it gets the work done.  Instead, I'll say that you have done more work than expected and it is good to consider whether the authors and working group will make good use of your expertise.
> 
>> Given that the protocol is already widely implemented interoperabily, the goal of getting a "RFC number" shouldn't override completely the goal of having a standard of quality for RFCs which rises to the level that a RFC can be understood by reading the RFC.
> 
> Yes, but that's often ignored for the sake of expediency.
> 
>> I think substantial editorial improvemenet could be made with, oh, a week's worth of work on the part of the editors fixing introductory material, clearing up references.
> 
> Ok.
> 
>> However, the most important thing for moving this document forward would be to insure that the normative requirements (MUST, MAY, SHOULD) are actually testable or at least determinable, in the path of moving the document to Draft Standard.... where each "feature" needs evaluation as to mulitple independent interoperable implementations of every feature.
> 
> There aren't a lot of RFCs that move from "Proposed" to "Draft".  Most working groups do not get their documents beyond "Proposed".  Convincing the IESG that it is worth the effort is not worth the effort. :-)
> 
> Please go ahead and post the review.
> 
> Best regards,
> -sm 
> _______________________________________________
> apps-review mailing list
> apps-review@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-review