Harald,
Using these --and my recent experience with
draft-klensin-ip-service-terms, which is still in the RFC
Editor's queue-- as examples, let me suggest that advancing all
of them is still consistent with what I took Dave to be
suggesting. In each case, there was evidence of a problem that
"some people" felt was worth solving. There was no indication
that there was controversy in the community about whether they
were right on the problem (again, independent of whether they
were right on the solution).
For the IESG to look at a completely quiet last call (or at
least quiet on the problem statement) and say "looks like there
is interest, like the problem is real, and there is no sign of
lack of consensus" seems to me to be a reasonable position.
But, if the Last Call produces an argument about whether the
problem being solved is reasonable or relevant to the
community, _then_ I think the burden shifts to the advocates to
demonstrate that there really is adequate community support for
the idea _and_ for their solution. And, if there isn't
relatively clear consensus on the answers, the default had best
be either "no" or "if there is really enough interest, it is
time to start thinking about WGs or equivalent mechanisms"
(which is a different form of "no" where approval as an
individual submission is involved).
I don't know if that is what Dave intended, but it is how I
interpreted his "default no" condition.
It does bother me that we can approve a something as a
standards-track document about which everyone but the authors
and the IESG are sound asleep, but the solution to that problem
is for the community to wake up and start taking responsibility.
john
--On Friday, 07 January, 2005 10:46 +0100 Harald Tveit
Alvestrand <harald(_at_)alvestrand(_dot_)no> wrote:
[note - this note does NOT talk about the language tags
document]
Recent standards-track/BCP RFCs that came in as individual
submisssions (you can tell this from the draft name in the
rfc-editor.xml file):
RFC 3936 - draft-kompella-rsvp-change
RFC 3935 - draft-alvestrand-ietf-mission
RFC 3934 - draft-wasserman-rfc2418-ml-update
RFC 3915 - draft-hollenbeck-epp-rgp
RFC 3912 - draft-daigle-rfc954bis
Apart from draft-alvestrand, I don't remember any of these
causing much of a stir at Last Call. Still, I think the
decision to advance them was appropriate.
The usual case for an individual submission is, I think:
- there are a number of people who see a need for it
- there are a (usually far lower) number of people who are
willing to work on it
- someone thinks that this isn't controversial enough for a
WG, isn't work enough that the extra effort of setting up a WG
is worth it, is too urgently needed to wait for a WG to get up
to speed, or other version of "doesn't fit with our WG process
- nobody's significantly opposed to getting the work done
A "default no" doesn't seem like a correct procedure here.
Harald
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf