--On 11. mai 2004 08:46 -0400 Scott Bradner <sob(_at_)harvard(_dot_)edu> wrote:
- The work can be done in the IETF, and the author agrees. The author
should (IMHO) be the one to inform the RFC Editor that he/she is
dropping the request to publish outside IETF review.
but that seems to drop a ball - the RFC Editor asks the IESG a question
imo the IESG should answer - maybe just say 'we are talking with the
author about doing this work in the IETF' but at least say something
to close the loop
Yes - the IESG should answer.
But I believe the question being asked is "is there a reason, based on
conflict with existing IETF work, that this document should not be
published?"
And the IESG should answer yes or no to that question.
Anything else should (IMHO) be advice to the RFC Editor and the author, and
not be part of the formal position-taking the IESG makes.
Because in the past, we've seriously bogged down independent publications
because we were debating (with or without the author) whether or not they
should be IETF work.
And we need to stop doing that.
Harald
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf