With my IAOC hat on, I'm delighted with this draft - lots
of rather precise items that will help prepare the RFP.
Now here are my *personal* comments on the text.
(I could have split this into 9 separate messages
but that seemed over the top.)
3.8. Allocation of Permanent Stable Identifiers
Something needs to be said about the assignment of STD numbers
and STD names. I don't know if it fits here, but either it
has to be specified as an action by the publisher, or this job
has to be moved into the IETF process.
...
o Potential Req- PERMID-2 - The IETF technical publisher should
permit early allocation of stable identifiers for or by the IESG
to satisfy referencing requirements of external bodies.
Should the two-month appeal period be mentioned here?
3.9. Document Format Conversions
...
o Current Req-DOCCONVERT-1 - The IETF technical publisher should
accept as input ascii text files and publish documents as ascii
text files, postscript files, and pdf files.
There has to be something wrong there. When the PS or PDF version
contains graphics etc, surely the publisher must have accepted
another format than pure ASCII?
3.11. Publication Status Tracking
Should we also have a requirement to include normative reference
chains in the status tracking?
3.13. Exception Handling
...
o Current Req-EXCEPTIONS-2 - The IETF technical publisher should
have the discretion to reject publication of an independent
submission based upon feedback from reviewers.
I don't think this is properly called an exception, and I think it
very much over-simplifies the issue - see my earlier message on
this topic.
o Current Req-EXCEPTIONS-3 - The IETF technical publisher should
permit documents to be put on hold awaiting the outcome of an
appeal.
Add: or a legal process.
3.15. Post Publication Corrections
We need to say something about technical vetting of errata. They
can't just be published without checking them.
Is this a task for the publisher? Does the publisher need IETF support
for this?
3.16. Indexing: maintenance of the catalog
I believe there is an important missing piece here, i.e. the creation
and maintenance of the hyperlinked index
(http://www.rfc-editor.org/rfcxx00.html today).
3.21. Tutorial and Help Services
Missing requirement: responding to indvidual email queries (with a ticket
system)
4.1. Post-approval timeframes
4.2. Publication Throughput
I think the metrics should include median dwell times as well as the 90th
percentile
and throughput.
Brian
_______________________________________________
Techspec mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/techspec
