Leslie,
This is getting fairly far from what I've understood to be
techspec's non-charter, but two additional observations...
--On Friday, 17 February, 2006 19:14 -0500 Leslie Daigle
<[EMAIL PROTECTED]> wrote:
>
> 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.
I think this is exactly right. From the standpoint of an RFP,
the right organization should be something like:
N. Documents will originate from different sources,
each with its own approval process. All but N.3 are
non-discretionary in terms of publication, although the
RFC Editor may return them to the authorizing body if
they are incomprehensible.
N.1 The IETF (IESG) approval process
N.2 IAB-authorized approval processes
N.3 Independent submissions
N.4 Other processes approved from time to time by the
IAB and IAOC.
N+1. Technical Editing
N+2. Copy editing
N+3. Formatting
...
And, if one gets to this level of detail, the RFP or contract
must address one other issue that arises naturally from multiple
paths: who has the right to set processing priorities and by
what mechanism. We have recently had a situation in which one
body has, from time to time, nearly starved other paths for
resources simply by insisting that its documents come first.
That may be reasonable, or may not, but, if two bodies make the
same demands...
john
_______________________________________________
Techspec mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/techspec
