[Techspec] Additional comment on draft-mankin-pub-req-08
Elwyn Davies <elwynd@googlemail.com> Mon, 12 June 2006 17:16 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fpq1S-00022D-6p; Mon, 12 Jun 2006 13:16:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fpq1Q-000228-MG for techspec@ietf.org; Mon, 12 Jun 2006 13:16:16 -0400
Received: from nz-out-0102.google.com ([64.233.162.193]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fpq1P-0005YM-Bl for techspec@ietf.org; Mon, 12 Jun 2006 13:16:16 -0400
Received: by nz-out-0102.google.com with SMTP id q3so1264345nzb for <techspec@ietf.org>; Mon, 12 Jun 2006 10:16:15 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=SPuUwMBJ5aD/KsqgwzvGzLjHoAtRmMYGlCNd6+dO2czW3GAnM2IV5DtroHp3ZpMncgj9lZhVPuKQ0Q/SUDb0+zusWReS8DaXGfiWru9Sc7Cn90rs98D0jXLUlabKyNHz3YyTdoS343Y+qKS5RBYlFB+gv2jwbZ20b0mJiX0vCMc=
Received: by 10.36.118.13 with SMTP id q13mr9083504nzc; Mon, 12 Jun 2006 10:16:12 -0700 (PDT)
Received: from ?81.187.254.247? ( [81.187.254.247]) by mx.gmail.com with ESMTP id 38sm9258042nza.2006.06.12.10.16.11; Mon, 12 Jun 2006 10:16:12 -0700 (PDT)
Message-ID: <448DA205.6040807@googlemail.com>
Date: Mon, 12 Jun 2006 18:19:01 +0100
From: Elwyn Davies <elwynd@googlemail.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: techspec@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Subject: [Techspec] Additional comment on draft-mankin-pub-req-08
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
I appreciate that the last call is strictly over, but one extra point came to mind when considering draft-iab-rfc-editor-00. The requirements in draft-mankin split into two parts: - Those that are specific to the IETF document 'stream' - most;y the 'front end' of the process - Those that apply mainly to the back end of the process and are relevant to any documents that are published by the RFC Editor For convenience when specifying requirements for IAB and IRTF documents etc it would be helpful if the two types of requirements were split into separate sections for easier cross referencing. I have suggested the sections in section 3 which appear to apply specifically to the IETF stream (marked S in the list below), whereas the others are generic (marked G). A small amount of swapping of section order would give the required result, I believe: S 1. Pre-approval review or editing G 2. Preliminary specification availability S 3. Post-approval editorial cleanup G 4. Validation of references G 5. Validation of formal languages G? 6. Insertion of parameter values S 7. Post approval, pre-publication corrections G 8. Allocation of permanent stable identifiers G 9. Document format conversions G 10.Language translation G 11.Publication status tracking S 12.Expedited handling G 13.Exception handling G 14.Notification of publication G 15.Post-publication corrections (errata) G 16.Indexing: maintenance of the catalog G 17.Access to published documents G 18.Maintenance of a vocabulary document G 19.Providing publication statistics and status reports G 20.Process and document evolution G? 21.Tutorial and help services I am not absolutely sure whether sections 6 and 21 are generic - the tutorual and help could be considered to be specific especially with respect to help desk provision at IETF meetings but it is applicable to all documents. Regards, Elwyn _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec
- Re: [Techspec] Additional comment on draft-mankin… John C Klensin
- [Techspec] Additional comment on draft-mankin-pub… Elwyn Davies
- Re: [Techspec] Additional comment on draft-mankin… Elwyn Davies
- Re: [Techspec] Additional comment on draft-mankin… Brian E Carpenter