![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
But this too is a change; if the people writing the IANA considerations section had desired public review of requests, they would presumably have used "IETF consensus" as the registration criteria; to me, the choice of "IESG review" indicates that the writers of the IANA considerations section thought that the IESG was able to come to a correct decision *without* having to ask for an IETF consensus.
My suggestion for a change would be a bit shorter:
As an experiment, the IESG will send out Last Calls for all requests requiring IESG approval that it wants to reject from <date> to <1 year later>. At the end of that time, it will evaluate the result, and either abandon the practice, modify the practice or make it a standard procedure.
I think that a blanket retrofitting of a new meaning on the "IESG approval" IANA considerations is a thoroughly bad idea.
Agree.
-- Jeff
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.