This IESG charter attempts to capture what the IESG has believed that it
has been asked to do by the IETF community. Most of the document is simply
collecting references to sections of other IETF BCP documents, and
attempting to form a coherent picture of what the IESG is supposed to be
doing.
I think it is useful to document current practice and the justification for
that practice.
I do not think it's a good idea to call it a charter, at least not at this
stage, because the work of documenting current practice needs to be kept
separate from the work of documenting desirable practice. Many people
understand the word 'charter' as a grant of rights/privileges/
responsibilities/etc. and that's not the same thing as documenting current
practice. If the document claims to grant rights to IESG, and people don't
like those rights, people will want to change the document, and that
interferes with the work of documenting current practice.
It's fine to request that the document that describes current practice be
labelled BCP; this is very much in line with the purpose of BCP. But if there
is pushback from the community that says this document is not desirable
practice, the document should be published as Informational and clearly
labelled as documenting current practice - NOT claiming that it is a charter.
Keith