RE: [Techspec] Editorial notes on draft-mankin-pub-req-08.txt

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 25 May 2006 16:28 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjIh2-0003fp-9x; Thu, 25 May 2006 12:28:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjIh0-0003Yf-SA for techspec@ietf.org; Thu, 25 May 2006 12:28:10 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FjHr4-0003jJ-Hz for techspec@ietf.org; Thu, 25 May 2006 11:34:30 -0400
Received: from balder-227.proper.com ([192.245.12.227]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FjHeX-0001Mc-6J for techspec@ietf.org; Thu, 25 May 2006 11:21:34 -0400
Received: from [10.20.30.249] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k4PFLOtF007433; Thu, 25 May 2006 08:21:25 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0623091ac09b757336ca@[10.20.30.249]>
In-Reply-To: <4DCBC973AF0D6E4FAF9CD998CE1C003802DE2636@eusrcmw720.eamcs.ericsson.se>
References: <4DCBC973AF0D6E4FAF9CD998CE1C003802DE2636@eusrcmw720.eamcs.ericsson.se>
Date: Thu, 25 May 2006 07:57:59 -0700
To: "Stephen Hayes (TX/EUS)" <stephen.hayes@ericsson.com>, techspec@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: RE: [Techspec] Editorial notes on draft-mankin-pub-req-08.txt
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: -2.3 (--)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc:
X-BeenThere: techspec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" <techspec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/techspec>, <mailto:techspec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/techspec>
List-Post: <mailto:techspec@ietf.org>
List-Help: <mailto:techspec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/techspec>, <mailto:techspec-request@ietf.org?subject=subscribe>
Errors-To: techspec-bounces@ietf.org

At 11:32 PM -0500 5/24/06, Stephen Hayes (TX/EUS) wrote:
>  > In section 4.1:
>>      o  Req-TIMEFRAMES-2 - The consensus of the IETF community is that
>>         the time required for a pre-publication review should
>>  be under 10
>>         days. The actual performance targets and metrics are
>>  expected to
>>         be determined as part of the contract negotiation process.
>>  The term "pre-publication review" is not defined anywhere in the
>>  document, and it probably should, given this consensus statement.
>
>It should probably refer to section 3.1.

That sounds fine. You might also want to change "pre-publication 
review" to "Pre-approval review or editing" to match the heading of 
3.1. "Pre-publication review" sounds like what is done just before 
the RFC is emitted.

>  > Section 5 talks about "potential issues" for the IETF. Two bullet
>>  items do not match the earlier part of the document.
>>
>>      o  Pre- vs Post-Approval Editing: If emphasis switches from post-
>>         approval editing to pre-approval editing, then IETF
>>  processes must
>>         be adapted to make use of this service.  The processes
>>  for post-
>>         approval editing can also be streamlined.
>>  Section 3.1 makes a requirement that the emphasis must switch. So,
>>  "If" should probably be "When".
>
>I'm not sure that 3.1 requires that the emphasis must switch to 
>pre-approval reviews.  We are putting a requirement that the 
>publisher support pre-approval reviews, but we have not yet decided 
>if the IETF will really make use of it.

    o  Req-PREEDIT-1: The IETF technical publisher should perform an
       editorial review of documents before WG last call and provide
       feedback to the authors to improve quality of the documents.  This
       review should strive to maintain consistency in appearance with
       previously published documents.
The phrase "should perform" is quite different than "should support". 
It seems that the consensus was that this should be done, so "should 
perform" is correct.

--Paul Hoffman, Director
--VPN Consortium

_______________________________________________
Techspec mailing list
Techspec@ietf.org
https://www1.ietf.org/mailman/listinfo/techspec