Having mulled it over a bit (and strictly as an individual
contributor here):

I agree about the complexity of trying to capture the
needs of all potential IETF-constellation publication paths.

However, I am concerned that having each (IAB, IRTF) define
their own requirements independently will create something of
an implementation quagmire for the publisher.  ("If it's a
Tuesday, and it's an IAB document, I have 3 days remaining
to get this out").

So, while requirements relating to approval may be
inapplicable to IAB documents (eg), format (conversion) and
publication tracking had better be consistent across all
paths.

I suggest that may mean separating requirements in the document
to be clear about which ones are invariant across all
IETF-group-produced documents, and which ones are specific to
WGs.  Or, call out the "approval" steps and make it clear
they are for IETF WG process, and that other approval
requirements may be created.

Or something.

Leslie.


Harald Tveit Alvestrand wrote:


--On mandag, februar 06, 2006 10:49:33 +0100 Brian E Carpenter <[EMAIL PROTECTED]> wrote:

Scope nit:

   This draft only addresses those documents submitted to the IETF via
   the IAB, IESG, or IRTF.


In fact nothing substantive is said about IAB documents. Perhaps it needs
to be stated as a requirement that the technical publisher shall accept
for publication, as IETF documents, only drafts that have been approved
by the IESG, or drafts from the IAB (which do not require IESG approval).


I'd state flatly that the techspec requirements apply to documents from the IETF that are published with IETF approval, as decided by the IESG.

If, as I think, we want the publication mechanism to be applicable to other documents (which includes independent submissions, IAB documents, IRTF documents and IAOC documents, if any), I think the requirements for those classes of documents need to be separate.

Trying to merge them makes the process of writing them down FAR too convoluted.

                     Harald


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


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

Reply via email to