Requirement on what criteria to specify on how long to publish a document. Proposed Resolution: Basically we are telling the technical publisher how high to jump. So we can have endless arguments on how to measure it and what number we should pick. I am going to throw out a number to get the fight started. It may turn out that the final number will be based upon contractual agreements, but it is good to have a target to start with.
Potential Req-TIMEFRAMES-1 - The IETF technical publisher should have a goal of an average publication time of 4 weeks and 98% of all documents should be published within 8 weeks. Documents held up due to references or due to a protocol action should be excluded from this statistic. Potential Req-TIMEFRAMES-2 - The IETF technical publisher should have a goal of an average stable indentifier allocation time of 4 weeks and 98% of documents should have a stable identifier allocated within 8 weeks of approval. Documents held up due to references or due to a protocol action should be excluded from this statistic. Fulfiling these guidelines means that the publisher would have to publish before the appeals window. Note however that the appeals process is only one mechanism. A legal action challenging a document could occur months or even years after its publication. A new potential requirement is added: Potential Req-INDEX-6 - The IETF can indicate to the publisher that it should change the status of a document (e.g., to Historical) and this should be reflected in the index. Add a bullet to Section 5 (IETF Implications of Technical Publication Requirements) indicating that the IETF needs to define a process to decide and inform the technical publisher of status changes to published documents as the result of an appeal, legal action, or some other procedural action. _______________________________________________ Techspec mailing list [email protected] https://www1.ietf.org/mailman/listinfo/techspec
