However I strongly disagree about the use of process. IESG should
not accept WG output that doesn't meet the quality required for
standardization (which includes breaking things).
Yes, but the proper way is for the WG to prepare its proposals and
then to discuss them with the IESG, usually via the Area Director in
the first instance.
the WG needs to make a good faith effort to try to make its
proposals conform to RFC 2026. a WG that fails to do this should be
summarily disbanded.
this is not specific to usefor. I'm just sick of groups insisting that
they have a right to publish whatever brain-damage the isolated,
narrowly foucsed WG thinks it has consensus on.