Spencer Dawkins wrote:
From: "Leslie Daigle" <leslie(_at_)thinkingcat(_dot_)com>
Following the note just sent about the proposed timeline for
reviewing the RFC Editor contract this year, here is the
STRAW proposal RFC Editor charter proposed by the IAB.
It is a modest extension of the RFC Editor paragraph as found
in RFC 2850 (the IAB Charter).
The purpose of this straw proposal is to inform discussions
scheduled for the GENAREA meeting at IETF65 in Dallas.
After the Dallas meeting, the IAB will provide a more formal
charter proposal.
What would help me most, in commenting on this charter, is an
understanding of how much editorial autonomy the IETF expects the RFC
Editor function to exercise in document publication.
My personal answer is that this is for the IETF to decide and
that is what the charter language allows. So we don't answer that
question before establishing the charter.
Now, I have opinions about what the IETF should decide in this area,
but that isn't the question on the table.
I have recently
participated in an exchange on/off the techspec mailing list that has
convinced me that I do NOT understand this (or, at least, that other
smart people who I respect understand it differently).
I'm not even sure that I am hooked up well enough to ask more specific
questions.
Or is this question premature, pending "editorial review and approval
processes, must be defined in IETF community consensus documents"?
I believe it's logically premature; of course we are debating some
of that in techspec, because we need parallelism in the timeline.
draft-irtf-rfcs-00.txt discusses another part of it.
Brian
Thanks,
Spencer
STRAW RFC Editor Charter
The RFC Editor executes editorial management for the publication of the
"Request for Comment" (RFC) document series, which is the permanent
document repository of the IETF community. The RFC series
constitutes the archival publication channel for Internet Standards
and for other contributions by the Internet research and engineering
community. RFCs are available free of charge to anyone via the
Internet. It is the responsibility of the IAB to approve the
appointment of an organization to act as RFC Editor and the general
policy followed by the RFC Editor.
Policies, including those for defining publication tracks and
their requirements, intellectual property rights, as well as
editorial review and approval processes, must be defined in
IETF community consensus documents before being put to the IAB for
approval.
Leslie Daigle.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf