Subject: [Techspec] Summary of pub-req scope discussions and proposals

From: "Stephen Hayes (TX/EUS)" <[email-masked]>
Date: Wed, 22 Feb 2006 17:16:04 -0600

The issue being discussed is whether the mankin-pub-req draft should address IESG approved documents or have a wider scope.

It has been pointed out that it is useful to have a common set of requirements on the technical publisher, but that the client organizations may well have differing processes that may be impossible to coordinate.

mankin-pub-req currently deals mainly with requirements on the technical publisher.  The need for further process work within the IETF is recognized within section 5, but is not fully dealt with.  So, with the exception of section 5, the technical publisher requirements should apply to all the client organizations.

It is recommended that:
1. The scope of pub-req be clarified to indicate that it applies to documents within the IETF family including IETF documents processed by the IESG, IAB documents processed by the IETF, and IRTF documents processed by the IRTF (other wording happily accepted).

2. Ensure that these organizations which use the technical publisher service have the opportunity to review mankin-pub-req so that it represents the consensus of the IETF family.

3. Modify section 5 to indicate that processes for working with and feeding documents into the technical publisher needs to be developed in the respective organizations, however indicate that this will be documented in companion documents which can be generated by the respective organizations.

4. Processes for arbitrating between competing resource requests by organizations within the IETF family needs to be dealt with, but mankin-pub-req does not seem like an appropriate place for documenting the priorities.  So this would not be covered in mankin-pub-req.

Regards, Stephen

_______________________________________________
Techspec mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/techspec