From: "Adrian Farrel" <adrian(_at_)olddog(_dot_)co(_dot_)uk>
This is a handy thread and brings into question what the 'S' in IESG
is supposed to mean.
As far as I can see, the IETF primarily develops protocols. Work
which does not revolve around developing protocols does not happen in
the IETF. Perpass is an example of this, because although it
*considers* pervasive monitoring, its *purpose* is the development of
protocols that are resistant to monitoring and creating an attitude
that monitoring must be considered in the development of other
protocols. Perpass *exists* because a critical mass of people want to
work on such protocols.
In regard to the IESG, it "steers" by deciding whether or not to
charter working groups. But its biggest job is reviewing standards
developed by the working groups. It certainly does not "allocate
resources", that is, decide that some topic needs to be worked on and
recruit people to do the work.
Dale