ietf
[Top] [All Lists]

A charter for the IESG

2003-03-07 09:57:07
Hello,

in December, I published an internet-draft called "draft-iesg-charter-00.txt", containing a proposed text for an IESG charter.
A revised version (-01) was published in January based on comments.

A version with some further clarifications is created, but not published before the cutoff - it's available at
http://www.alvestrand.no/ietf/chair/iesg-charter.txt

Some discussion has taken place on the POISED list (poised(_at_)lists(_dot_)tislabs(_dot_)com), but the point has been made that for such a potentially important document, the IETF list may actually be a more appropriate venue for discussion. Hence this note.

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 do not believe that it shows the IESG to be much different from what the community currently believes it is.

What I hope to do with this document is:

- Discuss it on this mailing list and on the POISED mailing list as the community finds appropriate

- Discuss it privately in San Francisco with those who are concerned, and in the plenary if there are questions raised from the community

- Send out a revised version some time after San Francisco

- Issue a four-week Last Call for BCP on the document once discussion has stabilized

- Approve it for BCP before the Vienna IETF

At the Vienna IETF, the "problem" working group is scheduled to make a consensus call on the process for *changing* the IETF process. While the shape of the result is still unknowable, I believe it's likely that among the outputs of such a process will be a greatly changed IESG charter.

But until then, I believe there is value in publishing this document.

What does the community think?

                Harald Alvestrand






<Prev in Thread] Current Thread [Next in Thread>