Re: Running code, take 2

--On Saturday, December 15, 2012 18:03 +0200 Yaron Sheffer
<yaronf(_dot_)ietf(_at_)gmail(_dot_)com> wrote:

> Hi John,
>
> According to Google, exactly one such report was issued:
> http://tools.ietf.org/html/draft-yevstifeyev-ion-report-06
> (the published RFC omitted the results of the experiment,
> somehow). And this particular experiment is not even mentioned
> in http://www.ietf.org/iesg/process-experiment.html. Two other
> experiments are listed, and I was unable to find any reports
> summarizing them.
>
> So I'm willing to concede that the "process experiment"
> experiment failed. But since I think it *could have been* a
> valuable process, and since I'm seeing an IESG member
> proposing to use it, I would request to hear from the IESG if
> they think RFC 3933 is still a management tool they'd like to
> use.
Yaron,

FWIW, _I_ still think it us a useful tool for situations in
which an experiment cannot otherwise be performed without
violating existing procedures.   In that regard, I've just been
trying to make two points:

(1) As far as I can tell, neither your proposal nor Stephen's
requires a violation of existing rules.   Both, again as far as
I can tell, can be performed by agreement between WG Chairs and
the relevant AD and at the discretion of the latter.   That
assumes that no one on the IESG would object strenuously and
that no one would find a decision to appeal on the grounds that
the faster procedure had the effect of suppressing important
input, but those risks would occur even if there were a formal
process experiment.

(2) One cannot justify a formal, 3933-style, process experiment
on the grounds that it would produce a report.  Reports are
possible without such experiments and, as you have seen, despite
the 3933 requirement the reports often do not appear in the
official record.

   john