![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
We need to stop calling this a charter, and start calling it documentation
of current practice. It's clearly useful to document current practice,
and the justification for current practice, especially when a lot of the
criticism of IESG practice is done out of ignorance of what that practice
actually is and the reasons why things are done that way.
Changing the title as Keith suggests would confuse the issue of whether what is in the document meets the community consensus test.
And for the record, I want to thank Harald for trying to write down the IESG Charter. There can be no question this creates hassle for him and others on the IESG, but there has been demand for such a document from some portion of the community for some time. I really appreciate him taking on this activity.
Ran rja at extremenetworks.com
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.