| | Re: Should the IESG manage or not? |
 | | In the critical edge cases, that would permit the IESG to kill an idea by saying: (i) That idea/request/documentcannot go forward without technical review (ii) We refuse to authorize or manage such a review, therefore it will not occur and the idea or document is dead. |
 | | What I don't think the IESG is ethically permitted to do, even under the provisions of 3932, is say "it conflicts with work being done now in the IETF or that might be done in the future, so it can't be published, but we won't identify the work or facilitate a review". |
 | | That would be reasonable except for the fact that the IESG has appeared to send a clear message that the response to such an I-D would be the statement that it needed technical review and, presumably, that the IESG was not willing to try to seek or allocate resources to get it done. |
| www.mail-archive.com /ietf@ietf.org/msg21428.html (2871 words) |