On 30 November 2011 15:30, Alessandro Vesely <vesely(_at_)tana(_dot_)it> wrote:
Is the IESG part of the problem?
For the status of RFC 5782 my conclusion is that there was some
kind of communication problem. The published comments indicate
that some ADs asked why the draft was not for standards track,
and one AD was quite willing to sponsor it for standards track.
(I asked, that's why I know this.)
This was a tricky case, because it was an IRTF ASRG draft, and
only the IETF (not the IRTF) can publish standards track RFCs.
At some point the author decided to give up on standards track
and use the ordinary IRTF status "informational".
There *is* a problem in communications with the IESG, e.g., at
the moment I have two "tickets", where I can't say if the mails
ever arrived, still wait in some queue for an AD to pick it up,
or were rejected with the rejection never making it to my inbox.
For similar communication issues with IANA requests folks have
suggested to create a visible trouble ticket tracker, maybe the
IESG should adopt this "happiana" proposal also for their own
communications.
-Frank