Technical Coordinators

[Black_David@emc.com]

Julian asked a couple of questions about technical
coordinators; I'm cc:ing the list because the answers
are of general interest.

> How is Technical Coordinator mechanism going to work?

The coordinators have direct responsibility for making sure that the work
required by their specific protocol gets done.  This offloads the chairs
in a manner in which each technical coordinator can focus primarily on
the protocol for which s/he is responsible (as opposed to the chairs who
have responsibilities spanning the protocols and things like the charter
and framework document).  Here are two examples of how TCs help:

- In the short term, WG meetings can go into split parallel sessions
	for protocol-specific issues.  TCs would be responsible for
	organizing (e.g., Agenda) and running the split sessions,
	avoiding a requirement for the chairs to be in multiple places
	at the same time :-).
- In the intermediate term, we are likely to be dealing with multiple
	documents per protocol.  Having the TCs responsible for
	tracking/encouraging/etc. the set of documents for each
	protocol distributes the workload (useful if there are a lot
	of documents involved).

In practice, RFC 2418 on how IETF WGs operate applies to the
per-protocol subgroups that result from this structure.  The TCs
would serve at the pleasure of the WG chairs in the same fashion
that the WG chairs serve at the pleasure of the Area Directors.

> Who are the current candidates?

Send nominations/recommendations to Steve (smb@research.att.com)
and myself (black_david@emc.com) directly - please do not use the
list for this purpose.

--David

---------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 42 South St., Hopkinton, MA  01748
+1 (508) 435-1000 x75140     FAX: +1 (508) 497-8500
black_david@emc.com       Mobile: +1 (978) 394-7754
---------------------------------------------------