--On onsdag, januar 18, 2006 12:21:55 +0100 Brian E Carpenter
<[EMAIL PROTECTED]> wrote:
Potential Req-TIMEFRAMES-1 - The IETF technical publisher should
have an goal of 90% of documents published within 4 weeks of
approval and all of the documents published within 8 weeks.
Documents held up due to references or due to a
protocol action should be excluded from this statistic.
I don't think that can be done except in the context of a bidding process.
There will be a direct tradeoff between the contract price and this goal,
and so it's not something that can be set in concrete except in the final
contract.
Also, because of the two month timeout in the RFC 2026 appeal process, it
turns
out that our standards process actually implies that an RFC MUST NOT be
published
until two months after approval.
I don't see that that follows - we can always declare the mis-published RFC
Historical and publish a fixed one later, as we did with (for instance) the
RFCs for RADIUS that came out with the wrong port numbers in them, or the
SNMPv3 RFCs that turned out to have the wrong encrypted-values in the
examples.
I don't think the harm from a couple of dead RFCs is big enough that we
need to insist on the wait.
Harald
_______________________________________________
Techspec mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/techspec
