[rfc-i] RFC Editor Structure

Frank Ellermann nobody at xyzzy.claranet.de
Wed Jun 4 07:59:16 PDT 2008

Olaf Kolkman wrote:

> The proposed model is posted on the RFC interest list, see
> http://mailman.rfc-editor.org/pipermail/rfc-interest/2008-May/000581.html
> and made available through 
> http://www.iab.org/documents/resources/RFC-Editor-Model.html

Thanks for info.  Some quick observations while looking at the
picture of your model:  You don't cover the rather convoluted
interactions between IESG and "ISS", to fix that please sort
the "stream" columns like that:  IAB | IETF | community | IRTF.

What does "selected by the community and confirmed by the IAB"
actually mean, is it the same idea as for area directors, i.e.
NomCom representing a random set of volunteers from visitors of
three out of five recent IETF meetings ?

Why should there be two persons - new "ISS" and new RFC-editor -
instead of one ?  In what way would a new "ISS" selected by the
NomCom be really independent from IETF / IESG considerations,
which is the whole point of this "independent" escape hatch as
noted two years ago in the RFC 4844 discussions by John Klensin ?

RFC number assignment should be the privilege of the RFC editor,
not of some "outsourced" RFC production entity.  This used to be
great magic in the past, and it is a completely subjective magic.

Moving some "RFC publisher" functions to the IETF secretariat
could make sense, if that is about maintaining a high traffic
Web server with tricky forms.  But the quality of some IETF Web
server forms is not yet up to the standard of some RFC editor
forms.  Working Web forms can't be expensive, please don't try
to fix it if it is not broken.


More information about the rfc-interest mailing list