Spencer Dawkins wrote:
I know the current situation splits the responsibility for maintaining
STD and BCP indexes between IETF and the technical publisher, but is
there any reason why we would choose to continue with the split
responsibility, if we were starting from scratch?
That, I think, is the point of "as directed by the IETF." It makes it
clear where the policy comes from.
Brian
Spencer
Requirement on the assignment of other identifiers than RFC numbers.
Proposed Resolution: Add in potential requirements along the lines of:
Potential Req- PERMID-3 - The IETF technical publisher should assign
additional permanent identifiers associated with various classes of
documents as directed by the IETF.
In section 5 (IETF Implications of Technical Publication Requirements)
a bullet is added indicating that the classes of documents and the
procedures for allocation of those numbers needs to be defined.
_______________________________________________
Techspec mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/techspec
_______________________________________________
Techspec mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/techspec
