Attendance/email registration matters from a number of logistical view
points (conference setup. server resources, potential revenue stream,.....).
From an actual work process point of view, it would seem the number of
active work groups and the number of drafts and RFC proposals created
impact WG and IESG workload the most. If you take the number of drafts /
RFC proposals and then some how factor in the breadth and depth of the
problem spaces they are addessing, then you have another view of the
scaling problem. One particular aspect that interests me is even
assuming the WG has the expertise to work a problem domain, what are the
challenges to IESG members to keep pace with wideining and deepening
problem domans - it would seem that at some point their feedback would
become administrative; but perhaps they are all extremely talented
people with the requisite spare time to keep up / or administrative
feedback is all that is required?
Sometimes friction is caused by truly deeply divergent view points /
experiences. Sometimes it is caused simply by a lack of bandwidth
combined with a very low latency expectation / high quality expectation;
and of course conversely sometimes the best is the enemy of the good.
FYI, anyone read all the drafts exploding our way in prep for the next
meeting? (rhetorical of course) And if not, are there challenges to IETF
members maintaining an end-to-end view point, or is it sufficient for
people to simply specialize in a certain area without an
evolving/debated architectural/mission framework in which to work?