Robert,
The IESG, and the IETF, simply do not have the power to tell the RFC editor what to do, it isn't in the IETF's job description to do that.
And that is of course true, and we do respect that. However, you are missing the fact there is two discussions ongoing, obviously the IETF is developing its own opinion but at the same time the larger community is updating the RFC editor model (h&b, independent submission model, rfc editor component split, etc). The latter work is formally lead by the IAB. This is the reason why I will NOT approve 3932bis solely based on IETF or IESG opinion, but have asked Olaf to ensure that whatever we do, the IAB is also happy with the end result.
(And this works two ways, by the way. My hands are tied with 3932bis if the non-IETF world is unhappy with it. Similarly, 3932bis is currently blocking the implementation of h&b.)
Jari _______________________________________________ Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf