I have one new "root cause" issue that I don't believe was included
in the original Problem Statement:
It takes too long to publish an RFC after final approval.
It currently takes several months for an RFC to be published after it
is approved by the IESG.
This results in several problems:
- RFCs come out much later than they should, contributing greatly to
the perception that the iETF is slow. The time to move from approved
I-D to RFC is often a significant percentage (perhaps averaging 20%
of more?) of the time required to develop and publish a specification.
- Stable references are not available until months after a
specification is fully approved, resulting in ambiguity about the
status of a document and encouraging the use of I-D names as
references, thus blurring the distinction between WG I-Ds and
- Too many changes are made to documents after WG and IESG approval
(copy editing, changes to reflect updated thinking/terminology,
etc.). These changes are often not reviewed or approved by the WG or
- Some RFCs are already out-of-date by the time they are published.
The document then contains the RFC publication date, which may result
in a mistaken impression about when the IETF held a specific view or
encouraged a particular practice.
I believe that the IETF should consider modifications to our document
handling process to reduce or eliminate the delay in publishing
At 2:36 PM +0200 5/10/05, Brian E Carpenter wrote:
Having finally read the list traffic up to date, I have a question.
Can anybody identify a *new* "root cause problem" at the same level
of abstraction as those identified in RFC 3774? Or is it the case
that (at that level of abstraction) we have only been re-discussing
the RFC 3774 problem set?
(Please try to be succinct... or change the subject header if you want
to change the subject.)
Ietf mailing list
Ietf mailing list