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
--On 6. januar 2005 10:48 -0800 Dave Crocker <dhc2@xxxxxxxxxxxx> wrote:
However the reason why many things come in as individual submissions is that the community doesn't care much.
I sure hope you are very, very wrong.
If the community does not care much, then I do not see the purpose in making it an IETF standard.
A standards process is primarily about gaining community support for a common way of doing something.
So if the IESG is satisfied enough to put out a lastcall, and nobody responds -- it doesn't have community support -- the default community position shouldn't be "no" but "no objection".
That's a default 'yes'.
We already have a problem with producing specifications that no one uses. A default 'yes' on outside submissions makes it likely we will get lots more.
d/ -- Dave Crocker Brandenburg InternetWorking +1.408.246.8253 dcrocker a t ... WE'VE MOVED to: www.bbiw.net
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf